← ccPlanning Academy · Metrics track

Occupancy — the burnout dial

Free visual lesson · about 5 minutes · short quiz at the end

ccPlanning academy · metrics

Occupancy — the burnout dial

The efficiency metric that quietly drives attrition if you push it too far.

Definition

How much of logged-in time is spent on contacts.

Occupancy is the share of time agents are actually handling contacts (talk + hold + after-call work) out of the time they were available to. 85% occupancy means 85% of available time was on contacts and 15% was waiting between them.

Don’t confuse it with…

Occupancy is not utilisation, not adherence.

Utilisation usually means productive time over paid time (so it includes breaks and shrinkage). Adherence is about being on the rostered activity. Occupancy is specifically the busy-vs-waiting ratio while available. Three different dials — people mix them up constantly.

The physics

You can’t hit 100% — and shouldn’t want to.

For an interactive channel, some waiting between contacts is unavoidable — it’s the slack that keeps queues short. 100% occupancy would mean a permanent queue. High occupancy and good service pull in opposite directions.

The burnout dial

Sustained high occupancy burns people out.

Push occupancy into the 90s for hours and agents get no breathing space between contacts — no recovery, relentless pace. The result is stress, errors, longer AHT and, eventually, attrition. The efficiency you gained on paper leaves through the door.

The scale effect

Big teams can run hotter than small ones.

A 200-seat operation can sit at high occupancy and still hold service, because large pools smooth out randomness. A 12-seat team at the same occupancy will see service swing wildly. Sensible occupancy targets depend on size — there’s no universal “good” number.

Reading it

Low occupancy isn’t always waste.

Quiet intervals naturally show low occupancy — you keep people available for the contacts that might arrive. Punishing low occupancy in a trough just means understaffing the next peak. Read it in context, not as a number to maximise everywhere.

The spiral, in numbers

Why 95% doesn’t save money

Push a team to 95% occupancy and it looks lean — barely any idle time. But with no recovery between contacts, AHT creeps up, errors rise, and a couple of agents leave. Fewer people, same work → occupancy climbs higher for those left.

That drives the next leavers. The “efficiency” you booked at 95% walks out of the door and comes back as a rehiring bill. It’s a spiral, not a dial.

The takeaway

A diagnostic, not a target to maximise.

Occupancy measures busy-vs-waiting while available. It trades off against service and, pushed too high for too long, against your people. Watch it for fragility and burnout risk — don’t chase it to 100%.

Now test yourself ↓

1 / 8

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: the efficiency metric that drives attrition

Occupancy is the share of agents’ logged-in, available time spent actually handling contacts — talk, hold and after-call work — rather than waiting between them; 85% occupancy means 85% busy and 15% waiting. It’s genuinely useful as a measure of how efficiently staffing matches demand, and genuinely dangerous the moment it becomes a target, because pushing it too high quietly burns your people out.

Three dials people confuse, and one they can’t beat

First, keep it distinct: utilisation usually means productive time over paid time (so it includes breaks and shrinkage), adherence is about being on the rostered activity, and occupancy is specifically the busy-versus-waiting ratio while available. Three different dials, mixed up constantly. And the physics is non-negotiable: for an interactive channel some waiting between contacts is unavoidable — it’s the slack that keeps queues short — so 100% occupancy would mean a permanent queue. High occupancy and good service pull in opposite directions.

Why it’s a spiral, read in context

Sustained occupancy in the 90s gives agents no breathing space between contacts: no recovery, relentless pace, leading to stress, errors, longer AHT and eventually attrition — and every leaver pushes occupancy higher for those who remain, driving the next round of leavers. Two things temper how you read it. Large teams can run hotter than small ones because big pools smooth out randomness, so there’s no universal “good” number — sensible targets depend on size. And low occupancy isn’t always waste: quiet intervals naturally show it because you’re keeping people available for contacts that might arrive, so punishing a trough just understaffs the next peak.

The principle to remember: occupancy is a diagnostic, not a target to maximise. It trades off against service and, pushed too high for too long, against your people — watch it for fragility and burnout risk, and never chase it to 100%.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. What does occupancy measure?

Occupancy is the busy-vs-waiting ratio while available — not utilisation or adherence.

2. Why can’t you run an interactive channel at 100% occupancy?

High occupancy and good service pull in opposite directions.

3. What happens if you sustain very high occupancy for hours?

No recovery time between contacts burns people out — it’s the burnout dial.

4. Why can a 200-seat team run at higher occupancy than a 12-seat team?

Pooling is why there’s no universal ‘good’ occupancy — it depends on size.

5. Is low occupancy in a quiet interval a problem to punish?

Punishing trough occupancy just understaffs the next peak — it’s a diagnostic, not a target everywhere.