How to Respond to Customer Complaints: Examples, Templates & 5-Step Framework (2026)

Most unhappy customers never say a word. Only 4% actually complain to your company. The rest leave quietly -- and tell everyone they know.

Responding to customer complaints well means acknowledging the issue, showing empathy, and offering a clear solution -- ideally within 24 hours. When a customer tells you what went wrong, you get a chance to fix it and keep their business. Getting this right is a core part of providing great customer support. According to Salesforce, 78% of customers stick with a company that handles their issues well.

Below you'll find 10 email templates for the most common complaint scenarios. Copy them, customize them, and send them. After the templates, we cover the key steps and best practices for handling any complaint.

10 Email Templates for Customer Complaints

1. Acknowledging a Complaint

Use this when a customer reports an issue and you need time to investigate.

Dear [Name],

Thank you for reaching out. I am sorry about your experience, and I want you to know we take this seriously.

I have forwarded your message to our [relevant team]. We are actively looking into this and will get back to you within [time frame].

If you have any questions in the meantime, reply to this email or call us at [phone number].

Best regards,

[Your Name]

[Your Title], [Company Name]

2. Delivery Delay

Use this when a package hasn't arrived on time.

Dear [Name],

I am sorry your order has not arrived yet. That must be frustrating.

I checked your tracking status, and your package is currently listed as [status]. Here is your tracking number: [tracking number]. You can check it here: [tracking link]

We expect delivery within [number] business days. If it does not arrive by then, please contact me directly and I will make it right.

Apologies again for the delay.

Best,

[Your Name]

[Your Title], [Company Name]

3. Wrong Item Received

Use this when a customer gets the wrong product.

Dear [Name],

I am so sorry we sent you the wrong item. That is completely our mistake.

Here is what we will do to fix this:

1. We are shipping the correct item today with express delivery at no extra cost.
2. You do not need to return the wrong item. Please keep it or donate it.

You will receive a shipping confirmation within the next few hours.

Sorry again for the mix-up. Let me know if there is anything else I can help with.

Best,

[Your Name]

[Your Title], [Company Name]

4. Billing or Overcharge Complaint

Use this when a customer spots a billing error or unexpected charge.

Dear [Name],

Thank you for letting us know about this billing issue. You are right -- you should not have been charged [amount/description].

I have processed a full refund of [amount]. It should appear in your account within [number] business days.

We have also updated your account to prevent this from happening again. If you notice anything else, please do not hesitate to reach out.

Best regards,

[Your Name]

[Your Title], [Company Name]

5. Dissatisfied Customer (General Complaint)

Use this when a customer is unhappy but hasn't described a specific issue.

Dear [Name],

Thank you for sharing your feedback. I am sorry we have not met your expectations.

We have been proud to serve you for [time period], and we want to make things right.

Could you share a few more details about what went wrong? You can reply to this email or call us at [phone number]. The more we understand, the faster we can fix it.

Your satisfaction matters to us, and we appreciate the chance to improve.

Best regards,

[Your Name]

[Your Title], [Company Name]

6. Angry Customer

Use this when a customer is clearly upset and frustrated. Stay calm, acknowledge their feelings, and avoid being defensive. For more on this, see our guide to dealing with difficult customers.

Dear [Name],

I hear you, and I am truly sorry. Your experience is not what we stand for.

I understand your frustration and I want to help. We would love the chance to make this right. Here is what I can do right now: [specific action or offer].

If you would prefer a different solution, I am open to that too. Please let me know what works best for you.

We value your business and want to earn back your trust.

Best,

[Your Name]

[Your Title], [Company Name]

7. Technical Issue or Software Bug

Use this when a customer reports a technical problem with your product.

Dear [Name],

I am sorry you are dealing with this. Technical issues like this should not happen, and I appreciate you reporting it.

Our team found the root cause: [brief explanation]. We have already [action taken, e.g., deployed a fix / started working on a fix]. You should see normal performance within [time frame].

As a gesture of goodwill, I have [credited your account / extended your trial / refunded this month's charge].

Please let me know if you experience any other issues. Thank you for your patience.

Sincerely,

[Your Name]

[Your Title], [Company Name]

8. Poor Service from an Employee

Use this when a customer complains about rude or unhelpful staff.

Dear [Name],

I am sorry you had that experience. That is not the level of service we expect from our team, and I take full responsibility.

I have personally reviewed your case and spoken with the team member involved. We are using your feedback to improve our training so this does not happen again.

I would like to make it up to you. [Offer: discount, free service, personal follow-up call, etc.]. Please let me know if that works for you.

Thank you for giving us the chance to do better.

Best regards,

[Your Name]

[Your Title], [Company Name]

9. Social Media Complaint

Use this when a customer posts a complaint on social media. Respond publicly first, then move the conversation to a private channel. Our guide on using social media for customer support covers this approach in depth.

Public reply:

Hi [Name], I am sorry to hear about your experience. That is not the standard we hold ourselves to. I have sent you a DM so we can get this sorted out right away.

Follow-up DM or email:

Dear [Name],

Thank you for bringing this to our attention. I want to personally make sure we resolve this for you.

Could you share your order number (or account details) so I can look into this? I will follow up within [time frame] with a solution.

Best,

[Your Name]

[Your Title], [Company Name]

10. Follow-Up After Resolution

Use this after you have resolved a complaint. It shows you care beyond the fix.

Dear [Name],

I wanted to check in and make sure everything is working well after [describe the fix].

If you run into any other issues, please reach out. We are always here to help.

Thank you again for your patience. We truly appreciate your business.

Best regards,

[Your Name]

[Your Title], [Company Name]

7 customer complaint examples (with solutions)

The email templates above give you the language. These seven scenarios give you the full picture — the complaint as the customer wrote it, what went wrong on your side, the response that worked, the resolution, and the outcome. Use them as a reference when a similar situation lands in your inbox.

Example 1: Delivery delay with no communication

The complaint (paraphrased from a customer email):

"I ordered the standing desk on March 3rd with 5-day delivery. It is now March 19th. No one has emailed me, no one has updated the tracker, and the chatbot keeps telling me my order is 'on the way'. I have a meeting room sitting empty. I want to know where it is or I want a refund."

What went wrong: The carrier missed the original pickup window. Operations knew but did not pass the information to the customer.

The response that worked: A human (not the chatbot) emailed back within two hours acknowledging the gap, named what went wrong, gave the new ETA with the carrier reference, refunded the delivery fee proactively, and offered a small credit for the inconvenience.

The resolution: Desk arrived three days later. The proactive refund and credit cost about £40. The customer left a 5-star review and ordered an office chair two weeks later.

The lesson: Customers tolerate delays. They do not tolerate silence. Naming what went wrong out loud is more powerful than any "we apologise for any inconvenience" template.

Example 2: Billing error — duplicate charge

The complaint:

"You charged my card twice this month for the same subscription. £39 each time. I expect this fixed today and an explanation of how it happened."

What went wrong: A bug in the payment processor retry logic charged the card a second time when the first charge appeared to fail but actually succeeded.

The response that worked: Immediate refund of the duplicate charge before any back-and-forth. Email explaining the specific bug, naming the team that fixed it, and confirming the customer's next bill would be £0 since they had effectively paid two months.

The resolution: Refund processed the same day. Free month applied. Customer stayed and upgraded to the annual plan four months later.

The lesson: With billing errors, refund first and explain second. The longer the money sits in your account, the more it feels like a fight.

Example 3: Product not as advertised

The complaint:

"Your marketing page says the integration syncs in real time. I just sat in front of a customer waiting nine minutes for data to appear. That is not real time. I feel mis-sold."

What went wrong: The marketing page overstated the sync frequency. The real refresh rate was every 10 minutes. Engineering had pushed back on the language; marketing had won.

The response that worked: Acknowledged the marketing language was wrong (not a fit issue). Confirmed the marketing team would update the page that week. Offered a one-month credit. Followed up two weeks later confirming the marketing page now reflected reality.

The resolution: Customer kept the account but downgraded to a lower tier. Two years later they upgraded again when a different feature shipped.

The lesson: When marketing oversold, own it explicitly. "We described that wrong" beats "let me explain what we meant" every time.

Example 4: Long hold time and rude agent

The complaint:

"I waited 47 minutes on hold and the agent who picked up sighed audibly. I have been a customer for six years. This is unacceptable."

What went wrong: A scheduling error left the queue understaffed. The agent who answered was on their third double shift that week.

The response that worked: A senior manager called the customer directly within 24 hours, did not make excuses for the agent, named the staffing issue, explained what was being done to fix it, and asked the customer what would feel right as a remedy.

The resolution: Customer asked for nothing. Said "I just wanted someone to listen." The manager sent a handwritten thank-you note a week later.

The lesson: Sometimes the resolution is being heard, not getting something back. Ask what would feel right. Customers often want less than you would offer.

Example 5: Service downtime affecting business

The complaint:

"Your system was down for four hours yesterday. We had 60 customer calls we could not log. I am losing trust. What is the SLA credit and what is your plan?"

What went wrong: A failed deploy caused a database lock that took four hours to resolve.

The response that worked: A detailed post-mortem email naming the root cause, the timeline, what was fixed, what was changing on the deploy process. SLA credit applied automatically without the customer having to ask. A dedicated 30-minute call offered with the head of engineering.

The resolution: Customer accepted the post-mortem, declined the call, renewed at the next cycle.

The lesson: Treat downtime like an incident, not a complaint. The customer wants to know it will not happen again — and they want enough technical detail to believe you.

Example 6: Returned product still charged

The complaint:

"I returned the printer last month using your prepaid label. UPS confirms delivery on April 4. I am still being charged the monthly fee. This is the second time I am writing about this."

What went wrong: The return tracking system did not auto-trigger the cancellation. The first email reached a queue that had no SLA on it.

The response that worked: The reply named the specific failure — the customer was right, the second-email gap was on the team — refunded all charges since the return date, and added a routing rule so any email containing a return tracking number jumped the queue.

The resolution: Full refund within 24 hours. Customer left a measured review noting it took two emails but that the second response was good.

The lesson: When the customer was right the first time and had to escalate, name that explicitly. Resist the urge to defend the original response. Repeat customers paying for a service they returned is a special category of trust damage.

Example 7: Onboarding friction (new customer)

The complaint:

"I just signed up two days ago. I cannot find the export function. Your help docs say it is under Settings but mine does not have it. I am about to give up."

What went wrong: The customer was on a trial tier that did not include export. The product UI did not say so; it just hid the option.

The response that worked: A reply within 90 minutes acknowledging the docs and the UI gave conflicting signals, naming the tier difference, offering to enable export for the rest of the trial as a goodwill gesture, and sending a calendar link for a 15-minute setup call.

The resolution: Customer took the call, converted to a paid plan, became a reference customer six months later.

The lesson: Onboarding complaints are gifts. The customer is still deciding. Fast, generous responses at this stage cost almost nothing and pay back enormously.

What every good complaint response has in common

Across the seven examples above, the same pattern shows up:

1. Reply fast. Within 24 hours for an email, the same day where possible.
2. Name the specific thing that went wrong — not "any inconvenience".
3. Lead with the resolution, not the explanation. Refund first, explain second.
4. Use the customer's own words back to them to show you actually read it.
5. Offer something concrete — a refund, a credit, a fix, a follow-up timeline.
6. Follow up once the issue is resolved to confirm and to invite further feedback.

The five-step framework below codifies this pattern into a checklist you can run on any incoming complaint.

5 Steps to Handle Any Customer Complaint

No matter the situation, these five steps work every time.

Step 1: Listen and Acknowledge

Let the customer explain the problem without interrupting. Then confirm you heard them. A simple "I understand why that is frustrating" goes a long way.

Step 2: Apologize Sincerely

Say sorry and mean it. Don't add qualifiers like "I am sorry if you feel that way." Own the mistake. According to a Nottingham School of Economics study, 45% of customers withdrew negative reviews after receiving a genuine apology. For more templates, see our apology email templates.

Step 3: Investigate the Issue

Dig into what happened. Ask clarifying questions if needed. The customer wants to know you are taking their problem seriously, not brushing it off.

Step 4: Offer a Solution

Give the customer clear next steps. If possible, offer options so they feel in control. Be specific about timelines -- say "within 2 business days," not "soon."

Step 5: Follow Up

Circle back after the fix. A quick email asking "Is everything working well now?" turns a negative experience into a lasting positive impression. This is how you build real customer loyalty. If your team handles volume, automated follow-up emails can send these check-ins on a schedule so no resolved ticket goes without a follow-up.

The Feel, Felt, Found Framework

This is one of the most effective ways to show empathy in a complaint response. Here's how it works:

• Feel: "I understand how you feel about this situation."
• Felt: "Other customers have felt the same way when this happened."
• Found: "What they found was that [solution] resolved the issue completely."

Example in action:

"I understand how frustrating it is to receive the wrong item. Other customers have felt the same way. What they found is that our express replacement process got the right product to them within 48 hours -- and that is exactly what I have set up for you."

This framework works because it validates the customer's emotions, normalizes their experience, and then redirects toward a positive outcome.

Best Practices for Complaint Responses

Respond Fast

Speed matters. According to Harvard Business Review, customers whose complaints are handled in under 5 minutes spend more on future purchases. Even if you don't have a full answer yet, send a quick acknowledgment.

Keep It Personal

Use the customer's name. Reference their specific issue. Nobody wants a response that feels copied and pasted, even if it starts from a template. Our guide on writing effective support emails covers this in detail.

Take Ownership

Never blame the customer or deflect responsibility. Phrases like "our system" or "an error on our end" build trust. Phrases like "you should have" destroy it.

Offer Real Solutions

A vague "we'll look into it" isn't enough. Tell the customer exactly what you will do, when they can expect results, and who to contact if the problem continues. When a refund or replacement isn't possible, offer store credit or a discount on their next purchase.

Use the Right Tools

A shared inbox helps your team collaborate on complaint responses. You can draft replies, get feedback from teammates, and make sure no complaint slips through the cracks. For faster responses, try using canned response templates as starting points.

Train Your Team

Make sure every team member knows how to handle complaints with empathy and confidence. Role-playing difficult scenarios helps your handle customer complaints for real situations. Mastering the number one customer service skill gives your team the foundation to de-escalate any complaint.

Learn from Every Complaint

Track complaint patterns. If you see the same issue three times, fix the root cause. Use customer feedback surveys to catch problems early before they turn into complaints. And when complaints go public, learn how to respond to negative reviews professionally.

How to End a Complaint Response Email

The sign-off carries more weight in a complaint reply than in any other support email. A weak ending makes the rest of the response feel hollow; the right ending leaves the customer feeling heard.

Three rules for ending a complaint email well:

1. Reaffirm the next step. Close with what you have committed to (e.g. "I will follow up with the resolution by Friday") so the customer leaves the message with a clear expectation.
2. Offer a direct channel. Give the customer one specific way to reach you back — your direct email or a reply-to address — rather than a generic "contact support" pointer.
3. Keep it human. Use the customer's name, sign with your own first name, and skip corporate boilerplate.

Sign-off templates for complaint responses

Use one of these closings instead of a generic "Best regards":

Standard sign-off (most situations):

Thanks again for letting us know, [Customer Name]. I'll be in touch by [date] with an update. If anything else comes up in the meantime, just reply to this email.

[Your Name]

When the customer is still upset:

I know this hasn't been easy, [Customer Name]. I appreciate your patience while we work through it. You can reach me directly at [email] if you need anything.

[Your Name]

When you have already resolved the issue:

Glad we could sort this out, [Customer Name]. If you notice anything else, please reply to this thread so we can keep the history in one place.

[Your Name]

When the resolution will take time:

Thanks for bearing with us, [Customer Name]. I'll send the next update on [specific date]. If you would rather hear about progress sooner, let me know and I will check in more often.

[Your Name]

What to avoid in a complaint email closing

• Generic auto-closures like "Have a great day!" — they feel dismissive after a complaint
• Sign-offs that promise nothing like "Let me know if I can help" — say what you will do, not what they could ask for
• Closing with an apology — the apology belongs in the body, not the sign-off, otherwise the email ends on a negative note
• No name in the signature — a faceless reply makes the customer feel like a ticket number

Complaint Response Email Subject Line Best Practices

The subject line decides whether a stressed-out customer opens your reply at all. The wrong subject line lands the email in their spam folder or gets ignored; the right one signals "this is the answer you were waiting for" before they even click.

Three guidelines for complaint response subject lines:

1. Lead with the resolution status, not the complaint topic. "Re: Booking #2026-1234 — resolved" beats "Re: Your complaint".
2. Keep it under 50 characters so the full subject is visible on mobile.
3. Match the original thread subject with a clear status prefix so the customer recognises the conversation.

Subject line templates by scenario

Scenario	Subject line template	Example
Acknowledgment (no fix yet)	Re: [Original subject] — investigating	Re: Booking issue at Marina Suites — investigating
Resolution offered	Re: [Original subject] — resolved	Re: Duplicate charge on order #4582 — resolved
Refund processed	Re: [Original subject] — refund issued	Re: Cancellation request — refund issued
Follow-up after fix	Following up on [Original subject]	Following up on your stay at Marina Suites
Escalation needed	Re: [Original subject] — escalating to [team]	Re: Booking issue — escalating to operations

Hospitality and hotel complaint response subject lines

For hotels, restaurants, B&Bs, and other hospitality businesses, complaint emails usually concern a specific stay, booking, or visit. The subject line should anchor on that context:

• Lead with the booking reference: Re: Booking 2026-1234 — apology and refund lands better than Re: Your complaint about our hotel.
• Name the property in multi-location chains: Re: Marina Suites stay (Booking 2026-1234) — resolution removes ambiguity if the chain has 12 properties.
• Avoid the word "complaint" in the subject — many email clients flag it. "Concerns about your stay" or just the booking reference is enough.

Hospitality subject line examples by complaint type:

Complaint type	Subject line
Room condition	Re: Booking #2026-1234 — room concerns and next steps
Service issue	Re: Booking #2026-1234 — apology and resolution
Billing dispute	Re: Charge for stay 2026-09-14 — refund processed
Noise/disturbance	Re: Booking #2026-1234 — compensation offer
Booking error	Re: Reservation 2026-1234 — corrected and confirmed

For hotels specifically, a personalised sign-off from the General Manager (rather than "Customer Service") often de-escalates the complaint further. The subject + sender combination signals seniority and ownership.

Common Issues to Address in Complaint Emails

Most customer complaints fall into one of five categories. A complaint response that misses the customer's actual issue feels generic and makes the situation worse. Use the categories below to make sure you have addressed what the customer actually wrote about.

1. The original problem itself

The thing the customer complained about — late delivery, wrong product, billing error, downtime. Acknowledge it specifically in the first sentence (not generically) so the customer knows you read their message.

2. The impact on the customer

How the problem affected them — missed an event because the package was late, charged twice while their card was already tight, downtime caused them to miss a customer of their own. Acknowledging the downstream impact is what separates "we are sorry this happened" from "we understand why this matters to you".

3. The communication gap

Many complaints are actually about silence rather than the original issue. The package was late and no one told them. Their email got no reply for two days. A frustrated customer who got a quick acknowledgment usually stays frustrated about the original issue only; a customer who got silence is frustrated about both.

4. The fix

What you are going to do, by when, and what they need to do (if anything) in the meantime. Vague fix language ("we will look into it") is the most common complaint-response mistake.

5. The prevention

For repeat customers or high-value relationships, naming the systemic fix matters as much as the immediate one. "We have changed our notification rules so this does not happen again" signals you have taken the complaint seriously beyond the individual case.

Skipping any one of these five categories leaves the customer feeling unheard. The shortest effective complaint response covers all five in 5–8 sentences.

Final Thoughts

Every complaint is a chance to keep a customer. Respond quickly, take ownership, and offer a clear solution. The templates above give you a strong starting point -- but always personalize them to fit each customer's situation. For more proven advice, browse our best customer service articles collection.

If your team handles complaints by email, the right tools make a big difference. SupportBee gives you a shared inbox for organizing and collaborating on support tickets, a customer portal where customers can track their requests, and a knowledge base that helps customers find answers on their own.

Start your free trial and see how SupportBee helps your team respond to complaints faster.

Frequently Asked Questions

How quickly should I respond to a customer complaint?

As fast as possible. Send an acknowledgment within the hour, even if you need more time to investigate. Fast responses show customers you take their concerns seriously.

What are the 5 steps to handle customer complaints?

1. Listen and acknowledge the issue.
2. Apologize sincerely.
3. Investigate what went wrong.
4. Offer a clear solution with a timeline.
5. Follow up after resolving the issue.

What should I avoid when responding to a complaint?

Avoid blaming the customer, using passive language, making excuses, or giving vague promises. Be direct, take responsibility, and provide specific next steps.

What tools help manage customer complaints?

A ticket system like SupportBee helps teams organize, prioritize, and track complaint tickets. Features like shared inboxes and internal comments let your team collaborate behind the scenes before sending a response.