Draft a response to this escalation email: [ESCALATION EMAIL]. My role and authority are: [MY ROLE AND AUTHORITY]. Verified facts and current status are: [VERIFIED FACTS]. Actions already taken and next actions are: [RECOVERY PLAN]. The recipient relationship, tone, and deadline are: [RECIPIENT AND TONE]. Write an email that acknowledges the impact without admitting fault, liability, root cause, or a remedy that has not been verified or approved. Do not repeat accusations, assign blame, speculate about individuals, or promise a completion date unless it appears in [VERIFIED FACTS] or [RECOVERY PLAN]. Produce: - Three subject-line options.
- A send-ready email of 150-250 words. - A short internal note listing claims, commitments, approvals, or sensitive items that should be checked before sending. The email should contain, in this order: acknowledgement of the recipient’s concern; concise statement of what is confirmed; the immediate containment or investigation action; the next update time or decision point; the owner or team responsible where appropriate; and one clear ask, such as confirmation of impact, access, priority, or a meeting time. Use plain language and avoid “we are looking into it” without saying what will happen next. If information is uncertain, say that it is being verified and specify when the recipient will hear next. For legal, security, privacy, safety, contractual, or regulated matters, avoid conclusions and flag required review by the appropriate internal professional. Before answering, check every factual statement and deadline against the supplied inputs, and flag any sentence that could be read as an admission, guarantee, or unauthorized commitment. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ESCALATION EMAIL] | Paste the email or summarize the escalation and the recipient’s stated concerns. | A customer says their Monday data export failed and asks why no one warned them before their board meeting. |
| [MY ROLE AND AUTHORITY] | State your role and what commitments, credits, timelines, or disclosures you may approve. | Customer Success Manager. I can coordinate engineering and offer a service credit only after finance approval. |
| [VERIFIED FACTS] | List confirmed facts, impact, investigation status, and known dates. | The export job failed from 7:10 to 9:40 a.m. Monday for 14 accounts. The customer's export completed successfully at 10:05 a.m. Root cause is not confirmed. |
| [RECOVERY PLAN] | List actions already completed, next actions, owners, and approved update times. | Engineering is reviewing logs today. I will send an update by 3 p.m. ET. Support will verify the customer's scheduled exports for the next five business days. |
| [RECIPIENT AND TONE] | State who will receive the email, their relationship to you, and the needed tone and deadline. | Send to the customer's VP of Finance by noon ET; calm, accountable, and concise. |
How to use
- Separate verified facts from likely explanations before pasting them into the prompt.
- State exactly what you are authorized to promise, approve, or disclose.
- Read the internal check note before sending, especially for credits, contracts, security, and timelines.
- Send this follow-up: “Make this more concise for an executive recipient while preserving the update time and removing any implied guarantee.”
Variations
Executive update
Use when leadership needs a concise status update during an active escalation.
Draft an executive escalation update about [INCIDENT OR ISSUE] for [EXECUTIVE AUDIENCE]. Use only these verified facts: [FACTS]. Current business impact is [IMPACT], and the recovery actions and decision needs are [ACTIONS AND DECISIONS]. Produce a subject line and a 120-180 word update with: current status, quantified impact if supplied, containment, next milestone, risks, and one decision or ask. Do not assign blame, speculate on root cause, or promise recovery before it is confirmed. Flag unsupported claims. Ask up to 3 questions only if a required input is missing.
Vendor escalation
Use when asking a supplier or service provider to correct a failure.
Write a vendor escalation email to [VENDOR] about [ISSUE], based on [EVIDENCE] and [CONTRACT OR SERVICE EXPECTATIONS]. We need [REQUESTED REMEDY] by [RESPONSE DEADLINE]. Produce a firm, factual email that identifies the impact, requests a named owner, immediate containment, root-cause timeline, corrective-action plan, and regular status cadence. Do not claim breach, demand a remedy beyond my authority, or state legal conclusions. Include an internal list of terms or remedies requiring procurement or legal review. Ask up to 3 questions only if a required input is missing.
Customer apology
Use after a verified service failure when a customer needs a direct response.
Draft a customer response about [VERIFIED INCIDENT] for [CUSTOMER]. The confirmed impact is [IMPACT], and approved remediation is [APPROVED REMEDIATION]. The next update will be [UPDATE TIME]. Write 150-220 words that acknowledges the disruption, states confirmed facts plainly, explains what has been done, gives the next update point, and offers one appropriate path for questions. Do not invent a root cause, promise future reliability, or offer unapproved compensation. Flag statements needing legal, security, or account-owner review. Ask up to 3 questions only if a required input is missing.
Tips
- Acknowledge the recipient’s operational impact, not just their frustration; this shows you understood why the issue matters.
- Use a specific next-update time even when root cause is unknown, then meet that commitment with a status update rather than silence.
- Keep investigation findings separate from confirmed facts until the technical, legal, or security owner approves the wording.
- Do not offer credits, refunds, contract changes, or security conclusions in a draft unless the responsible approver has authorized them.
FAQ
Should an escalation response apologize?
Acknowledge the disruption clearly. Use legal or company-approved language when the issue could involve liability, security, privacy, or a contractual dispute.
What if I do not know the root cause yet?
Say what is confirmed, what action is underway, and when the recipient will receive the next update. Do not guess.
How quickly should I reply?
Respond promptly with a factual acknowledgement and next update time, even if the full investigation or recovery plan is still in progress.