wowprompt

Reopened tickets review with root causes and fixes

Reviews tickets that customers reopened or contacted about again, finds why the first answer did not solve the problem, and lists fixes to replies, macros, help articles and the product. Use it monthly, or when the reopen rate climbs and the team cannot say why.

A table of reopened tickets with the reason each reopened, a grouped count of root causes, and a prioritised fix list with owners
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Reopened or repeat-contact tickets: [paste ticket ID, topic, first reply and the customer's follow-up for each, 10 to 50 tickets]
  • Total tickets closed in the same period: [number]
  • Macros or help articles used in the first replies: [names or paste, if any]
  • Teams that can own a fix: [e.g. support, product, billing, logistics]

Task

Find why each ticket came back and what change would have closed it the first time.

Steps

  1. For each ticket, choose one root cause: answer incomplete, answer wrong, customer did not understand, promised action not done, product bug, policy gap, or customer changed request.
  2. Quote the line of the first reply, or the missing step, that caused the reopen.
  3. Group tickets by root cause and by topic.
  4. Work out the reopen rate: reopened tickets divided by tickets closed, shown as a percentage with the arithmetic.

Output format

  1. | Ticket | Topic | Root cause | Evidence from the reply | Fix |
  2. | Root cause | Count | Share of reopens | Topics most affected |
  3. Fixes in priority order: | Fix | Type: reply, macro, article, product, process | Owner | Tickets it would have prevented |
  4. Two rewritten replies for the most common case, before and after.

Rules

  • Judge only from the text given; mark a ticket "unclear" rather than guessing a cause.
  • Do not blame individual agents; describe what the reply or process lacked.
  • A fix must be specific enough to act on this week, such as a missing step added to a named macro.
reopened ticketsrepeat contactsfirst contact resolutionroot cause analysissupport qualityticket review

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