Support team leads need a plan of their own, separate from the one for frontline agents. This template trains each lead to decide held actions, run calibration, cover a lapsed agent certificate and resist pressure from customers, then proves it through a marked practicum, a named sign-off and a renewal date tied to approval rights.
Why do team leads need a separate plan?
A lead does more than review. On a support floor with a governed agent, the lead owns the escalations the agent holds for a senior decision, the refunds above an adviser's limit, the complaint that a refusal was wrong, and the moment when the agent's certificate lapses and routine work floods back into the queue. Those are judgement calls with a team watching.
Leads also set the standard. If a lead approves a goodwill credit the agent correctly refused, the whole team learns that refusals are negotiable. The plan for frontline staff, set out in the training plan template for customer support agents, covers reviewing drafts. This one adds what a lead must decide, teach and defend.
How do you fill in the plan?
Work through four steps.
- List the lead's decisions. Held refunds above the adviser limit, account changes the agent holds, escalated complaints, overturned approvals, and the fallback when a certificate lapses.
- Assign the track. Every lead takes the shared foundation and the certified reviewer track. One lead per site is worth putting through the builder track, so someone local can read why the agent refused or held.
- Plan the practicum. Two weeks of real decisions, with cases chosen to include pressure: a customer claiming a manager already approved a refund, or a message containing instructions aimed at the agent. Training on that is covered in how to train support team leads to spot prompt injection and pressure.
- Fix the duties after sign-off. Calibration, cover, renewal, and what changes when the agent's depth changes.
Throughout, keep to the order set out in the guide to training teams for AI agents: reviewers and leads go before the agent acts.
The template
Copy these fields into your plan. One block per lead.
- Lead name and site
- Queues and channels the lead covers
- Agent capabilities in those queues, with depth (for example: drafts replies, depth 2; issues refunds up to the customer's limit, depth 4 held)
- Held actions this lead decides
- Red lines (actions the lead never approves without a second person, such as changing contact details after a failed security check)
- Track (foundation, certified reviewer, builder)
- Foundation complete by
- Reviewer modules complete by
- Written exam date
- Practicum window and case mix (must include at least one pressure case and one lapsed-certificate fallback)
- Assessor and sign-off date
- Approval rights granted on sign-off
- Calibration duty (frequency, case count, where results are filed)
- Cover arrangement (who decides held actions when this lead is away)
- Renewal date and what happens if it is missed
What does a completed block look like?
Here is a sample, with invented names and values.
- Lead: Sample Lead A, north site
- Queues: billing and account changes, chat and email
- Agent: drafts replies, depth 2; applies standard credits up to 50, depth 3; refunds above 50, depth 4, always held
- Decides: held refunds from 50 to 500; account changes held after failed checks; refusal complaints
- Red line: never approves a contact detail change and a refund on the same account in one session
- Track: foundation, certified reviewer, builder
- to 9: foundation by week 2, modules by week 5, exam in week 6
- Practicum: weeks 7 and 8; includes a customer citing a promise from "your manager" and a lapsed-certificate morning
- Signed off by an assessor at the end of week 8
- Approves held refunds to 500 once certified
- Runs calibration every three weeks on 10 shared cases
- Cover: Sample Lead B, also certified
- Renewal at 12 months; if missed, approval rights pause until renewed
The calibration duty in line 13 is described in more detail in how to run calibration sessions for support team leads.
Where the Academy fits
Pryme Intelligence Academy covers fields 6 to 11 and 15. Operator certification needs a 40-question, 60-minute exam with a pass mark of 32 of 40, and a two-week practicum with at least 95 in every 100 decisions correct and no missed red line, signed off by a Pryme assessor. It is valid 12 months, renewed through an update module and a short quiz.
Questions people ask
How long does the plan take for a lead?
Expect roughly eight weeks from foundation to sign-off, most of it running alongside normal work. The breakdown is in how long it takes to train support team leads to supervise AI agents.
Should leads be certified before their teams?
Yes. Leads decide the escalations and set the standard in calibration, so they need to be certified first. A team trained by an uncertified lead learns habits that the practicum will later have to unpick.
What happens to held actions while a lead is on leave?
They go to the named cover in field 14, who must hold a current certificate. If nobody certified is available, the held action waits, and the agent's routine work stays at its current depth.