How to keep support team leads ready for an AI agent’s 90-day recertification

Support team leads are the hinge of every cycle: they turn a recertification result into a team briefing, cover the held queue and send corrections back. Every 90 days the support agent is recertified on the team's own tickets. A ready team lead reads the result in detail, briefs in plain words, checks approver cover by shift, and coaches from the first fortnight's real tickets.

What does recertification ask of a support team lead?

Support staff see the agent's changes in their queue. The team lead sees them first and decides how the team learns them. The agent typically resolves routine tickets at depth 3, drafts replies at depth 2 and drafts refunds above the business's own limit for a person to make. Recertification re-runs the agent's cases and can move ticket types between resolved and drafted, change the refund limit, or add handover triggers.

Team leads also hold three duties nobody else does. They clear escalated holds that their staff cannot. They decide which edits their team makes to drafts are worth reporting to the builder, so the agent improves at the next cycle. And they keep approver cover on every shift, which depends on both the agent's depth and their team's certificates.

Team leads use agents for their own work too. A reporting agent compiles a team view at depth 1: edit rates by ticket type and by person, held refunds by age, handovers by reason. It drafts coaching notes at depth 2 from real tickets. The team lead decides what to coach and how.

For example, a team lead sees that one ticket type, delivery address changes after dispatch, moved from resolved to drafted at the last cycle. The team view shows two advisers editing almost every draft on that type and two sending them unchanged. That split is the coaching plan for the week.

Who owns what?

The team lead owns team readiness, coaching and shift cover for held work. The support manager owns the business's own limits. The builder owns recertification. The knowledge manager owns the help articles. Each adviser owns reading the change note.

Steps for each cycle

1. Agent, depth 1: compile the team view for the closing cycle.
2. Person (team lead): pick the corrections worth reporting, such as drafts that were wrong for the same reason more than once, and send them to the builder before recertification.
3. Person (builder): recertify.
4. Person (team lead): read the full result, not only the summary: which ticket types moved, why, and what the new refund limit is.
5. Person (team lead): write the team briefing in the team's language, with two real tickets per change.
6. Agent, depth 1: check shift cover: at least two certified approvers per shift for held refunds.
7. Person (team lead): brief the team and collect sign-offs.
8. Agent, depth 2: draft coaching notes from the first fortnight; the team lead coaches from them.

What should team leads keep relearning?

Reading the result. Team leads should understand why a ticket type moved: which gate the agent fell short on, typically grounded or scope, and what that means for drafts.

Teaching the agent. A correction that fixes one reply helps one customer. A correction that fixes a help article or a bound helps every future customer. Team leads learn to tell the two apart.

Clearing escalated holds. Team leads see the hardest refunds. They should read the deciding bound and the provenance of every fact, since a customer's own account of a missing parcel is declared.

Coaching after a depth change. When a ticket type moves from resolved to drafted, advisers suddenly need a skill they have not used on it for months. Coach accuracy before speed for two weeks.

Pryme Intelligence Academy's Operator track, whose modules include teaching the agent and running the rhythm, is aimed at exactly this role.

Controls and the evidence they leave

• Corrections sent before recertification. Evidence: the list sent to the builder and its outcome.
• Team briefing with sign-offs. Evidence: the briefing and named sign-offs.
• Shift cover check. Evidence: dated cover check per cycle.
• Named approval on escalated holds. Evidence: approvals in the append-only record.
• Practicum for new team leads. Evidence: the practicum log template for support team leads.

What to measure

Edit rates by ticket type and by person, before and after the cycle. Corrections reported that were reflected in the next recertification. Held refunds waiting at shift change. And repeat contacts on handed-over tickets. A team lead whose corrections never reach the next cycle is doing the agent's quality control by hand, every day.

Where does readiness slip?

The team lead forwards the change note without translating it. Advisers read "scope gate result" and learn nothing.

Corrections stay in the team. Advisers fix the same draft daily and nobody tells the builder.

Approver cover depends on the team lead alone. Whether team leads and advisers need a certificate to clear holds is the business's decision; see do support team leads need a certificate to approve AI agent actions. On who answers for errors, see are support team leads accountable for an AI agent's mistakes. Advisers run their own cycle; compare keeping customer support agents ready and the guide to AI literacy and certification for people who work with agents.