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
- 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.
- Quote the line of the first reply, or the missing step, that caused the reopen.
- Group tickets by root cause and by topic.
- Work out the reopen rate: reopened tickets divided by tickets closed, shown as a percentage with the arithmetic.
Output format
- | Ticket | Topic | Root cause | Evidence from the reply | Fix |
- | Root cause | Count | Share of reopens | Topics most affected |
- Fixes in priority order: | Fix | Type: reply, macro, article, product, process | Owner | Tickets it would have prevented |
- 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.






