What this benchmark answers
Use this table to pressure-test a staffing plan, explain why shrinkage cannot be ignored, and compare a quick estimate with your own interval-level forecast.
Original QueuePilot research
Contact center staffing benchmarks for volume and shrinkage.
A reproducible QueuePilot benchmark showing the scheduled headcount required as 30-minute call volume and shrinkage change.
Why contact center teams choose QueuePilot
Updated and maintained by QueuePilot
Published August 10, 2026 by the QueuePilot WFM research team. Re-run the documented method with the free Erlang C calculator.
Required scheduled agents by 30-minute volume and shrinkage
| Calls per 30 minutes | Productive agents | 20% shrinkage | 30% shrinkage | 40% shrinkage |
|---|---|---|---|---|
| 50 | 12 | 15 | 18 | 20 |
| 100 | 21 | 27 | 30 | 35 |
| 200 | 39 | 49 | 56 | 65 |
| 400 | 75 | 94 | 108 | 125 |
Methodology
QueuePilot calculated each scenario with Erlang C using a 30-minute interval, 300-second average handle time, an 80 percent service-level target answered within 20 seconds, and a 90 percent maximum occupancy. The productive-agent result is the smallest whole headcount that satisfies both the service-level and occupancy constraints. Scheduled headcount equals productive agents divided by one minus shrinkage, rounded up to a whole person.
This is a modeled benchmark, not a claim about an industry average. It deliberately changes only call volume and shrinkage so the effect of each variable remains inspectable. Real operations should substitute queue-specific AHT, interval volume, service goals, occupancy limits, schedules, skills, and arrival patterns.
What the benchmark shows
Volume does not translate to headcount with one universal calls-per-agent ratio. Queueing probability and occupancy create a nonlinear requirement, while shrinkage then grosses productive demand into scheduled headcount. At 100 calls per half hour, the same 21 productive-agent requirement becomes 27 scheduled agents at 20 percent shrinkage, 30 at 30 percent, and 35 at 40 percent.
At 400 calls per half hour, a ten-point shrinkage increase from 20 to 30 percent adds 14 scheduled people in this scenario. That is why a shrinkage assumption buried in a spreadsheet can move a hiring or overtime decision materially even when the demand forecast has not changed.
How to use the data
Start with the row closest to a busy interval, then reproduce it in the free Erlang C calculator. Replace the benchmark AHT and service target with your queue values. Next, compare required agents with the published schedule in QueuePilot Forecast Lab and review the intervals where the gap is largest.
For citation, name the source as QueuePilot Contact Center Staffing Benchmarks, August 2026, and link to this page. Preserve the methodology note so readers understand that the figures are modeled scenarios rather than observed industry averages.
Frequently asked questions
Is this an industry-average staffing benchmark?
No. It is an original, reproducible model benchmark that isolates volume and shrinkage under fixed Erlang C assumptions.
Why does scheduled headcount rise faster at higher shrinkage?
Scheduled headcount is productive demand divided by one minus shrinkage. As unavailable time rises, each additional shrinkage point consumes a larger share of the remaining productive schedule.
Can I reproduce these figures?
Yes. Use QueuePilot’s free Erlang C calculator with a 30-minute interval, 300-second AHT, 80/20 service level, 90 percent occupancy, and the listed shrinkage values.
QueuePilot helps teams improve forecasting, adherence, and intraday response.
Built for WFM analysts, supervisors, operations managers, and contact center leaders who need to catch staffing issues before customers call in.
Related reading and next steps
QueuePilot is coming soon
Join the waitlist for launch updates, early access, pricing, and guided onboarding with NICE CXone as the first-class integration.
Join the QueuePilot waitlist See plans and onboarding Sign in