IT Support SLA Explained: Response Times, Uptime & What to Expect

When you sign up with an IT support provider, the SLA is the document that determines whether you're getting genuine accountability or just vague promises. It's also the document most businesses never actually read — until something goes wrong and they discover their 'guaranteed' response time doesn't mean what they thought it did.

This guide breaks down what an IT support SLA should contain, what the key metrics actually mean, and how to negotiate terms that genuinely protect your business.

What Is an IT Support SLA?

SLA stands for Service Level Agreement. It's a formal contract between your business and your IT support provider that defines exactly what service you'll receive, how quickly they'll respond when things go wrong, and what happens if they fall short.

A good SLA removes ambiguity. Instead of 'we'll get back to you as soon as possible,' it says 'critical issues receive a response within 15 minutes and resolution within 4 hours during business hours.'

Key SLA Metrics Explained

Response Time vs Resolution Time

This is where most confusion lies, and where some providers exploit the gap:

• Response time: How quickly someone acknowledges your ticket and begins working on it. A 15-minute response time means a technician is assigned and has started investigating within 15 minutes
• Resolution time: How long until the issue is fully fixed. This is the metric that actually matters to your business, but it's harder to guarantee because complex issues take longer

Watch out for providers who guarantee fast response times but make no commitment on resolution. A 15-minute response means nothing if the actual fix takes three days.

Priority Levels

SLAs typically define three or four priority levels, each with different response and resolution targets:

• Priority 1 (Critical): Complete business outage — email down for everyone, server failure, ransomware attack. Target: 15-minute response, 4-hour resolution
• Priority 2 (High): Major impact affecting multiple users — shared drive inaccessible, key application not working. Target: 30-minute response, 8-hour resolution
• Priority 3 (Medium): Single user unable to work — laptop won't boot, email not syncing. Target: 1-hour response, next-business-day resolution
• Priority 4 (Low): Minor inconvenience — slow printing, non-urgent request. Target: 4-hour response, 3-day resolution

The exact numbers vary by provider. What matters is that they're clearly defined and that you agree on what constitutes each priority level. For deeper guidance, see our complete IT SLA guide.

Uptime Guarantees

If your IT provider manages your servers or cloud infrastructure, the SLA should include an uptime guarantee:

• 99.9% uptime ('three nines'): Allows 8.76 hours of downtime per year — standard for most business services
• 99.99% uptime ('four nines'): Allows only 52.6 minutes of downtime per year — premium tier
• 99.95% uptime: Allows 4.38 hours per year — Microsoft's guarantee for most Azure and Microsoft 365 services

Uptime guarantees should specify planned vs unplanned downtime. Scheduled maintenance windows (usually overnight or weekends) are typically excluded from uptime calculations.

What a Good IT Support SLA Should Include

Beyond response times and uptime, a comprehensive SLA covers:

• Scope of service: Exactly what's covered and what isn't — which devices, which applications, which users
• Support hours: Standard business hours (typically 8am-6pm Mon-Fri) vs extended hours vs 24/7. Out-of-hours support usually costs extra
• Escalation procedures: What happens if a ticket isn't resolved within the target time? Who gets notified? What's the escalation path?
• Reporting: Monthly or quarterly reports showing ticket volumes, response times, resolution times, and SLA compliance rates
• Service credits: What compensation you receive if the provider misses SLA targets — typically a percentage credit on your monthly fee
• Exclusions: Third-party outages (internet provider, Microsoft), force majeure, and issues caused by unauthorised changes should be clearly listed
• Review schedule: When and how the SLA is reviewed — annually at minimum, with the ability to adjust terms as your business changes

SLA Red Flags to Watch For

Some providers use SLA language that looks good on paper but means very little in practice:

• 'Best endeavours' response times: If the SLA says 'we aim to respond within 30 minutes' rather than 'we will respond within 30 minutes,' there's no actual commitment
• No resolution targets: Response-time-only SLAs let providers acknowledge your ticket quickly, then leave it in a queue for days
• Vague priority definitions: If it's left to the provider to decide what's 'critical' vs 'high priority,' they'll downgrade tickets to avoid breaching SLA targets
• No service credits: An SLA without penalties for non-compliance is just a marketing document
• Excessive exclusions: If the exclusion list is longer than the commitment list, the SLA isn't worth the paper it's written on

How to Negotiate a Better SLA

SLAs aren't take-it-or-leave-it documents. Here's how to negotiate terms that work for your business:

• Define your critical systems: Identify which applications and services absolutely cannot go down, and negotiate tighter SLAs specifically for those
• Insist on resolution targets: Response times alone are meaningless — push for written resolution commitments
• Request monthly reporting: Data transparency keeps your provider accountable. If they resist reporting, that's a red flag
• Include escalation to a named contact: For critical issues, you should be able to escalate to a senior engineer or account manager, not just a queue
• Negotiate review clauses: Build in a 90-day review after onboarding, with the right to adjust terms based on real-world performance

A managed IT support provider should be willing to discuss and tailor SLA terms to your specific needs. Providers who refuse any negotiation are often hiding behind weak service delivery.

What Happens When SLAs Are Breached?

If your provider consistently misses SLA targets, you have several options:

• Claim service credits: Most SLAs entitle you to a percentage refund for each breach — typically 5-10% of your monthly fee per incident
• Request a formal review: Ask for a root cause analysis and a plan to prevent recurrence
• Escalate internally: Speak to the provider's management, not just the account team
• Exercise termination clauses: Persistent SLA breaches usually give you the right to exit the contract early without penalty

Track every breach. Providers are more responsive when you can present documented evidence of consistent underperformance.