HiveDesk

Occupancy Rate: Definition, Formula, and the 85 Percent Ceiling

Occupancy rate is the share of logged-in time a contact center agent spends handling contacts rather than waiting for the next one, calculated as handle time divided by logged-in time; sustained occupancy above 85 percent is widely treated as a burnout risk.

·Updated ·10 min read

Occupancy rate is the percentage of an agent's logged-in, available time that is spent actually handling contacts, including talk, hold and after-call work. The remainder is idle time spent waiting for the queue. It is the metric that tells a workforce planner whether agents are being used efficiently, and it is also the earliest warning that a team is being run too hard.

Total handle time ÷ total logged-in time × 100Formula
80% to 85%; above 85% sustained is a burnout riskTypical range
Workforce management, efficiencyCategory
Utilization rate, shrinkage, average handle timeRelated metric

What Is Occupancy Rate?

Once an agent is logged in and in a ready state, there are only two things they can be doing: handling a contact or waiting for one. Occupancy is the first divided by the sum of both. It is a byproduct of the staffing decision rather than something agents control. Put more agents on a queue and occupancy falls; pull agents off and it rises. That is why occupancy is a management metric rather than a coaching metric, and why using it in individual scorecards is one of the classic mistakes in contact center management.

Occupancy behaves differently depending on the size of the queue. Large centers with hundreds of agents on a single skill can run 85 percent occupancy and still answer 80 percent of calls in 20 seconds, because the pooling effect smooths arrival randomness. A ten-agent team on the same service level target will typically sit closer to 65 or 70 percent, because with so few agents the queue needs slack to absorb bursts. This is a mathematical property of queuing, not a sign that the small team is inefficient.

Occupancy vs Utilization

The two terms are used interchangeably in some centers and mean different things in others. The difference is the denominator.

Occupancy rateUtilization rate
NumeratorTime handling contactsTime logged in and available (or productive time, depending on convention)
DenominatorLogged-in timeTotal paid or scheduled time
Includes breaks, training, meetingsNo, they are logged-out statesYes, they reduce the figure
Who moves itThe WFM planner, through staffing levelsScheduling, shrinkage control, attendance
Typical figure80% to 85%65% to 80%, depending on the definition

Call Centre Helper's comparison of the two metrics puts it simply: occupancy looks at activity during logged-in time only, while utilization spans the whole shift including training and meetings. A center can have healthy utilization and dangerous occupancy at the same time if it schedules lots of off-phone activity and then understaffs the phone intervals that remain.

How to Calculate Occupancy Rate

Occupancy (%) = Total handle time ÷ (Total handle time + Total available idle time) × 100

Handle time is talk plus hold plus after-call work. Available idle time is time in a ready state with no contact. Both come from the ACD and are usually reported per interval, per day and per skill group.

Worked example: a 50-agent inbound team, one day

On a Tuesday, the team logs 50 agents × 6.5 hours of logged-in phone time (after breaks, lunch, coaching and a team meeting) = 325 hours, or 19,500 minutes. The ACD reports:

  • Talk time: 12,200 minutes
  • Hold time: 980 minutes
  • After-call work: 2,650 minutes
  • Total handle time: 15,830 minutes
  • Available idle: 3,670 minutes
15,830 ÷ (15,830 + 3,670) × 100 = 81.2%

That is a comfortable day. Now look at the 11:00 to 11:30 interval on the same day, when three agents were pulled into an unplanned meeting: 47 agents logged in for 1,410 minutes, handle time 1,297 minutes, idle 113 minutes.

1,297 ÷ 1,410 × 100 = 92.0%

The daily average looked fine. The interval was brutal, and it is intervals that agents experience. This is why occupancy must be reviewed at the half-hour level, not just as a daily figure.

Occupancy Rate Benchmarks

The most widely quoted ceiling is 85 percent. Call Centre Helper reports that typical contact center occupancy ranges between 80 and 85 percent and warns that "if occupancy is consistently higher than 85%, you are risking advisor burnout." Its industry standards review also reports an observed average maximum occupancy of 83.3 percent across more than 190,000 entries into its Erlang calculator.

Those numbers apply to voice queues of reasonable size. Reasonable adjustments:

  • Small teams (under 15 agents on a skill): 65 to 75 percent is normal and healthy.
  • Blended and multi-skilled agents: occupancy runs higher because idle time on one queue is absorbed by another. The 85 percent ceiling still applies to the agent, not the queue.
  • Chat and messaging with concurrency: the metric needs redefining, since an agent handling three chats at once is "occupied" in a different sense. Most centers track concurrency and handle time separately.
  • Outbound dialer campaigns: predictive dialers routinely push occupancy into the 90s, which is one reason outbound attrition runs higher than inbound.

Why Occupancy Rate Matters

Occupancy is the metric that connects cost efficiency to human sustainability. Every point of idle time is paid time that produced nothing, so finance will always push occupancy upward. Every point above the ceiling is time an agent spent with no breathing room between calls, and the burnout statistics collected on this site show what that produces: rising absence, rising attrition and falling quality scores within a quarter or two.

There is a second reason it matters. Occupancy is the residual of the Erlang staffing model. If the planner staffs to an 80/20 service level target and the resulting occupancy is 92 percent, the queue is too small to hit that service level safely, and the options are to consolidate skills, accept a lower service level or add headcount. The occupancy number reveals the trade-off that the service level number alone hides.

How to Manage Occupancy Rate

Agents cannot improve occupancy. Planners can manage it.

  1. Set an occupancy ceiling as a staffing constraint, not a target. Staff to service level, then check that the resulting occupancy stays below 85 percent. If it does not, the staffing plan is wrong even if service level is met.
  2. Consolidate small skill groups. Pooling two 8-agent queues into one 16-agent queue lowers occupancy at the same service level, because the combined queue absorbs variability better.
  3. Schedule off-phone work into low-occupancy intervals. Coaching at 15:30 when occupancy is 70 percent costs nothing. The same coaching at 10:30 when occupancy is 88 percent tips the interval into overload.
  4. Review occupancy by interval, not by day. A daily average of 82 percent can contain four intervals above 90 percent. Those intervals are where absence and attrition are born.
  5. Use occupancy to challenge the forecast. Consistently low occupancy in a particular interval means the forecast is high or the schedule is padded. Consistently high occupancy means the reverse.
  6. Never put occupancy on an agent scorecard. An agent who "improves" occupancy is either avoiding after-call work or the queue got busier. Neither is coaching.

Occupancy is not a productivity score

An agent at 92 percent occupancy is not more productive than one at 78 percent. They are working on a queue that was staffed more thinly. Compare agents on quality, handle time and adherence; compare queues and intervals on occupancy.

How to Track Occupancy Rate

Occupancy needs contact-level data from the telephony or contact center platform: talk, hold, after-call work and ready-idle states per agent per interval. No time and attendance system captures those states, and HiveDesk does not compute occupancy.

What HiveDesk contributes is the logged-in time boundary and the off-phone context that explain occupancy swings. Shift schedules define when agents are supposed to be available. Clock-in and clock-out data from the desktop, mobile and browser apps show when they actually were, so a 92 percent occupancy interval can be traced to the three agents who were logged out at the time. Leave records show planned absence by day, and the timesheet view gives the paid-hours denominator that utilization, occupancy's sibling metric, requires. Pricing is $5 per user per month with scheduling, attendance, leave and timesheets included. See the contact center workforce analyst page for how planners use that data alongside ACD reports.

  • Utilization rate: the shift-level version of the same question
  • Shrinkage: the off-phone time that sits outside the occupancy denominator
  • Average handle time: the numerator of occupancy, broken into talk, hold and after-call work
  • Service level: the target that occupancy is traded off against
  • Schedule adherence: whether the agents who were supposed to be logged in actually were

For the staffing math behind occupancy, use the Erlang C calculator, which reports occupancy alongside agents required for any service level target, and the productivity benchmarking guide for how occupancy fits into a wider metrics set.

Frequently Asked Questions

What is a good occupancy rate for a call center?

Between 80 and 85 percent for voice queues of moderate size. Small teams on a single skill run lower, typically 65 to 75 percent, because they need more slack to absorb call bursts. Sustained occupancy above 85 percent is commonly treated as a burnout risk.

What is the difference between occupancy and utilization?

Occupancy is handle time divided by logged-in time, so it ignores breaks, training and meetings. Utilization divides by total paid or scheduled time, so those activities reduce it. Occupancy answers "how busy are available agents"; utilization answers "how much of what we pay for is on the phones."

How is occupancy calculated in a call center?

Divide total handle time (talk, hold and after-call work) by total logged-in time (handle time plus available idle time) and multiply by 100. Most centers report it per half-hour interval as well as per day.

Why is high occupancy bad?

Because the agent has no recovery time between contacts. Occupancy consistently above 85 percent is associated with rising after-call work, more errors, more absence and higher attrition. It also usually indicates the queue is understaffed for its service level target.

Should agents be measured on occupancy?

No. Occupancy is set by staffing levels and call arrival, not by agent behavior. Measuring agents on it rewards avoiding after-call work and punishes agents who happen to work quieter intervals.

Does occupancy include after-call work?

Yes. After-call work is part of handle time, so it counts as occupied. Only ready-idle time waiting for a contact counts as unoccupied.

Browse more workforce and contact center terms in the glossary.

Ready to Get Started?

Join teams worldwide who trust HiveDesk for workforce management, time tracking, and employee monitoring. $5/user/month, all features included.