AI agent · Customer service · Review against rules
Refund and goodwill requests
Every refund request needs the same checks across four systems before anyone can say yes. The agent does the checks, prepares the refunds your policy allows, and sends exceptions to a person with the facts already assembled.
Typical volumes for this process, not a client figure.
An adviser checks order, return and policy, then waits for a supervisor to approve.
Checked against policy and history; in-policy refunds prepared, the rest sent with reasons.
Where the time goes today
A refund request looks simple from the outside. Behind it, the adviser opens the order system to see what was bought and at what price, the carrier portal to see whether it was delivered, the warehouse system to see whether the return has arrived, and the payment gateway to see what was captured and whether anything has already been refunded. Only then can the policy be applied: the return window, excluded categories, the condition of the item, and what the customer is asking for.
Goodwill is harder. Most organisations have a matrix, sometimes written down, of what an adviser may offer for a late delivery or a damaged box, and a limit above which a supervisor must approve. In practice two advisers give different amounts for the same situation, and the approval queue grows every afternoon.
The errors are expensive and hard to reverse. The same order refunded twice because the customer asked by chat and by email. A refund issued before the return was received and the parcel never arrives. Money sent to a different card from the one charged. Goodwill granted on an account that has received three credits this quarter, which nobody saw because the history sits in another screen.
How the agent works
- Read the requestThe agent reads the message or chat and extracts the order, the items, the reason given and what the customer is asking for: a full refund, a partial refund, a credit or a replacement.
- Gather the factsIt pulls the order, proof of delivery, the warehouse return receipt, the captured payment and every earlier refund or credit on the account, across all channels.
- Apply the policyIt tests each condition in your policy and goodwill matrix and records the result: inside the window or not, category excluded or not, return received or not, amount within the limit for this reason and this customer.
- Prepare the outcomeWhen every condition passes and the amount is within the ceiling you set, it prepares the refund to the original payment method. Anything outside policy or above the ceiling goes to a reviewer with the reason written out.
- Record and replyIt posts the refund, logs the decision against the order and drafts the customer reply from an approved template. Refusals are drafted, not sent.
What stays with a person
Supervisors keep goodwill beyond the matrix, disputed facts and refusals. When the customer says the parcel never came and the carrier says it was delivered, the rules do not decide; someone has to weigh the evidence and the customer's history. Refusals are customer-facing and hard to take back gracefully, so the agent drafts them with the policy reason and a person sends them, at least until your overturn rate on drafted refusals shows that is no longer needed.
The review threshold is arithmetic. Compare what a wrongly granted refund costs, including the chance of recovering it, with the minutes a supervisor spends checking one. For low-value items the answer is often to let the agent post and sample afterwards.
What it reads, what it produces
| It reads | It produces |
|---|---|
| The customer message, chat transcript or call note | A decision record per request, with each policy condition and its result |
| The order management system: items, prices, dispatch | Refunds posted to the original payment method within the ceiling |
| Carrier tracking and proof of delivery | An approval queue with the reason each item is there |
| Warehouse return receipts and inspection notes | Customer replies drafted from approved templates |
| The payment gateway: captured amounts and earlier refunds | Weekly goodwill spend by reason, team and product |
| Your refund policy and goodwill matrix |
Controls that come with it
- An automatic ceiling per request and per customer per period
- Refunds only to the original payment method, never to new details
- A duplicate check across every channel before anything is posted
- A random sample of automatic refunds reviewed each week
- Refunds held until the payment file cut-off, so any can be voided before money leaves
- Every decision logged: facts read, conditions applied, amount, who or what approved
How you know it works
- Time from request to refund
- Refunds reversed or re-opened after posting
- Goodwill spend per hundred orders
- Duplicate refunds prevented
- Age of the supervisor approval queue
Is your process ready?
- Written rules: the refund policy is usually written; the goodwill matrix often lives in team leads' heads. Write it down, with limits by reason and by adviser grade, before anything is built.
- Systems: the order system and payment gateway must allow refunds by interface, and the licence for each must permit automated use.
- Cheap check: finance already reconciles refunds against returns and payments, so a wrong refund surfaces within days.
- Volume: hundreds of requests a day repays the build; a few a week does not.
- One description: customer service and finance often disagree on whether to refund when the return is dispatched or when it is received. Decide once.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Exceptions granted verbally by team leads never reach the written policy, so the agent refuses what advisers used to allow.
- Marketplace orders from third-party sellers follow different rules and must be recognised and routed out.
- Partial shipments and split payments make the refundable amount harder to compute than the order total suggests.
- Customers who ask again by another channel while a request is pending create a second case unless the duplicate check spans every channel.
Questions we get
Does the agent refund money on its own?
Only within the ceiling you set and only when every policy condition passes. Above the ceiling, outside policy or with any fact missing, it prepares the refund and waits for a person. Many teams start with the agent preparing everything and a supervisor approving in bulk, then raise the ceiling category by category as the weekly samples show the decisions hold.
Goodwill is judgement. How can software handle it?
Part of it is not judgement: a matrix that says a late delivery on a standard order earns a set credit is a rule. The agent applies that part consistently and records it. What remains, such as a long-standing customer with a poor experience outside the matrix, goes to a supervisor with the history already assembled, which is where the time was spent.
Could customers learn the rules and game them?
They can learn a policy whether a person or software applies it. The difference is that the agent sees every earlier refund and credit on the account, the address and the payment method, across all channels, every time. Repeated patterns are flagged to a person, and the data can feed a separate return fraud check if you run one.
How does this interact with card chargebacks?
Before posting, the agent checks whether a chargeback is already open on the same transaction, because refunding as well would pay the customer twice. If one is open, the request goes to the team handling disputes. After posting, the refund reference is stored against the order so that a later chargeback can be answered with evidence that the money was returned.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.