How many agents does 500 calls a day actually take?

With 500 calls spread over an 8-hour window, a 240-second average handle time, and an 80/20 service level target, you need 8 agents on the phones during the peak hour and 7 during an average hour. Gross the peak up for 30 percent shrinkage and the schedule needs 12. The peak figure assumes the busiest hour carries about 15 percent of daily volume, roughly 75 calls.

Why can't I staff 500 calls a day to the average hour?

The average hour is 62.5 calls and needs 7 agents, but a peak hour carrying 15 percent of the day is 75 calls and needs 8. Running 7 agents through that peak drops the service level from 87 percent to 73 percent, and 6 agents drops it to 46 percent. If your real peak share is higher, say a lunch hour carrying 25 percent of the day, averaging melts the queue entirely.

What is the difference between agents on the phones and scheduled agents?

Agents on the phones is the count Erlang C produces, the people actually available to answer calls at a given moment. Scheduled agents is that number grossed up for shrinkage, the share of paid time lost to breaks, meetings, training, and absence. For 500 calls a day, 8 agents on the phones at peak becomes 12 scheduled agents at 30 percent shrinkage.

How do I find my real peak hour share for 500 calls a day?

Export a month of interval data from your phone system in 30-minute or hourly buckets and divide each hour's volume by that day's total. At 500 calls a day, a month of data is enough to draw a stable intraday curve. Whatever peak share you find replaces the generic 15 percent planning assumption; if your busiest hour carries 25 percent of the day, that is 125 calls instead of 75, and 8 agents will not hold it.

What service level do 8 agents deliver at the peak of 500 calls a day?

At 75 peak-hour calls with a 240-second AHT, 8 agents on the phones answer 87 percent of calls within 20 seconds, comfortably above an 80/20 target, at 62.5 percent occupancy. Dropping to 7 agents gives 73 percent, and 6 agents gives 46 percent. The steps are large because each agent is 12.5 percent of the peak group at this size.

The call center staffing ladder

Call center staffing

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.

The short answer

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

Peak-hour calls: 75
Offered load: 5 erlangs
Agents on phones: 8
Scheduled agents: 12
Service level hit: 87%
Occupancy: 62.5%

Why the math lands there

500 calls spread across an 8-hour phone window averages 62.5 calls per hour, but the plan hinges on the busiest hour. Give that hour a 15 percent share of the day and it carries 75 calls, which at a 240-second AHT is 5 erlangs of work. Erlang C puts 8 agents on the phones there, answering 87 percent of calls within 20 seconds at 62.5 percent occupancy. Gross that up for 30 percent shrinkage and you schedule 12.

The average hour needs 7 agents at 59.5 percent occupancy, so peak and average staffing differ by exactly one agent. That sounds comfortable, and it is what makes 500 calls a day feel plannable on the back of an envelope. But the comfort comes entirely from the 15 percent peak share, which is a planning placeholder, not a measurement of your line.

Swap in a real day where lunch carries 25 percent of volume and the picture breaks. That hour brings 125 calls, more than 8 erlangs of offered work, and the 8 agents this page recommends cannot mathematically clear it: the queue grows for as long as the spike lasts. At this volume the daily total tells you almost nothing. The intraday curve is the plan.

1500 calls a day with roughly 15 percent landing in the busiest hour means planning for 75 calls in the peak hour; the average hour brings 62.5.
275 calls an hour times 240 seconds of handle time is 5 erlangs of offered load: 5 hours of phone work arriving every hour.
3Counting up from 5 agents, 8 is the first count where Erlang C clears the 80/20 target: 87 percent of calls answered within 20 seconds, with an average wait of 13.4 seconds.
4At 8 agents, occupancy is 62.5 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 8 on the phones means scheduling 12.

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
6	45.9%	141s	83.3%
7	72.6%	38.9s	71.4%
8the answer	87%	13.4s	62.5%
9	94.2%	4.8s	55.6%
10	97.6%	1.7s	50%

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	75	8	62.5%
Average hour	62.5	7	59.5%

If your handle time or target differs

Agents on the phones for 75 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	6 agents	7 agents
4 minutesthis page	8 agents	9 agents
5 minutes	9 agents	10 agents
6 minutes	11 agents	12 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 deserves the most suspicion. Support lines cluster calls around Monday mornings, lunch hours, and whatever your last outreach email triggered, and none of that shows up in a daily total. At 500 calls a day you have enough volume for a month of interval data to draw a stable curve, so pull a month of it in 30-minute buckets and measure your real peak share before trusting the one-agent gap between peak and average.

The margins are thin in both directions because every agent is 12.5 percent of the peak group. Sliding from 8 to 7 agents on the phones takes the peak hour from an 87 percent service level to 73 percent, and 6 agents delivers 46 percent. One sick call or one meeting that runs into the spike erases the buffer this math appears to give you within a single interval.

The 12 scheduled agents also assume the 30 percent shrinkage lands evenly across the day, and at this size it never does. Lunches want to happen exactly when the lunch spike does, and one team meeting can absorb half the peak group at once. Steering breaks and meetings away from the busiest 90 minutes is worth more here than a thirteenth hire, and it costs nothing but scheduling discipline.

The agent count is the input; the schedule is the work. Turning 12 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 500 calls a day actually take?: With 500 calls spread over an 8-hour window, a 240-second average handle time, and an 80/20 service level target, you need 8 agents on the phones during the peak hour and 7 during an average hour. Gross the peak up for 30 percent shrinkage and the schedule needs 12. The peak figure assumes the busiest hour carries about 15 percent of daily volume, roughly 75 calls.
Why can't I staff 500 calls a day to the average hour?: The average hour is 62.5 calls and needs 7 agents, but a peak hour carrying 15 percent of the day is 75 calls and needs 8. Running 7 agents through that peak drops the service level from 87 percent to 73 percent, and 6 agents drops it to 46 percent. If your real peak share is higher, say a lunch hour carrying 25 percent of the day, averaging melts the queue entirely.
What is the difference between agents on the phones and scheduled agents?: Agents on the phones is the count Erlang C produces, the people actually available to answer calls at a given moment. Scheduled agents is that number grossed up for shrinkage, the share of paid time lost to breaks, meetings, training, and absence. For 500 calls a day, 8 agents on the phones at peak becomes 12 scheduled agents at 30 percent shrinkage.
How do I find my real peak hour share for 500 calls a day?: Export a month of interval data from your phone system in 30-minute or hourly buckets and divide each hour's volume by that day's total. At 500 calls a day, a month of data is enough to draw a stable intraday curve. Whatever peak share you find replaces the generic 15 percent planning assumption; if your busiest hour carries 25 percent of the day, that is 125 calls instead of 75, and 8 agents will not hold it.
What service level do 8 agents deliver at the peak of 500 calls a day?: At 75 peak-hour calls with a 240-second AHT, 8 agents on the phones answer 87 percent of calls within 20 seconds, comfortably above an 80/20 target, at 62.5 percent occupancy. Dropping to 7 agents gives 73 percent, and 6 agents gives 46 percent. The steps are large because each agent is 12.5 percent of the peak group at this size.

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

Three people on the phones at peak, five on the schedule, and a rota that survives lunch.

3 on phones · 5 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 →

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.

6 on phones · 9 scheduled · 80/20

See the math →