What does a Remote Hands response time actually measure?
A response-time figure can start and stop at different moments. A provider that says it responds in thirty minutes may mean it acknowledged your ticket, while another that says four hours means a technician is standing at your rack. Compare commitments only after you know which clock is running.
Scroll the table sideways for more.
| Measure | What it means | Question to ask |
|---|---|---|
| Acknowledgement | Someone has seen the request and replied | Is this a person or an automatic reply? |
| Dispatch | A technician has been assigned and is on the way | Who confirms it, and how? |
| Arrival | The technician is on site and starting work | Does the clock include travel, parking and site check-in? |
| Resolution | The physical action is complete and verified | What is excluded, such as parts or access delays? |
What is the difference between a target and a guarantee?
A target is what the provider works toward. A guarantee has a defined remedy if it is missed, such as a credit or a right to cancel. Both can be useful, but they are not the same thing, and a provider that calls a target a guarantee should be able to show you the remedy in writing.
What can stop a response time from being met?
Most missed times are caused by things outside the technician's control, so the fine print matters.
- Site access: escorts, permits, badge approval or loading-dock restrictions
- Hours: a target that applies only in business hours does not cover a night-time outage
- Parts: replacement hardware that is not on site
- Incomplete requests: missing rack location, contact or authorization
- Traffic and travel time in dense metro areas
What should you ask before relying on a response commitment?
- Which of the four measures does the figure describe?
- Is it a target or a guarantee, and what is the remedy if it is missed?
- Which hours does it cover, and how are holidays handled?
- What do you need to send for the clock to start?
- How will you be told that a technician is assigned and on the way?
- What happens when site access delays the visit?
How should you plan around response times?
Treat any response time as one input to your own plan. Pre-approve site access and authorizers, keep rack locations and port maps current, and keep your own escalation channel for critical outages so you are never waiting on a single path.
How do response times differ by level?
Providers often set different targets for different severities. A critical outage normally gets a faster commitment than a planned install, and each level may cover different hours. Read each level separately instead of assuming one figure applies to everything.
- Which severity levels exist and how each is defined
- Which hours each level covers, including nights, weekends and holidays
- Whether the target is acknowledgement, dispatch or arrival
- What the provider needs from you before the clock starts
- How you are told that someone is on the way
What does a fair service-level agreement include?
- Defined measures, so both sides count the same thing
- Stated hours of coverage and holiday handling
- Exclusions that are reasonable and written down
- A remedy if the target is missed, such as a credit
- Regular reporting against the targets
- A review date to adjust targets to what actually happens
