Agent Occupancy Rate Calculator
Enter your contact volume, average handle time, and number of agents. See your occupancy rate, where it sits on the optimal–burnout spectrum, and how your service level changes as you vary headcount.
Inputs
Traffic intensity: 20.00 Erlangs
= 120 contacts × 300s ÷ 1800s. You need at least 21 agents to prevent queue collapse.
Results
Occupancy
100.0%
Service level (80/20)
0.0%
Traffic intensity
20.00 Erl
Erlang C probability
100.0%
Agents vs. occupancy & service level
| Agents | Occupancy | SL (80/20) | |
|---|---|---|---|
| 20 | 100.0% | 0.0% | |
| 21 | 95.2% | 28.8% | |
| 22 | 90.9% | 50.3% | |
| 23 | 87.0% | 66.0% | |
| 24 | 83.3% | 77.2% | |
| 25 | 80.0% | 85.0% | |
| 26 | 76.9% | 90.4% | |
| 27 | 74.1% | 94.0% | |
| 28 | 71.4% | 96.3% | |
| 29 | 69.0% | 97.8% |
Agent occupancy explained
What is agent occupancy in a contact centre?
Agent occupancy is the proportion of paid agent time spent handling contacts — calls, chats, or emails — as opposed to waiting for the next contact. Occupancy = traffic intensity ÷ agents seated. At 80% occupancy, an agent spends 80% of their shift handling contacts and 20% idle. High occupancy (>85%) causes burnout and rising AHT; low occupancy (<65%) wastes wage budget.
What is the ideal occupancy for a contact centre?
The industry benchmark for sustainable occupancy is 70–85%. Below 70% is cost-inefficient; above 85% risks service degradation as agents have no buffer to recover between contacts. At 90%+ occupancy, queue growth becomes self-reinforcing: rising wait times increase handle time (agent stress + repeat callers), which drives occupancy higher. Many centres target 80–82% as a planning ceiling.
How is occupancy different from utilisation?
Occupancy measures productive contact time as a fraction of paid time at desk. Utilisation includes all productive activities — contact handling, admin, training, meetings — as a fraction of total rostered time. Occupancy is always ≤ utilisation. A typical contact centre might have 75% occupancy and 88% utilisation after factoring in post-call work and admin time.
Why does occupancy rise when I add more agents?
Occupancy doesn't rise when you add agents — it falls. Occupancy = traffic ÷ agents, so more agents means each agent handles a smaller share of the total load and has more idle time between calls. The trade-off is cost: lower occupancy means more paid idle time. Erlang C lets you find the agent count where SL targets are met at an acceptable occupancy level.
Occupancy benchmarks by channel
Inbound voice
75–82%
Random arrivals demand a buffer. Above 85% queues compound.
Live chat (multi-session)
80–88%
Concurrency lets agents work at higher occupancy than voice.
Email / async
88–93%
No real-time queue penalty. Higher utilisation is sustainable.
Related calculators
See occupancy in your full staffing plan
Turnella shows interval-level occupancy heatmaps alongside service level, coverage, and cost — so you can see the whole picture.
Open Turnella — it's free →