Glossary
What is Agent Occupancy?
Agent occupancy is the percentage of an agent’s logged-in, available time that is spent actively handling contacts — talking, in after-call work, or otherwise on a contact — versus waiting for the next one. It measures how saturated agents are during the time they are available to take work, and it is one of the headline efficiency KPIs of any contact center.
How agent occupancy is calculated
The standard formula is:
Occupancy = (Handle time ÷ Available time) × 100
- Handle time is talk time plus after-call work — every second the agent was on or wrapping up a contact.
- Available time is total logged-in time minus auxiliary states (breaks, lunch, training, coaching).
An agent logged in for 8 hours, on aux for 1 hour, who spent 5.6 hours handling contacts has 7 hours available and 5.6 hours of handle time — occupancy of 80%.
Occupancy vs. utilization vs. adherence
Three KPIs that get conflated and measure different things:
- Occupancy is handle time divided by available time. Excludes breaks. Measures saturation while available.
- Utilization is handle time divided by total scheduled time. Includes breaks and aux. Measures saturation against the schedule as a whole.
- Schedule adherence is the percentage of scheduled time the agent was actually in the planned state. Measures whether agents follow the schedule.
A single 80% number can be any of the three depending on the tool’s definition. Defining which metric the operation reports is more important than the threshold debate.
What is a good occupancy rate?
Industry benchmarks settle in a narrow band:
- 80% to 85% is the conventional healthy range for inbound contact centers.
- Below 75% suggests overstaffing or a routing problem — agents are sitting idle when they could be productive.
- Above 90% is unsustainable. Burnout, attrition, and rising after-call work follow within weeks as agents skip notes to stay ahead of the queue.
The number is determined by the service-level target and the Erlang math: hitting a tight service level on a small queue inevitably requires lower occupancy because more buffer agents are needed.
Why high occupancy is a problem
It is tempting to push occupancy as high as possible — every percentage point looks like efficiency. In practice, occupancy above 90% sustained over weeks produces:
- Burnout and attrition — agents have no recovery time between contacts.
- Quality slippage — rushed after-call work, skipped CRM updates, missed coaching opportunities.
- Compliance risk — required disclosures get truncated or skipped on regulated calls.
- Brittle service level — there is no slack to absorb a volume spike, so abandon rate and ASA both deteriorate fast when traffic moves above forecast.
The 80% to 85% band exists because it produces sustainable operations, not because anyone celebrates idle time.
Agent occupancy frequently asked questions
What is agent occupancy in a call center?
Agent occupancy is the percentage of an agent’s available time — logged in and not on a planned break — that is spent actively handling contacts. It captures how saturated the agent is during the time the operation expects them to be productive.
What is the difference between occupancy and utilization?
Occupancy is handle time divided by available time and excludes scheduled breaks. Utilization is handle time divided by total scheduled time and includes breaks and auxiliary states. Occupancy measures intensity while available; utilization measures the schedule as a whole.
What is a good occupancy rate?
A widely used benchmark is 80% to 85% for inbound contact centers. Below 75% suggests overstaffing; above 90% is associated with burnout, quality slippage, and brittle service level. The right target depends on the service-level commitment and the queue’s Erlang math.
Why is high occupancy bad?
Pushing occupancy above 90% sustained leaves no recovery time between contacts. Agents burn out and attrit, after-call work gets rushed, compliance gets sloppy, and any small volume spike pushes abandon rate and average speed of answer sharply higher because there is no buffer in the schedule.
See how DialPhone fits
DialPhone’s contact center reports occupancy alongside service level, ASA, abandon rate, and adherence — so the operations team can balance the four against each other in workforce management rather than chasing a single number to a point that burns out the team.