Write an apology email to [CLIENT NAME AND ROLE] regarding [INCIDENT]. The relationship context is [RELATIONSHIP CONTEXT]. Confirmed facts are [CONFIRMED FACTS], actions already completed are [ACTIONS TAKEN], and the remaining remedy or decision is [REMEDY AND ASK]. Use a [TONE] tone. Write 160 to 230 words with a specific subject line. Follow this order: 1. Open with a direct apology and name the client impact. Do not use passive phrasing or lead with an excuse. 2. State only confirmed facts. Separate cause, impact, and uncertainty; do not speculate or blame a vendor, employee, or client. 3. Explain the concrete correction, owner where appropriate, and date or time window for the next update. Do not promise an outcome beyond our control. 4. Make one clear ask, such as approving a recovery plan, choosing a new date, or joining a short call. 5. Close with accountability and a direct contact path. Return the final email, then “internal review notes” listing wording needing legal, account-leadership, or operations approval. Also provide a 60-word version for a time-sensitive incident update. Do not invent compensation, refunds, causes, deadlines, policy commitments, or prior conversations. Ask up to 3 clarifying questions only if a required input is missing. Before answering, check that the apology names client impact, the remedy is specific, and every commitment is supported by my inputs.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CLIENT NAME AND ROLE] | Enter the recipient’s name, job title, and company if useful. | Priya Shah, Operations Director at Hartwell Foods |
| [INCIDENT] | Describe the service failure, delay, error, or missed expectation. | the September inventory dashboard was delivered two business days late and omitted two warehouse locations |
| [RELATIONSHIP CONTEXT] | State the relevant client relationship, project, contract, and sensitivity of the situation. | Hartwell is in the first quarter of an annual analytics-services contract |
| [CONFIRMED FACTS] | List only verified facts, including what happened, when, and the client impact. | The dashboard due Friday, September 18 was sent Tuesday, September 22. Locations WH-07 and WH-11 were excluded from the import. |
| [ACTIONS TAKEN] | List corrective actions already completed and their verified results. | We corrected the import, validated both locations against source files, and posted a complete dashboard Tuesday. |
| [REMEDY AND ASK] | State the remaining recovery action and response you need from the client. | Send a written root-cause review Friday and add a pre-delivery check. Ask Priya whether a 20-minute Thursday review would help. |
| [TONE] | Enter the desired tone, such as direct and accountable or formal and concise. | direct, accountable, and calm |
How to use
- List confirmed facts separately from suspected causes.
- Paste the actual remedy, owner, and update date; do not delegate commercial concessions or legal language to the model.
- Check that the opening names the impact and every promise has an owner or real time window.
- Follow up with: “Make this 130 words, preserve the apology and call ask, and remove any sentence not needed for the client to act.”
Variations
Missed deadline
Use when a deliverable is late but service is otherwise operating.
Write a [WORD COUNT]-word apology email to [CLIENT] for missing the [DELIVERABLE] deadline. Facts are [FACTS]. The revised delivery plan is [RECOVERY PLAN], and I need the client to [ASK]. Open with accountability, state the impact, give milestone dates, and make the ask. Do not blame dependencies or promise an unsupplied date. Flag commercial remedies needing approval. Ask up to 3 questions only if required input is missing.
Service incident
Use when a technical outage or data problem needs a timely client update.
Draft a client incident update for [CLIENT] about [INCIDENT]. Use [CONFIRMED TIMELINE], [KNOWN IMPACT], [CURRENT STATUS], and [NEXT UPDATE TIME]. Return a subject line, 120-word email, and 50-word status-page version. Distinguish confirmed cause from investigation status, avoid unsupported assurances, and state any client action needed. Do not invent restoration times or data-loss conclusions. Ask up to 3 questions only if a required input is missing.
Scope mistake
Use when your team misunderstood or failed to meet a project expectation.
Write an apology email to [CLIENT] after a scope mismatch on [PROJECT]. The agreed expectation was [AGREED SCOPE]; what we delivered was [ACTUAL DELIVERY]; the correction is [CORRECTION]; and the needed decision is [ASK]. Keep it constructive and non-defensive. Include a short proposal for documenting revised scope and acceptance criteria. Do not assign fault or revise contract terms without input. Ask up to 3 questions only if a required input is missing.
Tips
- Put the impact in the first two sentences; clients should not need to infer why the issue matters.
- Do not describe a suspected root cause as fact during an outage or data incident.
- Separate an apology from a refund, credit, or legal concession; those terms need approval.
- A credible recovery plan names a completed correction, a measurable next milestone, and an accountable owner.
FAQ
Should an apology email explain the cause?
Explain confirmed cause only when it helps the client understand the remedy. If the investigation is incomplete, say so and give the next update time.
Can AI write a message about refunds or liability?
It can draft from approved terms, but compensation, admissions, contractual changes, and legal language need the responsible owner’s review.