Occupancy vs Utilization in a Contact Center: The WFM Difference

July 1, 2026 · QueuePilot team

Occupancy and utilization get swapped constantly in contact center conversations. The swap sounds harmless, but it changes the management decision. Occupancy tells you how busy agents are while they are available for queue work. Utilization tells you how much of paid time turns into contact-handling work. Same operation, different denominator, different owner.

If you manage these as the same number, you will coach agents for a staffing-plan problem, set impossible productivity targets, and miss the shrinkage story hiding between the two.

The formulas

Occupancy measures contact-handling workload against available queue time:

Available queue-facing time includes talk, hold, wrap, and idle time while logged in for contacts. It excludes breaks, lunches, meetings, coaching, training, PTO, and other off-queue time.

Utilization measures contact-handling workload against paid time:

Paid time includes everything: queue work, idle time, breaks, lunches, meetings, training, and other shrinkage categories. That is why utilization is always lower than occupancy for the same agent or team.

A simple example

Take an eight-hour paid shift, or 480 minutes:

Occupancy = 300 ÷ (300 + 60) = 83.3 percent.

Utilization = 300 ÷ 480 = 62.5 percent.

Both numbers can be healthy. The difference is not poor agent effort. The difference is shrinkage. In this example, 120 of 480 paid minutes were off-queue, so shrinkage is 25 percent. The relationship is:

Run the math: 83.3 percent occupancy × 75 percent available paid time = 62.5 percent utilization.

That identity is powerful. If reported utilization, occupancy, and shrinkage do not roughly reconcile, something in your state mapping, payroll denominator, or reporting definition is wrong.

Who owns each number

Occupancy is mostly owned by planning. Agents do not create occupancy by trying harder. Occupancy rises when offered workload is high relative to staffed agents. It falls when staffing is heavy relative to demand. An agent can be perfectly disciplined and still have low occupancy because the interval is overstaffed.

That is why coaching individual agents on occupancy is usually nonsense. If the queue is slow, occupancy falls. If the queue is slammed, occupancy rises. The WFM team owns the staffing plan and the occupancy guardrail. Supervisors own state discipline and adherence.

Utilization is broader. It reflects how much paid time becomes productive contact work after shrinkage. Low utilization can mean too much off-queue time, poor scheduling discipline, excessive meetings, training load, absence, or simply an intentionally cushioned staffing plan. It is a leadership and planning metric, not a clean individual performance metric.

Healthy ranges

For voice teams, sustained occupancy in the low-to-mid 80s is usually healthy. Above 90 percent for long stretches, agents finish one contact and immediately receive the next one. AHT rises, error rates climb, burnout increases, and attrition follows. Below 70 percent for long stretches, the team is likely overstaffed or demand is badly fragmented.

Utilization depends heavily on shrinkage. A team with 85 percent occupancy and 30 percent shrinkage will have utilization around 59.5 percent. That can be normal. If leadership demands 80 percent paid-time utilization while also allowing 30 percent shrinkage, the implied occupancy is over 114 percent, which is impossible.

This is where bad executive dashboards create bad floor pressure. They show utilization as the productivity number without showing the shrinkage denominator. The floor gets told to improve a number the schedule design made impossible.

How QueuePilot uses the distinction

QueuePilot keeps occupancy and utilization separate because they answer different questions.

Occupancy is used as a staffing guardrail. Forecast Lab converts volume and AHT into requirements, then applies shrinkage and occupancy assumptions so the plan does not require agents to run at 96 percent occupancy for hours. Coverage Radar shows when intervals are overstaffed, balanced, or short.

Utilization is used to explain paid-time efficiency. If utilization is low, QueuePilot helps separate the causes: demand was low, staffing was high, shrinkage was high, adherence drifted, or offline work absorbed paid time. Those are different fixes.

For example, if occupancy is 86 percent but utilization is 55 percent, the queue-facing plan may be fine while shrinkage is too high. If utilization is 70 percent but occupancy is 94 percent, paid time looks efficient while the floor is too hot and burnout risk is rising. Looking at one number alone hides the story.

How to use the metrics in WFM reviews

Use occupancy when reviewing interval staffing quality:

Use utilization when reviewing paid-time design:

Then connect both to adherence. A perfectly staffed interval can still fail if agents are out of adherence. A high-shrinkage day can still hit service level if off-queue time moves into surplus intervals. The metrics only become operational when they are viewed together.

The common mistake

The common mistake is using utilization as a pressure metric and occupancy as a productivity metric. Flip that thinking.

Occupancy is the live queue-pressure metric. It tells you whether the interval plan is too hot, too soft, or balanced. Utilization is the paid-time efficiency metric. It tells you how much of the schedule becomes contact-handling time after shrinkage and off-queue work.

When you keep that separation clean, conversations get better. Analysts defend staffing assumptions with math. Supervisors coach adherence instead of queue demand. Leaders can see whether the problem is volume, shrinkage, overstaffing, or state discipline.

That is the point of WFM: not more numbers, clearer decisions.