IT Support SLA Response Times Explained

If your IT provider promises a "15 minute response" you could be forgiven for thinking your problem will be fixed in 15 minutes. It usually will not. This guide gives you IT support SLA response times explained in plain English, so you know what the numbers mean, what is reasonable and what to check before you sign.

What an IT support SLA actually is

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.

Response time versus 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 good IT support SLA response times look like

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.

IT support SLA response times explained: who sets the priority?

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.

24/7 monitoring is not the same as 24/7 support

Monitoring means software watches your systems and raises an alert. Support means a qualified person responds to that alert. Plenty of providers advertise round-the-clock cover when only the monitoring runs overnight.

Ask three direct questions. Who answers the phone at 2am on a Sunday? How quickly will they respond? Is out-of-hours work included in the price or charged on top? The answers tell you far more than the headline claim.

Business hours or round the clock: what do you need?

Match the cover to how your business really works. An office that runs 9 to 5 on weekdays may be well served by business-hours cover with an emergency line for critical issues. A business that trades in the evening, at weekends, or across time zones needs the fast response times to apply when you are actually working.

Cost rises with cover, so it pays to be honest about what an hour of downtime costs you. Our breakdown of IT support packages for small businesses shows how cover levels affect price.

What happens when the SLA is missed

An SLA without consequences is a brochure. Look for clear remedies: regular reporting on how the provider performed, escalation to a named senior person after repeated misses, and service credits or the right to end the contract if poor performance continues.

Ask for performance reported by priority. A high overall percentage can hide the fact that the critical tickets, the ones that matter most, were the ones that were missed. Also check whether the clock pauses while a ticket is "waiting on client", and whether you can see that in the ticket portal.

Questions to ask before you sign

Use this checklist when you compare providers, and keep IT support SLA response times explained clearly in each answer. It takes ten minutes and tells you whether the SLA is real.

• Are there separate response and resolution targets for each priority?
• Who sets the priority, and what are the written definitions?
• Is a response a named person, or an automatic acknowledgement?
• What hours do the targets apply, and what is the out-of-hours arrangement?
• What are the consequences of a miss, and are they in the contract?
• Will you get monthly reports split by priority?

If you already have an in-house IT person, the SLA only needs to cover the gaps. That is how co-managed IT services work, and the SLA can be set to match the cover you are missing.

Frequently asked questions

What is a good response time in an IT support SLA?

For a business-stopping problem, such as the whole office being offline or a suspected cyber attack, a good response is 15 to 30 minutes. For a single person with a workaround, a few business hours is normal. What matters is that each priority has its own written target, not one figure for everything.

What is the difference between response time and resolution time?

Response time is how long it takes a real person to acknowledge your problem and start work. Resolution time is how long it takes to fix it. A provider can hit every response target and still leave you waiting, so always ask for both numbers in writing.

Does 24/7 IT support mean someone is always at a desk?

Not necessarily. Many providers monitor systems around the clock but only have engineers on call or on shift at set times. Ask who answers the phone at 2am on a Sunday, how fast they respond, and whether out-of-hours work costs extra.

What happens if my IT provider misses the SLA?

That depends on the contract. A good agreement says what you get: monthly reporting, escalation to a named senior person after repeated misses, and service credits or a right to leave for sustained poor performance. If the contract is silent, the SLA is a promise with no consequence.

Who decides how urgent my problem is?

It should be set by clear rules written into the SLA, for example whole site down equals critical. If the provider grades every ticket on its own judgement, urgent issues have a habit of being treated as routine. Agree the definitions before you sign.

How Cloud Plus can help

At Cloud Plus we put response and resolution targets in writing for every priority, and we are happy to walk you through them before you commit. No jargon, no small print, and no surprises when something breaks. If you want to see how your current SLA compares, we will read it with you. Our guide to IT support for small business in the UK explains what a full service covers.

Get a quote from Cloud Plus and find out what a clear, measurable IT support agreement looks like for your business.