Free Calculator
Support Team Size Calculator
How many customer support agents does your team actually need? Enter your ticket volume, SLA targets, and working hours to get a data-driven recommendation based on the Erlang-C model.
Your Team's Numbers
Total support tickets your team receives per month
Max wait time before an agent picks up a ticket
Percentage of tickets answered within the target time
Hours per day your support team is available
Average time to resolve a single ticket (including wrap-up)
Your Results
Enter your numbers and click Calculate to see results.
Recommended team size
—
support agents
Avg. Wait Time
—
Agent Utilization
—
Service Level
—
Tickets / Agent / Day
—
What if you add AI automation?
See how AI ticket deflection reduces the agents you need.
Do more with fewer agents
TriageFlow's AI automatically triages, labels, and responds to routine tickets — so your team can focus on the conversations that matter.
Try TriageFlow FreeHow to calculate support team size
Figuring out the right number of customer support agents is one of the most impactful decisions a support leader can make. Too few agents means long wait times, frustrated customers, and burned-out staff. Too many means wasted budget and idle time.
The Erlang-C model
Our calculator is based on the Erlang-C formula, the industry-standard model used by call centers and support teams worldwide. Originally developed for telephone networks, Erlang-C accounts for the random arrival of tickets throughout the day and calculates the probability that a customer will have to wait before being served.
The model takes four key inputs:
- Arrival rate — how many tickets arrive per unit of time
- Handling time — how long it takes to resolve each ticket
- Number of agents — the variable we solve for
- Service level target — the percentage of tickets answered within a time threshold
Understanding the results
Recommended team size is the minimum number of agents needed to meet your SLA target. Agent utilization tells you how busy each agent is on average. A rate between 70-85% is considered ideal — below that, you have spare capacity; above that, agents are overloaded and service quality drops.
Average wait time is the mean time a customer waits in the queue before an agent becomes available. This is different from your SLA threshold, which defines the maximum acceptable wait time for a given percentage of tickets.
The impact of AI on staffing
Modern AI tools can automatically handle a significant portion of support tickets — from password resets to order status inquiries. By deflecting 20-50% of tickets with AI automation, the effective volume reaching human agents decreases dramatically. This means you need fewer agents to maintain the same (or better) service levels.
Use the "AI Automation" slider above to model how different levels of automation would affect your team size. Even modest automation rates of 20-30% can allow you to reassign agents to higher-value work.
Common benchmarks
| Metric | Typical Range |
|---|---|
| First response time (email) | 1 - 4 hours |
| First response time (chat) | 30 - 90 seconds |
| Average handling time | 5 - 15 minutes |
| Agent utilization | 70 - 85% |
| Tickets per agent per day | 20 - 50 |
| AI deflection rate | 20 - 50% |
Frequently asked questions
How many support agents do I need?
It depends on your ticket volume, SLA targets, working hours, and handling time. As a rough rule of thumb, divide your daily tickets by the number of tickets an agent can handle per day (typically 20-50). For a precise answer that accounts for peak times and queue dynamics, use our Erlang-C based calculator above.
What is the Erlang-C formula and why should I trust it?
Erlang-C is a proven mathematical model used for over a century in telecommunications and workforce management. It accounts for the randomness of ticket arrivals (customers don't contact you at perfectly even intervals) and accurately predicts wait times and staffing needs. Most enterprise workforce management tools use Erlang-C under the hood.
How does AI automation reduce the team size I need?
AI tools like TriageFlow can automatically resolve routine tickets — password resets, order tracking, FAQ-type questions — without any human involvement. If 30% of your tickets are handled by AI, that's 30% fewer tickets for your human agents, which directly translates to fewer agents needed to meet the same SLA.
What is a good agent utilization rate?
An agent utilization between 70% and 85% is widely considered optimal. Below 70%, you likely have overcapacity. Above 85%, agents are at risk of burnout, and service quality tends to degrade because there's no buffer for unexpected spikes.
Does this calculator work for email, chat, and phone support?
Yes. The Erlang-C model is channel-agnostic. Just adjust the handling time and SLA target to match your channel. For live chat, handling times are often shorter (3-5 minutes) with tighter SLAs (30-90 seconds). For email, handling times are longer (5-15 minutes) but SLAs are measured in hours.
Need fewer agents for the same ticket volume?
TriageFlow's AI handles routine tickets automatically so your team can focus on what matters. Start your free trial today.