Use reopen rate as a quality signal
Reopen rate and reopened tickets tell you how often solved tickets come back. That’s a quality signal: high or rising reopen rate often means premature “solved,” wrong solution, or handoff issues. This guide covers what to measure, how to read it, and what to do when reopens spike.
What reopen rate means
Reopen rate is the proportion of tickets that are reopened after being solved (or closed). Reopened tickets is the count. Definitions can vary (e.g. reopened by customer vs by agent; within 7 days vs ever). Pick a definition, document it, and use it in all reports. See the glossary for reopen rate and customer reopen rate if you track by requester.
Why tickets reopen (root causes)
- Solved too early — Agent marked solved before the customer confirmed or before the fix was verified.
- Wrong or incomplete fix — The solution didn’t address the root cause.
- Handoff or process — Ticket was reassigned or bounced; the next agent didn’t have context.
- Customer expectation — Customer disagrees that the issue is resolved or has a follow-up; some reopens are valid.
Understanding which of these dominates (e.g. by tag, group, or time) helps you fix the right thing. For more on quality signals, see support metrics dashboard and support ops metrics.
What to put on a reopen dashboard
- Reopen rate — Percentage (or count) of tickets reopened in the period. Compare to last period so you see trend.
- Reopened tickets count — Absolute number; useful alongside volume so you see if reopens are growing.
- Breakdown — By group, tag, or assignee so you can see where reopens concentrate.
Link this to your support metrics dashboard and review it with resolution time and first reply time so you get the full picture (speed + quality).
How to reduce avoidable reopens
- Definition of “solved” — Align on when a ticket is truly solved (e.g. customer confirmed, or fix verified). Train and remind agents.
- Quality checks — Sample solved tickets for correctness and completeness before considering the case closed.
- Handoffs — When tickets move between agents or groups, ensure context is passed (internal notes, tags, summary).
- Knowledge and process — If certain tags have high reopen rate, improve articles, macros, or escalation so the right fix is applied the first time.
- Drill to tickets — Use a view of reopened tickets (by tag, group, or time) to spot patterns and coach or fix process.
For more on resolution and quality, see Zendesk resolution time report and support dashboard template.
Common mistakes
- Treating all reopens as bad — Some reopens are valid (e.g. follow-up questions). Track trend and segment; focus on avoidable reopens.
- No breakdown — A single reopen rate hides where the problem is. Segment by tag, group, or assignee.
- Ignoring reopens in resolution time — Full resolution time (to final close) includes time after reopens. If reopen rate goes up, resolution time can too. See resolution time.
FAQ
What’s a good reopen rate?
It depends on your product and process. What matters is trend: stable or decreasing is usually good; a sudden rise is a signal to investigate.
How do I report reopen rate in Zendesk?
Zendesk Explore can report on ticket lifecycle (solved → reopened). You need a metric that counts tickets that were solved and then reopened in the period (or a ratio of reopened to solved). Exact steps depend on your dataset; the idea is: count reopens, divide by solved (or total closed) in the same period, and show over time and by segment.
Where does reopen rate fit in our weekly review?
After volume, backlog, first reply, and resolution time. Use it as the quality beat in your support metrics dashboard or support dashboard template.