Support SLA Calculator
Calculate the team size, coverage, and response times your support team needs to meet its service level agreements.
Open source on GitHubYour metrics
Time to fully resolve a ticket
To compare against the required size
Plan your team around your SLAs. Know your staffing needs before tickets pile up.
Right-size your team
Determine exactly how many support agents you need to meet your SLA targets based on ticket volume and business hours.
Meet SLA targets
Calculate if your current team can meet response time commitments and identify gaps before they impact customers.
Optimize performance
Plan coverage schedules and identify opportunities to improve efficiency without adding headcount.
Support SLA formulas. The calculations behind help desk service levels.
| Metric | Formula | Example |
|---|---|---|
| SLA compliance | (Tickets answered within target ÷ total tickets) × 100 | 182 of 200 within 1 hour = 91% |
| Required agents | Tickets per day × handle time ÷ (hours per day × 60 × efficiency) | 400 × 12 min ÷ (8 × 60 × 0.8) = 12.5 → 13 agents |
| Tickets per hour | Tickets per day ÷ support hours per day | 400 ÷ 10 h = 40 per hour |
| Average first response time | Total time to first reply ÷ tickets with a reply | 3,000 min ÷ 200 = 15 min |
| SLA breach rate | (Tickets breaching target ÷ total tickets) × 100 | 18 of 200 = 9% |
More free tools. Free, open source, no sign-up. See all tools · Source on GitHub
Frequently asked questions
What is the SLA formula for customer support?
The most common support SLA calculation is compliance: tickets answered within the target time divided by all tickets, times 100. If 182 of 200 tickets got a first reply within 1 hour, SLA compliance is 91%. Track it separately per priority level, since each usually has its own target.
What is an SLA in customer support?
A Service Level Agreement (SLA) is a commitment between a service provider and customer that defines the expected level of service, including response times, resolution times, and availability. In customer support, SLAs typically specify how quickly tickets must be acknowledged and resolved.
How is average handle time calculated?
Average Handle Time (AHT) is the total time spent on a ticket from first response to resolution, including research, communication, and follow-up. Calculate it by dividing total handling time by number of tickets over a specific period. Most support teams have AHT between 10–30 minutes depending on complexity.
Why does the calculator use an 80% efficiency factor?
Support agents aren’t working on tickets 100% of the time. They need breaks, attend meetings, handle administrative tasks, and deal with system issues. The 80% efficiency factor accounts for this reality and provides more accurate staffing recommendations.
How can I reduce my required team size?
You can reduce required team size by: 1) Decreasing average handle time through better tools (like video support), 2) Implementing self-service options to reduce ticket volume, 3) Using automation for common issues, 4) Improving first-contact resolution rates, and 5) Better agent training and knowledge management.
What’s a realistic SLA response time target?
Common SLA targets vary by industry and support tier: Priority/Critical issues: 15–30 minutes, High priority: 1–4 hours, Normal priority: 8–24 hours, Low priority: 24–48 hours. B2B SaaS companies typically aim for 1-hour response times for paid customers during business hours.
How does video support affect these metrics?
Video lets agents see the issue directly instead of trading messages to understand it, which usually shortens handle time and cuts follow-ups. A lower handle time means the same team can handle more tickets or meet tighter SLAs. Measure your own average handle time before and after, then enter it here to see the effect on staffing.