IT Support SLA Response Times Explained
An IT support SLA sets how fast your provider must respond to a problem and how fast it must be fixed, graded by urgency. A good one has separate response and resolution targets for each priority, such as 15 to 30 minutes for a business-stopping fault. Cloud Plus managed IT support UK explains what the numbers mean here.
What is an IT support SLA?
An SLA, or service level agreement, is the part of your IT support contract that says how fast your provider will react when something goes wrong. It sets targets for each type of problem and says what happens if those targets are missed. It is a promise you can measure.
A good SLA covers four things: how problems are graded by urgency, how quickly someone responds, how quickly the problem is fixed, and when the service is available. If any of those four is missing, you are relying on goodwill rather than a contract.
If you are still comparing providers, our guide on how to choose an IT support provider shows where the SLA fits in the wider decision.
What is the difference between response time and resolution time?
Response time is how long it takes a real person to acknowledge your request and start working on it. Resolution time is how long it takes to put the problem right. They are two separate clocks, and both should appear in your contract.
This is where many businesses get caught out. A provider can meet a response target by sending an automatic email. The ticket is "responded to", the SLA is met, and your team is still locked out of their accounts.
- Response time: the clock stops at the first meaningful reply from a person.
- Resolution time: the clock stops when the problem is fixed and you agree it is fixed.
- Ask for both: a provider who will only commit to response times is not measuring how long you wait for a fix.
What are good IT support SLA response times?
There is no single legal standard, so targets vary between providers. As a guide, a sensible SLA has four priority levels, with the fastest response reserved for problems that stop the whole business. The figures below are typical examples, not guarantees from any one provider.
- Priority 1, critical: whole business or site down, or a security incident in progress. Response in 15 to 30 minutes, at any hour. Fix target of around 4 hours, worked on continuously.
- Priority 2, high: a department or key system affected, or one person completely unable to work. Response within about an hour. Fix target of around 8 business hours.
- Priority 3, standard: one person affected with a workaround available. Response within about 4 business hours. Fix within a couple of business days.
- Priority 4, requests: new starters, changes and questions. Response within a business day, with the work scheduled and agreed.
If a provider quotes the same response time for everything, either the fast figure is meaningless or the slow figure will hurt you when it matters most.
Who decides how urgent a ticket is?
The SLA should say, in plain words, which problems count as critical, high, standard or a request. If the provider grades every ticket by its own judgement, urgent issues tend to drift down to "standard", where the response is slower.
Agree the definitions before you sign, because IT support SLA response times explained on paper only help if the grading is fair. "Whole office cannot work" should always be critical. You should also be able to ask for a ticket to be raised in priority and get a straight answer.
