Agents needed for 300 calls an hour
300 calls an hour with a five-minute handle time is 25.0 erlangs of work and needs 30 agents on the phones to answer 80 per cent within 20 seconds, at 83% occupancy. The table runs the same Erlang C calculation across handle times and two common targets; every row opens the calculator with those inputs so you can change anything else.
| Handle time | Erlangs | Agents for 80/20 | Occupancy at 80/20 | Agents for 90/60 | To schedule at 30% shrinkage |
|---|---|---|---|---|---|
| 180 s | 15.0 | 19 | 79% | 19 | 28 |
| 240 s | 20.0 | 25 | 80% | 25 | 36 |
| 300 s | 25.0 | 30 | 83% | 30 | 43 |
| 360 s | 30.0 | 36 | 83% | 36 | 52 |
| 420 s | 35.0 | 41 | 85% | 42 | 59 |
| 480 s | 40.0 | 47 | 85% | 47 | 68 |
| 600 s | 50.0 | 57 | 88% | 58 | 82 |
Click a handle time to open the calculator with that row's inputs.
Assumptions
- Calls arrive at random across a 60-minute interval; Erlang C with no abandonment.
- Agents shown are on the phones for the whole hour. The last column divides by 0.7 and rounds up.
- No occupancy ceiling is applied; small volumes come out under 85%, large ones above it, and the staffing requirement calculator adds the ceiling.
Frequently asked questions
- Why does 300 calls an hour need more agents than the erlangs?
- Erlangs are the average number of calls in progress. Calls bunch, so agents above that average are needed to keep queues short; the gap is the price of the service level target, and it shrinks as a share of the total at higher volumes.
- Is this per hour or per day?
- Per hour, for one hour that looks like this. A day has quiet and busy hours; the week planner spreads a daily or monthly total across intervals and adds the hours up.
Stop doing this one interval at a time
Pebble WFM forecasts your demand, computes the staffing requirement for every interval, builds the roster and publishes it, with self-service for agents and a copilot that can do what a planner can. Explore a sample organisation on day one.
Start your free month
No card needed.