Draft an escalation email to a client about the issue below. [CLIENT AND AUDIENCE]: recipient names, roles, relationship, and who should be copied. [ISSUE AND VERIFIED FACTS]: what happened, when it began, affected scope, and facts we have confirmed. [CLIENT IMPACT]: the client-facing consequence, including deadlines, users, revenue, service level, or risk where known. [ACTIONS TAKEN AND PLAN]: completed actions, current owner, next diagnostic or recovery steps, and their expected timing.
[DECISION OR HELP NEEDED]: the specific approval, information, access, or meeting I need from the client. [TONE AND AUTHORITY]: required tone, sender role, and any commitments already approved. Write for a client who needs a clear picture, not an internal incident log. Lead with the issue and impact in plain language. Distinguish verified facts from items still being investigated. State what we have done, what happens next, who owns the next update, and when the client will hear from us again. Ask for one clear action from the client, with a deadline only if it is real. Do not assign blame, expose internal personnel disputes, use vague phrases such as "we are working on it," or promise a fix time that has not been approved. If an outage, security, contractual, legal, or regulatory issue is involved, preserve the exact approved language in my notes and flag any wording that needs review by the responsible professional. Produce: a specific subject line; a 160-230 word email; and a three-bullet internal send check listing claims that require confirmation. Before answering, verify that every date, impact claim, and commitment is supported by my inputs, and that the requested client action is explicit. Ask up to 3 clarifying questions only if required information is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CLIENT AND AUDIENCE] | List the client recipients, their roles, and any people who should be copied. | Priya Nair, VP Operations at Northline Foods; copy her IT director and our account executive. |
| [ISSUE AND VERIFIED FACTS] | Describe the confirmed issue, timeline, scope, and unknowns. | Since 8:10 a.m. ET, warehouse supervisors cannot export the daily pick report. The dashboard still shows current inventory. Engineering reproduced the export failure. |
| [CLIENT IMPACT] | State the known business or operational effect on the client. | The morning shift is using a manual report, which may delay the 11:00 a.m. replenishment review. |
| [ACTIONS TAKEN AND PLAN] | List completed actions, owners, next steps, and real update timing. | We rolled back a reporting-service change at 9:05 but exports still fail. Elena from engineering is tracing the job queue. We will update by 10:30 a.m. ET. |
| [DECISION OR HELP NEEDED] | Specify the exact information, access, approval, or meeting needed from the client. | Ask Priya to confirm whether her team can use the manual CSV template through noon and to send any urgent export requests to support. |
| [TONE AND AUTHORITY] | State the sender role, desired tone, and commitments you are authorized to make. | Direct and accountable. I am Director of Customer Success. Do not promise restoration time. |
How to use
- Paste verified facts and separate them from open questions before running the prompt.
- Confirm that the named owner can actually make the stated next update.
- Read the email for implied guarantees, especially around restoration times, credits, or root cause.
- Follow up with: "Create a 60-word update for the same recipients after this new fact: [NEW FACT]."
Variations
Executive escalation
Use this when a senior client sponsor needs a concise status and decision request.
Write an executive escalation email to [CLIENT EXECUTIVE] from [SENDER ROLE] about [ISSUE]. Use only these verified facts: [FACTS]. State the client impact as [IMPACT], our recovery path as [PLAN], and the decision needed by [DATE OR EVENT] as [ASK]. Keep it under 150 words with a subject line. Do not include technical detail, blame, or unapproved commitments. Check that the email separates confirmed facts from investigation items.
Missed deadline
Use this when a delivery milestone will be late.
Draft a client email acknowledging that [DELIVERABLE] will not meet the planned date of [ORIGINAL DATE]. Explain the verified cause at the right level: [CAUSE]. Give the revised plan, dependencies, and update date: [RECOVERY PLAN]. Ask for this client decision or input: [ASK]. Write 150-200 words with a subject line. Do not call a revised date committed unless it is approved. Check that the impact and next decision are clear.
Security incident notice
Use this only with approved incident facts and counsel-approved language.
Using the approved language in [APPROVED NOTICE TEXT], draft a client incident notification for [CLIENT]. Include only these confirmed facts: [FACTS], the actions already taken: [ACTIONS], and the client action or contact route: [NEXT STEP]. Keep it factual and under 180 words. Do not infer data exposure, cause, scope, legal obligations, or remediation. Flag any item that needs security, legal, privacy, or contractual review before it is sent.
Tips
- Use a timestamped update commitment that you control, such as "we will update you by 3:00 p.m. ET," rather than a speculative fix estimate.
- Describe customer impact in operational terms, not internal system names or team activity.
- If root cause is not confirmed, say what is known and what is being investigated; a premature cause statement is hard to retract.
- Put a single client ask near the end so the recipient knows exactly how to unblock the recovery plan.
FAQ
Should an escalation email apologize?
A brief acknowledgment is appropriate when the client has been affected. Pair it with facts, ownership, and the next update rather than extended apology language.
Do I include a root cause?
Only when it is verified and approved for client communication. Otherwise state that investigation is ongoing and commit to the next update.
Can AI decide whether an issue requires legal review?
It can flag likely triggers, but your security, legal, privacy, and account owners should determine required review and approved wording.