Support leaders review two things: the hardest individual decisions, such as escalated complaints and goodwill above the team's limit, and the patterns across their reviewers and agents. Train both. Calibrate leaders on past escalations, shadow them reading the workspace beside a certified head of support, and sign them off on decisions and on the pattern calls they make.
What does support leadership review?
In a support operation with agents, front-line staff handle most held items and drafts. Leadership sees the residue: complaints escalated by the agent or a reviewer, goodwill and refunds above front-line limits, disputes about refusals, and cases where a customer asks for a manager. That residue is small but carries most of the reputational risk.
Leaders also review the system. Which bound decides most refusals? Which reviewer approves every draft unedited? Which held items wait longest, and why? Whether to propose a change to the business's limits, or ask for a capability to be recertified. These are decisions too, and they are where leadership training is usually thinnest.
The head of customer support owns the programme. A peer leader with a current certificate runs calibration. The builder who maintains the support agent joins pattern sessions.
What should leaders learn beyond what reviewers know?
- Reading verdicts at scale. A rise in refusals after a limit change is a consequence, not a fault. A rise in held items after a certificate lapse is expected; agent certificates lapse after 90 days and a run that clears no depth drops the agent to depth 1 the same day.
- Separating reviewer problems from agent problems. One reviewer who never declines is a coaching issue. All reviewers editing the same paragraph is a brief issue.
- Proposing, not configuring. Depth is earned on evidence, not set by a leader who wants faster handling. Leaders propose limit changes; the people who own limits decide.
- Knowing what is withheld. Some actions are withheld at the platform floor for every agent at every depth. Leaders stop teams searching for workarounds.
The steps
- Person (head of customer support): lists leader decision types and red lines. Decision types: resolve an escalated complaint, approve goodwill above limit, uphold or overturn a challenged refusal, propose a limit change. Red lines might include: overturning a refusal without recording the reason; approving goodwill above authority; proposing a depth change without certification evidence.
- Person (leader): completes the learning above and the reviewer-level learning if not already certified.
- Person (peer leader): runs calibration on 30 past escalations and 10 pattern cases built from anonymised workspace data.
- Agent, depth 2: drafts escalation responses and goodwill offers in shadow mode; the trainee leader decides in a shadow queue while the certified leader decides for real.
- Agent, depth 1: prepares a weekly pattern pack: refusals by deciding bound, held items by age, edits and declines by reviewer.
- Person (trainee leader): writes a one-page reading of the pack with proposed actions; the certified leader does the same independently.
- Person (head of customer support): compares readings and decisions, and signs off after two weeks at the bar.
- Agent, depth 1: logs decisions, readings and proposals.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Escalated complaint | Drafts a response from the case history | 2 | Leader decides and sends |
| Goodwill above front-line limit | Prepares and holds | held | Leader with authority decides |
| Challenged refusal | Shows the bound that decided | refused | Leader upholds or proposes a limit review |
| Pattern pack | Compiles weekly figures | 1 | Leader interprets and acts |
| Limit change proposal | Shows affected cases | 1 | Owners of the limits decide |
What does a good pattern reading look like?
A hypothetical week: refusals for refunds rose sharply on Tuesday; the pack shows the deciding bound moved from "certificate" to "customer's limits" the same day. A weaker reading says the agent got worse. A good reading notes that the business lowered the refund limit on Monday, checks that customers refused were told how to reach a person, and asks whether the new limit is producing the intended outcome.
The same pack shows one reviewer approved every draft unedited for five days. A good reading proposes a conversation and a sample, not a disciplinary step. Leaders learn to state what they see, the likely cause and one action.
Which controls matter, and what evidence do they leave?
- Authority limits for leaders. Evidence: the admin record of who may approve which goodwill amounts, with certificate expiry.
- Recorded reasons for overturned refusals. Evidence: the reason against each decision.
- Weekly pattern readings. Evidence: the one-page reading and the actions taken.
- Independent shadow decisions. Evidence: trainee and certified leader decisions filed separately.
What should you measure?
Agreement on escalation decisions. Agreement between independent pattern readings. Actions from readings completed. Overturned refusals later confirmed as right. Red-line misses, which must be zero.
Where does it usually go wrong?
Leaders skip training because they are senior. They then make the decisions with the highest stakes on the least practice.
Pattern reading is left to a reporting analyst. The analyst can describe the numbers; only the leader can decide what to do.
Leaders overturn refusals to please customers and never feed back the reason. The agent and the limits never improve.
The front-line programme is training the support team to review agent decisions, and the reviewer's view is in how customer support agents review an agent's decisions. Leaders should also run an incident drill for support leadership and assess themselves against the competency matrix for support leadership. The guide to training teams for AI agents sets the order.
Where the Academy fits
Pryme Intelligence Academy's Operator track covers reading the workspace, usage and billing, and running the rhythm, which is the leader's half of the job. Certified Pryme Operator is valid for 12 months, renewed through an update module and a short quiz. Teams on paid plans get an admin view of every reviewer's progress, results and certificate expiry.
Questions people ask
Should support leaders be certified before their teams?
Ideally at the same time or first. Leaders who have not been through review cannot coach it, and teams notice.
Can a leader raise an agent's depth to cut queues?
No. Depth depends on certification evidence, and the lower of the role's ceiling and the evidence wins. Leaders can ask for recertification with more cases.
How often should leaders read the pattern pack?
Weekly at minimum, and daily during a change such as a new limit, a new capability or a certificate lapse.