How to respond to a customer complaint: four replies to copy

A customer has just told you something went wrong. It came in by email this morning, or as a message on your business page, or it was said across the counter while two other people waited, and now it is sitting with you. Knowing how to respond to a customer complaint is mostly a matter of order: what you say first, what you find out before you offer anything, and what the reply has to contain so the customer stops wondering what happens next. This post gives that order, four worked email replies you can adapt (all invented, none from a real business), the things a reply must never do, and a log that turns complaints into fixes.

How to respond to a customer complaint: the order that works

The six steps below are the same whether the complaint came by email, by phone, in a message or in person. What changes is how fast the first one has to happen.

1. Acknowledge it within a time you have set

The acknowledgement and the answer are two different messages. The first says three things: you have the complaint, who is dealing with it, and when the customer will hear back. It does not say whose fault it was, because you do not know yet. "Thanks for telling us, I'm sorry you've had to write. I'm looking into it now and will come back to you by Thursday" is enough.

Set the deadline before you need it. Our advice for a small business: an emailed or messaged complaint gets its acknowledgement the same business day, and a complaint made by phone or in person gets it on the spot, which means listening to the end, repeating back what you heard and writing it down while the customer watches. Leave it unanswered for days and the next version of it you see may be public.

2. Find out what happened

Open the record before you open a reply window: the order, the invoice, the ticket, the booking, the delivery note. Start from the record, because a reply written from memory risks being wrong in a detail the customer will notice.

When the complaint is about a member of staff, hear that person first. A customer who says an employee was rude has a real grievance, and the employee may have a different account; you need both before you write a word to either. Whatever you find, the reply to the customer never names the employee as the problem (that is covered below), and the conversation with the employee stays private.

3. Decide what you can offer

There are three kinds of answer, and most replies contain one of them. Put it right: redo the job, replace the item, fix the fault. Make up for it: a refund, a credit, a waived fee. Explain: when the record shows no fault on your side, the answer is a clear account of what happened and what the customer can do now.

Decide before you write, and decide what the offer costs you. A credit you would give anyone who asked is a policy, so write it down and apply it the same way next time. A credit you cannot afford to repeat is a one-off, and the reply should not imply otherwise.

4. Reply with a specific next step and a date

Every reply needs one sentence that says what happens next and when. "We'll sort this out as soon as possible" leaves the customer waiting for a second email; "the refund of 49 dollars was issued this morning and will show on your statement within five business days" ends the matter. Our advice on timing: send this reply within three business days of the complaint, and if the investigation needs longer, send the date by which you will have the answer instead. Answer in the channel the complaint used: an email gets an email, a letter gets a letter, a client who called gets a call and a short email confirming what was agreed.

5. Follow up after the fix

A week or so after the fix, send one line: did it work, and is there anything else. This catches the replacement that never arrived and the credit that never showed, and it is the moment to turn a complainer into someone who speaks well of you. Set the date when you send the reply, so it does not depend on remembering.

6. Log it

Record the complaint, the type, what you offered and what changed afterwards. The log is where the second billing complaint in a month becomes a fix to your invoicing rather than another apology; the template is at the end of this post.

Four complaint types, with a reply for each

The four situations below are invented, and so are the businesses and the amounts. Each reply follows the order above: acknowledge, say what the record showed, say what you are doing, and give a date. A complaint about food, a damaged delivery or the quality of a physical product takes the shape of the product example: ask for what you need to see (a photo, the order number), replace or refund, and give the date. Before the examples, the decisions behind them.

A billing complaint: charged twice

A small software company's customer writes that they were billed twice for the month after updating their card. The record shows two charges of 49 dollars on the same day. There is nothing to investigate beyond that, so the reply is short:

Hi Dana, thanks for flagging this and I'm sorry about it. You're right: the card update on 2 October created a second charge of 49 dollars alongside the usual one. I've refunded the duplicate this morning; it should show on your statement within five business days, and I've checked that next month's billing is back to a single charge. If it isn't on your statement by 10 October, reply to this email and I'll chase it with our payment provider. Thanks again for telling us rather than leaving it.

A complaint about a price increase is a billing complaint with no error in it, which makes it harder. Our advice: say what changed and the date you announced it, and if you cannot show that the customer was told before the new price applied, honour the old price until the next renewal and say so. An increase the customer read about before it applied is a decision they made; one discovered on an invoice is a complaint.

A late or missed service

A cleaning company missed a booked visit; the customer came home to an uncleaned house before guests arrived. The record shows the booking was on the schedule and the team was sent elsewhere. The fault is yours, so the reply says so and leads with the fix:

Hi Mr Okafor, I'm sorry. Your visit on Tuesday was in our schedule and we sent the team to the wrong job; that is our mistake, not a mix-up on your side. I've booked a full clean for Thursday at 9am at no charge, and this week's invoice has been cancelled. If Thursday doesn't suit, reply with a day that does and I'll move it. I'll check in on Friday to make sure the visit went as it should.

A product or software problem

A customer of a small software business reports that the export feature stopped working after an update. You cannot see the fault from the complaint alone, so the honest reply asks for what you need, gives a workaround and still carries a date:

Hi Priya, thanks for reporting this, and sorry it's getting in the way of your week. I've reproduced a problem with CSV export on some accounts since Tuesday's update and the fix is being tested now; I expect it to be live by Monday and I'll email you when it is. In the meantime, exporting as a spreadsheet file still works from the same menu. So that I can confirm your account is covered by the fix, could you tell me which browser you're using and send a screenshot of the error? If Monday slips, you'll hear from me before then, not after.

A complaint that is wrong on the facts

A customer demands a refund, saying they were promised a 30-day money-back period. Your terms say 14 days, the signup page says 14 days, and the account is 23 days old. The reply states the record without arguing, offers what you can, and leaves a door open in case you are the one who is wrong:

Hi Sam, thanks for getting in touch, and I'm sorry this wasn't clearer at signup. I've checked, and the money-back period on your plan is 14 days; it's shown on the pricing page and in the confirmation email from 12 September, and your account is now at 23 days, so I can't issue a refund under it. What I can do: cancel the plan today so nothing further is charged, and keep your account open until the end of the paid month so you can export your data. If you saw 30 days written anywhere on our site, send me the page and I'll look at it again; if we got it wrong, I'll refund you.

That last sentence matters. If the customer is wrong, it costs you nothing; if they are right, it saves you from defending a mistake in public.

What a reply must never do

Five rules, and the first four are about tone and trust:

• Never blame. Not the customer, not a named employee, not "the system". The reply explains what happened and what you are doing; who was at fault is your business to sort out afterwards.
• Never promise what you cannot deliver. A date you miss is a second complaint. If you do not know when the fix will land, say when you will next update them.
• Never reveal another customer's details. "Another client had the same problem last week" is fine; a name, a company or an order number is a breach of that customer's trust, and a question for whatever privacy law applies where you trade.
• Never move a private complaint into public. Quoting a customer's email on your social media page, even to show how well you handled it, is something we advise against: a customer who finds their email on your page has no reason to write to you privately next time.
• Never offer anything in exchange for removing or changing a public review, and never threaten over one. Google's policy for user-contributed content on Maps lists offering incentives such as payment, discounts or free goods "in exchange for posting any review or revision or removal of a negative review" as prohibited, and the same page lists "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers" as not allowed (Google's policy page, read 2026-10-05). In the US, the Federal Trade Commission's rule on fake reviews and testimonials, announced on 14 August 2024 and in force 60 days after its Federal Register publication, bans incentives "conditioned on the writing of consumer reviews expressing a particular sentiment" and bars "unfounded or groundless legal threats, physical threats, intimidation" used "to prevent or remove" a review (FTC announcement, read 2026-10-05). Fix the problem and reply to the review; whether the customer edits it is theirs to decide.

None of this is legal advice. The rules above are stated as their publishers have them; if a complaint involves a legal claim, a regulator or a threat of action, ask a lawyer before you reply.

When a private complaint is about to become a public review

Some customers tell you they will post a review if this is not sorted. Treat it as information, not a threat: the person is giving you the chance to fix it privately first. The six steps above are the fix. Reply within your deadline, give the date, and follow up.

If a review appears anyway, answer it in public in the same order, shorter: thank them, say what you have done or are doing, and give a way to continue privately ("I've emailed you today with the refund confirmation"). A public reply is written for the next customer as much as for the one who wrote the review; what it shows them is how you behave when something goes wrong, which is the whole reason reviews matter to a business (why reviews are important for a business). Never ask the customer to take the review down as a condition of anything, and never argue the facts in the thread; if you believe the review breaks a platform's rules, the route is in can a business remove bad reviews.

If you are answering reviews on several sites, reputation and review management software collects them into one inbox and alerts you to new ones; for a business with a handful of reviews a month, a weekly check of each site does the same job for free.

A complaint log you can keep in a spreadsheet

One row per complaint, ten columns. The example row is invented.

Read the log once a month and count the Type column. One late job is a bad day; three in a month is a scheduling problem, and the fix is to the schedule, not to the apology. The Change made column is the easiest one to leave empty, and it is the column that stops the same complaint arriving next month. The log tells you what the customers who complained think; to hear from the ones who did not, pair it with a short survey (customer satisfaction survey questions).

What a good reply will not fix

A well-written reply does not rescue a product people dislike, a price the market will not pay, or a team too small for the bookings it takes. If the log shows the same type every month, the reply is the cost of not fixing the cause. Answering complaints well also takes time: budget for the investigation as well as the reply, and for the follow-up a week later. For a business with a few complaints a week, a shared inbox and the log are enough; once several people are answering and complaints are getting lost between them, help desk software gives each one a ticket, an owner and a deadline, at a per-agent price you should weigh against the volume.

The one thing to do this week

Set the three deadlines (acknowledge the same day, reply with a date within three business days, follow up a week after the fix), write them where the people who answer email can see them, and start the log with the next complaint that arrives. When a complaint closes well, that customer has just watched you handle a problem and is a fair person to ask for a review, and asking the right way is the subject of how to get more reviews.