'We guarantee a 4-hour SLA'
'We guarantee a 4-hour SLA.' It's one of the most common lines in any maintenance contract — and one of the most misunderstood. Ask ten IT managers what that sentence means, and you'll likely get ten different answers. Some assume it means a technician will be on-site within four hours. Others assume the problem will be fixed within that window. In most cases, neither is exactly right.
Understanding the difference between response time and resolution time isn't just semantics — it's the difference between what a contract promises and what actually keeps your infrastructure running.
What Response Time Actually Means
Response time is how long it takes for your maintenance provider to acknowledge a ticket and begin actively working on it. That might mean:
A technician calling to gather details about the issue
Remote diagnostics starting on the affected system
A support engineer confirming receipt and beginning triage
What it does not necessarily mean is that a person is physically standing in front of your failed hardware. Response time is about how quickly someone begins to work with you — not how quickly the problem goes away.
What Resolution Time Actually Means
Resolution time — sometimes called "time to repair" or "time to restore" — is the metric that actually matters when something is down: how long until the issue is fully fixed and the system is back in service.
Resolution time depends on a lot more than provider speed. It's affected by:
Whether a replacement part is needed, and whether it's in stock
Whether the fix can be done remotely or requires an on-site visit
The complexity of the failure and whether escalation is needed
Travel time to your location, if on-site work is required
This is why a provider can hit their response SLA every single time and still leave you with hours or days of downtime.
Why the Gap Catches Buyers Off Guard
Most maintenance contracts are written — and marketed — around response time because it's the easier number to guarantee. It doesn't depend on parts logistics or technician availability at your specific location, so providers can commit to it confidently.
Resolution time is harder to promise, because it depends on variables outside the provider's full control. That's exactly why it's the number you should be asking about before you sign anything. A provider that can only speak to response time, and gets vague when you ask about resolution time, is telling you something important.
Questions to Ask Before You Sign
When you're evaluating an SLA, push past the headline number:
Is on-site dispatch included in the response window, or does it start after?
What's your first-time-fix rate — how often is an issue resolved on the first visit or first remote session?
Do you have parts on hand locally, or are they sourced per ticket?
How do response and resolution times change outside business hours?
Ask for real performance data, not just contract language. A provider confident in their delivery should have resolution-time metrics ready to share.
Why This Matters More for Aging and EOSL Hardware
The gap between response and resolution time tends to widen as hardware ages. End-of-Life (EOL) and End-of-Service-Life (EOSL) equipment often requires parts that OEMs no longer stock, which can stretch resolution time significantly — even if a technician responds right on schedule. This is one of the areas where a dedicated Third-Party Maintenance provider, with proactive parts sourcing and testing, can meaningfully outperform OEM support on the metric that actually matters: how long your systems are actually down.
The Bottom Line
A fast response means someone showed up. A fast resolution means the problem is gone. Both matter, but only one of them determines how much downtime your business actually absorbs. When you're comparing maintenance providers, don't stop at the SLA headline — ask what happens after the clock starts.
Comments