Response time is not resolution time
The most common misunderstanding about SLAs is the difference between responding and resolving. A response target says how soon a technician will acknowledge your request and start working on it. A resolution target, where one exists, says how soon the problem should be fixed. Many SLAs only commit to response, because some problems depend on things outside the provider's control, such as a hardware part arriving or Microsoft fixing an outage.
That is reasonable, but it means a one-hour response promise does not mean your issue will be gone in an hour. Ask any provider to explain both. If they offer resolution targets, ask how often they meet them and how they report it. If they do not, ask what they do to keep a long-running issue moving and how you will be updated while it remains open.
How priority levels work
SLAs usually sort requests into priority levels, often three or four. The top level covers outages affecting the whole business, such as email down for everyone or the server offline. The next covers a problem stopping one person or a small group from working. Lower levels cover inconveniences and routine requests like a new shared mailbox or a software install that can wait a day.
The definitions decide which target applies, so read them carefully. If the SLA says critical issues are only those affecting all staff, then the business owner's laptop dying before a client meeting might count as normal priority. A good provider will use judgement, but it helps to agree in writing how urgent requests should be flagged, who can escalate, and how disputes about priority are settled.
Business hours and the small print
Most SLA clocks run only during business hours. A response target of four business hours for a request logged at 4.30pm on Friday may not be reached until Monday morning. That is normal, but it surprises people who read the number without the hours that sit behind it. Check what the provider counts as business hours, and whether public holidays and regional anniversary days pause the clock.
After-hours cover is often separate. It may be included for critical issues, charged at a higher rate, or not offered at all. If your business runs evenings, weekends or shifts, make sure the SLA reflects when you actually work, not just standard office hours. Ask how an urgent problem is reported after hours and who receives it.
What happens when targets are missed
Some SLAs include service credits, where the provider reduces your bill if targets are missed beyond a threshold. Others simply commit to reporting performance and discussing it in reviews. Credits sound attractive, but they are usually small compared with the cost of downtime. Their main value is that they make the provider measure and take note of missed targets.
More useful than credits is a clear process for repeated failure. If targets are missed month after month, you should be able to escalate to senior staff and, ultimately, leave the contract without penalty. Ask whether the agreement includes a performance-based exit clause, and what counts as a pattern of failure rather than an unlucky week.
What an SLA cannot do
An SLA describes the provider's commitment, not your systems' resilience. No agreement can stop a fibre cable being dug up down the road or a laptop being left on a bus. Those risks are managed through design: backup internet connections, cloud backups, spare hardware and tested recovery plans. An SLA only tells you how fast someone will begin helping when things go wrong.
Be wary of SLA figures that look too good. A provider promising a fifteen-minute response for everything during every hour of the year either has a very large team or will struggle to meet the promise. Realistic targets that are consistently met are worth more than impressive ones that are quietly missed.
Checking the SLA is being met
Ask for monthly reporting showing how many requests were logged at each priority, average response times and any targets missed. Most ticketing systems record this automatically, so the information should be easy for the provider to share. Review it at least quarterly and raise any patterns early, such as one type of request that always takes longer or a run of missed targets in a busy month.
Also listen to your staff. Numbers can look fine while people feel unsupported, for example if requests are acknowledged quickly but then sit untouched for days. A short informal check with a few staff each quarter tells you whether the service feels responsive in practice, not just on paper. Combine that impression with the reports and you get a fair picture of whether the agreement is working for your business.
In short
- Most SLAs promise a response time, not a fix time.
- Priority definitions decide which target applies, so read them closely.
- SLA clocks usually run in business hours only; check after-hours cover separately.
- Ask for monthly performance reports and a clear route for repeated failures.