How many agents does an 80/20 service level take at 200 calls an hour?

200 calls an hour at a 240-second handle time is 13.3 erlangs of workload, and 17 agents on the phones clear an 80/20 target at 81.0 percent answered within 20 seconds, a one-point margin. Scheduling 25 at 30 percent shrinkage is what keeps 17 in seats, and the ratio works out to 8.5 agents per 100 calls.

Can 16 agents hold 200 calls an hour?

Not to target. Sixteen agents deliver 69 percent within 20 seconds against an 80/20 goal, and 15 fall to 51 percent. Seventeen clears the bar by a single point, which is the defining feature of this volume: one absence converts a passing hour into a clearly failing one.

Why do you schedule 25 agents when only 17 are needed on the phones?

The 17 figure counts agents actively available to take calls. In a typical operation about 30 percent of paid time never reaches the queue because it goes to breaks, meetings, training, and absence, so scheduling 25 is what keeps roughly 17 on the phones through the interval.

Is it worth scheduling an 18th agent for 200 calls per hour?

An 18th agent on the phones lifts service level from 81.0 percent to 89 percent. Since 17 clears the 80 percent target by only one point, teams at this volume often staff to 18 in their riskiest hours as insurance against forecast error or a heavy handle time day, rather than as a deliberate target upgrade.

What occupancy do agents run at with 17 agents handling 200 calls an hour?

Occupancy comes out at 78.4 percent, meaning agents spend 78.4 percent of their logged-in time handling calls. That is close to what most operations treat as a sustainable ceiling, so a bad hour should be fixed by adding people to the queue, not by expecting the existing 17 to absorb more load.

The call center staffing ladder

Call center staffing

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

17 agents on the phones, 25 on the schedule, and exactly one point of margin over the 80/20 target.

The short answer

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

Calls per hour: 200
Offered load: 13.3 erlangs
Agents on phones: 17
Scheduled agents: 25
Service level hit: 81%
Occupancy: 78.4%

Why the math lands there

Two hundred calls an hour at a 240 second AHT is 13.3 erlangs of workload, and Erlang C puts the answer at 17 agents on the phones: 81.0 percent of calls answered within 20 seconds, an average speed of answer of 16.8 seconds, and occupancy of 78.4 percent. At 30 percent shrinkage you schedule 25 to keep 17 available. That works out to 8.5 agents per 100 calls, the pooling dividend of a larger queue.

Look at how little room that answer leaves. Seventeen agents clear the 80 percent target by a single point. Drop to 16 and service falls to 69 percent; at 15 it is 51 percent, and callers can tell something is wrong. One agent pulled into an unplanned meeting, a product issue that stretches handle time, or a forecast that runs a few percent hot is enough to put the interval underwater.

This is the volume where the Erlang answer is right on average and wrong at 11am. A flat 200 calls an hour is a planning input, not something arrival patterns actually do, and one point of headroom does not survive contact with a real Tuesday. The useful takeaway is not 17. It is 17 with a single point of slack, which moves the job from setting a staffing number to defending it interval by interval.

1200 calls an hour times 240 seconds of handle time is 13.3 erlangs of offered load: 13.3 hours of phone work arriving every hour.
2Counting up from 14 agents, 17 is the first count where Erlang C clears the 80/20 target: 81 percent of calls answered within 20 seconds, with an average wait of 16.8 seconds.
3At 17 agents, occupancy is 78.4 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 17 on the phones means scheduling 25.

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
15	50.8%	81.4s	88.9%
16	69%	34.8s	83.3%
17the answer	81%	16.8s	78.4%
18	88.8%	8.5s	74.1%
19	93.6%	4.4s	70.2%

If your handle time or target differs

Agents on the phones for 200 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	14 agents	14 agents
4 minutesthis page	17 agents	18 agents
5 minutes	21 agents	22 agents
6 minutes	25 agents	26 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 treats the hour as one homogeneous block, and at 200 calls an hour that assumption does real damage. The 81.0 percent service level is an hourly average; if arrivals clump in the quarter hour after a marketing send or an outage notice, that interval misses badly while the hourly number still reads as a pass. This is the volume where forecasting at the 15 or 30 minute interval stops being a luxury, because you have enough calls to see real patterns and enough exposure to pay for ignoring them.

The 30 percent shrinkage that turns 17 into 25 scheduled is an average, and averages hide clustering. If a team meeting and a pair of coaching sessions land in the same hour, 25 scheduled can mean 15 on the phones, and 15 agents deliver a 51 percent service level. The Erlang table does not know your meeting calendar. Your intraday plan has to, which means shrinkage at this scale needs to be placed on the schedule, not only budgeted in the headcount.

Occupancy of 78.4 percent leaves almost nothing to absorb a bad hour by pushing agents harder; the model has already priced in most of their capacity. The recovery lever is movement: pull a cross-trained agent off email, slide a break out of the peak, postpone a coaching block. Each move adds one head, and one head is the gap between 69 and 81.0 percent. Someone has to be watching the queue in real time to make those calls, which is why this is roughly the volume where a real-time view becomes part of the job description.

The agent count is the input; the schedule is the work. Turning 25 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 does an 80/20 service level take at 200 calls an hour?: 200 calls an hour at a 240-second handle time is 13.3 erlangs of workload, and 17 agents on the phones clear an 80/20 target at 81.0 percent answered within 20 seconds, a one-point margin. Scheduling 25 at 30 percent shrinkage is what keeps 17 in seats, and the ratio works out to 8.5 agents per 100 calls.
Can 16 agents hold 200 calls an hour?: Not to target. Sixteen agents deliver 69 percent within 20 seconds against an 80/20 goal, and 15 fall to 51 percent. Seventeen clears the bar by a single point, which is the defining feature of this volume: one absence converts a passing hour into a clearly failing one.
Why do you schedule 25 agents when only 17 are needed on the phones?: The 17 figure counts agents actively available to take calls. In a typical operation about 30 percent of paid time never reaches the queue because it goes to breaks, meetings, training, and absence, so scheduling 25 is what keeps roughly 17 on the phones through the interval.
Is it worth scheduling an 18th agent for 200 calls per hour?: An 18th agent on the phones lifts service level from 81.0 percent to 89 percent. Since 17 clears the 80 percent target by only one point, teams at this volume often staff to 18 in their riskiest hours as insurance against forecast error or a heavy handle time day, rather than as a deliberate target upgrade.
What occupancy do agents run at with 17 agents handling 200 calls an hour?: Occupancy comes out at 78.4 percent, meaning agents spend 78.4 percent of their logged-in time handling calls. That is close to what most operations treat as a sustainable ceiling, so a bad hour should be fixed by adding people to the queue, not by expecting the existing 17 to absorb more load.

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 an hour?

The Erlang answer is 39 agents on the phones and 56 scheduled, but 85.5 percent occupancy makes 39 a floor to staff above, not a target.

39 on phones · 56 scheduled · 80/20

See the math →

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

Peak hour math says 14 on the phones, the average hour says 12, and the schedule that closes that gap is shaped, not flat.

14 on phones · 20 scheduled · 80/20

See the math →