One Message Can Heal
Create Your Sorry Card

Apology guides

Apology for a Service Outage or Website Downtime

During an outage, communicate the affected service and the next update. Do not describe the incident as resolved before the actual customer workflow has been checked.

2 min readGuidance & examples

Describe what is known

Name the affected feature and scope. Say when an issue is still under investigation rather than publishing an unverified cause. Keep security-sensitive incident details out of a public apology.

Separate workarounds from a fix

Offer a workaround only if it has been tested. If recovery time is uncertain, announce the next status update instead of a completion deadline.

Check before sending

Confirm names, references and dates. Replace every bracketed field with a verified detail, and remove any sentence that describes an action you have not taken. Choose a private channel when the case includes personal information.

Example wording to personalize

These are drafts. Replace bracketed details and remove any claim that is not true in your situation.

An incident acknowledgment

We are sorry that [service] is currently unavailable. The confirmed impact is [scope]. [Tested workaround, if available]. We are investigating and will provide the next update at [time and time zone].

Questions about this apology

What should I verify before sending this message?

Name the affected feature and scope. Say when an issue is still under investigation rather than publishing an unverified cause. Keep security-sensitive incident details out of a public apology.

Can I promise a result or completion time?

Include only an authorized, checked commitment. If a result is uncertain, give an honest status and a realistic next update instead.

A practical way to write this message

Name the affected service and confirmed scope. Point to a real status channel and avoid promising restoration before it is verified.

Example 1

We are sorry [service] is unavailable for [confirmed users or feature]. The team is investigating, and the next verified update will be posted at [channel/time].

Example 2

Our earlier message suggested [feature] was restored too soon. I apologize. Its current confirmed status is [status]. Please refer to [official channel] for updates.
Can I say no data was affected?

Only after the responsible assessment confirms that. Keep operational status separate from any unverified data-impact statement.

Make your message personal.

Use the ideas here as a starting point. Bring your own words and details to the creator when you are ready to make your sorry card or message.

Create your sorry card