How to set an approver rule for the support leadership

Support leadership approves what the front line cannot: refunds above the team limit, exceptions to policy, bulk goodwill, and changes to the agent's house rules. Team leads take the first band; the head of support takes the second and every bulk action; rule changes need the head of support plus a second approver. Rights follow current certificates.

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

In most support teams the front line handles the routine: the agent answers, advisers approve drafts and small refunds. Above that sits leadership: team leads, support managers and the head of support. They approve the escalations, decide the exceptions, and set the rules that decide what the front line and the agent may do alone. Our explainer on what an agent approver is covers the duty, and the approver rule for the support team covers the front line.

The head of support owns the leadership rule, with finance signing off money bands. The agent owner configures it. Our guide to AI agent skills by role covers what support leaders need to know.

What are the steps?

1. Head of support: lists what reaches leadership. Refunds and credits above the adviser band; exceptions to published policy, such as a return outside the window; complaint outcomes; bulk goodwill after an outage; changes to house rules, templates and the support agent's limits.
2. Head of support: assigns the first band to team leads. Refunds and exceptions up to a set amount.
3. Head of support: takes the second band and all bulk actions. Bulk goodwill touches many customers and costs real money.
4. Head of support: puts rule changes under two people. The head of support plus a second approver, often from finance or risk, with the support agent's owner told before the change.
5. Head of support: separates complaint outcomes from the person whose decision is complained about.
6. Head of support: ties each band to a current certificate. Agent owner configures and files.

Why should house rule changes need two leaders?

House rules decide what the support agent does without asking anyone. A change to the refund limit, the returns window or the goodwill grid changes thousands of future decisions. One leader under pressure from complaints might loosen a rule; one under pressure on cost might tighten it. Either way, the effect lands on customers and on the agent's behaviour from the next conversation.

So the rule asks for a second approver and tells the agent's owner first. The owner decides whether the change alters the agent's depth or bounds enough to need re-certification. A change that lets the agent refund more at depth 3, for example, should be certified at the new limit before it goes live.

Bulk goodwill after an outage is the other leadership-only action. The agent can build the list of affected customers from the record, propose an amount per customer and show the total. The head of support checks the selection logic and a sample before release.

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 support leadership.

Two approvers on rule changes. Evidence: both names and the agent owner's acknowledgement on each change.

Complaint independence. Evidence: the complaint approver differs from the original decision-maker.

Bulk action sample. Evidence: the sample reviewed and the head of support's name.

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

What should you measure?

• Escalations per hundred contacts, which shows whether front-line bands fit real demand.
• Policy exceptions by reason, as a guide to rules that need changing.
• Rule changes without a second approver. The target is none.
• Time from escalation to decision.
• Leader coverage, using the competency matrix for support leadership.

Where does it usually go wrong?

Leaders approve to clear the queue. Escalations pile up and leaders release them in bulk. Track time per decision.

Leaders overrule refusals instead of changing rules. A customer complains that the agent refused a refund outside the window, and a lead approves it as an exception. That is fine once. But if leads approve the same exception every week, the agent keeps refusing customers who will be granted it on escalation, which is the worst of both. Decide whether the rule is right, and change it properly if not.

Exceptions become policy by accident. The same exception approved fifty times is a de facto rule nobody wrote down. Turn it into a house rule or stop approving it.

Fraud cases land in support escalations. A customer pressing for a refund may be a fraudster. Compare the approver rule for the fraud team and route suspected fraud there.

Where the Academy fits

Pryme Intelligence Academy's Operator track is designed for team leads and operations managers, including running the rhythm and keeping knowledge current. Leaders who change house rules and limits often benefit from the Builder track as well. A support organisation can tie each leadership band to a current Certified Pryme Operator certificate and see renewals in the admin view.