A customer asks for a refund three days outside the stated window. The agent knows it should probably be granted and cannot authorise it.
It goes to a supervisor, who is in a meeting. It is decided the following afternoon in the customer's favour, which is the outcome everybody expected at the start.
The refund cost a modest sum. The process cost two people's time, a day of the customer's patience and a review that mentions how long everything takes. The decision was never the expensive part.
1. Give front line agents a discretionary limit
A stated amount they can resolve without asking. Below that threshold, escalation costs more than the decision itself and produces a worse outcome for everybody.
2. Write down what the exceptions actually are
Just outside a window, a first time customer, a delivery failure, a genuine misunderstanding. These recur constantly and are treated as novel every time.
3. Decide the default answer for each
Not a rule that removes judgement, but a stated starting position. An agent who knows the usual answer decides faster and more consistently.
4. Make consistency the standard rather than generosity
Customers compare outcomes. A business where the result depends on who answered will be worked out, and the inconsistency costs more than either policy would.
5. Record every exception with a reason
Not to police agents, but because a policy overridden fifty times a month is a policy that is wrong, and nobody will see that without the record.
6. Review the patterns quarterly
The exception log is the best product and policy feedback in the business, and it is usually collected and never read.
7. Distinguish goodwill from a fault
A refund because something went wrong is not a concession, it is a correction, and treating the two the same confuses both the agent and the customer.
8. Publish the policy properly first
A great many exception requests come from a policy the customer could not find or could not understand, which is the ground in cancellation policy questions that decide a booking.
9. Give the reason when declining
A refusal with a reason is accepted far better than a refusal that quotes a policy number. The reason also lets the customer judge whether to escalate.
10. Have a stated escalation path
Where an agent genuinely cannot decide, one named route with a timescale, which is the same structure as handover questions between bot and agent.
11. Handle the out of hours cases deliberately
A customer asking on a Saturday should not wait until Monday for a decision that is within a stated limit, which is the ground in weekend and holiday cover questions.
12. Watch for the pattern behind a spike
A rise in refund requests for one product or route is a signal about the product rather than about customers, and it should reach somebody who can act on it.
13. Do not let discretion become a secret
Where a business routinely grants something, saying so publicly wins more goodwill than granting it reluctantly to whoever asks twice.
14. Apply the stated policy automatically
An assistant that applies the published policy, grants what falls inside the agreed discretionary limits, explains the reason where something is declined and escalates only the genuine judgement calls gives every customer the same answer at any hour. The same consistency applies to codes and concessions, as covered in how to handle discount and coupon questions with a. See features, start at try, and the sector view sits under small business.