It’s Monday morning and the calls are pouring in.
But you planned well and you’ve got the right agent capacity in place.
For the morning interval of 9:00AM to 9:30AM, here’s what your stats look like using a simple Erlang C calculator:
Your Service Level objective is 80/30.
In this same scenario, you can see that the Occupancy Rate – which is an outcome or result – stands at 96%.
Simply put – that means during this 30 minute interval, your Agents are talking or doing their after call work for 29 minutes.
That means that they will experience only 1 minute of Available Time over the course of that half hour (not much).
What about calls handled per Agent?
Well – if we are receiving 1,000 calls distributed across 209 Agents that works out to an average of 4.8 calls per Agent for that interval (using simple math).
In this Centre, the workload drops significantly in the afternoon.
For the afternoon interval of 4:00PM to 4:30PM, here’s what your stats look like using a simple Erlang C calculator:
Your Service Level objective remains (obviously) at 80/30.
Based on a Talk Time of 4 minutes, an After Call Work time of 2 minutes (kept at the same levels as the morning interval for purposes of simplicity) and a volume of 150 calls, you require 35 Agents to login and be part of capacity so that you can achieve your 80/30.
But you can see that the Occupancy Rate – which is an outcome or result – has fallen from its morning level of 96% down to 86% – even though we are still meeting our Service Level of 80/30.
What about calls handled per Agent?
Well – with 150 calls across distributed across 35 Agents that works out to an average of 4.3 calls per Agent for that interval (using simple math).
This compares to the 4.8 average calls per Agent in the morning interval.
Simply put – no.
The Agents who are logged into capacity in the afternoon interval of 4:00PM to 4:30PM are operating in smaller group.
Put another way, they are working with only 34 other colleagues in their ‘pool’.
In the the morning interval there were 209 Agents in the pool – clearly a much bigger pool.
At the same Service Level achievement, smaller pools have lower Occupancy rates as compared to larger pools.
When I teach this principle for certification exam purposes I like to say:
Big pool – big Occupancy…
Small (or smaller) pool – smaller Occupancy…
This outcome stems from the mathematical realities of how inbound Centres & queues work.
In all cases, measuring call centre agents on number of calls handled is incorrect – from a mathematical standpoint, an operations standpoint and a people management standpoint.
There are operational realities at work over which agents don’t have control.
One of those realities is the Pooling Principle.
Would it be fair to say that the Agents working from 9:00AM to 9:30AM are more productive than the Agents working from 4:00PM to 4:30PM?
No – it wouldn’t.
And yet around the world, in too many centres, agents are still judged or evaluated by how many calls they take.
Sometimes people tell me – yes Dan I get it, but I still target agents on the quantity produced.
But you can’t say you ‘get it’ and then do that – it’s contradictory.
If you are operating with large pools of agents across many intervals – keep your eye on the Occupancy rates they are experiencing.
The purpose is not to judge them – but to help them.
It’s proven that when Agent Occupancy hits 88% and above for long periods of time (day after day, week after week, month after month), burn-out sets in.
Understanding of the Pooling Principle also helps with queue design – for example whether to split a large queue into smaller queues – or combine smaller queues into a larger queue.
As a side note, I’ve avoided creating an ‘extreme’ example intentionally (i.e. a .5 call Per Agent variance between morning and afternoon.)
But for some centres – especially those with multiple queues – Occupancy figures can swing much more dramatically.
For the advanced reader – yes there are normalisation techniques that help you understand the ‘rate’ of call handling across groups with different Occupancy rates.
I’ll share that article on Call Handling Normalisation shortly!
Related articles you may enjoy: