An SLA (service level agreement) is the part of an IT contract that says how fast the provider shows up when something breaks. It's also where marketing does its best work, because "15-minute response" sounds like a promise about your problem getting fixed and usually isn't. Here's how to read one.
Response is not resolution
The distinction that matters most. Response time is how fast a human acknowledges your ticket. Resolution time is how fast your problem is fixed. An SLA can promise 15-minute response and deliver it by having someone email "we're looking into it" while nothing happens for two days. Most SLAs only bind response, because resolution is genuinely hard to promise. That's fair. What you want is a provider who reports both numbers, so you can see what "we responded" actually led to.
Priority levels, translated
SLAs sort tickets into priorities, usually P1 through P4. In plain words:
- P1, everything is on fire. Server down, network down, nobody can work. Typical promise: response in 15 to 60 minutes, work continues until it's fixed.
- P2, a group is blocked. A department's app is down, a shared drive is gone. Response in 1 to 4 hours.
- P3, one person is stuck. A laptop won't start, email won't sync. Response in 4 to 8 business hours.
- P4, annoying but livable. Slow machine, new monitor request. A day or two.
Read who assigns the priority. If the provider classifies unilaterally, your outage can become their P3. Good contracts define priorities by business impact in plain language and give you an escalation path when you disagree.
Questions that separate a real SLA from a page of marketing
- What are the hours? "24/7 monitoring" often means software watches all night, not people. Ask what happens when the alert fires at 3 a.m. and who exactly wakes up.
- Is there a remedy? An SLA without consequences is a mood board. Service credits for missed targets are standard; ask how often they've been paid out.
- What's the time-to-human? Response clocks can be satisfied by autoresponders. Ask how long until a person who can actually fix things is engaged. This is the metric that predicts how support will feel.
- Do you get reports? Monthly ticket and response stats should arrive without asking. Providers who measure themselves in front of you tend to be the ones hitting their numbers.
What we think SLAs are actually for
Honestly: the SLA is a floor, not the relationship. A shop that needs the contract to make them answer the phone will find the letter of it. A good shop beats its SLA all year and the document just sits there. Use the SLA to filter out the first kind, then judge the second kind by their first 90 days. The paper tells you the minimum. The onboarding tells you the truth.
Want this handled instead of homeworked? That's the job.
Email us →