In short
A good complaint response follows a simple arc: listen, acknowledge, apologise, act, follow up. Handled well, a complaint is one of your best chances to build loyalty - customers whose problems get resolved quickly often become more loyal than those who never had one. Below is a five-step framework plus seven copy-and-paste templates.
Every complaint is a customer telling you exactly what to fix, for free. The difference between a churned customer and a loyal one is rarely the problem itself - it’s how the reply lands. This guide gives you a repeatable framework and templates for the situations support teams face most.
A five-step framework for any complaint
- Listen and read fully. Understand the whole issue before you reply. Skimming leads to answers that miss the point and make things worse.
- Acknowledge and empathise. Show you get why they’re frustrated. “I understand how disruptive this is” costs nothing and changes everything.
- Apologise and own it. A sincere apology isn’t an admission of guilt - it’s basic respect. Avoid “sorry you feel that way”; it reads as blame.
- Act - offer a concrete fix. Say specifically what you’ll do and by when. Vague reassurance erodes trust; a clear next step rebuilds it.
- Follow up. Circle back once it’s resolved to confirm the customer is happy. This is the step most teams skip, and it’s the one they remember.
7 complaint response templates
1. General complaint acknowledgement
Hi [First name],
Thank you for telling us - I’m sorry this has been frustrating. I’ve read through everything and I want to make it right. Here’s what I’m doing now: [action], and I’ll come back to you by [time].
2. Product not working / a bug
Hi [First name],
You’re right, this shouldn’t behave this way, and I’m sorry for the disruption. I’ve reproduced it and raised it with our team as [priority]. As an immediate workaround: [steps]. I’ll update you the moment it’s fixed.
3. Slow or missed response
Hi [First name],
I’m sorry we left you waiting - that’s not the standard we hold ourselves to. I’m picking this up personally right now. Here’s where things stand: [update].
4. Billing dispute
Hi [First name],
Thanks for flagging this, and I understand the concern. I’ve reviewed [charge] and here’s what happened: [explanation]. To put it right, [refund/adjustment] - you’ll see it by [date].
5. Angry or emotional customer
Hi [First name],
I hear you, and I’m genuinely sorry. You’ve every right to be frustrated. Let me focus on fixing it: [concrete action]. I’ll own this until it’s resolved and keep you updated at every step.
6. Complaint you can’t fully resolve
Hi [First name],
I want to be straight with you: [what we can’t do and why]. I’m sorry that’s not the answer you were hoping for. What I can do is [alternative], and I’d like to make that happen for you.
7. Follow-up after resolution
Hi [First name],
I wanted to check in now that [issue] is sorted - is everything working as it should? If anything still feels off, just reply and I’m on it. Thanks again for your patience while we fixed this.
Turning complaints into improvements
One complaint is a data point; ten of the same complaint is a roadmap. Tag complaint tickets by theme, review them monthly, and fix the root cause - a confusing screen, a missing help article, a slow process. The cheapest complaint to handle is the one that never gets raised again. (See our guide on reducing support ticket volume.)
Respond fast, own the problem, and be specific about the fix. Do that consistently and complaints stop being something to dread - they become the clearest signal you have of what to improve next.