How many agents do you need for 50 calls per hour?

Six agents on the phones hold an 80/20 service level at 50 calls an hour with a 240-second handle time, answering 88.1 percent of calls within 20 seconds at a 13.3-second average wait. Keeping 6 available through breaks, meetings, and absence means putting 9 on the schedule at 30 percent shrinkage.

What happens if you staff 5 agents instead of 6 for 50 calls an hour?

Five agents deliver a 72 percent service level with a 47-second average speed of answer, missing the 80/20 target. Four agents collapse to 38 percent with a 237-second average wait. Small queues degrade nonlinearly, so each agent removed below six costs more service level than the previous one.

Where do the other 3 scheduled agents go at 50 calls an hour?

Three of every ten paid hours go somewhere other than the queue at 30 percent shrinkage, to breaks, meetings, training, and absence. Nine scheduled is the smallest roster that reliably leaves 6 on the phones through that loss; eight scheduled averages only 5.6 available, which parks the queue at the 5-agent tier and its 72 percent service level for much of the day.

Does a team handling 50 calls an hour need a dedicated WFM analyst?

Usually not. Fifty calls an hour is too big for informal everyone-answers coverage but too small to fund a WFM function, so the work has to be absorbed by process: a rotating queue owner each shift, a defined backup order, and a written overflow rule. The staffing math itself is stable at 6 on the phones and 9 scheduled; the ownership rules are what most teams at this size are missing.

What occupancy should you expect at 50 calls an hour?

Six agents handling 3.3 erlangs of load run at 55.6 percent occupancy, meaning they spend a little over half their logged-in time on calls. The idle time is the structural cost of a small queue, not a productivity problem. If you fill it with other work, phone availability must preempt that work, or the 88.1 percent service level the model predicts will not materialize.

The call center staffing ladder

Call center staffing

How many agents do you need for 50 calls an hour?

Six on the phones, nine on the schedule, and an open question the math cannot answer: who owns the queue.

The short answer

Handling 50 calls an hour at a 4-minute average handle time with an 80/20 service level takes 6 agents on the phones; at 30 percent shrinkage you schedule 9.

Calls per hour: 50
Offered load: 3.3 erlangs
Agents on phones: 6
Scheduled agents: 9
Service level hit: 88.1%
Occupancy: 55.6%

Why the math lands there

Fifty calls an hour carry 3.3 erlangs of offered load at a 240-second average handle time. Six agents on the phones clear the 80/20 target comfortably, answering 88.1 percent of calls within 20 seconds with an average speed of answer of 13.3 seconds. Five agents land at 72 percent and miss the target, so six is the floor. At this size staffing moves in whole agents, and the step from five to six is the difference between missing and beating the goal.

Six on the phones is not six on the payroll. At 30 percent shrinkage, breaks, meetings, training, and absence consume three of every ten paid hours, so you schedule 9 agents to keep 6 available for calls. That puts you at 12 agents on the phones per 100 calls, a worse ratio than bigger queues manage, because 3.3 erlangs is too little traffic to pool efficiently. The inefficiency is structural, not a sign your team is slow.

This volume sits in an awkward middle. It is too much traffic to leave to whoever picks up first, and too little to fund a dedicated WFM analyst watching the queue. At 55.6 percent occupancy, your six agents are between calls nearly half their logged-in time, which makes blending them into tickets, email, or back-office work almost irresistible. The headcount math is the easy part. Deciding who owns the queue when nobody's title says queue is the real design problem at 50 calls an hour.

150 calls an hour times 240 seconds of handle time is 3.3 erlangs of offered load: 3.3 hours of phone work arriving every hour.
2Counting up from 4 agents, 6 is the first count where Erlang C clears the 80/20 target: 88.1 percent of calls answered within 20 seconds, with an average wait of 13.3 seconds.
3At 6 agents, occupancy is 55.6 percent: the share of each logged-in hour spent handling calls rather than waiting for the next one.
4Breaks, meetings, training, and absence take agents off the phones for 30 percent of paid time, so keeping 6 on the phones means scheduling 9.

One agent either way

Erlang math is a cliff, not a slope. This is the same hour with one or two agents more or fewer on the phones.

Agents on phones	Answered in 20s	Average wait	Occupancy
4	37.8%	236.8s	83.3%
5	71.6%	47s	66.7%
6the answer	88.1%	13.3s	55.6%
7	95.5%	4s	47.6%
8	98.4%	1.2s	41.7%

If your handle time or target differs

Agents on the phones for 50 calls an hour, across handle times and the two most common service level targets. Adjust every input live in our Erlang C calculator.

Average handle time	80/20 target	90/30 target
3 minutes	5 agents	5 agents
4 minutesthis page	6 agents	7 agents
5 minutes	7 agents	8 agents
6 minutes	8 agents	9 agents

Scheduled headcount sits above every number here: this page assumes 30 percent shrinkage, and your own rate comes out of our shrinkage tool.

What Erlang C does not tell you

Erlang C assumes all six agents are available for the entire interval. At this team size that assumption is fragile: pull one person into a meeting and the interval runs on five agents, dropping the service level from 88.1 percent to 72 percent and stretching average speed of answer from 13.3 to 47 seconds. Two overlapping absences leave four agents, a 38 percent service level, and a 237-second average wait, roughly as long as the calls themselves. A calendar invite is a staffing decision here, whether or not anyone treats it as one.

The model also assumes agents are dedicated and interchangeable, and at 50 calls an hour they rarely are. With occupancy at 55.6 percent, the idle time between calls gets filled with tickets, follow-ups, or back-office tasks, and blended agents drift out of availability without anyone deciding it. The fix is not more headcount, it is explicit rules: a named primary rotation each hour, a defined backup order when primaries are mid-call, and an escape hatch that lets blended staff finish focused work without silently shrinking the phone pool.

Finally, the 88.1 percent is an interval average with nobody assigned to defend it. Larger centers have a real-time analyst spotting a bad half hour as it happens; at this size the first signal is usually the abandon report the next morning. A rotating queue-owner duty, one person per shift who watches the live queue and triggers the overflow rule, costs nothing in headcount and covers the gap a WFM function would otherwise fill. Write the overflow rule down, callback offer or voicemail threshold included, before the bad hour arrives.

The agent count is the input; the schedule is the work. Turning 9 scheduled agents into shifts that follow your call curve, respect breaks, and survive swaps is what Soon builds automatically, with intraday coverage tracking when the forecast misses.

Frequently asked questions

How many agents do you need for 50 calls per hour?: Six agents on the phones hold an 80/20 service level at 50 calls an hour with a 240-second handle time, answering 88.1 percent of calls within 20 seconds at a 13.3-second average wait. Keeping 6 available through breaks, meetings, and absence means putting 9 on the schedule at 30 percent shrinkage.
What happens if you staff 5 agents instead of 6 for 50 calls an hour?: Five agents deliver a 72 percent service level with a 47-second average speed of answer, missing the 80/20 target. Four agents collapse to 38 percent with a 237-second average wait. Small queues degrade nonlinearly, so each agent removed below six costs more service level than the previous one.
Where do the other 3 scheduled agents go at 50 calls an hour?: Three of every ten paid hours go somewhere other than the queue at 30 percent shrinkage, to breaks, meetings, training, and absence. Nine scheduled is the smallest roster that reliably leaves 6 on the phones through that loss; eight scheduled averages only 5.6 available, which parks the queue at the 5-agent tier and its 72 percent service level for much of the day.
Does a team handling 50 calls an hour need a dedicated WFM analyst?: Usually not. Fifty calls an hour is too big for informal everyone-answers coverage but too small to fund a WFM function, so the work has to be absorbed by process: a rotating queue owner each shift, a defined backup order, and a written overflow rule. The staffing math itself is stable at 6 on the phones and 9 scheduled; the ownership rules are what most teams at this size are missing.
What occupancy should you expect at 50 calls an hour?: Six agents handling 3.3 erlangs of load run at 55.6 percent occupancy, meaning they spend a little over half their logged-in time on calls. The idle time is the structural cost of a small queue, not a productivity problem. If you fill it with other work, phone availability must preempt that work, or the 88.1 percent service level the model predicts will not materialize.

How many agents do you need for 25 calls an hour?

4 agents on the phones, 6 on the schedule, and an occupancy number you will need to defend.

4 on phones · 6 scheduled · 80/20

See the math →

How many agents do you need for 100 calls an hour?

10 agents on the phones, 15 on the schedule, and a service level cliff hiding one absence away.

10 on phones · 15 scheduled · 80/20

See the math →

How many agents do you need for 500 calls a day?

The answer is 8 on the phones at peak and 12 on the schedule, but only if your day is as flat as this page assumes.

8 on phones · 12 scheduled · 80/20

See the math →