Customer Support · Intermediate
Apology for a Real Failure
Own a mistake without corporate fog
When to use it
When you actually broke something: lost data, a wrong charge, a missed deadline. Use it for a single customer or for an email to everyone affected.
We got something wrong. Write the apology. What happened: {{issue}} How bad it was for them: {{severity}} What we are doing: {{resolution}} Structure: 1. What happened, factually, in one sentence 2. What it cost them — acknowledge the actual impact, not the inconvenience 3. What we are doing about it and when 4. What we are changing so it does not recur 5. Compensation, if any, stated without being asked twice Rules: - Active voice. "We deleted your data", not "data was lost". - No "if you were affected", no "some users may have experienced" - Do not ask for understanding - No more than 150 words
Try it: fill the variables
Example
Inputs
- {{issue}} The problem in one line
- A sync bug on 14 October overwrote shared calendar events with older versions for 3 hours.
- {{severity}} How bad it is for the customer
- Their clinic lost 41 patient appointments from the shared calendar; staff rebooked them by phone.
- {{resolution}} What you can actually offer
- Restored all events from backup; adding a version check before sync writes; crediting two months.
Output
On 14 October, a bug in our sync overwrote your shared calendar with an older version for three hours. For your clinic that meant 41 appointments disappeared and your team had to call patients to rebook them. That was hours of work you should never have had to do. We have restored every event from our backup; you can check them now. We are adding a version check so sync can no longer write an older copy over a newer one; it goes live on 24 October. We have credited two months to your account. You don't need to do anything for it.
Why it works
Naming the real cost instead of 'the inconvenience' shows you understood what happened to them. Active voice and the ban on 'if you were affected' remove the hedging that makes apologies read as legal statements, and stating compensation upfront saves the customer a second email.
More from this pack
- Reply to a TicketA straight answer to a support message, no service-desk theatre
- Say No Without Losing the CustomerRefuse a request clearly and offer the nearest real thing
- Bug Report From a Vague TicketTurn a frustrated message into something engineering can act on
- Angry Customer, Real AnswerRespond to hostility by resolving, not by soothing
From the Global Prompt Library (TextDeck Community License 1.0), version 53723a8. GitHub
Three keys. Every prompt.
Copied to clipboard