How to set an approver rule for the support team

Front-line advisers approve the agent's drafted replies and refunds or replacements in a small band above what the agent may do alone. Account changes that affect security, such as a new email or phone number, are held for a second adviser after verification. Everything larger goes to team leads. An adviser's approval band lasts only while their certificate is current.

What does the support team approve, and who owns the rule?

Support agents handle a large share of customer questions: order status, how-to questions, returns, simple refunds. Some of their actions are held for a person: replies on sensitive topics, refunds just above the agent's limit, replacements, and changes to account security details. The front-line advisers who approve these are the first layer of control, and the support team's approver rule names who they are and what they may release.

The support manager owns the rule; the head of support signs it off. The agent owner configures it. Our explainer on what an agent approver is covers the role, and our guide to AI agent skills by role sets out what support advisers need to know.

What are the steps?

1. Support manager: lists the agent's actions by depth. Depth 1: reads orders, account history and help content. Depth 2: drafts replies on sensitive topics, such as bereavement or complaints. Depth 3: answers routine questions, issues refunds and replacements within a small limit, books returns. Depth 4: refunds above the limit, changes account email, phone or password recovery details.
2. Support manager: assigns depth 2 drafts to any adviser on shift, who reads and sends.
3. Support manager: sets the adviser band for refunds and replacements above the agent's limit.
4. Support manager: holds security changes for a second adviser after verification through a channel on file.
5. Support manager: routes anything above the band to team leads under the leadership rule.
6. Support manager: ties each band to a current certificate. Agent owner configures and files.

Why do security changes need a second adviser?

Account takeover often starts in support. A caller or chatter claims to be the customer, knows enough to sound convincing, and asks to change the email address because they "lost access". If the change goes through, every later security message goes to them.

The agent holds the change and verifies through a channel already on file: a code to the existing phone or email. If verification fails, it refuses and passes the contact to an adviser. If verification succeeds, a second adviser, not the one talking to the customer, releases the change. The adviser in the conversation is the one being persuaded; the second adviser sees only the evidence.

This is a narrow rule, but it prevents expensive harm. Fraud teams should see these cases; compare the approver authority matrix for the IT team, which applies the same idea to staff password resets.

Which controls make the rule work, and what evidence do they leave?

Bands by role. Evidence: approver names matched to the approver authority matrix for the support team.

Sensitive drafts sent by people. Evidence: an adviser named on each sensitive reply.

Verified security changes with a second adviser. Evidence: verification method and second adviser's name on each change.

Refunds to the original payment method. Evidence: payee matched to the original payment on each refund.

Rights lapse with certificates. Evidence: certificate status on each approval date.

What should you measure?

• Security changes approved by the adviser in the conversation. The target is none.
• Refunds in the adviser band, by reason and adviser.
• Customer satisfaction on held contacts compared with contacts the agent closed alone.
• Time from hold to decision during peak hours.
• Sensitive replies corrected by advisers, grouped by topic.

Where does it usually go wrong?

The band is too narrow. If most refunds are held, advisers release without reading. Revisit the band through the support manager.

Advisers release their own conversations' security changes. Usually because the second adviser is busy. Staff for it.

Compliance and IT rules are copied. Compare the approver rule for the compliance team and the approver rule for the IT team: different risks, different bands.

Replacements are treated as free. A replacement order costs as much as a refund and is easier to abuse, because it ships goods rather than returning money to the original payment method. Put replacements in the same band as refunds of the same value, and let the agent flag customers with repeated claims for an adviser to review.

Approvers lose context between shifts. A held refund raised at the end of one shift is approved at the start of the next by an adviser who never saw the conversation. The held action should carry the full conversation and the agent's sources, so the approver decides on the evidence rather than on the summary line.

Advisers do not know the agent's limit. They think the agent "can't do refunds" and process them manually. Train advisers on exactly what the agent does at each depth.

Where the Academy fits

Pryme Intelligence Academy's Operator track is designed for reviewers who work the queue every day, including human review and teaching the agent. Lessons can be read or listened to as audio, which suits advisers learning between shifts. A support team can make each approval band depend on a current Certified Pryme Operator certificate.