wowprompt

Escalation note from support to the engineering team

A structured bug escalation that turns a customer complaint into steps to reproduce, impact, and evidence an engineer can act on. Use it when a support ticket points to a product fault that agents cannot fix themselves.

An engineering escalation note with a one-line summary, severity, reproduction steps, expected and actual results, and customer impact
The output this prompt produced, unedited.

The prompt

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

  1. Title: under 80 characters, naming the feature and the failure, for example "Saved cards missing at checkout on Android 3.4"
  2. 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
  1. Summary: two sentences
  2. Steps to reproduce: numbered, starting from a logged-out state
  3. Expected result and actual result, as two labelled lines
  4. Environment: a short table with Field and Value
  5. Customer impact: who is affected, how often, and what it costs them
  6. Evidence: list of screenshots, error messages, or timestamps mentioned in the ticket
  7. Workaround to give customers meanwhile
  8. 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.
bug escalation templatesupport to engineering handoffbug report from ticketescalation notesteps to reproduce

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity