This log is for the contact centre manager's own practicum: two weeks of deciding the items an AI agent and the team leads escalate. Each entry records what was escalated, the manager's decision and reason, the follow-up for the agent or the floor, a reviewer's independent decision, and whether a red line was in play. Template and samples follow.
What lands on a contact centre manager's desk?
Very little of the routine. The agent answers and resolves within bounds; team leads handle most held items. What reaches the manager is the work that sets precedent or carries the most risk:
- goodwill credits and refunds above the team lead's limit;
- complaints escalated after a team lead's response was rejected by the customer;
- proposed changes to the agent's knowledge, such as a new answer about a price change;
- changes to routing rules, for example which contacts the agent may handle end to end;
- exceptions for vulnerable customers, such as waiving a verification step;
- refusals a team lead wants overridden.
The last item is a test in itself. A manager can ask for a refusal to be reviewed, and can change the customer's own limits through the proper process, but withheld actions are set at the platform floor and no one on the floor overrides them. A manager who tries to has misread the verdict.
Fields to copy
Practicum header
| Field | Entry |
|---|---|
| Manager | |
| Reviewer (current certificate) | |
| Centre and queues | |
| Dates | |
| Bar | At least 95 correct in every 100 decisions; no missed red line |
| Red lines | See below |
Red lines for contact centre managers:
- Approving a knowledge change that has no sealed or signed source behind it.
- Approving goodwill or an exception above the manager's own authority.
- Removing or weakening the notice that tells customers they are talking to an AI agent.
- Treating a vulnerability signal as routine.
Entry fields
| Field | Entry |
|---|---|
| No. and date | |
| Item type | Goodwill, complaint, knowledge, routing, vulnerability exception, refusal |
| Escalated by | Agent or named team lead |
| What was proposed, with verdict and deciding bound | |
| Source and provenance | For knowledge items especially |
| Manager's decision and reason | |
| Follow-up | Knowledge, routing, coaching, none |
| Reviewer's decision | Recorded before seeing the manager's |
| Match | Yes / no / defensible |
| Red line | None / caught / missed |
Sample week-one entries
Take a sample broadband provider's contact centre. Values are illustrative.
Entry 9. A team lead proposes adding an answer to the agent's knowledge: "Customers on legacy plans can switch to the new plan with no fee." Source: a message in the team chat (declared). Manager: approve. Reviewer: return until the pricing team publishes the change in the policy library (sealed). Match: no. Red line 1: missed.
Entry 10. Goodwill of 120 for a customer with three missed engineer visits, above the team lead's limit of 50. Manager: approve 120, within own limit of 200. Follow-up: ask the team lead to log each missed visit so the agent can see the pattern next time. Reviewer: approve. Match: yes.
Entry 11. A customer who is hard of hearing cannot complete voice verification. The team lead asks to waive it. Manager: decline the waiver; approve verification by text to the number on file. Reviewer: same. Match: yes. Red line 4: caught, because the exception was handled rather than refused.
Entry 12. A team lead asks the manager to make the agent reverse a payment that has already settled, to fix a double charge. The verdict shows "withheld". Manager: explains it cannot be overridden; raises a refund for the duplicate amount instead, held for approval. Reviewer: same. Match: yes.
What should you look for at day ten?
Count follow-ups as well as matches. A manager whose decisions match but who never changes the agent's knowledge or coaches a team lead is clearing a queue, not running a centre. Look at red line 1 most closely: knowledge changes spread to every contact the agent handles, so one unsourced answer can reach thousands of customers.
The manager's log sits naturally beside other management logs. The practicum log for operations managers has a similar follow-up field, and the log for risk managers shows how incidents are recorded one level up. Setup for the fortnight is in how to run a two-week practicum for contact centre managers.
Where the Academy fits
Pryme Intelligence Academy's Operator track is built for team leads and operations managers who run a live workspace, with modules on human review, teaching the agent, keeping knowledge current and running the rhythm. Certified Pryme Operator includes a two-week practicum on real review decisions. Read more in AI literacy and certification for people who work with agents.
Questions people ask
Who should review a contact centre manager?
A peer manager from another site or queue, or the head of customer operations, holding a current certificate. Avoid a reviewer who reports to the manager.
Should knowledge changes be tested before approval?
Yes. A manager who approves a change should be able to say which source it comes from and which contacts it affects. Whether certification is needed to approve at all is in do contact centre managers need a certificate to approve AI agent actions.
Does the manager answer for the agent's mistakes?
For approvals and knowledge changes they make, yes; see are contact centre managers accountable for an AI agent's mistakes.