Goal
Create a concise escalation brief that gives the receiving owner enough verified context to assess impact, make the requested decision, and continue customer communication.
Success Criteria
- Customer impact, severity, scope, and timeline are stated factually.
- Verified facts, customer claims, hypotheses, and unknowns are separated.
- Actions already taken and their results are complete.
- The requested decision, owner, urgency, and next communication are explicit.
Inputs
- Customer message and relevant interaction history
- Account, product, order, or incident facts
- Timeline, reproduction evidence, logs, and screenshots
- Troubleshooting or remedies already attempted
- Applicable policy, service level, and escalation criteria
- Current owner, receiving team, and communication commitments
Constraints
- Include only customer data necessary for the escalation.
- Do not assign blame, speculate about root cause, or promise an outcome.
- Do not relabel severity to create urgency.
- Preserve exact customer commitments and approved timelines.
Instructions
- Summarize the customer, issue, business impact, scope, and current status.
- Build a chronological timeline of reports, evidence, actions, and responses.
- Separate confirmed facts, customer-reported facts, hypotheses, and unknowns.
- List troubleshooting and remedies attempted with their observed results.
- State the escalation trigger and the precise decision or action needed.
- Assign the next owner and draft the next customer update using approved facts.
- Record follow-up timing, dependencies, and closure evidence.
Output
- Escalation summary
- Customer impact and severity evidence
- Timeline
- Facts, hypotheses, and unknowns
- Actions taken and results
- Decision or action requested
- Ownership and customer communication plan
Quality Check
Confirm that the brief can be understood without reading the full ticket, every severity claim has evidence, unnecessary customer data is removed, and the receiving owner knows the next decision.
Stop Rules
Immediately route safety, security, privacy, legal, regulatory, or threat concerns through the approved path. Do not authorize compensation, disclose internal findings, or make customer commitments.