SLA in plain English
SLA stands for Service Level Agreement. In customer support, it simply means: "We promise to respond to your issue within X hours." That's it.
Different types of issues get different SLA targets based on urgency:
- Critical — production down, payments not working, data loss. SLA: 1–4 hours.
- High — major feature broken, significant customer impact. SLA: 4–8 hours.
- Medium — partial functionality issue, workaround available. SLA: 24 hours.
- Low — minor issues, feature requests, questions. SLA: 48–72 hours.
Why SLAs matter (even for small teams)
Without SLAs, support tickets sit in a queue with no priority. A critical production issue gets the same queue position as a question about how to export a report. Agents pick what's easiest, not what's most urgent. Customers with serious problems wait hours for responses.
With SLAs, everything has a deadline. Critical tickets are flagged immediately. The team knows what to tackle first. Managers can see at a glance which tickets are at risk of breaching.
💡 SLA vs response time vs resolution time: SLA usually refers to first response time (how long until someone acknowledges the ticket). Resolution time (how long to fully fix it) is a different metric and harder to SLA against because it depends on the complexity of the issue.
Setting realistic SLA targets for Indian support teams
The most common mistake is setting overly aggressive SLAs that the team can't sustain. Here are realistic targets based on team size:
| Priority | Team of 1–3 | Team of 4–10 | Team of 10+ |
|---|---|---|---|
| Critical | 4 hours | 2 hours | 1 hour |
| High | 12 hours | 8 hours | 4 hours |
| Medium | 48 hours | 24 hours | 12 hours |
| Low | 72 hours | 72 hours | 48 hours |
Start conservative. It's far better to promise 48-hour response and consistently deliver in 12 hours than to promise 8 hours and miss it regularly. Once you're consistently meeting your targets, tighten them.
SLA tracking built into Resolvo
Set priority-based SLA targets. Get alerts before tickets breach. Free to start.
Set Up SLA Tracking →How to set up SLA in Resolvo
- Go to Settings → SLA Configuration in your Resolvo dashboard
- Set hours for each priority level (Critical, High, Medium, Low)
- Enable SLA alerts — you'll get notified when a ticket is approaching breach
- The ticket queue automatically sorts by SLA risk — most urgent at the top
Resolvo's dashboard shows a "SLA Risk" indicator for any ticket within 2 hours of its deadline. Agents can see immediately which tickets need attention first without manually calculating times.
The most common reasons teams breach SLAs
- Tickets assigned to agents who are OOO — solution: auto-reassign unresponded tickets after 1 hour
- Priority not set correctly — solution: use inbound rules to auto-set priority based on keywords (e.g., "payment failed" → Critical)
- Queue checked infrequently — solution: enable email + Slack notifications for SLA-at-risk tickets
- Too many Critical tickets — solution: tighten your definition of Critical; most things are Medium
What to do when you breach an SLA
Breaches happen, especially early on. When they do:
- Respond to the customer immediately, even if just to acknowledge and explain the delay
- Log the breach — what ticket, what priority, how long over
- Identify the root cause (was someone OOO? Was it a Friday afternoon surge?)
- Adjust your process or targets for next time
A customer who experiences a breach but receives a genuine, prompt acknowledgement often rates the support interaction higher than a customer who received a technically on-time but robotic response.
Final thoughts
SLA is a simple concept dressed up in enterprise jargon. Set realistic targets, make sure the team can see which tickets are at risk, and review breaches honestly when they happen. That's the entire system. Start with four priority levels and four targets, and refine from there.
Built-in SLA tracking for your support team
Priority queues, breach alerts, SLA reports. Free to start on Resolvo.
Start Free →