Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Agent |
Reopens are the closest thing support has to a quality measure, and the one most teams never build.
Build it
- Ticket updates dataset, because this is about status history.
- Metric: tickets that went from solved back to open.
- Attribute: by month, and by group.
- Show it as a share of tickets solved, not as a count.
Why it is the honest number
A reopen means the customer was told the matter was finished and did not agree. No survey, no sampling, no goodwill effects: they came back.
That makes it harder to game than satisfaction and more meaningful than volume.
Read it as a share
Reopens rise with volume. As a percentage of solves it stays comparable month to month, which is what you need to see whether anything changed.
Where they cluster
- One subject. The article or the process behind it is wrong.
- One agent. Usually closing too early rather than answering badly, and that is coachable.
- One customer type. Often an expectation set somewhere else in the business.
Some reopens are fine
A customer replying "thanks, one more thing" reopens a ticket and nothing went wrong. Where that is common, count only reopens within a short window after solving, which is much closer to what you actually mean.
Watch it against speed
Pushing resolution times down usually pushes reopens up. Those two on one chart show whether faster is actually better, and that is a conversation worth having with real numbers.
Comments
0 comments
Article is closed for comments.