Think of this as a glossary you can keep open next to the contract. For a full walkthrough of how SLAs work, see The Complete Guide to MSP SLAs for SMBs.
How quickly the provider acknowledges your request and starts working on it. A fast response doesn't mean a fast fix. Ask whether "response" means a real technician or an automated email.
How long it takes to actually fix the problem. Many SLAs give resolution targets rather than guarantees, because some issues depend on outside vendors.
Categories (often P1 to P4) that determine how fast an issue is handled. A typical setup:
| Priority | Typical meaning | Example |
|---|---|---|
| P1 / Critical | Business stopped or security incident | Whole office offline, ransomware |
| P2 / High | Major impact on many users | Email down for a department |
| P3 / Medium | One user can't work normally | Laptop won't connect to VPN |
| P4 / Low | Request or minor issue | New software install |
Check who decides the priority, and whether you can escalate if you disagree.
The hours when SLA clocks run. If the SLA is "4-hour response during business hours" and you call at 4:45 p.m. Friday, the clock may not finish until Monday.
Whether help is available outside business hours, what it covers (often only critical issues), and whether it costs extra.
A percentage promise for how often a service will be available, such as 99.9%. Common for hosted services, less common for overall IT support. Check how it's measured and what's excluded.
Who your issue goes to if it isn't fixed in time, and how you reach a manager. A good SLA names roles, not just "we'll escalate."
What you get if the provider misses its targets, such as a credit on your bill. If there's no remedy, the SLA is a goal, not a commitment.
What's not covered: often third-party software, personal devices, projects, or issues caused by changes you made. Read this section carefully.
The list of what's included in your monthly fee. If something isn't on the list, assume it may cost extra.
Scheduled times when the provider can apply updates or make changes that might cause brief interruptions. Make sure they fit your business hours.
How the provider shows SLA performance, such as monthly reports on response times, ticket volumes, and missed targets. If they don't report it, you can't verify it.
More warning signs are in Managed IT Provider Red Flags for SMBs.
An SLA is only useful if you understand it before something breaks. Spend twenty minutes with these terms and the contract, and you'll know exactly what to expect when it matters.
Many providers target a response within an hour or less for critical issues during covered hours. What matters most is that it's written down and reported on.
Often, especially coverage hours, priority definitions, and reporting. It's worth asking.
They should. Check whether security incidents are treated as top priority and what incident response is included versus billed separately.
Ask each provider for their SLA document and compare these twelve terms side by side. Our guide on how to audit an MSP before you sign can help.
Cloud Cover puts response times, priorities, and coverage in writing, and reports on them. We're happy to walk through our SLA line by line.
Schedule a call with Cloud Cover, or tell us a little about your business below and we'll follow up.