Occupancy is the share of an agent's logged-in time spent handling calls, including after-call work. The sustainable ceiling is about 83% (Call Centre Helper) — above that, attrition starts paying for whatever efficiency you gained.
It is the one contact-centre metric where a better number is not better.
The calculation
Occupancy = time handling contacts ÷ time logged in.
An agent logged in for 8 hours who spends 6 hours 20 minutes on calls and after-call work is at 79% occupancy. The remaining hour and 40 minutes is available time — waiting for the next call.
Note what is not in the denominator: breaks, training and meetings are shrinkage, not idle time. An agent in a team meeting is not logged in and unoccupied; they are not logged in at all. Mixing the two produces an occupancy figure that looks comfortable while people are drowning.
Why 100% is a failure state
The intuition is that idle agents are waste. The arithmetic says otherwise.
Calls arrive randomly. If every agent is on a call the moment a new one arrives, that caller queues — and because arrivals cluster, queues form far below full utilisation. Available time is not waste; it is the buffer that absorbs randomness. Removing it does not increase throughput, it converts throughput into wait time.
Above roughly 83%, three things follow. Agents lose recovery time between calls, so handle time creeps up and quality drops. Service level becomes volatile — small volume changes produce large queue swings. And attrition rises, which is the expensive one: replacing an agent costs more than the idle minutes ever did.
Occupancy and service level pull against each other
You cannot maximise both. Higher occupancy means fewer spare agents, which means longer waits. The Erlang C model makes this explicit — every service-level target implies an occupancy, and every headcount implies both.
This is why small queues struggle. A five-agent queue cannot run at high occupancy and hit an 80% in 20 seconds target simultaneously; there is not enough pooling. A fifty-agent queue can. If your occupancy is low and you cannot raise it without breaking service level, the answer is usually to merge queues, not to cut headcount.
Reading it honestly
Occupancy is measured over an interval, and the interval matters. A daily figure of 78% can contain a 95% morning and a 60% afternoon, which is two different problems averaged into the appearance of health.
Check it per interval alongside service level. Sustained high occupancy with good service level means you are running hot and should add heads. High occupancy with poor service level means you are already short. Low occupancy with poor service level means the problem is not headcount at all — it is routing, or the forecast, or handle time.
The occupancy calculator works it out per interval from logged-in and handling time.
Frequently asked questions
What is a good occupancy rate? Roughly 75–85%, with about 83% as the practical ceiling (Call Centre Helper). Sustained figures above that trade attrition for short-term efficiency.
Is occupancy the same as utilisation? No. Occupancy measures handling time against logged-in time. Utilisation usually measures against total paid time, so it includes breaks and training and comes out lower.
Why is our occupancy low when everyone is busy? Usually because breaks and meetings are being counted as logged-in time. Occupancy should only count time an agent was available to take a call.
Can occupancy be too low? Yes — persistently below about 70% normally means overstaffing for the volume, or a queue too small to pool effectively.
