Escalation Summary
Summarise a support case for escalation: the timeline, customer impact, what's been tried, the evidence and the decision needed from the next team.
- customer-support
- service
- operations
- intermediate
The prompt
Summarise this support case for escalation to ESCALATING TO, so they can understand it in two minutes and decide without reading the whole thread. Use this: - The case history, with dates: CASE HISTORY - Who is affected and how badly: CUSTOMER IMPACT - Evidence I have, such as logs, screenshots, error messages or ticket links: EVIDENCE - The decision or action I need from them: DECISION NEEDED Write, under 250 words, in this order: 1. Subject line: the product area, the problem and its severity, under 12 words. 2. The ask: one sentence saying what I need from them and by when. 3. Impact: how many customers or accounts are affected, any contract or revenue risk I've mentioned, and any deadline. 4. Timeline: 3-6 dated bullets from the first report to now. 5. Tried so far: what support did and what happened each time. 6. Evidence: what's attached and what each item shows. 7. Open questions: what we still don't know. Rules: - Keep facts and guesses apart; mark anything not confirmed as "unconfirmed". - Don't overstate severity to get attention; if the impact is unknown, say so. - Leave out customer names, emails and payment details unless the receiving team needs them to act; use ticket or account IDs.
Fill in the blanks
Type your details to see them in the prompt above, then copy it. What you type stays in this tab: it isn't saved or sent anywhere.
Example
- ESCALATING TO
- Engineering on-call, payments team
- CASE HISTORY
- 3 Oct: customer reports invoices stuck on "processing". 4 Oct: reproduced on two test accounts. 6 Oct: manual resend workaround stopped working.
- CUSTOMER IMPACT
- 14 accounts on the Pro plan can't send invoices; one says they'll cancel if it isn't fixed by Friday
- EVIDENCE
- Error ID INV-502 in the browser console, a screen recording, the list of affected account IDs
- DECISION NEEDED
- Confirm whether this is a known bug and give an estimate, or approve a manual workaround
How to use it
- Fill in the blanks above, or paste the prompt into your AI chat and replace the words in capitals there. How blanks work
- Save it to your library to use it again. Your copy keeps the blanks, so next time you only fill them in.
- Use it where you chat. With the Save My Prompts extension, pick the prompt inside ChatGPT, Claude or Gemini and fill the blanks there.
Related prompts
- Support Case Handoff Note
Hand an open support case to the next shift or tier 2 with what's been tried, where it stands, the next step and how the customer is feeling.
- Support Ticket Triage
Sort a batch of support tickets by issue, urgency, customer impact and the team that should take them, flagging missing data and safety cases.
- Empathetic Support Reply
Reply to a customer's issue with empathy, a clear answer and practical next steps, without promising anything beyond what your policy allows.
- Refund Policy Explanation
Explain a refund decision to one customer in plain words, saying what they get or don't, why, what happens next, with a respectful close.
- Service Outage Update
Draft a status update during an outage with confirmed facts, the current action, the impact on customers and when the next update will come.
- De-Escalation Response Coach
Get calm reply options for an upset customer's message that acknowledge what went wrong for them and set respectful boundaries where needed.