A refund is the wrong answer to a complaint whenever the customer did not ask for their money back, because what it says is "we would rather pay you than understand you". It is the right answer when the customer paid for something they did not get and wants the money, and nothing else. For the common complaints at a counter (a wait, a rude interaction, a wrong order that was corrected, a chronic fault, a lapsed service) the customer wants to be heard, to know what went wrong, and to believe the next visit will be different. A refund answers none of those and closes the case in a way that looks resolved on every report. That is why it becomes the default in groups that measure speed, and why reopened cases and quiet departures follow it.
This article covers what a refund says to the customer, the five kinds of complaint where it is the wrong answer and what to offer instead, the two kinds where it is the right one, why it becomes the default across a branch network, and how to set remedy authority so the person on the call has something better to reach for.
What a refund says
From the business's side, a refund is generosity: the customer is unhappy, give them their money back, done.
From the customer's side it reads differently, depending on what they said. A customer who wrote "I waited twenty-five minutes and the person at the desk did not look up once" and receives a refund has been told their experience was worth a certain amount of money and is now settled. They did not mention money. They mentioned being ignored. The refund proves the business did not read the message.
It also ends the conversation. A customer who has been refunded has nothing left to say, which is what the business wanted, and nothing left to expect, which is not. A complaint is usually made by a customer who intended to return. The refund tells them the business would rather close the file than keep them.
None of this makes refunds wrong. It makes them specific. They answer one kind of complaint and are reached for on all of them.
Five complaints where a refund is the wrong answer
The wait
"Stood in a queue for twenty minutes at 8am." The customer is describing a staffing or layout condition. A refund of their coffee does not change Tuesday morning, and the customer knows it. What they want is to be told the branch knows about the morning queue and what it is doing, and to see it be different.
Offer instead: an honest account. "The 8am shift has been one short since the start of the month; a second person starts Monday." Then a second contact when it has happened. No money.
The rude interaction
"The person at the counter was abrupt and made me feel like a nuisance." The customer is describing how they were treated by a person. A refund does not touch that, and offering one can make it worse: it suggests the business thinks the treatment had a price.
Offer instead: that it was heard, that the manager has it, and that the pattern (never the individual) is being worked on. If there is a specific thing to say ("the team has been short at that hour and it should not have reached you"), say it.
The chronic fault
"The card machine has been broken for a month." "The changing room lock still does not work." The customer is reporting a condition they have seen on several visits. A refund for today's visit treats a month-long fault as a single bad day.
Offer instead: the fix, with a date, and a second contact when it is done. A customer who tells head office about a broken lock wants the lock fixed. That is the whole remedy.
The wrong thing that was corrected
The order came out wrong, the customer said so, the branch replaced it. The customer's message is about the mistake, not the outcome. A refund on top of the replacement is the branch paying twice for a problem it already fixed, and it tells the customer that a corrected mistake is still a failure.
Offer instead: acknowledgement that the mistake was noticed by head office too, and nothing more unless the customer asks. If the same mistake is appearing at several branches, it is an issue and belongs on the list, which is a better use of the message than a refund.
The lapsed service
"You used to do table service at this branch and now you do not." "The loyalty card does not seem to work here any more." The customer is describing a policy they think changed. Often it did not; the branch stopped doing it. A refund does nothing about either.
Offer instead: the answer. If the service lapsed locally, restore it and say so. If it was a decision, say that and why. The customer asked a question. Answer it.
Two complaints where a refund is the right answer
The customer paid for something they did not receive and wants the money. A service not performed, a product not delivered, a charge that should not have been made. Refund it, the same day, on the call, without making the customer argue for it.
The customer asked for a refund. Even where the business would have offered something else, a customer who has said what they want should get it where the request is reasonable. The alternative is a negotiation, and a complaint that becomes a negotiation is a case that gets reopened.
In both, the refund is the remedy because it is what the customer named. In the five above, it is the remedy because it is what the business had to hand.
Why the refund becomes the default across a group
Three mechanisms, and they compound.
Speed is measured and the refund is fast. A group that tracks time to resolution and nothing else will see refunds close cases in a day. The remedy budget quietly becomes the recovery process, and the reopened-case rate, if anyone measured it, would show why.
The caller has no other authority. If the branch manager can refund up to a certain amount and cannot promise a rota change, a repair date or a policy answer, the refund is the only thing they can offer on the call. Giving the caller nothing but money produces calls that offer nothing but money.
The complaint is read as a transaction. A case handled from a list of transactions ("order 4471, complaint received, refund issued") never asks what the customer actually said. The customer's words are where the right remedy is written, and a process that does not read them cannot find it.
Setting remedy authority so there is something better to reach for
The fix is not to forbid refunds. It is to give the person making the call three other things they are allowed to say.
Authority to describe. The caller can tell the customer what the branch knows about the condition and what is being done. That needs the caller to know, which means the branch manager sees the issue list for their own location.
Authority to commit. Within limits, the caller can promise a fix date for a repair, a re-do at the customer's convenience, a second contact when something has changed. Those limits are set in writing, by role, like the refund limit is.
Authority to escalate with a name. Where the fix is above the caller's authority (a rota budget, a policy), the caller says who decides and when they will hear, and that is a specific person and a specific day.
With those three, the refund becomes one option on a list, used when the customer names it. Without them, it is the only option, and it gets used for everything.
Outhentik gives the caller the material for the first of these: a customer who asks to hear back becomes a case with an owner, a state and a clock, and the branch manager sees every message and every issue about their own location, so the person making the call knows what the branch knows.
What not to do
Refund as the opening offer. Listen first. The right remedy is usually in the message.
Refund and close. If the customer described a condition, the case is not resolved until the condition is addressed and the customer has been told.
Measure resolution speed alone. It selects for refunds. Measure reopened cases alongside it, and remedy spend by branch against reopen rate.
Give the branch a refund limit and nothing else. A caller with one tool uses it.
Offer a refund the customer did not ask for and then ask for anything in return. A review, a rating, a second visit. The remedy stops being a remedy and becomes a transaction, and a remedy conditional on a review is the kind of incentivised review Google's Maps user contributed content policy says will be removed.
Treat a refused refund as a difficult customer. A customer who turns down money and keeps talking is telling the business what they actually want. Listen to that.
What to expect
Remedy spend will fall at some branches and rise at others once authority is set in writing. The group total matters less than whether reopened cases fall where the spend changed.
Calls will take longer. A call that offers an account, a date and a second contact is longer than one that offers a refund. It is also the last call on that case more often.
Some customers will still want the money. Give it to them, on the call, without argument. The article is about the default, not the exception.
Customers who are refunded, or given any other remedy, can still leave and can still post a review anywhere they like. The remedy gives the business the chance to put the problem right. It does not buy anything about what the customer says elsewhere, and should not be offered as if it did.
Frequently asked questions
When should a business give a refund for a complaint?
When the customer paid for something they did not receive and wants the money, or when the customer asks for a refund and the request is reasonable. In both cases, on the call, the same day, without making the customer argue.
Why is a refund sometimes the wrong response to a complaint?
Because the common complaints at a counter are not about money. A customer describing a wait, a rude interaction, a chronic fault or a lapsed service wants to be heard, to know what went wrong and to believe the next visit will be different. A refund answers none of that and tells the customer the business would rather pay than understand.
What should you offer instead of a refund?
An honest account of what the branch knows and what it is doing, a fix with a date, a re-do at the customer's convenience, or the answer to the question the customer asked. And a second contact when the fix has happened. The right remedy is usually written in the customer's message.
Why do businesses default to refunds?
Because refunds are fast and resolution speed is what gets measured; because the caller has refund authority and no other kind; and because the complaint is handled as a transaction rather than read as a message. All three are fixable by the group, not the caller.
How do you set refund authority across branches?
In writing, by role and amount, alongside authority to describe what the branch is doing, to commit to fix dates and re-dos within limits, and to escalate to a named person with a day. Then measure reopened cases and remedy spend by branch together.
Should a refund be offered in exchange for a review?
No. A remedy tied to a review or a rating stops being a remedy, and Google's review policy treats a review given in exchange for a remedy as incentivised content to be removed. Offer the refund where it is the right answer and ask for nothing.
Try Outhentik free for 7 days, no credit card required
Outhentik gives head office a direct line from customers at every branch: every message read the same way, a case with an owner for each customer who asks to hear back, and a daily view of which problems repeat and where. The person making the call sees what the customer wrote and what the branch already knows, which is where the right remedy is found.