Reopened Tickets
The ticket was closed on Tuesday with a note that said the mapped drive was back. On Wednesday the user replied "It's gone again", and the ticket reopened itself. The tool counted it and the technician took it personally. The reopen was not an insult. It was the cheapest piece of quality information the desk gets all week: a user telling you, for free, that the fix did not hold. It arrived within a day of the close, on the same ticket, with the whole history attached. Most desks treat reopens as a score to keep low. The useful desks treat them as a report to read.
This series is about reading it. It covers what a reopen is telling you and the four kinds of reopen, one of which is a thank-you. It covers measuring reopens honestly, by category before by agent. It covers the root causes behind them, from the premature close to the workaround mistaken for a fix. Then comes handling a reopened ticket well, without starting from zero. It covers preventing reopens with a verification step and a confirmation window. And it covers the weekly reopen review that feeds problem management. A reopen rate of zero is not a target. It is a sign that replies are not reopening tickets, which is worse.
Articles in This Series
- What a Reopen Is Telling You About Your Desk
The reopen as a signal, not an insult; and the four kinds: not fixed, fixed then broke again, a different problem, a thank-you. Covers why the rate matters more than any one case, and a classification card. - Measuring Reopens Honestly Without Fooling Yourself
The definition, the window, the thank-you problem, by category before by agent, what a rising rate means, and the metric definition to write down. - The Root Causes Behind Reopens and the Fix for Each
Premature close, no verification, a workaround mistaken for a fix, the wrong problem solved, a communication gap, and a cause table with the fix for each. - Handling a Reopened Ticket Well, Without Starting Over
Acknowledge, do not restart from zero, same owner where possible, the second reopen goes up, and the reopen acknowledgment reply. - Preventing Reopens with a Check Before the Close
Verification before closing, the confirmation window, the fix-check question, updating the knowledge base, and a pre-close verification checklist. - The Reopen Review: Turning Reopens Into Fixes
The weekly look at reopened tickets, finding the pattern, feeding problem management, and the review sheet.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.