Public Apology Statement and Recovery Note Writer

Draft a public apology and recovery note with accountable language, verified facts, audience-specific versions, next steps, and review safeguards.

Prompt Template

You are a crisis communications writer helping draft an accountable public apology and recovery note. Write for:

Organization/person: [name and context]
Incident or mistake: [what happened, in plain facts]
Audience affected: [customers, community, employees, partners, users, public]
What is confirmed: [verified facts only]
What is still unknown: [open investigation items]
Impact or harm: [service disruption, safety concern, offensive statement, delay, privacy issue, financial impact, trust breach]
Responsibility stance: [full responsibility, shared responsibility, investigation ongoing, legal constraints]
Actions already taken: [fix, refund, removal, policy change, outreach, investigation, support channel]
Next actions and timeline: [what will happen next and when]
Channels: [website, email, social post, press statement, internal note, customer message]
Tone: [sincere, concise, formal, human, executive, plain language]
Words or claims to avoid: [legal restrictions, unverified details, blame, excuses, confidential data]
Reviewers: [legal, comms, leadership, support, affected stakeholders]

Create:
1. Core apology statement with clear acknowledgement, responsibility, impact, action, and next update.
2. Short social version that does not sound evasive.
3. Longer email or website note with facts, what changes, and support/contact details.
4. Internal talking points for support, sales, or community managers.
5. FAQ with careful answers for likely hard questions.
6. Review checklist for legal risk, accuracy, empathy, privacy, and overpromising.
7. Phrases to remove because they minimize harm, shift blame, or sound generic.
8. Follow-up update template for when the promised actions are complete.

Use only supplied facts. Mark anything unverified as a question for reviewers instead of filling it in.

Example Output

Public Statement

We are sorry for the disruption our billing error caused on Tuesday. Some customers were charged twice for their monthly subscription, and that should not have happened. We have reversed the duplicate charges, paused further billing retries while we verify the fix, and emailed affected customers with their refund status.

We are reviewing the release process that allowed this error through and will share a follow-up by Friday with the changes we are making. If you were affected and have not received an email from us, contact [support channel] so we can investigate your account.

Avoid

- "We are sorry if anyone was inconvenienced."

- "This was caused by our payment provider" unless verified and still owned.

- "Everything is fixed" before monitoring confirms it.

Reviewer Questions

Has finance confirmed all duplicate charges were reversed? Can we state the number of affected customers? What refund timeline is accurate by payment method?

Tips for Best Results

  • 💡Start with the impact on affected people before explaining internal causes.
  • 💡Use verified facts and explicit next steps instead of dramatic language.
  • 💡Prepare support talking points before publishing the public note.
  • 💡Do not promise timelines, refunds, or policy changes until owners have approved them.