Step 1 of 4
Support Team Size Calculator

How many tickets do you handle monthly?

Include all support requests across all channels.

5,000
tickets per month
100100K

Benchmark: Agents typically handle 20-40 tickets/day for mixed channels, up to 80/day for email-only.Source: Zendesk Benchmark Report

About this tool

How to size a customer support team

Customer support headcount is the single largest cost line in most CX organizations, and it’s also the easiest one to get wrong. Underhire and SLAs slip, agents burn out, and CSAT drops. Overhire and you pay 30 percent more than needed to maintain the same service level. This calculator gives you a defensible number that you can take into a hiring plan, a budget review, or a board update. It uses the Erlang C formula for staffing (the same one call centers have used for decades) and adapts the inputs for modern channels — email, chat, voice, and social — where concurrency, response-time expectations, and complexity all vary.

Plug in your monthly ticket volume by channel, your target service level (for example, 90 percent of chats answered within 60 seconds), and your operating hours. The calculator returns the full-time-equivalent (FTE) headcount you need, plus a recommended buffer for shrinkage (training, PTO, attrition, breaks). You can then layer in AI automation: if you deflect 50 percent of tier-one tickets with an AI agent, the human team size drops accordingly. The result is a realistic staffing plan that survives finance scrutiny and matches how 2026-era support orgs actually run.

  • Channel-specific productivity assumptions (email vs. chat vs. voice)
  • Erlang C-based modeling for queue dynamics and SLA targets
  • Shrinkage buffer (PTO, training, attrition) baked in
  • Toggle AI deflection to see headcount impact in real time

Frequently asked questions

For email, a typical agent handles 400 to 600 tickets per month at sustainable quality. Chat agents handle 800 to 1,200 because of concurrency (running 2 to 3 conversations simultaneously). Voice agents handle 250 to 400 calls per month. These numbers assume average handle times of 8 to 15 minutes and SLA targets in line with industry norms.

Shrinkage covers everything that prevents an agent from being on a ticket: PTO, training, meetings, breaks, sick days. A healthy support org plans for 25 to 35 percent shrinkage. New teams or high-attrition orgs should plan closer to 40 percent. The calculator defaults to 30 percent and lets you override.

Yes. There’s a toggle for AI deflection rate. If your AI agent resolves 60 percent of tickets, only the remaining 40 percent flows to humans, and the recommended headcount drops accordingly. This is the most leverageable input — even a conservative AI program changes hiring plans materially.

Generic Erlang C calculators assume voice-only operations. We adapted the formula for modern omnichannel support, factoring in chat concurrency, async email SLAs, and the way AI agents change the queue. The math is rigorous; the inputs are realistic.

At minimum, quarterly. Whenever ticket volume grows or shrinks more than 15 percent month over month, when you launch a new channel, or when you change your SLA targets. Companies that rerun this exercise every quarter avoid both burnout and overhiring.

Want to skip the math? Book a 30-minute demo and we’ll model your exact savings live with our team. Book a demo →