How Many Support Agents Do You Need?
Staffing a support team is a balancing act. Too few agents and your SLA targets slip, queues grow, and customers churn. Too many and you're burning budget on idle capacity. The right number depends on ticket volume, handle time, operating hours, and your target response time.
Industry data shows the average support agent handles 40-60 tickets per day at 75% utilization. But this varies wildly by complexity — a simple password reset takes 2 minutes, while a technical escalation can take 45 minutes. Your staffing model must account for your specific ticket mix.
This calculator uses the Erlang-based staffing model adapted for customer support. Enter your metrics and see exactly how many agents you need — then compare how AI automation changes the equation by deflecting routine tickets before they reach a human.
40–60
Tickets per agent per day
75%
Optimal utilization rate
70%
AI deflection rate
Calculate Your Team Size
Frequently Asked Questions
How many support agents do I need?+
The number of agents depends on your monthly ticket volume, target response time (SLA), average handle time, and operating hours. A general formula: agents needed = (monthly tickets × average handle time) ÷ (available hours per agent × utilization rate). This calculator automates that calculation and factors in absenteeism and peak demand.
What is agent utilization rate?+
Agent utilization rate is the percentage of an agent's available time spent actively handling tickets. Industry standard is 70-80%. Pushing above 85% leads to burnout, higher turnover, and declining quality. This calculator uses 75% as the default, which balances productivity with sustainable workload.
How does AI reduce the number of agents needed?+
AI agents handle 70-95% of routine inquiries autonomously — password resets, order status, FAQ answers, appointment scheduling. This reduces the human ticket volume by that percentage, meaning you need fewer agents. A team of 10 handling 5,000 tickets might only need 3-4 agents when AI handles the routine volume.
What SLA response time should I target?+
Industry benchmarks: live chat under 1 minute, email under 4 hours, phone under 30 seconds. For most B2B SaaS companies, a first response time of 1-2 hours is competitive. E-commerce and travel typically need faster response — under 30 minutes. This calculator lets you set your target and see the staffing impact.
Should I staff for average or peak ticket volume?+
Staff for a realistic peak — typically 1.3-1.5× your average volume. Understaffing for peaks causes SLA breaches and customer churn. This calculator applies a 1.3× peak factor by default. AI helps here significantly because it scales instantly during spikes without additional hiring.