Agents needed for 750 calls an hour
750 calls an hour with a five-minute handle time is 62.5 erlangs of work and needs 70 agents on the phones to answer 80 per cent within 20 seconds, at 89% 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 | 37.5 | 43 | 87% | 42 | 62 |
| 240 s | 50.0 | 56 | 89% | 56 | 80 |
| 300 s | 62.5 | 70 | 89% | 69 | 100 |
| 360 s | 75.0 | 83 | 90% | 83 | 119 |
| 420 s | 87.5 | 96 | 91% | 96 | 138 |
| 480 s | 100.0 | 109 | 92% | 109 | 156 |
| 600 s | 125.0 | 136 | 92% | 136 | 195 |
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 750 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.