How to apologize to a customer in writing

A customer apology letter works when it names the exact problem, takes clear responsibility, and explains what you're doing differently. Generic language and vague regret make it worse. The reader already knows something went wrong; they're reading to see if you understand what it was and whether you're serious about fixing it.

The four-part structure

Acknowledge the specific issue. Not "we had a problem" but "your order arrived three weeks late." Name the date, the order number, the service that failed. This proves you know what happened and that you're not sending a form letter to everyone. It also prevents the customer from wondering if you understand their particular situation.

Take responsibility without excuses. Say what you did wrong. Do not explain why it happened, do not blame a vendor or a system, do not soften it with "unfortunately" or "we regret that." Those words move the focus away from your failure and onto circumstances. The customer does not care about your circumstances. They care that you broke something. Own it cleanly.

Explain the fix. What are you doing about it right now, and what are you doing so it does not happen again? The immediate action matters (refund, replacement, credit, whatever is appropriate). The system change matters more. If you can only say "we'll try harder," you have not thought this through. Be specific about the process change, the person assigned, the timeline, or the tool you're implementing. This is where the letter stops being an apology and starts being a commitment.

Offer something forward-looking. Not a bribe, but a gesture that says you want to earn back the relationship. This might be a discount on the next order, a credit toward future service, or simply a direct line to you if something goes wrong again. Keep it proportional to the failure. A small gesture on a major failure reads as insulting; a large gesture on a minor one reads as performative.

Three examples

Late delivery

"Your order 4782 was supposed to arrive by March 15. It did not arrive until April 2. That's on us. We missed our own deadline, and I know that disrupted your plans.

Here's what happened: we underestimated the lead time on a component and didn't flag it early enough to source it elsewhere. That's a planning failure, not a vendor problem. We've now built a 10-day buffer into our supply-chain timeline for that item, and our operations manager is reviewing every lead time in our system this month to catch similar gaps.

I'm crediting your account for the full shipping cost of this order. Going forward, if you order from us again and we're running behind, you'll hear from me directly before the promised date passes. You have my direct line: [your phone number]."

Billing error

"We charged you twice for your December invoice (invoice 8841). You were billed on December 3 and again on December 10. That should never have happened, and I apologize for the confusion and the time you spent catching it.

The error was in our billing system when we migrated to new accounting software in early December. We failed to test the duplicate-transaction scenario thoroughly before going live. We've now run a full audit of all transactions from December 1-15 and identified 47 other customers affected. We've already issued refunds to all of them. Your refund of $[amount] processed today and should appear in your account within two business days.

To prevent this from happening again, we've implemented a manual review step for any transaction flagged as a potential duplicate, and our accounting team is spot-checking 5% of all transactions weekly. If you see anything unusual on your next invoice, email me directly and I'll investigate it personally before it processes."

Poor service experience

"You called on March 22 with a question about your service, and the person who answered was dismissive and unhelpful. You shouldn't have had to call back. I'm sorry.

That was a failure on my part to train my team on how to handle questions they don't immediately know the answer to. The right response is 'let me find out' or 'I'm going to connect you with someone who knows,' not 'that's not really how this works.' I've reviewed that call with the team member, and we've built a new protocol for handling out-of-scope questions. Every person on my team now knows they have permission to say 'I don't know' and to get you to someone who does.

I'd like to make this right. I'm extending your service for one month at no charge. More importantly, I'm giving you my direct email. If you reach anyone on my team and don't get a straight answer, email me and I'll handle it myself."

What not to do

Do not apologize for the customer's feelings ("I'm sorry you felt disappointed"). Apologize for your action. Do not use the word "but" after your apology—it cancels everything before it. Do not make the letter about you and your stress or your good intentions. Do not send it unsigned or from a generic support address. A customer apology is a commitment, and it needs a name and ideally a way to reach that person directly.

When to send it

Send it fast, before the customer has to ask for an apology or escalate the complaint. A letter that arrives three days after the failure is better than an email that arrives the same day—it shows you took time to think it through instead of sending a panic response. But do not wait a week. The customer is already frustrated; a delayed apology adds insult to injury.

The letter should arrive as a physical note, not an email. Email apologies disappear into the inbox. A letter sits on a desk. It signals that you considered this serious enough to do something that takes time and costs money. That signal matters.