A complaint is the cheapest consulting you will ever be handed. The customer read your whole business, found the weak seam, and wrote it down for free. Most small teams answer complaints with silence or a defensive paragraph — and both cost the same thing: the customer. Handled well, a complaint is the cheapest loyalty program in commerce. This is the reply.
The hour rule. The first reply is not the answer — it is the promise of one. "Hi Maria — it's Tom, I own the place. I've read your note and I'm on it; you'll hear back from me by 4pm today." Ninety seconds, and it does most of the work: the biggest driver of complaint outcomes is not the compensation, it is the speed of the first human response. Whoever receives the complaint owns it — forwarding an angry email without answering is ignoring it, with extra steps. Public complaint? One visible reply that a human has it, then take the detail private.
The five-line reply.
- Their name and thanks for telling you. The complaint you hear is a customer still in the game; the dangerous ones never say anything and just don't come back.
- What you heard, restated in their words. The specific, unglamorous detail is the proof a human read it.
- What happened, honestly, no internals. "The order fell out of the Saturday run and no one caught it. That's on us." One sentence. Your org chart is not their problem.
- What you're doing about it, with a date and a name. "We're remaking it at no charge for Sunday pickup, and I've added an order-confirmation call for every custom order." "We're looking into it" translates to "we are doing nothing."
- The make-good, sized to the miss, offered not negotiated. The fix is the apology; the gesture is the punctuation. Not so small it's an insult, not so large every future complaint becomes an auction.
Never in the reply: "but", "unfortunately", "as per our policy", or "we apologize for any inconvenience" — that last one apologises to nobody for nothing.
The rules. One public reply, then private (the public reply is marketing that only exists because something went wrong). Whoever answers owns it to the end. Refund the small ones fast, investigate the large ones honestly — the customer hears the same five lines either way. One log, every complaint. Never blame the customer or a named staff member in writing.
The traps. The paste-job apology ("any inconvenience"). The over-explanation before acknowledgement. Compensation before understanding — it buys silence and trains complainers. Hiding the public complaint (the re-post always has an update). The discount reflex (it tells the customer the problem was a pricing problem; it almost never was).
The log and the monthly read. One complaint is a bad day; three in the same category is a process failure, and no reply fixes it. Read the categories monthly — late, wrong, rude, broken, billing — and let each cluster point at one process change. That change is the only response that compounds.
Worked example: the bakery and the one-star review. A $3,800-a-year regular posted a one-star at 9:40am — custom cake twenty minutes late, message missing. Owner saw it 10:15, public reply up 10:40, five lines private, cake remade and delivered same day on the house (~$70). The customer updated the review the same afternoon: "they fixed it within hours — this is how you run a business." The Friday standing order grew by two dozen. "The reply cost seventy dollars. The silence would have cost me the customer and rented my reputation to their worst morning."
Related: the voicemail greeting script is the other half of the first-impression contract; the chargeback response template is when the complaint skips the conversation and goes to the bank; the missed-call text-back setup catches the complaint that never got written down at all. Full page: Customer Complaint Response Template.
From the Hive80 Lab ops kit — The First 30 Minutes (free), Ops Starter Kit ($14), Ops Starter Kit Vol. 2 ($27), Ops Mega Bundle ($49).
Top comments (0)