One Message Can Heal
Create Your Sorry Card

Apology guides

Apology for a Software Bug, Login or Password Reset Issue

A technical apology should help a user understand the next safe step. Avoid asking for passwords or confidential account information through a public message.

2 min readGuidance & examples

Identify the affected workflow

Specify the action that fails and any confirmed scope. For a login problem, distinguish an account-specific issue from a wider outage. Do not promise a fix that has not been released or tested.

Provide a safe support route

Use the normal support channel and ask only for information needed to identify the case. A reset link should use the legitimate service domain; never ask someone to send their password.

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.

A bug acknowledgment

I am sorry [feature] is not working as expected. We have confirmed [issue]. [Safe workaround, if verified]. Please contact [support channel] with [non-sensitive reference] so we can update your case.

Questions about this apology

What should I verify before sending this message?

Specify the action that fails and any confirmed scope. For a login problem, distinguish an account-specific issue from a wider outage. Do not promise a fix that has not been released or tested.

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

Explain the affected action in language the user understands. Offer a tested workaround only when it applies to their issue.

Example 1

I am sorry you cannot complete [action] because of [confirmed issue]. The tested workaround is [step], if suitable. We will update [channel] when the status changes.

Example 2

We did not explain the problem with [feature] clearly. I apologize. [Known fact] is confirmed; [open question] remains under review.
Should the message include an untested fix?

No. Label a suggested investigation step accurately and do not describe it as a verified solution.

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