Fill in these first
- Ticket text or chat transcript: [paste, with personal details removed]
- Product area: [checkout, login, mobile app, billing, notifications]
- Platform and version: [web browser, Android or iOS version, app version]
- Number of customers affected so far: [count, or "one reported"]
- Workaround found: [describe, or "none"]
- Business deadline, if any: [sale date, contract date, or "none"]
Task
Write an escalation note that an engineer can pick up without reading the original ticket or asking support a follow-up question.
Output format
- Title: under 80 characters, naming the feature and the failure, for example "Saved cards missing at checkout on Android 3.4"
- Severity: S1 to S4 with a one-line justification
- S1: service down or money at risk
- S2: core feature broken, no workaround
- S3: feature broken, workaround exists
- S4: cosmetic or minor
- Summary: two sentences
- Steps to reproduce: numbered, starting from a logged-out state
- Expected result and actual result, as two labelled lines
- Environment: a short table with Field and Value
- Customer impact: who is affected, how often, and what it costs them
- Evidence: list of screenshots, error messages, or timestamps mentioned in the ticket
- Workaround to give customers meanwhile
- Open questions for engineering
Quality rules
- Separate what the customer reported from what support confirmed; label each.
- Quote error messages exactly as written in the ticket.
- Mark any step support could not reproduce as "Not reproduced by support".
- No customer names, emails, phone numbers, or payment details.
- No blame and no adjectives such as "terrible" or "urgent!!"; let severity carry the urgency.






