There is a specific moment, somewhere between finding out you were wrong and writing it down, where most apologies quietly turn into explanations. The sentence starts as an admission and ends as a description of circumstances, and by the last clause the reader has been told, politely, that it was not really anybody's fault.
Customers read that instantly. It is the difference between a letter that repairs something and a letter that makes them decide not to bother next time.
The Explanation Trap
You need exactly one sentence of cause, and it has to be a sentence that makes you look worse rather than better. "A handoff between two teams that nobody owned" is useful, because it names a real gap you are now responsible for closing. "An unexpected issue with our fulfillment partner" is not, because it relocates the failure to somebody the customer did not hire.
The test: read your cause sentence back and ask whether it would satisfy a customer who is already annoyed. If it sounds like the setup for why this was understandable, cut it.
An Apology and a Complaint Response Are Not the Same Letter
An apology is something you initiate. You found the mistake, or you fixed it, and you are writing because the relationship deserves acknowledgment. You control the timing and the framing.
A complaint response is a reply. Someone has already written down what went wrong, usually in detail, sometimes angrily, and often with a list. The reply has to address their list rather than your summary of it, in their order, including the parts that are uncomfortable. Answering four of five points reads as answering none of them.
Examples by Situation
A Billing Error
Ken, we billed you twice for October and the second charge sat on your account for three weeks before we caught it. That is our error, and worse, you were the one who had to notice. The refund cleared yesterday. There is now a duplicate-charge check in the nightly run so the next one gets caught the same day. Sorry for the time you spent proving something that was ours to find.
The Wrong Order Shipped
Alicia, you ordered the walnut and we sent the oak, and then the replacement went to your old address. Two mistakes on one order is more than anyone should have to manage on our behalf. The right piece is on the truck for Thursday and I confirmed the address myself this morning. Thank you for staying patient considerably longer than we had earned.
A Technical Outage
Nate, our system was down for six hours on the fourteenth and your team could not reach their files during a close week. I am sorry. It was a failover that did not fail over, and it has been rebuilt and tested twice since. I am aware that an outage during close is not the same as an outage on a quiet Tuesday, and we treated it that way internally.
A Formal Written Complaint
Ms. Okafor, I have read your letter of the third in full, and you are right on every point. The technician arrived outside the window. He did not put down covers. The person you called afterward told you that was normal, and it is not normal here. He has been retrained on site protocol, the call was reviewed with the whole support team, and your carpet cleaning is booked for the ninth at our cost. Thank you for writing rather than simply leaving.
Answering a Complaint Point by Point
Notice what the last example does. It restates each of the customer's three complaints in her own terms before responding, and it concedes the third one, the dismissive phone call, which is the one most businesses would quietly skip because it implicates a second employee.
That concession is what makes the rest credible. A reply that agrees with everything except the most embarrassing item tells the reader precisely where your limit is.
When the Mistake Was Not Actually Yours
Sometimes the carrier lost it, the client approved the wrong file, or the customer misread the terms. You still write the letter, and you still do not litigate it. What you apologize for shifts: not for causing the problem, but for the experience of dealing with it, which genuinely was yours to manage.
"The shipment was held up in transit and you spent two days chasing an answer from us that we should have had ready" is honest, does not accept a fault you do not own, and still gives the customer the acknowledgment they actually want.
Making It Repeatable
Almost nobody fails to send these out of indifference. They fail to send them because the right moment is two to five days after a resolution, which is exactly when the team has moved on to the next fire. The letter that would have mattered most gets written never.
Trigger it from the system where tickets and jobs already close, and the timing takes care of itself. Related reading: apology letters to clients, letters for poor service, and the full customer apology guide.
Should you explain why the mistake happened?
One sentence, and only if it makes you look worse rather than better. A cause that names a real gap you are closing gives the customer something concrete. A cause that points at a partner, a system, or an unusual circumstance relocates the blame to someone the customer never chose to do business with, and they read it as an excuse regardless of whether it is true.
What is the difference between an apology letter and a complaint response?
An apology is initiated by you, so you choose the framing and the timing. A complaint response is a reply to a document the customer has already written, which means it has to address their specific points in their order, including the uncomfortable ones. Answering most of a complaint reads to the sender as answering none of it.
Do you apologize for a mistake the customer has not noticed yet?
Usually yes, when the mistake affected them materially, such as an overcharge or a data error. Being told about a problem you found yourself is one of the few genuinely trust-building experiences a business can create, and the alternative is that they discover it later and reinterpret every previous interaction in that light.
How formal should a written apology be?
Match the register of the relationship, not the seriousness of the mistake. Formal language on a small error sounds like liability management, and casual language on a serious one sounds like you have not grasped it. In both directions the failure mode is the same: the customer stops reading it as a person talking to them and starts reading it as a company issuing a statement.
How quickly should you respond to a written complaint?
Acknowledge within one to two business days even if the resolution takes longer, then send the substantive letter once the fix has actually held. Silence during the gap is what turns a complaint into a review, and an acknowledgment that names a date you will come back is enough to hold the relationship open while you sort it out.
Scribble drafts a handwritten apology from the real details when a ticket or job closes, sends it to you for approval, and mails it in real ink. See how it works.
Book a Demo- Templates & ExamplesApology Letter to a Client: Examples for Professional ServicesA client is not a customer. They have a contract, a budget they defended internally, and a boss who is going to ask what happened. Here is how to write the letter that keeps the account, with examples for missed deadlines, work errors, and overruns.
- Templates & ExamplesApology Letter for Bad Service: Examples That Get Customers BackBad service is not a broken product. Nobody made a mistake, someone made a choice, and that is harder to write about. Here is what to send after rude staff, long waits, and the slow accumulation of small failures.
- Templates & ExamplesCustomer Apology Letter Examples: What to Write After You've Let Someone DownA refund settles the invoice. A letter settles the relationship. Here is how to write an apology that actually repairs trust — the structure, real examples by industry, and how to send one every time a service failure gets resolved.