Write an apology email without unconfirmed compensation
Acknowledge impact and known responsibility while keeping remedies within confirmed authority
4 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Write an apology email based only on verified facts and confirmed authority.
Incident, impact, timing, cause status, and uncertainty:
[incident]
Completed actions, planned actions, owners, updates, and approved remedies:
[response]
Recipient, tone, authority limits, and contact route:
[recipient]
Acknowledge the recipient's concrete impact, apologize directly, and distinguish known facts from ongoing investigation. Do not speculate about cause or fault. State only actions and timelines that are confirmed. Do not promise refunds, credits, replacement, reimbursement, prevention, or outcomes unless explicitly approved. If compensation is requested but unresolved, explain the review path and expected update without implying approval. Return: subject, send-ready email, commitment audit, and facts requiring confirmation.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Verified incident facts
A duplicate billing job charged Northwind twice for invoice INV-2048 on 6 August. The duplicate amount was £840. Finance confirmed the duplicate; the technical cause is still under investigation. Northwind says the charge affected its available balance.
Confirmed response
Billing was paused at 10:20 BST. Finance submitted a reversal at 11:05 BST; the bank's posting time is unknown. Engineering will provide an investigation update by 8 August 16:00 BST. A service credit was requested but has not been approved; Account Operations will review it by 9 August.
Recipient and boundaries
Northwind finance manager. Calm and accountable. Sender cannot approve credits or promise bank timing. Direct replies go to billing@example.test.
Example output
Subject: Apology and update on duplicate charge for INV-2048
Hello,
I’m sorry that invoice INV-2048 was charged twice on 6 August and that the duplicate £840 charge affected your available balance. Finance has confirmed the duplicate. We are still investigating the technical cause and will provide an update by 8 August at 16:00 BST.
We paused billing at 10:20 BST and Finance submitted a reversal at 11:05 BST. The bank controls when it appears, so I cannot yet give a posting time. Account Operations is reviewing the requested service credit and will provide its decision by 9 August; the credit is not yet approved.
Commitment audit: promises only investigation update and credit decision dates; does not promise credit approval, bank timing, or recurrence prevention. Confirm the sender name before sending.
Why this works
1
Separating apology from remedy authority allows accountability without unauthorized promises.
2
A commitment audit makes operational and financial promises visible before sending.
Check the result
Does the email acknowledge the specific impact without speculating about cause?
Is every action, deadline, and remedy confirmed and authorized?
Is any unresolved compensation request described as a review rather than a promise?
ChatGPT