Contact centre managers should learn to plan two workforces at once: agents that handle contacts at a certified depth, and people who decide what agents hold. That means understanding depth as capacity, the decision chain behind each held contact, how certificate lapses change staffing overnight, and how to read quality from the record rather than from a few recorded calls.
How does depth turn into capacity planning?
Depth is how far an agent may act, per capability: 1 read, 2 draft (a person sends), 3 execute routine work within bounds, 4 move money or take hard-to-undo actions, 5 coordinate other agents. In a contact centre, each contact type sits at a depth.
| Contact type | Typical depth | Planning effect |
|---|---|---|
| Policy questions, status updates | 3 | Leaves the human forecast |
| Payments and refunds within limits | 3 or 4, once certified | Mostly leaves; exceptions remain |
| Complaints, cancellations, changes of details | 2 | Still needs a person per contact, but shorter |
| Vulnerability, bereavement, disputes | Held | Needs skilled staff, often longer handling |
The manager’s forecast now has two lines: what agents absorb at their current depth, and the held and escalated work that lands on people. The second line is usually harder and slower per contact than the old average.
Why are certificate lapses a staffing event?
Because depth is earned, not configured, and it expires. The role sets a ceiling, certification on the centre’s own past contacts sets the depth, and the lower wins. Certificates lapse after 90 days. A run that clears no depth drops the agent to depth 1 the same day.
If the agent handling billing queries at depth 3 fails a run on Monday morning, every billing query from Monday lunchtime needs a person. A manager who knows the re-certification calendar plans cover in advance and has a contingency for a failed run, the same way they plan for a system outage.
What should a manager understand about held contacts?
Why they were held, and who may decide them. Every action meets five bounds: role scope, certificate, sources, the centre’s own limits and the platform guardrails. The lowest decides, and the verdict names which. A refund held because it is above the limit needs someone with refund authority. A reply held because a source was unavailable needs IT, not a reviewer.
So the rota changes. It is built not only by channel and hour but by decision type: who can approve refunds, who handles complaints, who takes vulnerable customers. The held queue’s age becomes a service level in its own right.
How does quality assurance change?
From sampling calls to reading the record. Every verdict is filed in an append-only record with the facts the agent used and their sources. A manager can see every contact an agent handled, every reviewer decision and every overturn, not a sample of five calls per adviser per month.
Useful measures: reviewer overturn rate by contact type, time to decide held items, refusals by bound, complaints mentioning the agent. A rising overturn rate on one contact type points to the agent’s sources or brief, not the reviewers.
What must customers be told?
That they are dealing with an AI system. In the EU, the AI Act requires people to be told when they interact with one. Elsewhere it is good practice and customers increasingly expect it. Managers should also ensure every customer can reach a person on request, and that the route is not buried.
What does a manager’s first month look like?
Take a contact centre manager at a mid-sized insurer. Week one: map every contact type to a depth and a decision owner. Week two: build a rota by decision type and set a target age for held items. Week three: learn to read the record and run the first calibration session with reviewers. Week four: put certificate dates in the workforce plan. Insurance supervisors shape the detail; compare contact centre manager training in Australian insurance with in France.
How do other manager roles compare?
The capacity and oversight questions overlap with what operations managers should learn first and what risk managers should learn first. Why the contact centre manager is the safeguard is argued in why contact centre managers are the real control. The overview is in AI agent skills by role.
Where the Academy fits
The Operator track in Pryme Intelligence Academy includes modules on reading the workspace, usage and billing, and running the rhythm, which map directly to a contact centre manager’s week. The admin view shows each person’s progress, results and certificate expiry dates, which helps when building a rota by decision type.
Questions people ask
Will the centre need fewer advisers?
Fewer for routine contacts, often more skilled ones for held and complex work. Measure for a few months before resetting headcount.
Should agents handle peak overflow?
They can, within their certified depth. Make sure held items from peak days have reviewers, or the backlog moves rather than disappears.
How do we handle a customer who wants a person?
Transfer them, and record the request. Never make the route harder to find.