Customer Complaint Response Examples: 25 Templates That Actually Work

Most complaint replies fail for the same reason: they explain before they acknowledge. The customer wants to know you understood what happened. Everything else comes second.

Below are twenty-five responses you can copy, covering delivery problems, refunds, billing, service quality, staff behaviour, repeat failures, public reviews and the awkward cases where the fault is not clearly yours. Each one notes when to use it and what to change. If you only read one section, read the next one: the structure underneath all twenty-five is what makes them work, and it is what lets you write the twenty-sixth yourself.

The five-part structure behind every good complaint response

Every template here follows the same shape. Learn the shape and you stop needing templates.

Two rules sit on top of it.

Specificity beats sympathy. "I am so sorry for any inconvenience caused" is weaker than "Your order was due Tuesday and it has not moved since Friday." The second proves you looked.

Never make the customer repeat themselves. If they gave you an order number, use it. If they described the fault, describe it back. A reply that asks for information they already sent reads as though nobody read the message.

Before you write: is this your fault?

This single question changes the wording of everything that follows, and getting it wrong is expensive in both directions.

• •Clearly your fault. Apologise plainly, once, early. Do not hedge it with "if". Do not explain before apologising.
• •Clearly not your fault. Empathise without accepting liability. "I understand how frustrating that is" is not an admission. "I am sorry we let you down" is.
• •Unclear. Acknowledge the experience, commit to finding out, give a date. Do not guess at fault in writing while you are still investigating, in either direction.

An apology is a statement about your conduct. Empathy is a statement about their experience. You can always offer the second. Offer the first only when it is true.

Delivery and fulfilment

Template 1 - Late delivery

Use when: the order has missed its promised date and you know where it is.

Hi [Name], your order [number] was due on [date] and it has not arrived. I am sorry. It is currently [status] and the carrier now expects it to reach you by [new date]. I have [refunded the shipping / added a credit] without you needing to ask. If it has not arrived by [date], reply to this message and I will [replace it / refund it in full] the same day.

Change: the new date must be one you believe. A second missed date costs more than the first.

Template 2 - Damaged product

Use when: the item arrived broken.

Hi [Name], thank you for sending the photos. That is not the condition anything should reach you in and I am sorry. A replacement is going out today on [service], arriving [date]. Please keep the damaged item until the new one arrives, then [return instructions / dispose of it, no need to return]. I have also passed the photos to our packing team because this is the kind of damage that usually points to how it was boxed.

Change: decide in advance whether you want the damaged item back. Asking for a return on a low-value item costs more than it saves and reads as distrust.

Template 3 - Wrong item received

Use when: they got something other than what they ordered.

Hi [Name], you ordered [correct item] and received [wrong item]. That is our mistake. The correct item is dispatched today and will reach you by [date]. A prepaid return label for the wrong item is attached, and there is no rush on it. You will not be charged twice at any point.

Change: send the replacement before the return arrives, not after. Making the customer wait on your logistics is what turns a mistake into a complaint.

Template 4 - Order never arrived

Use when: tracking says delivered and the customer says otherwise.

Hi [Name], tracking shows your order as delivered on [date] but you have not received it. I believe you. I am opening an investigation with [carrier] today, and I am not going to make you wait for its outcome: a replacement is going out [today / tomorrow] and will reach you by [date]. If the original turns up, keep it or send it back, whichever is easier.

Change: if your margin cannot absorb this, say what you can do instead, specifically. What you must not do is tell a customer their parcel was delivered when they are standing in their hallway saying it was not.

Template 5 - Partial or missing items

Use when: part of the order is missing.

Hi [Name], your order should have contained [full list] and [missing item] was not in the box. Sorry about that. It is being sent now, by [service], arriving [date]. You do not need to return anything. If anything else is missing or not right, tell me in one message and I will sort it all at once.

Change: that last sentence matters. A customer who has found one problem is often about to find another, and inviting it saves a second complaint.

Money

Template 6 - Refund request within policy

Use when: they are entitled to it. Do not slow this down.

Hi [Name], refund processed. [Amount] is on its way back to your [card / account] and usually shows within [number] working days, depending on your bank. You do not need to do anything else. If it has not appeared by [date], reply here and I will chase it.

Change: nothing. Resist the urge to ask why first. If you want the reason, ask after the refund is done, as a question they may ignore.

Template 7 - Refund request outside policy

Use when: they are asking for something the policy does not cover.

Hi [Name], I have looked at this properly. Our returns window is [period] and this order was placed on [date], which puts it outside it, so I cannot process a standard refund. What I can do is [specific alternative: credit, exchange, partial refund, repair]. If that does not work for you, tell me what would and I will see whether it is possible.

Change: name the specific alternative before they ask. A "no" with nothing after it reads as a door closing.

Template 8 - Billing error or overcharge

Use when: you charged the wrong amount.

Hi [Name], you are right, and I am sorry. You were charged [wrong amount] on [date] and the correct amount is [right amount]. The difference of [amount] has been refunded and should appear within [number] working days. The cause was [brief cause], and it has been corrected so it will not repeat on your account.

Change: billing complaints need a cause. Money errors frighten people, and "we have fixed it" without "here is what happened" does not settle it.

Template 9 - Double charge

Use when: the same payment went through twice.

Hi [Name], I can see both charges on [date], [amount] each. The second one was an error and it has been refunded in full. Depending on your bank it will either disappear from your statement or appear as a separate credit, usually within [number] working days. Nothing is outstanding on your side.

Change: tell them which of the two forms the reversal will take. People checking a statement for a refund that arrived as a pending-drop give up and complain again.

Template 10 - Cancellation that was not processed

Use when: they cancelled and were billed anyway.

Hi [Name], you cancelled on [date] and were still charged on [date]. That should not have happened and I am sorry. The charge of [amount] is refunded and the subscription is now fully cancelled, with nothing scheduled. You will get a confirmation email separately so you have it in writing.

Change: always send the separate written confirmation. This is the complaint customers most expect to have to make twice.

Product and service quality

Template 11 - Product not as described

Use when: the listing oversold it, or was unclear.

Hi [Name], you expected [what the listing implied] and received [what it actually is]. I can see why, reading the page back. You can return it for a full refund with the label attached, or keep it with a [amount] partial refund if it is still useful to you. Either way I am rewriting that description this week, so thank you for the prompt.

Change: only promise the rewrite if you will do it. If the listing was accurate and the customer misread it, use Template 19 instead.

Template 12 - Service quality complaint

Use when: the work was done badly.

Hi [Name], thank you for telling me rather than just not coming back. [Specific thing that went wrong] is below the standard we work to. Here is what I am doing: [specific action, with who and when]. I would like to [redo it / credit you / refund the portion affected]. Which would you prefer?

Change: ending with a choice beats imposing a remedy. Customers who pick their own resolution complain less about it afterwards.

Template 13 - Technical issue or outage

Use when: something broke and it affected them.

Hi [Name], [service] was unavailable between [time] and [time] on [date] and that affected your [specific impact]. Sorry. The cause was [plain-language cause] and it is resolved. [If applicable: your account has been credited for the affected period.] You can see the current status at [link], and I will write again if anything changes.

Change: plain language, not architecture. "A database upgrade ran longer than planned" is useful. "A cascading failure in our ingest layer" is not.

Template 14 - The same issue for the third time

Use when: this has happened before and they have told you before.

Hi [Name], this is the third time [issue] has affected you, on [date], [date] and now [date]. Fixing it again is not a good enough answer, so I am not going to offer that on its own. [Named person / I] now owns this specific problem for your account, [specific structural change] is in place, and I will check in with you on [date] whether or not it recurs. If it does happen again, [what you will do: refund, release, exit without penalty].

Change: this is the one complaint where a discount without a structural change makes things worse. It reads as being paid to go away.

Template 15 - Long wait for a reply

Use when: your own response time was the problem.

Hi [Name], you wrote on [date] and this is the first proper reply. That is too slow and the delay is on us, not on you. On the original issue: [answer, in full, right here]. [Brief, honest reason: a volume spike, a person out, a message routed wrongly.] I am not going to promise it will never happen again, but [specific change] is in place from today.

Change: answer the original question in the same message. An apology for being slow that still does not answer the question is a second slow reply.

People, and the awkward cases

Template 16 - Employee behaviour complaint

Use when: a member of staff is the subject.

Hi [Name], thank you for telling me about your experience with [team / location] on [date]. What you have described is not how we want anyone to be treated here. I am looking into it directly, and because it involves a member of staff I will not be sharing the outcome of that internally-handled part with you, which I hope you understand. What I can tell you is what changes for you: [specific action]. I would also like to [remedy], if you will let me.

Change: never name or discuss the employee's discipline with the customer. Confirm the complaint is taken seriously, then move to what the customer gets.

Template 17 - Earlier message never answered

Use when: they are chasing something that fell through a gap.

Hi [Name], your message of [date] was not answered and there is no good reason for that. Here is the answer: [answer]. I have also checked whether anything else of yours is sitting unanswered, and [there is nothing / there was one more, which I have now dealt with: detail].

Change: that second sentence, where you go and look, is the whole value of this reply.

Template 18 - When you are clearly at fault

Use when: there is nothing to investigate. You got it wrong.

Hi [Name], this one is straightforwardly our mistake. [What happened, in one sentence, without softening.] I am sorry. [Remedy, already done, not offered.] I am not going to explain the internal reason because it does not change anything for you, but it has been dealt with at our end.

Change: do the remedy before you send the message, then report it as done. An offer invites negotiation. A completed action ends the thread.

Template 19 - When fault is not clear

Use when: you genuinely do not know yet, or the evidence points both ways.

Hi [Name], thank you for the detail, it helps. I want to give you an accurate answer rather than a fast one, so I am checking [specific thing] and will come back to you by [date and time]. In the meantime, so you are not stuck: [interim measure]. If it turns out [outcome A], here is what happens; if [outcome B], here is what happens.

Change: setting out both outcomes in advance is what stops the second message being a fight. They already know the rules before the answer lands.

Template 20 - When the customer caused it

Use when: it was their error, and they are upset anyway.

Hi [Name], I have checked what happened. [Neutral description of the sequence, with no blame words: "the address entered at checkout was X" rather than "you entered the wrong address".] That means [consequence]. Here is what I can do: [specific help, even if limited]. For next time, [one practical tip].

Change: describe the sequence, not the person. "The delivery address on the order was..." and "You put the wrong address" contain the same fact and land completely differently.

Template 21 - Unreasonable or abusive messages

Use when: the demand is impossible, or the tone has crossed a line.

Hi [Name], I want to help and I will stay on this with you. What I can do is [specific options]. What I am not able to do is [the thing asked for], and that is not going to change however the conversation goes. [If the tone is the issue:] I would also ask that we keep this civil. I will keep replying as long as we can do that.

Change: be concrete about the limit and keep the door open. Most people who have been shouting calm down when they are met with a clear boundary rather than a wall of apology. For the full de-escalation method, see the angry-customer guide linked at the end.

Public channels need a different shape

A complaint in public is read by people who are not the complainant. That changes what the reply is for.

Template 22 - Public complaint on social media

[Name], that is not right and I would like to fix it. I have sent you a DM so we can get your order details without posting them publicly. Short version for anyone reading: [what happened] and [what we are doing about it].

Change: reply publicly once, move to private, then come back publicly when it is resolved. A thread that ends with "sent you a DM" and silence looks like a thread that was buried.

Template 23 - Complaint by WhatsApp

WhatsApp is read on a phone, usually within a minute. The structure holds, the format does not: no greeting paragraph, no sign-off, short lines.

Sorry about this [Name] - I can see order [number] is still showing as not dispatched.

>

Sending a replacement today, with you by [date].

>

Shipping refunded, nothing needed from you.

>

Anything else on the order not right?

Change: one idea per message bubble, but send them together rather than drip-feeding. Three notifications in a row reads as a system, not a person.

Template 24 - Negative public review

Thank you for the review, [Name]. [Specific acknowledgement of their actual point, not a generic line.] [What has changed since, or what you are doing.] If you would like me to look at your order directly, [contact route]. Either way, the feedback was useful.

Change: write it for the next reader, not the reviewer. They are the one deciding whether to buy. Never dispute the facts in public, even when you are right. The full approach to reviews and survey feedback is in the negative-feedback guide linked below.

Closing the loop

Template 25 - Follow-up after resolution

Almost nobody sends this, which is exactly why it works.

Hi [Name], following up on [issue] from [date]. [Remedy] should have reached you by now. Did it, and is everything working as it should? No need to reply if all is well, but if anything is still off I would rather hear it from you than not.

Change: send it three to seven days after the fix. Any sooner and the remedy has not landed; much later and it reads as a survey.

When to escalate, and how to hand over

Escalate when any of these is true: the customer has asked for a manager, it is the third contact on the same issue, money above your discretion limit is involved, there is a legal, safety or press dimension, or you can feel yourself getting defensive.

Handing over badly undoes the escalation. The receiving person needs the history so the customer does not retell it.

Hi [Name], I am bringing [Manager name] into this because [reason, framed as useful to them, not as passing the parcel]. They have the full history including [key facts], so you will not need to go over it again. You will hear from them by [date and time].

Then actually brief the manager. The single most common escalation failure is a customer repeating their story to a more senior person who has not read the thread.

How to adapt these to your business

Keep the structure, replace the vocabulary. Write how you speak. A reply that sounds like a legal department from a business that normally sounds like a person reads as a lawyer being brought in.

Lead with the specific detail. Their order number, the product, the date, the thing they said. One concrete detail in the first line does more than three sentences of sympathy.

Match their register. Casual message, casual reply. Formal complaint, formal reply. A one-line WhatsApp message does not need six paragraphs back.

Set your own compensation ladder before you need it, so the decision is not made under pressure: what you can refund without asking, what needs a manager, what is never offered. Write it down once.

Review your templates quarterly. A template that no longer matches your policy is worse than no template, because it gets sent confidently.

Turn your recurring answers into something customers can reach themselves

A pattern worth watching: the same complaint arriving repeatedly usually means an answer is missing somewhere earlier. If half of your late-delivery complaints would not exist with a clear dispatch-time page, the template is treating a symptom.

Once your team has agreed how it answers a recurring issue, that wording is worth keeping somewhere customers can find it, not only somewhere agents can paste it. You can turn your policies and recurring answers into a self-service page and edit every line before it goes anywhere, which is the point: a template is only useful if it says what you would actually say.

For everyday replies that are not complaints, order status, delivery windows, changing an order, see customer support reply templates.

Frequently asked questions

How quickly should I respond to a customer complaint?

Faster than the customer expects, which in practice means within a few working hours and in all cases within one working day. The precise number matters less than this: an acknowledgement within an hour saying "I have this, full answer by 2pm" buys you most of the goodwill of an immediate fix, and costs thirty seconds.

Should I always offer compensation?

No. Offer it when the fault is clearly yours and the customer lost something real: time, money or an occasion. Offer it automatically on your own repeat failures. Do not offer it as a reflex on first contact for a problem you can simply solve, because it trains customers to complain for credit and it signals that you expect the fix to be inadequate.

What if the complaint is unreasonable?

Separate the demand from the experience. The experience is usually real even when the demand is impossible. Acknowledge the first, be specific and unmovable about the second, and offer whatever genuine alternative exists. Template 21 covers the wording.

Should I apologise if it was not our fault?

Apologise for the experience, not for a fault you did not commit. "I am sorry you have been left waiting" is honest and costs nothing. "I am sorry we got this wrong" is an admission, and in a disputed or insured matter it can matter.

Should I respond to a complaint publicly or privately?

Both, in that order. One short public reply so other readers see it was handled, then move to private for the details, then a brief public close when it is resolved.

How many complaint templates does a small team actually need?

Five or six covering your most common issues, plus the structure in this article for everything else. A library of fifty nobody can find is slower than no library at all.