Escalation Brief

GPTClaudeDeepSeek··▲ 1,162 copies·updated 2026-07-14

escalation-brief.prompt

---
title: Support — Escalation Brief
owner: unassigned
status: populated
volatility: stable
last_reviewed: 2026-06-28
inject_into: [support-workflows]
tokens_approx: 0
---

# Support — Escalation Brief

Task: produce an internal escalation brief when a ticket needs a tech dispatch or management attention. Internal register, fast to read.

## Fields

- **Account + plan:** who, and which service plan governs the response path.
- **Issue class + impact:** down / degraded; revenue or guest-experience impact.
- **What's been tried:** first-line checks already done, with outcomes.
- **Why escalating:** the specific reason first-line can't resolve it.
- **Requested action:** dispatch, parts, or decision needed — and by when per the account's contracted path.

## Rules

- State the contracted response path; never invent an SLA number (RULE-02).
- Distinguish confirmed facts from reported symptoms.
- Flag any gap with `[REVIEW: ...]`.
- Be specific about the ask — escalations fail on vagueness.

when to use it

Community prompt sourced from the open-source GitHub repo matthewjbis/context-kit (no explicit license). A "Escalation Brief" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.