Should the CEO always send the apology email?

For significant incidents affecting many users, a founder/CEO signature increases trust. For routine customer service issues, the Support Team voice is more appropriate. Match the severity of the incident to the seniority of the sender.

How do I balance transparency with legal risk?

Stick to confirmed facts. Don't speculate on cause. Don't admit negligence beyond what's already clear. 'A configuration error caused X' is transparent. 'We were negligent in our QA process' creates legal risk. When in doubt, involve legal counsel before sending.

Should I send this to all users or just affected ones?

Only to affected users. Sending crisis communications to unaffected users unnecessarily alarms people who had no issue and damages trust with them too.

What if the crisis is public (social media, press)?

For public crises, the email to affected users is accompanied by a public statement on social media and/or your status page. The two should be consistent — different messages to different audiences in the same crisis destroys credibility.

Gemini Professional Apology & Crisis Email Prompt

You are a crisis communications specialist who has managed PR situations for companies from startups to Fortune 500s.

Category

✍️ Writing

Difficulty

Intermediate

Models

Last Updated

2026-06-28

Works with

ChatGPT Claude Gemini

⚙️ Fill in your variables

what went wrong

who was affected

remedy offered

your role

📋 Prompt

You are a crisis communications specialist who has managed PR situations for companies from startups to Fortune 500s.

Situation: [what went wrong]
Affected parties: [who was affected]
Remedy: [remedy offered — refund/credit/fix/explanation]
Sender: [your role — CEO/Support Team/Founder]

Task: Write a complete apology communication:

CORE PRINCIPLES:
- Take full responsibility with no 'if you were affected' hedging
- Explain what happened (briefly) without making it an excuse
- State what you've done/are doing to fix it
- State what you've done to prevent recurrence
- Make it right, specifically

FORMAT:
Subject: Direct and honest (not 'An Important Update')
Opening: Acknowledge the problem directly in sentence 1
Explanation: What happened (facts only, 2–3 sentences)
Impact acknowledgement: Name what this cost the affected party
Fix: What you're doing right now
Prevention: What structural change prevents this recurring
Remedy: Specific offer
Close: Personal sign-off, real name, real title

Constraints: No passive voice. No corporate-speak. No 'we apologise for any inconvenience'. This is a real communication to real people.

📄 Example output

Subject: We lost your data. Here's what happened and what we're doing.

Hi [Name],

On Tuesday between 2:14am and 6:02am GMT, a database migration error deleted saved prompts for 847 accounts — including yours. I'm writing to tell you exactly what happened, what we've done, and what we're giving you to make this right.

What happened: During a scheduled migration to our new database infrastructure, a configuration error caused a rollback that overwrote data written after our last backup (taken at 11:59pm Monday). 847 accounts lost data created in that window.

We know this affected your work. Losing saved configurations and custom prompts isn't just inconvenient — it represents real time you'll have to spend recreating that work.

Here's what we've done: We've restored everything we could from the 11:59pm backup (available now in your account). We've implemented real-time replication to a second database so this specific failure mode is no longer possible. Our backup interval moves from daily to every 15 minutes starting today.

Here's what we're giving you: 6 months of ToolsNova Pro, free — no code needed, applied to your account automatically.

I'm sorry. This was our fault, and we'll do better.

[Founder Name]
Founder, ToolsNova

🏆

Best model for this prompt

Claude

Claude (Opus 4 / Sonnet 4)

💡 Pro Tips

Send the apology within 4 hours of a major incident — every hour of silence costs more trust than the incident itself

'We apologise for any inconvenience' is the most hated phrase in crisis communications — never use it

Name the specific impact on the customer, not just the event itself — show you understand what it actually cost them

Offer something before they ask for it — proactive remedies retain 3x more customers than reactive ones

⚠️ Common Mistakes

The 'if you were affected' hedge — it signals you're more concerned with liability than with people

Explaining too much — the explanation section should be factual and brief, not a defence

Promising changes you haven't made yet — only commit to changes already in motion

Using 'An Important Update' as a subject line — it's the most generic crisis email subject in existence and signals evasion

❓ FAQ

Should the CEO always send the apology email?
For significant incidents affecting many users, a founder/CEO signature increases trust. For routine customer service issues, the Support Team voice is more appropriate. Match the severity of the incident to the seniority of the sender.
How do I balance transparency with legal risk?
Stick to confirmed facts. Don't speculate on cause. Don't admit negligence beyond what's already clear. 'A configuration error caused X' is transparent. 'We were negligent in our QA process' creates legal risk. When in doubt, involve legal counsel before sending.
Should I send this to all users or just affected ones?
Only to affected users. Sending crisis communications to unaffected users unnecessarily alarms people who had no issue and damages trust with them too.
What if the crisis is public (social media, press)?
For public crises, the email to affected users is accompanied by a public statement on social media and/or your status page. The two should be consistent — different messages to different audiences in the same crisis destroys credibility.

🔗 Related Prompts