Most complaint replies fail in the first sentence. The customer describes a problem, and the response opens with context: how the process normally works, how unusual this is, what the policy says. All of it may be true, and none of it answers the question the customer is actually asking, which is whether anyone understood what happened.
A complaint is not a request for information. It is a request for acknowledgement, a remedy, and some evidence that the same thing will not happen again. Templates help, but only once the shape of the reply is right, so the method comes first and the 12 templates follow.
iShort answer
Answer a complaint in four moves: acknowledge the problem in the customer's own words, confirm what you know and what you are still checking, correct it with a specific action and a date, then thank them and close the loop on that date. Everything else is variation. Price complaints are value complaints, so restate value and offer a real alternative instead of defending or discounting. Public complaints get a short public acknowledgement and a private resolution. Escalate rather than answer when there is a legal claim, a safety issue, a repeat of something already marked resolved, or a remedy larger than you can approve.
Four moves, in this order. Reordering them is what makes a well-intentioned reply land badly: explanation before acknowledgement reads as a defense, and a remedy without a date reads as a brush-off.
Acknowledge
Name the problem in the first sentence, in the customer's terms. No context, no policy, no preamble. This is the sentence that decides whether the rest gets read.
Confirm
State what you have verified and where you are still checking. Say 'I do not know yet' rather than guessing at a cause, because a wrong guess becomes the second complaint.
Correct
One specific action, one named owner, one date. Replace 'as soon as possible' with something the customer can hold you to, and only promise what you can approve.
Thank and close
Thank them for reporting it, say what changes because they did, and follow up on the promised date even when there is nothing new to report.
What a complaint response actually has to do
A complaint reply carries four jobs at once, and a reply that nails three of them still fails.
| The job | What it sounds like when it is missing |
|---|---|
| Prove the problem was understood | "Thanks for reaching out about your recent experience" |
| Say what is true, including the unflattering parts | "There may have been a slight delay on our end" |
| Commit to a remedy someone owns | "We will look into this as soon as possible" |
| Give the customer a reason to believe the next time is different | Nothing at all, which is the usual case |
The fourth job is the one most templates drop. A customer who gets a refund and no explanation has been paid off, not reassured, and the complaint that follows will go somewhere more public.
The A.C.T. Response Method
Acknowledge, Confirm, Correct, Thank. The initials collapse the two middle steps because they are one breath in practice: you say what you know, then say what you will do about it.
Acknowledge
The first sentence names the problem, in the customer's terms, with no lead-in. Compare:
| Instead of | Write |
|---|---|
| "Thank you for contacting us regarding your recent order." | "Your order arrived three weeks late, and the two emails you sent about it went unanswered." |
| "We are sorry to hear you had a less than ideal experience." | "You were charged twice for the same invoice, and the second charge is still on your statement." |
| "I understand your frustration." | "You have now explained this to three different people, and none of them fixed it." |
The right-hand column is uncomfortable to write, which is the point. It is also the sentence customers quote back when they later say the issue was handled well.
Confirm
State what you have verified and what you have not. The instinct under pressure is to supply a cause immediately, and a cause offered before it is checked becomes the next complaint when it turns out to be wrong.
"I can see the double charge on the 14th and I have confirmed it was not authorized by you. I do not yet know how it happened, and I will have that answer by Thursday" is a stronger reply than a confident, invented explanation.
Correct
One action, one owner, one date. "As soon as possible" is not a date, "we are working on it" is not an action, and "the team" is not an owner.
Thank and close the loop
Thank the customer for reporting it and say what changes because they did. Then follow up on the date you gave, even if the only thing to report is that nothing has moved. The follow-up that arrives with no news still proves someone is holding the thread.
Three checks before you write a word
Is this a complaint, or a question wearing a complaint's clothes?
- If the customer wants an outcome changed→Complaint. Use A.C.T.
- If the customer wants to know how something works→Answer the question first, then ask whether anything still needs fixing
Has this customer raised this before?
- If first time→Resolve it at first touch if you can
- If second time or later→Escalate. A repeat means the first fix did not hold, and repeating it will not work
Is anyone else watching?
- If private email, chat, or ticket→Write for one reader, with full detail
- If public review, social post, or forum thread→Write two replies: a short public one and a full private one
12 complaint response templates
Square brackets mark the parts that must be replaced. A template with an unedited bracket in it does more damage than no reply at all, and it happens often enough to be worth a proofread every time.
1. Price complaint
The most common complaint, and the one most often answered badly. A price complaint is nearly always a value complaint: the customer is not saying the number is wrong, they are saying they cannot see what it buys.
Hi [Name], That is a fair thing to raise, and it deserves a straight answer rather than a sales pitch. [Plan/product] is [price] because it includes [the two or three things that actually drive the cost, in outcome terms, not feature names]. For [type of customer], that is usually worth it because [specific outcome]. For [other type of customer], honestly, it is not. Based on what you have described, [one of the following]: - [Smaller plan] covers [what they said they needed] at [price], and you can move up later without redoing setup. - Annual billing brings it to [price] per month, which is [amount] less over a year. - If [use case] is the whole job, we are probably not the right fit at your budget, and I would rather say that now than have you discover it in month three. Which of those is closest to what you need? [Your name]
2. Shipping or delivery delay
Hi [Name], Your order [number] was due on [promised date] and it has not arrived. That is [number] days late and we did not tell you it was slipping, which is the part I am sorriest about. Here is where it actually is: [current status, in plain terms]. The realistic delivery date is [date], not [vague reassurance]. I have [specific action taken: refunded the shipping, upgraded the remaining leg, sent a replacement]. If it has not arrived by [date], reply to this email and I will [specific remedy] with no further questions. Thank you for chasing this rather than just writing us off. [Your name]
3. Product defect or damage
Hi [Name], The [product] you received on [date] is [specific fault they described]. It should not have left us in that condition. A replacement is going out today and will reach you by [date]; the tracking number is [number]. You do not need to return the damaged one, [or: a prepaid return label is attached and nothing happens until you use it]. I have passed the photos to [team/person] because [reason it matters: a batch issue, a packaging problem]. If the replacement shows the same fault, tell me and we will stop sending them and sort out a refund instead. [Your name]
4. Service failure and a missed commitment
Hi [Name], On [date] we told you [commitment]. That did not happen, and you had to be the one to notice. What went wrong: [honest one-line cause, or "I am still confirming exactly where this dropped, and I will tell you by [date]"]. What happens now: [action], owned by [name], done by [date]. I will write to you on [date] either way, including if the answer is that it has slipped again. [Your name]
5. Billing error or a duplicate charge
Hi [Name], You were charged [amount] twice on [date]. I have confirmed the second charge and it was not authorized by you. The refund for [amount] was issued at [time] and reference [number]. Depending on your bank it will show between [date] and [date]; if it has not landed by [date], send me that reference and I will chase it from our side rather than asking you to talk to your bank. I am still establishing how the duplicate happened and will tell you when I know. [Your name]
6. It does not do what the customer expected
Hi [Name], You bought [product] expecting it to [what they expected], and it does not do that. If that came from something we wrote or said, that is on us to fix. To be straight about the current state: [what it does do], and [what it does not do, plainly]. [Feature] is [on the roadmap with no date / not something we plan to build], and I am not going to imply otherwise to keep the sale. Given that, [refund offer / alternative configuration / workaround that genuinely works]. Tell me which you would prefer. I have also flagged [the specific page or claim] to [team] because if it read that way to you it is reading that way to others. [Your name]
7. The same problem, again
Hi [Name], This is the second time [problem] has hit you, after we told you on [date] it was resolved. It clearly was not, and repeating the same fix would waste your time. I have escalated this to [name/role], who owns [system/area], and it is no longer being handled as a routine ticket. [Name] will contact you directly by [date]. In the meantime [interim measure so they are not stuck]. You should not have to chase this a third time, so if you have not heard from [name] by [date], reply here and I will. [Your name]
8. A complaint about a staff member
Hi [Name], Thank you for telling me about the conversation on [date]. Being spoken to that way when you were already dealing with [issue] is not acceptable, and I am not going to explain it away. I am handling this with [person/their manager] directly. Out of fairness to a colleague I will not share the outcome of that, and I hope that makes sense; it is the same discretion you would expect if it were your employer. What I can do is make sure the original issue actually gets fixed: [status and next step, with a date]. From here, [name] is your point of contact and you will not be routed back to the same conversation. [Your name]
9. A refund request outside policy
Hi [Name], You are asking for a refund on [purchase] from [date], which is outside our [length] refund window. I am [approving it anyway / not able to approve it], and here is the honest reason: [reason]. [If approving] The refund of [amount] is processed and will show by [date]. The policy exists for [reason], and this situation is different because [reason]. [If declining] What I can do instead is [genuine alternative: credit, extension, swap, partial]. If none of those work for you, [escalation route], and I will make sure it is looked at rather than closed. [Your name]
10. A public complaint on social media
Two replies, not one. The public reply is written for the people reading over the complainant's shoulder.
That should not have happened, and I would like to fix it rather than explain it. I have sent you a DM with a direct line to me. [First name], [role].
Hi [Name], [First name] here, following up from [platform]. You posted that [problem, in their words]. Give me [the one piece of information needed: order number, account email] and I will have an answer for you today rather than routing you through the queue. For what it is worth, you were right to post it. Nothing moved when you emailed on [date], and that is a failure on our side, not a reason to be annoyed with you. [Your name]
11. The customer is angry and also mistaken
Hi [Name], You have spent [time] on something that should have taken minutes, and that part is completely fair. On what happened: [the actual sequence, stated neutrally, with dates]. I am not saying this to score a point. I am saying it because the fix is different depending on which it is. Given that, the thing that will actually solve it is [action]. I have started it and it will be done by [date]. Where we did go wrong is [any genuine failing, however small: the page was unclear, the confirmation email did not send]. I have raised [that] with [team]. [Your name]
The concession at the end matters. A reply that corrects the customer on every point, with nothing conceded, is technically accurate and reliably escalates. If the facts genuinely leave nothing to concede, concede the experience: the situation was confusing, and it was confusing on your surface.
12. A complaint with no clear ask
Hi [Name], Something has clearly gone badly wrong and I would rather fix it than send you a form asking you to categorize it. From your account I can see [what you can observe: a failed payment, three tickets in a week, an order stuck at a status]. Is it that, or something else? If it is easier, reply with one line and I will take it from there. If you would rather talk, [booking link or phone route] and pick any slot. [Your name]
The channel changes the shape, not the substance
A.C.T. holds everywhere. What changes is length, the number of audiences, and how much detail is safe to include.
| Scenario | Best pick | Why |
|---|---|---|
| Full A.C.T. | One reader, no character limit, and a written record both sides keep. Use the whole method and put the date in its own line. | |
| Live chat | Acknowledge instantly, resolve second | Silence reads as absence. Acknowledge in one line while you look, then work the rest of the method as you go. |
| Public review (Google, G2, app stores) | Short public reply | Written for future readers, not the reviewer. Acknowledge, state the fix, offer a direct route, stop. Never mention account details. |
| Social media | Public acknowledgement, private resolution | Reply publicly within the hour so the thread does not run unanswered, and move specifics to DM. |
| Phone | A.C.T. out loud, then in writing | Nothing is on the record until it is written down. Send the summary and the date by email while still on the call. |
For review and survey responses specifically, where the audience is future customers rather than the person who wrote it, responding to negative customer feedback works differently enough to be worth its own playbook.
When to resolve and when to escalate
Resolving at first touch is usually right, and there are six cases where it is not.
| Escalate when | Because |
|---|---|
| There is a legal or regulatory claim | An improvised reply becomes evidence |
| Safety, harm, or a health issue is involved | The remedy is not a service decision |
| A data breach or privacy request is mentioned | Statutory deadlines start on receipt |
| The customer threatens to publicize | It needs a coordinated response, not a fast one |
| The same problem has already been marked resolved | The first fix did not hold; repeating it wastes the customer's time |
| The remedy is bigger than the responder can approve | Promising it and withdrawing it turns one complaint into two |
Escalation is not an admission that the first responder failed. The failure mode is the opposite: a responder who improvises a promise the business then walks back.
When the complaint carries real anger rather than a factual dispute, the sequencing changes and the scripts change with it. That is covered in de-escalating an angry customer.
What happens after you hit send
Three habits separate teams whose complaint volume falls from teams whose volume stays flat.
- Follow up on the date you gave, including when there is no news. The unprompted update is the single cheapest trust-building action available.
- Tag the cause, not the channel. "Email" is not a category. "Shipping estimate wrong at checkout" is, and five of those in a month is a product fix rather than five service tickets.
- Feed the answer back into your help content. Every complaint that could have been prevented by a clearer page is a permanent reduction in future volume, and it is the same content a chatbot retrieves from.
Publishing your response benchmarks is optional. Measuring them is not, and the number should come from your own resolution data rather than a figure lifted from an industry report.
Automating the first touch without automating the apology
The gap between a complaint arriving and a human seeing it is where most damage happens. That gap is worth automating. The apology is not.
An AI chatbot for customer service trained on your own help content, policies, and past resolutions handles the useful part of the first touch: acknowledging within seconds, answering the routine questions that turn out not to be complaints at all, and collecting the order number and context the human will need. SiteGPT trains on 12 or more content sources, including help centers, so the bot answers from the same policies your team quotes rather than a separately maintained script.
The line to hold is where the bot stops. It should not negotiate a remedy, concede fault, or try to resolve a complaint carrying anger, legal language, or a safety issue. Those need a human, quickly, which is why easy escalation to a person matters more on complaint traffic than on any other kind. SiteGPT escalates on demand when the customer asks for a human and notifies the team, on every plan.
For drafting individual replies rather than automating the first touch, the free AI reply generator and AI email response generator take a complaint and return a draft you then edit into something true.
Frequently asked questions
What is the best way to start a response to a customer complaint?
Name the problem in the first sentence, in the customer's own words rather than a softened version. That opening tells the customer they were understood, which is what they are checking for. Openings that lead with context, policy, or an apology template read as a defense.
Should you apologize even if the complaint is not your fault?
Apologize for the experience, not for a fault you did not commit. "I am sorry this turned into a week of chasing us" is true regardless of cause. Hedged apologies of the "sorry you feel that way" shape read as blame-shifting and reliably escalate.
How fast should you respond to a customer complaint?
Fast enough that the customer is not left wondering whether the message arrived, which usually means acknowledging on the same working day even when the resolution takes longer. Set the target from your own resolution data, not from an industry benchmark.
How do you respond to a customer complaining about price?
Do not defend it, and do not immediately discount it. Restate what the price covers in terms of the outcome the customer wanted, then offer a genuine alternative. If the product is not a fit at their budget, say so.
Should you respond to complaints publicly on social media?
Yes, briefly, then move the detail to a private channel. The public reply exists for the people reading over the complainant's shoulder, so keep it short and never include account details.
When should a complaint be escalated instead of answered?
When there is a legal or regulatory claim, a safety issue, a privacy request, a threat to publicize, a repeat of something already marked resolved, or a remedy larger than the responder can approve.
Can a chatbot handle customer complaints?
It can handle the first touch: acknowledging instantly, answering the routine questions that are not really complaints, and collecting context for the human. It should not negotiate remedies, concede fault, or handle complaints carrying anger or legal language.