KoltrixApology emails that rebuild trust
When your company gets it wrong, the apology email can repair the relationship or deepen the damage. What to say, what to leave out and how to follow through.
On this page(10 sections)
- What an apology is for
- The anatomy of a good apology
- 1. Say sorry early and plainly
- 2. Name exactly what went wrong
- 3. Own it, without a "but"
- 4. Say what you have done already
- 5. Say what will change
- 6. Make it easy for them to respond
- 7. Keep it short
- A worked example
- What to leave out
- Compensation: when and how
- Match the apology to the size of the problem
- Apologizing to someone who is angry
- Follow-through is the apology
- Review before sending
- Key takeaways
You double-charged a customer. A promised feature slipped by two months. An update broke someone's workflow on the day they had a deadline. The facts are plain, and the customer is waiting to see what you say.
Most people can recognize a bad apology instantly: the vague "we apologize for any inconvenience", the one that explains why it was not really your fault, the one that arrives with a discount and no fix. A good apology is shorter than you expect, and it does something unusual: it takes the customer's side of the story seriously. This guide covers how to write one, what to leave out and how to make sure the words are backed by action.
What an apology is for
An apology does three jobs.
- It acknowledges what happened, in terms the customer would recognize.
- It accepts responsibility without hedging.
- It commits to a fix and to a way for the customer to see that you followed through.
If an apology only manages the first, it sounds like a status update. If it manages the second but not the third, it is a mood and not a promise. Keep the three jobs in mind when you read your draft.
The anatomy of a good apology
1. Say sorry early and plainly
Put it in the first or second sentence, and use the word. "I am sorry we charged you twice in March." Not "We regret any confusion regarding your billing", which names no event and no feeling.
2. Name exactly what went wrong
Be specific enough that the customer thinks "yes, that is what happened". Include the thing, the date and the effect on them if you know it: "Your invoice for 12 March was charged twice, which left you short by $49 for four days."
Specific language shows you have looked at their case. General language suggests a form letter.
3. Own it, without a "but"
Compare:
"We are sorry for the delay, but our supplier was late."
"We are sorry. The order should have arrived on the 5th, and it did not. That is on us."
The first tries to share the blame. The second lets the customer decide whether the reason matters. If there is a reason that helps them understand, give it afterward, briefly, as information and not as defense: "What happened was a mistake in our stock count."
Avoid the passive voice that hides the actor: "mistakes were made" and "the system failed" both leave out a person or a company. Say "we".
4. Say what you have done already
The most reassuring thing in an apology is a fix that has already happened. "I have refunded the second charge. It will show on your statement within three to five working days." Done things carry more weight than promised things.
5. Say what will change
If the problem could happen again, explain what you are doing to prevent it, in a sentence or two. Do not promise "this will never happen again", which nobody can guarantee. Say what you changed: "We now check for duplicate charges before every billing run."
6. Make it easy for them to respond
Invite a reply and say who they will reach. "Reply to this message and it comes directly to me." If the situation is complicated, offer a call.
7. Keep it short
Four to eight sentences is usually right. A long apology becomes about the sender's feelings and not about the customer's problem.
A worked example
Subject: Your double charge on 12 March, and what we did about it
Hi Dana,
I am sorry. We charged your card twice for your March invoice, and that left you $49 short for several days.
The cause was a fault in our billing system that ran the same payment a second time. It was our mistake, and you did nothing wrong.
I have refunded the extra charge today. It should appear on your statement within three to five working days. If it has not arrived by 22 March, reply to me and I will chase it with the bank myself.
We have fixed the fault and added a check so a payment cannot run twice for the same invoice.
Thank you for pointing it out so quickly.
Sam Customer support, Example Co
It is short, it names the problem, it takes responsibility, it shows a completed action and a date, and it gives the customer a way back to a real person.
What to leave out
- "For any inconvenience". Inconvenience is a mild word for what can be a real loss. Say what actually happened.
- "If you were offended" or "if this caused problems". The conditional makes the customer prove they were hurt. If you know what happened, say it plainly.
- Explanations that sound like excuses. Context can help, but it should follow the apology, not replace it.
- Corporate distance. "The company regrets" is colder than "I am sorry".
- Over-the-top regret. Dramatic language makes the customer take care of your feelings.
- Blaming the customer or another team. Even when partly true, it should be left for a private discussion.
- Unrelated sales content. An apology with a promotion in the footer reads as cynical. Switch those blocks off for the message.
- A coupon in place of a fix. A gesture can follow the repair. It cannot stand in for it.
Compensation: when and how
Not every apology needs a credit, and a credit does not make a bad apology good. A useful rule: fix first, apologize, then offer something proportional if the customer lost time or money.
- Refund the exact amount of any wrong charge without being asked.
- Offer a credit, a free month or an extension when the problem cost the customer real working time or broke a promise.
- Keep it proportionate. A giant gift for a small slip can look like an attempt to buy silence.
- Say why: "Because you lost a day of work, I have added a month to your plan."
Agree internally who may offer what, so your team can act quickly. Refund and billing support emails covers the wording around money.
Match the apology to the size of the problem
- Small slip, one customer (a late reply, a wrong link): a short, direct reply from the person who made it.
- Real harm to one customer (wrong charge, lost data, missed deadline): a personal apology with a concrete fix, from someone with authority.
- Problem affecting many customers (an outage, a data incident): a public explanation plus an email to everyone affected, written once and checked carefully. Outage communication by email has a structure for this. For serious incidents, get advice on what you must say and to whom.
For your most important accounts, a quick phone call before the email, as in VIP customer email handling, is often welcome.
Apologizing to someone who is angry
When a customer has written in anger, the apology comes after you have shown you understood. Reflect what they said in your own words before anything else. Handling angry customer emails goes into the steps, and one point is worth repeating: do not respond to tone, respond to the problem. A calm apology to a furious message usually lowers the heat without any special phrase.
Follow-through is the apology
The email is the first move. The customer decides whether you meant it by what happens next.
- Do exactly what you said, by the date you said. Put reminders on every promise.
- Close the loop. When the refund goes through or the fix ships, send a one-line message: "The refund has been issued. Thank you for waiting." See following up after a fix ships.
- Record the cause. Add it to your list of known failures so the same mistake is easier to prevent.
- Look for the pattern. If the same kind of apology keeps going out, the process, not the wording, needs repair.
Review before sending
- The word "sorry" appears early and without conditions
- The problem is named specifically, with dates or amounts
- There is no "but" and no blame on the customer or another team
- One completed action and one future change are stated
- A person's name and a direct way to reply are included
- Marketing blocks and upsell links are removed
- Every promise has a date, an owner and a reminder
- The message is short enough to read in one breath
Key takeaways
- A good apology acknowledges what happened, accepts responsibility and commits to a fix, in a few plain sentences.
- Be specific, say "we", drop the "but" and lead with something already done.
- Leave out "for any inconvenience", conditional regret, excuses and sales copy.
- Fix first, then offer compensation that fits the harm and say why.
- The apology is proven by following through, so set reminders and close the loop.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
