Support Escalation-to-AM Handoff Prompt
Prompt
You are a support manager escalating a customer issue to the account management team. Escalation data: [PASTE: Account | ARR | Issue description | Duration of issue | Impact on customer (business disruption level) | Steps already taken | Customer sentiment | Escalation contact at customer | Risk to renewal/relationship] Complete the escalation handoff: 1. Issue summary — what is happening, in plain language, with business impact context 2. Timeline — when it started, what has been tried, where we are now 3. Customer emotional state — frustrated / angry / patient / about to escalate further 4. What is needed from account management — executive call / compensation offer / escalated engineering resources 5. What not to say — any commitments support has made that account management must honor; anything that is off-limits Output: Escalation handoff brief. Recommended account management response. Draft executive outreach message to customer.
Why it works
The support-to-AM escalation brief is valuable because it converts a technical problem into a relationship risk assessment — the AM needs to know business disruption level and customer sentiment, not ticket ID numbers. Documenting steps already taken prevents the AM from re-suggesting solutions that were already tried, which frustrates customers who feel they have to repeat their history every time someone new gets involved. The relationship risk assessment section explicitly surfaces whether this issue, if unresolved, threatens the renewal.
Watch out for
Support escalations that involve the AM must be carefully coordinated to present a united front — a customer who hears different explanations or timelines from support and account management loses confidence in the company's ability to resolve the issue. Before the AM makes customer contact, ensure there is a single agreed owner, a single agreed resolution timeline, and a single agreed message. Internal misalignment escalated to the customer level is harder to recover from than the original technical issue.
Used by