Your IT support SLA is the document that decides how quickly problems get fixed, what your provider is accountable for, and what you’re owed when things go wrong. Most SMEs sign one during onboarding and never look at it again – until something breaks.
At Microbyte, we’ve been providing managed IT services to businesses since 1992. Over 30 years, one question has come up more than any other: Is our IT support SLA actually protecting us? This guide gives you the tools to find out, including two specific numbers you can ask your provider for today.
What is an IT Support SLA?
A Service Level Agreement (SLA) is a legally binding contract between you and your IT provider that defines exactly what service you’ll receive, how quickly problems will be fixed, and what happens if those standards aren’t met.
ITIL (IT Infrastructure Library), the recognised industry-standard framework for IT service management, defines an SLA as a documented agreement that identifies both the required services and the expected level of service. It’s what turns “we’ll sort it” into something you can hold a provider to commercially. Without one, you’re relying on goodwill – and goodwill has no resolution time target.
What Every Complete SLA Covers
An SLA should make clear commitments across all of the following:
- Response and resolution timeframes by incident priority
- Uptime and availability guarantees
- Support hours, including cover for bank holidays
- Escalation procedures when an issue isn’t resolved at first contact
- Reporting cadence and the format of performance data you’ll receive
What Separates an SLA From a Vague Support Contract?
A genuine SLA does three things: it defines the service scope, commits to measurable performance targets, and specifies what you’re owed if those targets are missed. Any contract that is vague in one of those three areas is incomplete. The gap becomes clear when something goes wrong, and you have no written recourse.
What Makes an SLA Commercially Enforceable
ITSM (IT Service Management) frameworks place SLAs at the centre of client-provider accountability. They’re the mechanism that stops “we’ll look into it” from becoming a pattern of delay with no commercial consequence attached. Without that contractual structure, a provider can miss targets repeatedly with no financial exposure.
Types of IT Support SLA
Not every IT support contract is structured the same way. Knowing which type you have matters when you sit down to review it.
- Service-Based SLAs: A standardised contract offering identical service parameters to all clients. A universal 99.9% uptime guarantee applied to every customer on the same plan is a typical example.
- Customer-Based SLAs: A custom agreement covering all the services a specific business uses under one contract. If you have unusual operating hours, specialist software, or compliance requirements, this is the type to negotiate for.
- Multi-Level SLAs: A tiered agreement separating corporate, customer, and service-level commitments into distinct layers. These tend to appear in larger organisations where different teams have different IT needs.
Which Type Is Right for Your Business
For most UK SMEs running between 10 and 250 users, a Customer-Based SLA offers the strongest protection. A one-size-fits-all contract wasn’t designed around your specific business hours, systems, or risk profile.
If you’re uncertain which type you currently have, reviewing your contract alongside IT consultancy services can surface the gaps before they become incidents.
What Should Your IT SLA Include?
A complete IT support SLA covers eight areas. If yours is missing any of them, you have a gap worth addressing before you renew.
The Eight Components Every SLA Must Cover
Exclusion Clauses: What They Actually Mean
Three types of exclusions appear in almost every IT support SLA, and most clients don’t read them until something goes wrong. Reading them in advance tells you exactly where your provider’s liability ends, which matters most when you actually need to make a claim.
The Three Standard Exclusions
- Third-party outages: If Microsoft Azure or your internet service provider (ISP) experiences an outage, your IT provider isn’t liable. Example: Microsoft 365 is unavailable for three hours due to a Microsoft data centre failure. Your provider’s SLA clock doesn’t start because the fault isn’t theirs.
- Client-owned hardware failure: If a server you own fails and your provider hasn’t been managing its maintenance, standard resolution times may not apply. Example: an ageing server you declined to replace finally fails. The SLA window doesn’t begin until your provider has physical access to it.
- Force majeure: Floods, fire, and extended power cuts. Your provider will work to restore services, but they’re not liable for the outage itself.
Knowing these clauses before you sign means no disputes and no surprises when something actually goes wrong.
Response Times and Resolution Targets
When your systems go down, two numbers determine the damage: how long before someone responds, and how long before it’s fixed. Your SLA should commit to both, split by incident priority.
Standard Industry Benchmarks
Mean Time To Resolve (MTTR) is the average time from ticket logged to full resolution. A provider can acknowledge a critical incident in five minutes and still take three days to fix it. MTTR is the metric that actually tells you how long your business was affected.
High availability targets should appear clearly alongside those figures. The baseline for mission-critical SaaS tools and managed networks is 99.9% uptime – “three nines” – which allows approximately 8.76 hours of downtime per year. For customer-facing applications, 99.99% availability (“four nines”) reduces that to under 53 minutes annually.
An SLA that doesn’t separate targets by priority level isn’t giving you a meaningful commitment.
The Watermelon Effect: When Green Metrics Hide Red Reality
The Watermelon Effect occurs when your provider’s performance metrics appear green – compliant, on target, every box ticked – while your team’s actual experience is red. The report says everything’s fine. Your people know differently.
Here’s a concrete example. Your provider commits to 99.9% uptime. Across the year, they hit it.
But that 0.1% downtime – roughly eight hours – falls on three consecutive Monday mornings at 9 am, right when your team is logging in, and your phones are ringing. The SLA report says compliant. Your business lost three Monday mornings of trading.
Why Surface-Level Metrics Mislead
The same pattern shows up in ticket metrics. A provider that closes tickets quickly to avoid breaching response targets can do so without resolving the root cause. The metric stays green.
The problem returns the following week. Each time, it costs your team the same amount of time.
Two Questions to Bring to Your Next Review Meeting
These questions cut through surface-level compliance figures:
- “What is your SLA compliance rate during our core business hours, specifically – not across the full 24-hour reporting period?”
- “Can you show us a real-time experience report, rather than just uptime log exports?”
If they can’t answer the first, they’re measuring performance on their schedule, not yours. If the second draws a blank, you have no independent view of what your team’s day-to-day experience actually looks like.
How to Spot a Weak SLA: Two Diagnostic Numbers
Most IT contracts look reasonable on paper. These two metrics reveal what a provider is delivering in practice – and you can request both of them today.
First Contact Resolution Rate
First Contact Resolution (FCR) is the percentage of support issues resolved the first time they’re raised, without the client needing to follow up or log the same problem again. Most providers track this internally. Ask them to share it.
The threshold to know: an FCR below 65% signals real inefficiencies and knowledge gaps within the support team. Strong providers target an FCR above 80%. Best-in-class managed IT providers often exceed that consistently across their client base.
Reactive Ticket Ratio
Ask your provider: in the last three months, what percentage of support tickets were reactive? In other words, how many were raised because a problem had already occurred, rather than being caught by monitoring before it affected anyone?
If more than 90% of tickets are reactive, you’re not receiving managed IT. You’re receiving a break-fix repair service. Our “Stamp Out Support” philosophy is built on the opposite model – proactive monitoring that identifies and resolves the majority of issues before your team even knows they exist.
A well-managed environment generates 20% to 30% of its tickets through automated monitoring alerts, not user complaints.
Two Metrics to Request Before You Renew
The two numbers to request at any SLA review meeting:
- FCR rate above 65% – strong providers target above 80%
- Reactive ticket ratio below 90% of total ticket volume
A provider who won’t share these metrics doesn’t have confidence in their own numbers. If that’s where you are, our guide to switching IT provider covers what a stronger alternative looks like.
Security Obligations in Your SLA
An IT support SLA that says nothing about cybersecurity isn’t fit for purpose.
According to the UK Government’s Cyber Security Breaches Survey 2024 (gov.uk), 50% of UK businesses and 32% of charities reported a cybersecurity breach or attack in the preceding 12 months. Phishing was the dominant attack vector, affecting 84% of targeted businesses.
Cyber Essentials as a Five-point SLA Checklist
Cyber Essentials is a UK government-backed framework covering five foundational security controls. Ask your provider to confirm that each of the following is explicitly written into your contract:
- Firewalls: Boundary firewalls configured and maintained as part of the managed service
- Secure configuration: Devices and software set up securely from the outset and reviewed on a defined schedule
- User access control: Account permissions managed and reviewed on an ongoing basis
- Malware protection: Anti-malware installed, updated, and actively monitored
- Patch management: Security updates applied within a contractually defined timeframe
What Compliance Means for Your Contracts
Embedding these controls isn’t optional for businesses working with public sector or NHS clients – it’s a regulatory prerequisite.
The NCSC supply chain security guidance (ncsc.gov.uk) highlights a critical gap: only 11% of UK businesses have reviewed the cyber risks posed by their immediate IT supply chain. Your provider’s security posture directly affects yours.
Microbyte holds Cyber Essentials Plus certification independently, verified through an external audit. Whether your business runs Windows-based or Mac IT support environments, that certification is the baseline your insurer and procurement team will ask for.
Beyond the SLA: XLAs and the Experience Gap
Your SLA confirms the server is running. An Experience Level Agreement (XLA) tells you whether your team can actually work.
While traditional SLAs measure technical compliance, XLAs incorporate qualitative data: Net Promoter Scores (NPS), Customer Effort Scores (CES), and sentiment analysis of
user feedback. The question shifts from “did we meet our targets?” to “did your people get their jobs done?”
Do You Have Visibility of Both?
Forward-thinking providers are beginning to offer both. When evaluating a new or existing contract, ask whether experience metrics sit alongside the traditional SLA data. A provider who can answer that question is thinking about your business outcomes.
One who can’t is focused on their own compliance rate.
How Much Does an IT Support SLA Cost?
On-site IT support SLA costs in the UK typically range from £500 to £5,000 per month, depending on business size, scope of cover, and whether security monitoring is included in the base price.
What Drives the Cost Variation
- Business size: A 15-user business and a 150-user business have fundamentally different support demands and ticket volumes
- Response time commitments: Faster guaranteed response times carry a premium, as they should
- 24/7 cover: Genuine round-the-clock support from your own engineers costs more than a 9-5 desk with an overnight answering service
- Security scope: SLAs that include active security monitoring cost more than helpdesk-only contracts
Frequently Asked Questions
- What are SLA expectations?
- How do you ensure compliance with SLAs?
- What is SLA, and how does it apply to IT services?
- What are your expectations for SLAs and customer service?
What Are SLA Expectations?
SLA expectations define the measurable standards your IT provider must meet, covering response times, resolution targets, uptime guarantees, and support hours. For UK SMEs, the baseline expectation includes responding to critical outages within one hour, a Mean Time To Resolve (MTTR) under four hours for critical incidents, and maintaining overall SLA compliance above 90% to 95%. Your specific expectations should reflect your business hours and risk profile.
How Do You Ensure Compliance With SLAs While Providing Technical Support?
Compliance requires real-time ticket monitoring, automated alerts as response windows approach, and regular internal performance reviews against agreed targets. We track all active incidents against SLA commitments, escalate any ticket approaching its deadline, and provide monthly compliance reports for every client. Our target is above 95% SLA compliance across all priority levels, with a First Contact Resolution (FCR) rate above 80%.
What is SLA and How Does it Apply to IT Services?
A Service Level Agreement (SLA) is a legally binding contract between a business and its IT service provider that defines the quality, scope, and timelines for the services delivered. In managed IT, an SLA commits to specific response and resolution times by incident priority, minimum uptime percentages, and financial penalties or service credits if those commitments are missed.
What Are Your Expectations for Service Level Agreements and Customer Service?
Expect your SLA to be specific, measurable, and commercially enforceable – not built on vague language like “we’ll respond promptly.” You should be able to request your provider’s SLA compliance rate at any time, understand exactly what happens when a target is missed, and receive regular performance reports without having to chase them. A provider unwilling to share these metrics doesn’t have confidence in their own numbers.
An IT support SLA you can’t evaluate isn’t protecting your business. If you don’t know your provider’s FCR rate or reactive ticket ratio, it’s time for a review.
Microbyte works with businesses across Peterborough, London, Cambridge, and Bedford – get in touch and we’ll tell you what your contract covers and what it doesn’t.
