Writing an apology that repairs trust
A generated draft gets you most of the way. The rest is knowing what separates an apology that wins a customer back from a defensive non-apology that makes things worse, and where the real fix lives.
What a real apology looks like
Same mistake, two very different emails. The first hides behind passive voice and policy, never quite saying sorry. The second owns it in the first line, says what happened, and makes it right. Only one of them earns the customer back.
The situation
A billing bug double-charged a customer $49.
A defensive non-apology
“We apologize for any inconvenience this may have caused. A charge appears to have been processed in error. Please allow 5–7 business days for the matter to be reviewed by our billing department.”
An apology worth sending
Subject: We charged you twice — fixing it now Hi [name], we charged you $49 twice on [date], and that's on us. I'm sorry — a surprise on your statement is exactly the kind of thing you shouldn't have to catch for us. I've already refunded the extra $49; it'll be back on your card within 3 business days. If it isn't, reply straight to me and I'll chase it personally.
Six habits behind an apology that lands
A generated draft gets you about 80% of the way. These are the habits that close the gap, whether you're apologizing for an outage or a one-line mistake.
Don't bury it under context or warm-up. "I'm sorry" up front tells the customer you're not about to argue. Everything after it lands softer.
"A charge was processed in error" hides who did it. "We charged you twice" owns it. The carrier, the system, the third party. None of that is the customer's problem.
Vague apologies read as insincere. Name the actual issue, the amount, the dates. Specifics prove you looked, instead of pasting a template.
An apology with no remedy is hollow. Say exactly what you're doing (the refund, the credit, the replacement, the new date) and when it'll happen.
A long apology reads like a defense. Two short paragraphs beat a wall of text. The customer wants to know you get it and you're fixing it. That's it.
An apology with the wrong figure or date does more harm than none. AI sounds confident even when it's wrong about your details. You're the editor, not the rubber stamp.
Here's the part an apology generator can't do: most apology emails trace back to an issue that took too long to resolve, or a customer who felt ignored while it dragged on. Solve problems fast enough, and keep people informed while you do, and most apologies never need writing. That means a findable help center and an AI agent that resolves the common issues before they turn into something you have to say sorry for.
A generator vs preventing the apology
An apology generator helps you write a great email after the mistake. Selvo works upstream: it resolves the issue while it's still a support question and keeps the customer informed, so the situation that needs an apology happens far less often. Here's where the two diverge.
| Capability | Generator | Selvo |
|---|---|---|
| Writing the apology | ||
| Drafts an apology email to a customer | ||
| Knows your product, policies, and history with the customer | Only what you paste in | Trained on your help center and inbox |
| Applies your brand voice | Re-describe it every time | Set once |
| Preventing the apology | ||
| Resolves the issue before it needs an apology | ||
| Answers customers 24/7 so nothing waits | ||
| Keeps every message in one place so none slip | ||
| Hands off to a human when unsure | ||
| Trust & cost | ||
| Cites a source the customer can verify | ||
| Audit log of every conversation | ||
| Price | Free | $0.10 per resolved chat |
