When things break: own it, fix it, make the customer whole.
An apology that names the specific failure beats five paragraphs of "we apologise for any inconvenience". State what broke, what you're doing about it, and what the customer can expect next. Do not over-explain the root cause unless asked. Do offer a credit before the customer asks for one, the gesture is what registers, not the dollar amount. Avoid passive voice ("mistakes were made") and never start with "unfortunately". The recovery is not the apology email itself, it's whether you followed through on the next step you committed to.
Apology: downtime
Copy-paste email template for a sincere apology after a multi-hour outage, with a service credit and a what-we-changed line.
Open →Apology: billing error
Copy-paste email template apologising when the team charged the wrong amount or the wrong account, with refund timing.
Open →Apology: slow response
Copy-paste email template for apologising when a ticket sat too long without a reply, with the new owner and a timeline.
Open →Apology: feature removed
Copy-paste email template for apologising when a feature a customer relied on was removed, with the reason and an alternative.
Open →Apology: data incident notification
Copy-paste email template for the required notification disclosing a data exposure incident affecting the customer data.
Open →Apology: wrong info given
Copy-paste email template for correcting a previous reply that contained wrong information, with the accurate answer.
Open →Apology: agent behaviour
Copy-paste email template for apologising after a previous customer support agent was dismissive or disrespectful.
Open →Apology: missed commitment
Copy-paste email template for apologising when the team promised a delivery, fix, or callback and missed it.
Open →Pricing change: explanation
Copy-paste email template explaining and apologising for a price increase that upset a long-standing customer.
Open →Apology: issue cannot be resolved
Copy-paste email template for honestly telling a customer the team cannot fix their problem, with what you can do instead.
Open →Build a real macro library. Not a Google Doc.
SupportWire's macros learn from your replies. Variables auto-fill. AI suggests the right one.