Escalation Summary

Goal

Transform a raw customer issue report into a clear internal escalation brief that communicates business impact, timeline of events, what is blocked, and the specific ask of each involved team.

Trigger

When a customer issue requires cross-team escalation and stakeholders need a concise, actionable brief to coordinate a response.

Steps

1. 1

   Analyze the customer issue below and extract all key facts before writing anything: $customer_issue

   • □Identify the affected customer(s) and account tier
   • □Note when the issue was first reported or detected
   • □Capture any symptoms, error messages, or behaviors mentioned
2. 2

   Assess and articulate the business impact. Quantify where possible: revenue at risk, number of users affected, SLA breach risk, or reputational exposure. Assign a severity level (P1–P4) with a one-sentence justification.

   • □Impact is quantified or clearly scoped
   • □Severity level is assigned and justified
3. 3

   Reconstruct the timeline of events in chronological order. Include when the issue started, when it was reported, key investigation milestones, and any customer-facing communications that have already occurred.

   • □Timeline entries are timestamped or relatively dated
   • □Customer communications are flagged separately
4. 4

   Identify what is currently blocked: decisions that cannot be made, work that cannot proceed, or commitments that cannot be met until this issue is resolved. Be explicit about dependencies.

   • □Each blocker is tied to a specific outcome or team
   • □Dependencies between blockers are noted if they exist
5. 5

   Define the specific ask for each team involved (e.g., Engineering, Support, Customer Success, Legal, Leadership). Each ask must include a clear action verb, a deliverable, and a requested response time or deadline.

   • □Every team has exactly one focused ask
   • □Each ask has a deadline or urgency indicator
   • □Asks are written as actionable directives, not open questions
6. 6

   Compose the final escalation brief as a single cohesive document. Open with a two-sentence executive summary, then present each section in order: Impact & Severity, Timeline, What Is Blocked, Team Asks. Close with the escalation owner's name placeholder and next check-in time.

   • □Executive summary stands alone for a reader with no context
   • □All sections are present and consistently formatted
   • □Document is scannable in under 60 seconds

Output format

Deliver a structured escalation brief with clearly labeled sections: (1) Executive Summary — 2 sentences max, (2) Impact & Severity — severity level + quantified scope, (3) Timeline — chronological bullet list, (4) What Is Blocked — bulleted blockers with owners, (5) Team Asks — one action-oriented ask per team in a table or labeled list with deadlines. Use plain, direct language suitable for a Slack post or email to senior stakeholders.