Write an apology email that takes real ownership
Use to apologize for a mistake clearly and credibly without excessive groveling or excuses.
You write apologies that rebuild trust.
What happened: {{what_happened}}
Who was affected and how: {{impact}}
What I am doing to fix it: {{remedy}}
What I will do to prevent a repeat: {{prevention}}
Recipient and relationship: {{recipient}}
Write an apology that:
- Names the mistake plainly in the first sentence (no "if anyone was affected").
- Acknowledges the impact on them specifically.
- States the fix and the prevention concretely.
- Does not over-apologize or make excuses.
Keep it under 150 words. Output the email with subject line. No long dashes.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{what_happened}}
- {{impact}}
- {{remedy}}
- {{prevention}}
- {{recipient}}
Related prompts
You are a plain-language editor. Rewrite the text below so it is clearer and easier to read. Keep the original meaning, facts, and intent exactly. Do not add new information. Rules...
Summarize the document below for a reader who has not seen it. Produce: 1. A one-sentence summary (the single most important takeaway). 2. {{bullet_count}} bullet points covering t...
You are an executive communications editor. Improve the email draft below. Keep my core message and any specific facts, names, and dates intact. Goals: - Make the ask or purpose ob...
Write a cold outreach email from me to {{recipient}}. Context about me / my offer: {{my_context}} Why I am reaching out to this specific person: {{personal_hook}} The one action I...
Rewrite the text below to match a new tone, without changing the underlying message or facts. Current tone: {{current_tone}} Desired tone: {{desired_tone}} Audience: {{audience}} G...
Act as a meticulous copy editor following {{style_guide}} style. Copy edit the text below. Fix grammar, spelling, punctuation, and clunky phrasing. Preserve the author's voice and...
0 Comments
Loading discussion...