Every support agent can be made to look good in a demo. The test comes later, in the conversation where a customer asks for something the business has not decided to give: a refund outside policy, a fee waived, a delivery date nobody has confirmed. An agent that says yes to keep the customer happy has made a promise the business now has to keep or break.

Three kinds of request

Sort support work into three, and the design of the agent follows.

• Answer. Order status, account details, how-to questions, policy explanations. The agent answers from approved sources and cites which one. This is most of the volume.
• Draft and hold. Refunds, credits, exceptions and anything that moves money. A refund is depth 4 and a support role stops at depth 3, so the agent drafts both the approval and the decline, sends neither, and holds the decision for a named person with the policy clause and the customer’s history attached.
• Refuse, with a reason. Legal advice, promises outside policy, anything no source covers. The agent says what it cannot do and routes the customer to who can. A refusal that names its reason is a service; one that does not is a dead end.

Channels are part of the role

Which channels an agent may use is set by its role, not by convenience. A support agent is permitted on email, live chat and consumer messaging, because for a support case the thread is the record; a Finance agent is never on consumer messaging, because a payment instruction there could never be evidence. That is a records question before it is a trust question, and it is why the role sits above the customer’s own settings.

What to measure

Resolution rate on its own rewards an agent for saying yes. Measure three things together:

• Resolved within depth. Conversations the agent closed using only what it is certified to do.
• Held correctly. Requests it held for a person that a person then agreed needed holding.
• Refused with a reason. Refusals that named the bound and gave the customer a next step.

A falling held-correctly rate tells you the agent is holding too much; a rising complaint rate on refunds tells you it is holding too little. Both are visible because both are recorded.

A worked case: the late refund

A customer asks for a refund on an order delivered nine days late. Policy allows refunds within seven days of delivery. The agent reads the order, the delivery record and the policy, and drafts two replies: an approval citing the late delivery, and a decline citing the seven-day window. It sends neither. A named person sees both drafts, the clause and the order history, picks one in under a minute, and the decision is recorded against their name.

Write the policy the agent reads

A support agent is only as consistent as the policy behind it. Most support policies were written for people, who fill gaps with judgement and with the person at the next desk. An agent fills gaps by refusing, with a reason, which is safe but slow. Before deployment, go through the ten most common exception requests and write down the rule for each: who qualifies, up to what amount, with what evidence. Every rule you write is a class of request the agent can draft confidently instead of refusing.

Handover without repetition

When a conversation moves to a person, the customer should never have to say it again. The agent hands over a file, not a transcript:

• What the customer asked for, in one line.
• What the agent checked, with the records it read.
• What it drafted, if anything, and why it stopped.
• The policy clause that applies, or a note that none does.

A person who receives that file can decide in a minute. A person who receives a transcript starts again.

Refusals in plain words

The way an agent refuses matters as much as the refusal. Compare two answers to a customer asking for a fee to be waived:

“I’m sorry, I can’t help with that.”

“I can’t waive fees myself. I’ve passed your request to our team with your account history, and you’ll hear back today. If it’s approved, the fee will be refunded to the same account.”

The second says what the agent cannot do, what it has done instead, who decides and when. It is longer, and it is the one that does not turn into a complaint.

Where to start

Start with the questions your team answers most and enjoys least: order and account status, how-to questions and policy explanations. Put refunds and exceptions in draft-and-hold from day one, and expect them to stay there: a refund is depth 4, and no ceiling takes a support role past 3.

Questions people ask