SLA: The Agreement That Defines Your IT Support Quality
If your business contracts (or is considering contracting) an IT support service, there is one document that should be non-negotiable: the SLA, or Service Level Agreement. Without a clear SLA, any promise of service is just words.
An SLA is a formal contract between your business and your IT support provider that establishes, in measurable and verifiable terms, exactly what service you will receive, within what timeframes, and what happens if those commitments are not met.
What an IT Support SLA Should Include
Response Times
Response time is the maximum period from when you report an issue to when a technician begins working on it. Do not confuse response time with resolution time: responding means someone is already dedicated to your problem, not that it has been fixed.
A professional SLA defines response times according to incident priority:
| Priority | Description | Response Time |
|---|---|---|
| Critical | System down, business paralyzed | 30 minutes - 1 hour |
| High | Degraded service, multiple users affected | 2 - 4 hours |
| Medium | Individual problem affecting work | 4 - 8 business hours |
| Low | Query or improvement with no immediate impact | 24 - 48 business hours |
Resolution Times
In addition to when they start attending to your issue, the SLA should indicate how long it takes to resolve the problem. Resolution times are usually broader and depend on complexity:
- Critical incidents: target resolution in 4-8 hours
- High incidents: resolution within 1 business day
- Medium incidents: resolution within 2-3 business days
- Low incidents: resolution within 5 business days
Coverage Hours
This defines when you can contact support and when they will respond:
- Standard hours: Monday to Friday, 8:00 AM - 6:00 PM
- Extended hours: Monday to Friday, 7:00 AM - 10:00 PM
- 24/7: continuous coverage, including holidays
For most SMEs, standard hours with an out-of-hours emergency service is typically the most balanced option between cost and protection.
Communication Channels
The SLA should specify how you can report incidents and which channels are available:
- Phone: for emergencies and direct communication
- Email/ticket: for documented incidents with tracking
- Web portal: for checking incident status
- Chat: for quick queries
Metrics and Reports
A good SLA includes metrics that allow you to verify compliance:
- Compliance percentage for response times
- Average resolution time by priority
- Service availability (guaranteed uptime)
- Number of recurring incidents (indicates underlying problems)
These metrics should be delivered in a periodic report (monthly or quarterly) that you can review.
Penalties and Compensation
What happens if the provider fails to meet the SLA? A serious agreement includes consequences:
- Invoice discounts for non-compliance
- Service credits for the next billing period
- Right to terminate without penalty after repeated failures
Why Your Business Needs an SLA
Clear Expectations for Both Parties
Without an SLA, the relationship with your IT provider is based on subjective perceptions. You think they take too long; they think they are responding reasonably. With an SLA, there are concrete numbers that eliminate ambiguity.
Business Protection
An SLA guarantees that critical incidents receive the urgency they deserve. When a system outage is costing you money every minute, you cannot depend on the provider’s goodwill: you need a written commitment.
Cost Control
Knowing exactly what is included in the service protects you from surprise invoices. The SLA should specify which services are covered and which are billed separately:
- Included: incidents, preventive maintenance, monitoring, updates
- Not included (with defined rates): new projects, expansions, hardware
Foundation for Continuous Improvement
Periodic SLA reports reveal trends: if a particular type of incident keeps recurring, it indicates an underlying problem that needs to be addressed. Without data, systematic improvement is impossible.
Signs of a Poor SLA
Be cautious if your support contract exhibits any of these characteristics:
- No defined timeframes: “we will respond as soon as possible” is not a commitment
- No priority distinction: a downed server is not the same as a question about Excel
- No metrics: if it is not measured, it cannot be improved or claimed against
- No penalties: an SLA without consequences for non-compliance is merely a statement of intent
- Excessive fine print: exclusions that hollow out the substance of the commitments
Key Questions Before Signing an SLA
Before contracting an IT support service, make sure you get clear answers to these questions:
- What is the guaranteed response time for critical incidents?
- What coverage hours does the service include?
- How are incidents reported and tracked?
- What reports will I receive and how often?
- What happens if the agreed timeframes are not met?
- Which services are included and which have additional costs?
- What is the availability commitment (uptime)?
- Is there a minimum contract term? What are the cancellation conditions?
An SLA That Actually Works
At SOINTE, we believe an SLA should be a living document that reflects the reality of the service, not a piece of paper that gets signed and filed away in a drawer. All our IT support contracts include clear SLAs with guaranteed response times, monthly reports, and no fine print.
If your business is looking for IT support with real, verifiable commitments, get in touch with us. We will explain exactly what our service includes, within what timeframes, and how we measure it.