Escalation Summary

Goal

Produce a concise internal escalation brief that captures business impact, issue timeline, current blockers, and a specific ask for each team that needs to act.

Trigger

When a customer issue requires cross-functional action and needs to be escalated internally with clarity and urgency.

Steps

1. 1

   Using your connected tools (for example the support ticket system, CRM account record, call transcripts, and recent email threads), gather everything relevant to $customer: open tickets, reported symptoms, account tier, revenue at risk, and any prior communications about this issue. If a needed tool isn't connected, ask the user to paste what's available.

   • □Account tier and ARR or revenue impact identified
   • □All relevant tickets or case numbers located
   • □Recent communications reviewed for context
2. 2

   Construct a precise timeline of the issue: when it was first reported, key escalation moments, any workarounds attempted, and current status. Flag how long the customer has been blocked and whether any SLA or renewal date is at risk.

   • □First reported date and current duration captured
   • □Workarounds or partial fixes noted
   • □SLA breach or renewal risk flagged if applicable
3. 3

   Summarize the customer-facing business impact in concrete terms: which workflows or users are affected, what the customer cannot do right now, and the downstream consequences if unresolved (churn risk, executive escalation, public exposure, etc.).

   • □Impact is stated in customer business terms, not just technical symptoms
   • □Scope of affected users or processes quantified where possible
   • □Churn or relationship risk level stated explicitly
4. 4

   Identify every internal team that must act to resolve or mitigate the issue (e.g. Engineering, Support, Product, Legal, Customer Success, Executive Sponsor). For each team, write one specific, time-bound ask — what they need to do, by when, and what decision or output is expected from them.

   • □Every blocking team is named
   • □Each ask is specific and time-bound
   • □No team has a vague or duplicate ask
5. 5

   Assemble the final escalation brief with these clearly labeled sections: (1) Executive Summary (2–3 sentences), (2) Customer Impact, (3) Issue Timeline, (4) What Is Blocked, (5) Team Asks, and (6) Recommended Next Step with a proposed owner and deadline.

   • □All six sections present and clearly labeled
   • □Brief is self-contained — a reader with no prior context can act on it
   • □Tone is factual and urgent without being alarmist

Output format

A structured escalation brief with six labeled sections: Executive Summary, Customer Impact, Issue Timeline, What Is Blocked, Team Asks (one bullet per team with a specific time-bound request), and Recommended Next Step. Written in clear, direct internal prose. Length should be scannable in under 2 minutes — no more than one page equivalent.