Agent Occupancy & Utilisation Calculator
Contact-centre occupancy (handle time ÷ logged-in available time) and utilisation (handle time ÷ paid time) from calls, AHT, available and paid hours — healthy ranges, idle time per hour and the effect of adding or removing an agent.
How it works
Occupancy = (contacts × AHT) ÷ (agents × available hours); utilisation = (contacts × AHT) ÷ (agents × paid hours) = occupancy × (1 − shrinkage)
Occupancy is the share of an agent’s available, logged-in time spent actually handling contacts (talk, hold, wrap-up); the remainder is waiting for the next call. It is an output of staffing, not a target to schedule to: Erlang C will show that hitting a service level in a small queue forces occupancy down, while large pooled queues run naturally above 85%. Sustained occupancy above about 90% shows up within weeks as longer handle times, more sick days and attrition, so most centres cap planning occupancy at 85%. Utilisation goes one step further and divides by paid time, folding in shrinkage; it is the finance view of productivity and is typically 55–65% even in well-run operations.
Worked example
3,840 calls at 300 s is 320 hours of work. Forty-eight agents logged in for 6.5 hours (312 available hours) run at 102.6% occupancy — over capacity; queues will build. Fifty-two agents would bring it to 94.7% and fifty-six to 87.9% (around 8 minutes idle per hour).
Frequently asked questions
Occupancy vs utilisation vs adherence?
Occupancy measures busy time within available time; utilisation measures busy time within paid time; adherence measures whether agents were in the state the schedule said, when it said.
What occupancy should I plan for?
Use it as a ceiling (85%) in the Erlang C calculation rather than a target; if the result comes out at 70% for a tiny team, that is the price of the service level, not a staffing error.
Related calculators
Workforce planning estimate; local employment law, union agreements and your own historical data should govern actual schedules and targets.