How many agents do you need to handle 2000 calls a day?

2000 calls a day over an 8-hour window peaks around 300 calls an hour, and that hour takes about 25 agents on the phones at a 240-second handle time and an 80/20 target, delivering 86.2 percent answered within 20 seconds. Schedule 36 at 30 percent shrinkage, and treat both figures as a sizing estimate to confirm against a forecast built on 15- or 30-minute intervals.

How many agents does the average hour need at 2000 calls a day?

Spread across an 8-hour phone window, 2000 calls a day averages 250 calls an hour, which takes 21 agents on the phones at a 240-second AHT and an 80/20 target, running at 79.4 percent occupancy. A peak hour carrying 15 percent of daily volume takes 300 calls and 25 agents. That four-agent swing between average and peak is why interval-level staffing replaces per-day math at this scale.

What happens if you staff fewer than 25 agents at peak?

At 300 calls an hour with a 240-second AHT, 24 agents on the phones deliver a 79 percent service level, one point under an 80/20 target, and 23 agents drop it to 68 percent. The decline is steep because occupancy already sits at 80.0 percent with 25 agents, so there is little slack to absorb a missing person. Keep shrinkage events like meetings and training out of the peak hour when you build the schedule.

Why should a 2000-call-a-day operation staff by interval instead of by hour?

Hour-level Erlang math assumes calls arrive evenly across each hour, and at 300 calls in the peak hour they rarely do. Arrival curves bunch into 15- and 30-minute windows, so a plan that hits the target on hourly averages can still miss 80/20 inside the hour. Standard practice at this volume is a forecast per 15- or 30-minute interval, a requirement computed per interval, and shift starts and breaks placed against that curve.

Is 36 scheduled agents a reliable budget number for 2000 calls a day?

For 2000 calls a day it is a defensible starting envelope: 25 agents on the phones at peak, divided by the 70 percent of paid time left after 30 percent shrinkage, rounds up to 36 scheduled agents. Whether the real answer lands above or below that depends on your measured peak share, your actual shrinkage, and how well shift start times track your arrival curve. Use 36 to frame the budget and let an interval plan set the operating number.

The call center staffing ladder

Call center staffing

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

About 25 agents on the phones at peak and 36 on the schedule, and the volume where per-day arithmetic officially hands off to interval planning.

The short answer

2000 calls a day over an 8-hour line, with the busiest hour carrying about 15 percent of volume, peaks at 300 calls an hour: that hour takes 25 agents on the phones, and 36 scheduled at 30 percent shrinkage.

Peak-hour calls: 300
Offered load: 20 erlangs
Agents on phones: 25
Scheduled agents: 36
Service level hit: 86.2%
Occupancy: 80%

Why the math lands there

The headline number comes from the peak hour, not the day. 2000 calls across an 8-hour window averages 250 an hour, but if the busiest hour carries about 15 percent of daily volume, that is 300 calls hitting the queue at once. At a 240-second AHT that is 20 erlangs of work, and Erlang C puts 25 agents on the phones to hold 80/20, landing at 86.2 percent of calls answered within 20 seconds and 80.0 percent occupancy. At 30 percent shrinkage, that means 36 scheduled agents.

At 2000 calls a day, per-day arithmetic is a sizing sanity check, not an operating plan. The gap between the 300-call peak and the 250-call average hour is four agents, 25 versus 21, and inside any single hour the arrival curve moves more than that. Operations at this volume staff 15- or 30-minute intervals from a forecast, and the 15 percent peak-share assumption baked into this page is the first thing that forecast should replace.

What these numbers are good for is the budget conversation. 36 scheduled agents is a defensible headcount envelope to put in front of finance, built from stated assumptions anyone can challenge: 240-second AHT, 80/20 target, 30 percent shrinkage, 15 percent peak share. The honest next step is a plan built at the interval level from your own arrival data, in a scheduler that can hold shifts, breaks, and coverage in one view.

12000 calls a day with roughly 15 percent landing in the busiest hour means planning for 300 calls in the peak hour; the average hour brings 250.
2300 calls an hour times 240 seconds of handle time is 20 erlangs of offered load: 20 hours of phone work arriving every hour.
3Counting up from 20 agents, 25 is the first count where Erlang C clears the 80/20 target: 86.2 percent of calls answered within 20 seconds, with an average wait of 10 seconds.
4At 25 agents, occupancy is 80 percent: the share of each logged-in hour spent handling calls rather than waiting for the next one.
5Breaks, meetings, training, and absence take agents off the phones for 30 percent of paid time, so keeping 25 on the phones means scheduling 36.

One agent either way

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

Agents on phones	Answered in 20s	Average wait	Occupancy
23	67.6%	33.3s	87%
24	78.6%	17.9s	83.3%
25the answer	86.2%	10s	80%
26	91.3%	5.7s	76.9%
27	94.6%	3.3s	74.1%

Peak hour vs average hour

A daily total hides the curve. These are the two hours your day swings between under this page's assumptions; your real intraday pattern replaces them the moment you have interval data.

Hour	Calls	Agents on phones	Occupancy
Peak hour	300	25	80%
Average hour	250	21	79.4%

If your handle time or target differs

Agents on the phones for 300 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	19 agents	20 agents
4 minutesthis page	25 agents	26 agents
5 minutes	30 agents	31 agents
6 minutes	36 agents	37 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

The 15 percent peak-share rule of thumb is the weakest assumption on this page, and at this volume you no longer need it. Your ACD already logs arrivals by half hour, and whether your true peak carries more or less than the assumed 15 percent matters directly, because each point of peak share is 20 calls an hour at 2000 calls a day, enough to move the agent requirement. A queue running 250 calls in an average hour should forecast from its own intervals, not borrow a generic curve.

Occupancy at exactly 80.0 percent is something to manage, not celebrate. The margin below 25 agents is steep: 24 on the phones drops the service level to 79 percent, already under target, and 23 drops it to 68 percent. Two agents lost to a meeting that ran long or a pair of sick calls is the difference between 86.2 percent and 68 percent in the same hour. A team that lives at 80 percent occupancy all day also has no recovery capacity when a half hour comes in heavier than forecast, which is exactly the failure mode interval planning exists to catch.

Everything here is computed on whole hours, and hour-level Erlang C assumes calls spread evenly across those 60 minutes. At 300 calls in the peak hour they will not, and a plan that is right on the hourly average can still miss 80/20 in the half hour that carries the bunching. The 25 and 36 on this page size the problem, they do not solve it; the operating answer lives one level down, in the intervals.

The agent count is the input; the schedule is the work. Turning 36 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 to handle 2000 calls a day?: 2000 calls a day over an 8-hour window peaks around 300 calls an hour, and that hour takes about 25 agents on the phones at a 240-second handle time and an 80/20 target, delivering 86.2 percent answered within 20 seconds. Schedule 36 at 30 percent shrinkage, and treat both figures as a sizing estimate to confirm against a forecast built on 15- or 30-minute intervals.
How many agents does the average hour need at 2000 calls a day?: Spread across an 8-hour phone window, 2000 calls a day averages 250 calls an hour, which takes 21 agents on the phones at a 240-second AHT and an 80/20 target, running at 79.4 percent occupancy. A peak hour carrying 15 percent of daily volume takes 300 calls and 25 agents. That four-agent swing between average and peak is why interval-level staffing replaces per-day math at this scale.
What happens if you staff fewer than 25 agents at peak?: At 300 calls an hour with a 240-second AHT, 24 agents on the phones deliver a 79 percent service level, one point under an 80/20 target, and 23 agents drop it to 68 percent. The decline is steep because occupancy already sits at 80.0 percent with 25 agents, so there is little slack to absorb a missing person. Keep shrinkage events like meetings and training out of the peak hour when you build the schedule.
Why should a 2000-call-a-day operation staff by interval instead of by hour?: Hour-level Erlang math assumes calls arrive evenly across each hour, and at 300 calls in the peak hour they rarely do. Arrival curves bunch into 15- and 30-minute windows, so a plan that hits the target on hourly averages can still miss 80/20 inside the hour. Standard practice at this volume is a forecast per 15- or 30-minute interval, a requirement computed per interval, and shift starts and breaks placed against that curve.
Is 36 scheduled agents a reliable budget number for 2000 calls a day?: For 2000 calls a day it is a defensible starting envelope: 25 agents on the phones at peak, divided by the 70 percent of paid time left after 30 percent shrinkage, rounds up to 36 scheduled agents. Whether the real answer lands above or below that depends on your measured peak share, your actual shrinkage, and how well shift start times track your arrival curve. Use 36 to frame the budget and let an interval plan set the operating number.

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 →

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

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

17 on phones · 25 scheduled · 80/20

See the math →