Call center staffing calculator: how many agents do you actually need?
Enter your interval volume, average handle time, target occupancy, and shrinkage to estimate required agents and your staffing gap. Free, no signup, with the math written out below so you can defend the number.
A staffing requirement is the number of agents you need logged in and available during a specific interval to handle the contacts that arrive in that interval at the quality target you have set. It is not a daily headcount and it is not the number of people on the payroll. Contact centers live and die at the interval level, usually 15 or 30 minutes at a time, because demand is never flat. A team that is perfectly staffed across the day on average can still miss service level badly at 10:30 AM and sit half idle at 2:00 PM.
The staffing requirement starts from workload. Workload, often expressed in erlangs, is simply the volume of contacts in the interval multiplied by the average handle time, converted into hours of work. If 200 calls arrive in a 30-minute interval and each takes 6 minutes to handle, that is 1,200 minutes, or 20 hours of work, landing inside a half-hour window. No schedule survives that arithmetic unless someone planned for it.
The formula this calculator uses, written out
This calculator uses the workload method: required agents equals workload hours divided by the interval length in hours, divided by target occupancy, then divided by one minus shrinkage. In text: take contacts in the interval multiplied by average handle time in seconds, convert to hours, spread it over the interval, inflate it because agents cannot be busy 100 percent of the time (occupancy), and inflate it again because a chunk of every scheduled hour disappears to breaks, meetings, training, and absence (shrinkage).
For example, with 420 contacts in a 30-minute interval at 360 seconds AHT, the workload is 42 hours. Spread over half an hour, that is 84 concurrent productive agents. At 85 percent target occupancy you need about 99 agents on the queue, and at 30 percent shrinkage you need roughly 142 agents on the schedule. That is the same gross-up logic, requirement divided by (1 minus shrinkage) and by occupancy, that QueuePilot uses in its Forecast Lab.
How to choose your inputs
Use a real interval from a busy day, not a daily average, because averages smooth away exactly the peaks you are staffing for. Pull AHT from the same queue and channel you are modeling, including after-call work, since wrap time is real work even though the caller has hung up. Set target occupancy between 80 and 90 percent for voice; planning at 100 percent occupancy looks efficient on paper and produces burnout and queue collapse in practice. For shrinkage, most contact centers land between 25 and 35 percent once breaks, meetings, coaching, training, and absence are honestly counted. If you have never measured it, start at 30 percent and refine with our shrinkage calculator.
If you want the answer driven by a service level target like 80 percent of calls answered in 20 seconds rather than an occupancy target, use the Erlang C calculator instead. The workload method here is faster and easier to explain to leadership, while Erlang C models the queueing behavior directly. The two approaches usually land within a few agents of each other at contact center scale.
From a one-interval answer to a real staffing plan
A calculator tells you the requirement for one interval with inputs you typed in. A staffing plan needs that same answer for every interval of every day, driven by a forecast instead of a guess, compared against actual schedules, and re-checked intraday as volume and AHT drift. That is the job QueuePilot does: interval-level forecasting with confidence ranges, automatic staffing requirements, coverage gap detection, and plain-English intraday recommendations when the day stops following the plan.
Frequently asked questions
How many agents do I need per call volume?
Multiply contacts in the interval by average handle time to get workload, divide by the interval length, then divide by target occupancy and by one minus shrinkage. For example, 100 calls in 30 minutes at 300 seconds AHT is about 16.7 hours of workload, which needs roughly 20 productive agents at 85 percent occupancy and about 28 scheduled agents at 30 percent shrinkage.
What is a good occupancy target for a call center?
Most voice teams plan between 80 and 90 percent occupancy. Below 80 percent you are usually overstaffed; sustained occupancy above 90 percent drives agent burnout, higher AHT, and attrition. Chat and email can run higher because of concurrency.
Should I include shrinkage in staffing calculations?
Yes, always. Shrinkage is the share of paid time agents are not available for queue work, including breaks, meetings, training, coaching, and absence. Ignoring a typical 30 percent shrinkage means scheduling 30 percent fewer people than you actually need.
Is this calculator the same as Erlang C?
No. This page uses the simpler workload method with an occupancy target, which is fast and easy to defend. Erlang C models queueing behavior to hit a service level target such as 80/20. Use our free Erlang C calculator when you need the service-level-driven answer; the results are usually close.