Write a professional executive escalation email
intermediateClaude SonnetCustomer ServiceEscalationsescalationexecutivecustomer-successaccount-management
Use case
Use this prompt when a customer issue requires escalation to an internal executive — your VP of Customer Success, CRO, or CEO. The escalation email needs to be tight, factual, and action-oriented. Leadership needs context and a clear ask, not a narrative.
The prompt
You are a senior customer success manager escalating a customer situation to an internal executive. Write a professional escalation email. Situation: - Customer name and account tier:{{customer_name}},{{account_tier}}- Customer contract value:{{contract_value}}- Issue description:{{issue_description}}- How long this has been ongoing:{{duration}}- Impact on the customer:{{customer_impact}}- What's been done to try to resolve it:{{attempted_resolution}}- Why it now requires executive attention:{{escalation_reason}}- Specific ask of the executive:{{executive_ask}}(e.g., "approve a service credit," "personally call the customer's COO," "prioritize engineering fix") - Risk if not addressed:{{risk}}(e.g., churn, PR risk, legal threat, strategic account damage) - Executive recipient:{{executive_name}},{{executive_title}}- Sender:{{sender_name}},{{sender_title}}Write an escalation email that: - Subject line: clear and specific — includes the customer name and the nature of the escalation - Is under 250 words - Opens with the situation summary — not with pleasantries - Presents facts, not emotions — no "the customer is very upset" (state observable facts instead: "the customer has submitted 3 escalated tickets in 7 days and threatened to cancel") - Includes a clear, specific ask — not "please advise" but a concrete action - States the risk of inaction in one sentence - Closes with the next step you're taking regardless of the executive's involvement Tone: professional peer communication, not a subordinate asking for help. You're briefing a decision-maker, not escalating up a chain of command.
Variables
{{{{customer_name}}}}Replace with your {{customer name}}{{{{account_tier}}}}Replace with your {{account tier}}{{{{contract_value}}}}Replace with your {{contract value}}{{{{issue_description}}}}Replace with your {{issue description}}{{{{duration}}}}Replace with your {{duration}}{{{{customer_impact}}}}Replace with your {{customer impact}}{{{{attempted_resolution}}}}Replace with your {{attempted resolution}}{{{{escalation_reason}}}}Replace with your {{escalation reason}}{{{{executive_ask}}}}Replace with your {{executive ask}}{{{{risk}}}}Replace with your {{risk}}{{{{executive_name}}}}Replace with your {{executive name}}{{{{executive_title}}}}Replace with your {{executive title}}{{{{sender_name}}}}Replace with your {{sender name}}{{{{sender_title}}}}Replace with your {{sender title}}
Example
Input
customer_name: Harlow Retail Group account_tier: Enterprise contract_value: $180,000/year issue_description: Signal anomaly detection has been generating false positive alerts for 5 days; customer team disabled the feature duration: 5 days customer_impact: customer's team has disabled Signal, which was the primary value driver for their Enterprise upgrade; they have no real-time ops monitoring while issue is unresolved attempted_resolution: tier-1 support exhausted all standard fixes (sensitivity adjustment, cache clear, data source check) with no resolution; escalated to engineering 2 days ago; engineering has not yet identified root cause escalation_reason: engineering escalation is not moving fast enough given the account value and relationship risk; customer has mentioned their upcoming renewal twice in the last 2 days executive_ask: ask the VP of Engineering to personally prioritize this fix with a 24-hour resolution commitment, and consider whether a personal call from you to Josephine (their VP of Ecommerce) would be warranted risk: churn and expansion loss ($180K ARR + potential $30K expansion); customer is actively questioning the value of their Enterprise upgrade executive_name: David executive_title: Chief Revenue Officer sender_name: Alicia Chen sender_title: Senior Customer Success Manager
Output
Subject: Executive escalation — Harlow Retail Group (Enterprise, $180K ARR) David, Briefing you on a situation that needs your attention today. **Harlow Retail Group** ($180K ARR, Enterprise) has had Signal anomaly detection generating false positive alerts for 5 days. Their team disabled the feature 2 days ago — Signal was the primary justification for their Enterprise upgrade. They currently have zero real-time ops monitoring. We escalated to engineering 2 days ago with no root cause identified yet. Standard remediation has been exhausted. Meanwhile, their VP of Ecommerce, Josephine Park, has mentioned their upcoming renewal (4 months out) twice in the last 2 days — unprompted. **My ask of you:** 1. Request that VP Engineering prioritize a 24-hour resolution commitment on this specific account 2. Consider a direct call to Josephine to acknowledge the situation at the executive level — this is the kind of gesture that changes a renewal conversation If this isn't resolved this week, I assess high churn probability at renewal, plus the $30K expansion conversation we had 2 weeks ago is effectively off the table. I'm sending Josephine an update today with a 24-hour engineering update commitment. I'll keep you posted. Alicia Chen Senior Customer Success Manager
Tips for best results
- 1The specific ask is the most important part of an escalation email. 'Please advise' is not an ask — it creates more work for the executive. 'Approve a $5K service credit' or 'call their COO this week' is an ask.
- 2State observable behaviors, not emotional states. 'The customer is very upset' is subjective. 'The customer mentioned their renewal unprompted twice in 2 days' is a fact — and more alarming.
- 3Include the contract value prominently. Executives calibrate their response to the financial stakes — make those stakes visible.
- 4End with what you're doing next regardless of their involvement. This shows you're managing the situation, not just escalating and waiting.
- 5Escalate earlier than feels comfortable. An escalation that comes after a churn is too late — the executive needed 72 hours to take action.
Related prompts
De-escalate an angry customer email thread
advancedGenerate a carefully calibrated response to an angry or hostile customer email that acknowledges their frustration, takes accountability, and redirects toward resolution.
Customer Servicede-escalationangry-customerescalation
Decide whether and how to escalate a support ticket
intermediateEvaluate a support ticket against a structured escalation framework and generate a recommended action with rationale.
Customer Serviceescalationsupport-processtriage
Write a customer-facing incident postmortem
advancedGenerate a clear, honest customer-facing incident postmortem that explains what happened, what was done, and what's changing — in plain language.
Customer Servicepostmortemincidenttransparency
Need help implementing this prompt in your workflow?
Book a call