Every managed IT proposal includes an SLA, and most business owners skim past it without really understanding what it commits the provider to, or how to tell a genuine commitment from marketing language. Here's how to read one properly.
What SLA Actually Means
A Service Level Agreement is a defined, measurable commitment - typically around response time, sometimes resolution time, and occasionally uptime for hosted systems. The key word is measurable. If a proposal says "fast response times" with no number attached, it isn't an SLA, it's a claim.
Response Time vs Resolution Time
These are frequently confused, and providers sometimes lean into that confusion:
- Response time - how long until someone acknowledges the ticket and starts working on it
- Resolution time - how long until the issue is actually fixed
A 15-minute response time on a critical issue is meaningless if resolution regularly takes two days with no update in between. A properly written SLA addresses both, or at minimum is explicit that only response time is being committed to.
Typical Response Time Benchmarks
Realistic, well-staffed managed IT response times in the Perth market generally look like this:
- Critical (total outage, active security incident): 15-30 minutes, often with a defined emergency phone line, not just a ticket queue
- High (major function down for one user or team): 1-2 hours
- Medium (a single application issue, non-blocking): 4-8 business hours
- Low (a general request, no urgency): 1-2 business days
Anything significantly faster than this across the board, without a large support team to back it up, is worth questioning rather than assuming it's simply better service.
What a Proper SLA Should Also Cover
- How priority level is determined, and by whom - self-selected by the client, or triaged by the helpdesk
- What consequence follows a missed SLA - a service credit, a fee reduction, or nothing at all
- Whether the SLA applies 24/7 or only during business hours, with a separate after-hours tier
- How SLA performance is reported and tracked, not just promised
Why SLAs Get Missed
The most common cause isn't a bad provider, it's an understaffed one. A provider that's grown its client base faster than its technician headcount will start missing response times even with good intentions and a well-written SLA on paper. Ask directly about technician-to-client ratios and average ticket volume per technician if fast response is a priority for your business.
Reading Between the Lines of a Proposal
When comparing quotes, check whether the SLA is a specific, numbered commitment in the actual contract, or a general statement in marketing material that never makes it into the signed agreement. Only the former is enforceable. See our guide on comparing IT provider quotes properly for other clauses worth scrutinising alongside the SLA.
Frequently Asked Questions
Does a fast response time mean the issue gets fixed quickly too?
Not necessarily, and this is the most common misunderstanding of SLAs. Response time is how quickly someone acknowledges and starts working the ticket, not how quickly it's resolved. A complex issue might have a 15-minute response but take hours to fully resolve - the SLA should ideally cover both, but many only commit to response.
What counts as a 'critical' priority ticket versus a lower one?
Typically, critical means a total outage affecting the whole business or a security incident in progress - the network is down, or ransomware has hit. High priority is a significant issue affecting one person or system but not the whole business. Everything else, like a single application acting up, is usually medium or low.
Are 24/7 SLAs standard, or only for critical issues?
Most standard managed IT agreements cover business hours only, with critical/emergency response available outside those hours as a separate tier, sometimes at additional cost. True 24/7 coverage across all priority levels is less common outside larger enterprise contracts, and worth clarifying if your business genuinely operates around the clock.
What should happen if my provider consistently misses their SLA?
A well-written agreement includes service credits or fee reductions for missed SLAs, and repeated breaches are grounds to invoke exit clauses without penalty. If missed SLAs keep happening with no consequence and no improvement plan offered, that's a strong signal worth acting on.
Our SLAs are numbered commitments in the contract, not marketing copy - and we report against them, not just promise them.
Managed IT Services →Not sure if your current SLA is realistic?
Call 0433 087 091 - we'll benchmark your current provider's response times against what's typical for your business size, no obligation.
Get a Free SLA ReviewFor related reading, see our guides to what to expect from an IT helpdesk and what to include in a managed IT services agreement.