When your email server goes down or a critical workstation stops responding, how fast your IT support responds can mean thousands of dollars in lost productivity. Service Level Agreements (SLAs) set explicit guarantees for response and resolution times, turning vague "we'll fix it soon" into measurable commitments. Understanding what these numbers mean helps you avoid overpaying for speeds you don't need while ensuring you're not left stranded during emergencies.
What Are Response vs. Resolution Times?
Response time is how quickly an IT support technician acknowledges your ticket and begins investigating the issue. Resolution time is when the problem is actually fixed and back to normal operation. These aren't the same thing, and conflating them is where customers often get burned. A vendor might promise a 30-minute response time but take 8 hours to actually resolve your issue—technically meeting their SLA while you hemorrhage revenue.
Response times typically range from 15 minutes to 4 hours depending on your service tier, while resolution times might span 1 to 48 hours. Premium managed IT services often guarantee faster responses for critical issues.
How SLAs Are Typically Structured
Most IT support providers tier their SLAs by severity level:
- Critical/Severity 1: Complete system outage affecting multiple users or revenue generation. Response time: 15–30 minutes; resolution target: 2–4 hours.
- High/Severity 2: Major functionality impaired but workarounds exist. Response time: 1–2 hours; resolution target: 4–8 hours.
- Medium/Severity 3: Single user or minor service issues. Response time: 4–8 hours; resolution target: 24 hours.
- Low/Severity 4: Documentation requests, password resets, general questions. Response time: 24 hours; resolution target: 48 hours or longer.
This tiered approach lets you pay for the speed you actually need. A small dental practice doesn't need 15-minute response guarantees for non-urgent items, but they absolutely need them for their practice management system.
What You Should Actually Look For
Check escalation procedures. If a technician can't resolve your Severity 1 issue in the guaranteed timeframe, does it automatically escalate to a senior engineer? Many SLAs collapse under pressure because there's no escalation clause—one junior tech keeps working on the problem past the deadline with no backup.
Verify uptime guarantees are separate. Some vendors bundle uptime SLAs (99.9% availability) with response/resolution SLAs, but they're different metrics. Uptime protects you if their monitoring fails; response/resolution protects you if your infrastructure fails and you need help.
Understand business hours vs. 24/7. Standard support is 8am–6pm business hours, Monday–Friday. Expect to pay 25–50% more for after-hours coverage. If your business operates evenings or weekends, clarify exactly when response time clocks start ticking.
Look for credit clauses. Legitimate SLAs include service credits if the provider misses their commitment—usually 5–10% of monthly fees per missed SLA. If there's no penalty for missing targets, it's not really an agreement.
Red Flags in IT Support SLAs
Watch out for vendors that promise resolution times longer than your business can tolerate. A 24-hour resolution SLA for a critical system outage is essentially worthless. Similarly, "best effort" language anywhere in the SLA means there's no actual guarantee—they'll try their best, but no penalty if they fail.
Avoid providers who don't clearly define what counts as "resolution." Does it mean the issue is fixed, or just that a technician has acknowledged it? Get this in writing.
Cost Considerations
Standard managed IT support runs $100–$300 per employee per month with 4–8 hour resolution SLAs. Premium tiers with 1–2 hour guarantees cost $250–$500+ monthly. Some vendors charge per-incident for on-demand support ($75–$200 per ticket) without SLAs, which works only if your needs are truly sporadic.
Platforms like Mercoly let you compare and evaluate IT support providers side-by-side, making it easier to match SLA commitments with your actual business requirements and budget.
Frequently Asked Questions
Q: Can an IT support provider have different SLAs for different clients? Yes—SLAs are customizable based on your contract. A startup might accept 8-hour resolution times to save costs, while a financial services firm pays more for 2-hour guarantees.
Q: What happens if an IT support provider misses their SLA? You're typically owed a service credit (5–10% of that month's fees), though some contracts allow you to terminate without penalty or pursue damages.
Q: Should I choose the fastest SLA available? Not necessarily. Faster SLAs cost more and matter most for revenue-critical systems; less urgent infrastructure can use standard tiers to keep costs manageable.
Start by documenting which systems actually require rapid response, then match your SLA tiers accordingly—you'll save money and get realistic protection where it counts.