Escalation summary for engineering or management

Condense a long, messy ticket history into a crisp escalation note with impact, timeline, what has been tried and what you need.

Change note: Initial version

Prompt

Write an escalation summary from the ticket history below so the receiving team can act without reading the whole thread.

Escalating to: {{recipient}}
Ticket history:
{{history}}

Customer and account context: {{context}}
Urgency: {{urgency}}

Format (use these exact headings, keep the whole note under 250 words):
**One-line summary**: what is broken, for whom, since when.
**Customer impact**: business and emotional impact, in concrete terms.
**Timeline**: dated bullet list of key events only.
**Already tried**: actions and results so far.
**Evidence**: error messages, IDs, steps to reproduce, links or attachments mentioned in the history.
**The ask**: the specific decision or action needed, and by when.
**Open questions / unknowns**: things we do not yet know.

Rules: state facts, not opinions about the customer; separate confirmed facts from guesses by labelling guesses "unconfirmed"; do not invent IDs, dates or error text. If a required item is missing from the history, write "not provided".

Variables

• {{recipient}}Escalating toselectrequired

  Options: Engineering, Billing / Finance, Customer success manager, Support management, Legal / Compliance

  Default: Engineering

• {{history}}Ticket historylongrequired

  Default: Mar 4: Customer reports CSV export hangs at 90%. Mar 5: Agent asked for file size, 40k rows. Mar 6: Tried again, same result; error 'timeout 504'. Mar 7: Customer says month-end reporting is due Mar 10 and they have exported manually 3 times. Mar 8: Agent tried exporting smaller date ranges; works under 10k rows.

  Paste the messages or notes in order

• {{context}}Account contexttextrequired

  Default: Enterprise plan, 85 seats, renewal in 6 weeks

• {{urgency}}Urgencyselectrequired

  Options: Low, Normal, High, Critical

  Default: High

Example output

**One-line summary:** CSV export of ~40k rows times out (504) for an Enterprise customer since Mar 4; exports under 10k rows work.

**Customer impact:** Month-end reporting is due Mar 10. The team has been exporting manually; 85-seat account renews in 6 weeks.

**Timeline**
- Mar 4: export hangs at 90%.
- Mar 6: reproduced, 504 timeout.
- Mar 8: workaround confirmed for ranges under 10k rows.

**Already tried:** Repeat exports; smaller date ranges (works under 10k rows).

**Evidence:** Error "timeout 504"; file size about 40,000 rows. Account ID: not provided.

**The ask:** Investigate the large-export timeout, or raise the limit for this account, before Mar 10.

**Open questions:** Does it affect other accounts (unconfirmed)? Exact export endpoint: not provided.

Notes

A fixed template with a 'The ask' section means the receiver knows exactly what is needed and by when. The 'not provided' rule exposes gaps you can fill before sending rather than hiding them.