Support metric guide
Ticket reopen rate explained
Measure the proportion of solved support tickets that reopen, distinguish unique tickets from reopen events and use the cases to improve lasting resolutions.
Define the solved cohort, reopen window and whether customer replies trigger reopens.
Distinguish reopened tickets from the number of reopen events.
Pair the rate with full resolution time and customer feedback.
Product shortlist
Tools for tracking reopens
Test whether each product reports unique reopened tickets, repeat reopen events and the automation or status change that caused them.
Zendesk
Best for: Teams that expect multiple channels, mature routing and increasing operational complexity
The Support Team plan supplies core email ticketing, routing, analytics and automations. The broader Suite adds live chat, messaging, telephony and a knowledge base.
£15 per agent/monthSupport Team, paid yearly; checked September 2026
Useful strengths
- GBP pricing and a clear entry ticketing plan
- Strong upgrade path for multichannel operations
Watch for
- Suite Team rises to £45 per agent/month
- Small teams may buy more process than they need
- 14-day trial
- GBP pricing available
- Per-agent pricing
Freshdesk
Best for: Growing teams that need proper ticketing, self-service, automation and reporting
A broad email-first help desk with ticketing, a shared inbox, a customer portal, knowledge base and out-of-the-box reporting on its entry paid plan.
$19 per agent/monthGrowth, billed annually; checked September 2026
Useful strengths
- Ticketing, shared inbox and knowledge base on Growth
- Clearer route into routing, SLAs and custom reporting
Watch for
- Omnichannel needs differ from the email-first Freshdesk plan
- AI and connector usage can add cost
- Free trial
- Email-first help desk
- Per-agent pricing
Zoho Desk
Best for: Budget-conscious teams and businesses already using the Zoho ecosystem
The free edition covers three users and email ticketing. Paid tiers add broader messaging, knowledge-base, reporting, automation and telephony capabilities in stages.
Free for 3 usersPaid plans vary by selected billing currency; checked September 2026
Useful strengths
- Three-user free edition
- Broad channel and Zoho integration range
Watch for
- Plan and currency selectors make budgeting less immediate
- Live chat and advanced routing are plan-dependent
- 15-day trial
- Free edition
- Three users on free plan
Gorgias
Best for: Online shops that need order context and ecommerce actions inside support conversations
Unlike per-seat tools, Gorgias prices its help desk by billable ticket volume. Its strongest case is the depth of its Shopify and ecommerce workflow integrations.
$10/month for 50 ticketsStarter includes 3 agent seats; checked September 2026
Useful strengths
- Deep Shopify order context and actions
- Costs scale by tickets rather than only by agent seats
Watch for
- Overages and AI resolutions need modelling
- Entry plan is email-only and has limited operations features
- 7-day trial
- Shopify-focused
- Ticket-volume pricing
A reopened support ticket is a case that was marked solved and later returned to active work. A rise in reopens may reveal incomplete answers, a broken automation or simply a product change that made follow-up easier. Treat it as a quality signal to investigate, not a league-table score.
Zendesk defines reopened tickets as tickets reopened after being solved, while “reopens” counts the number of times the status moved out of solved. Those are different numerators. A ticket reopened three times contributes one unique ticket but three events.
Choose a cohort-based formula
For a stable rate, use unique tickets solved in a defined period that reopened within a fixed follow-up window ÷ all tickets solved in that period × 100. For example, if 200 tickets were solved during a week and 12 of those reopened within the next seven days, the seven-day cohort reopen rate is 6%. Do not publish that cohort before all 200 cases have had the full seven days to reopen.
Another dashboard may divide reopened tickets observed this week by tickets solved this week. That is easy to display but mixes different cohorts: the reopen may belong to a case solved months ago. Label it as a weekly operational ratio if you use it. Never compare two rates until the denominator, window and status rules match.
Check what triggers the reopen
Read a sample by reason. Did the proposed fix fail? Was the customer asked to confirm an action that never happened? Did an automatic rule close a ticket after a short period of silence? Did the customer ask a new but related question? Did a specialist handoff lose the original context? Distinguish legitimate follow-up from a failed resolution, and keep both visible.
Zendesk's reporting recipe shows a way to count reopened tickets; it is a tool-specific report, not an editorial definition of a cross-platform rate. Test a case in your own system, including a customer reply after solve and a same-update status change. Status automation can affect which events appear.
Fix the cause, not the number
If reopens follow incorrect macros, revise the answer and add a final check before solving. If they follow a supplier handoff, keep support ownership and a promised update. If they follow premature auto-closure, adjust the rule and keep pending cases visible. If they are actually new questions, consider a clear new-ticket rule and explain it to agents so reporting remains consistent.
Pair the rate with full resolution time, repeat contacts and CSAT. A low reopen rate with high repeat contact may simply mean customers are creating fresh tickets. A high rate during a complex incident may reflect honest continuing ownership, not worse service. Use actual conversations to make the call.
Review the distribution by issue reason and closure route rather than announcing one team-wide target. If most reopens follow an automatic closure after customer silence, test a longer reminder sequence and a clearer explanation of how to resume the case. If reopens cluster around refunds, check whether the refund was actually completed before the ticket was solved. Sample both reopened and never-reopened tickets: some customers may give up or start over instead of replying to the original thread.
Record the action and compare the same cohort window later. Changing a seven-day window to thirty days will naturally find more returns; changing how tickets are merged can move the rate as well. Keep the measurement rule stable while you evaluate a workflow change.
Sources
- Zendesk: Support metric definitions
- Zendesk: reporting reopened tickets
- Freshdesk: ticket volume trends
The cohort formula and improvement framework are Support Sorted's editorial guidance.
Frequently asked questions
Questions readers ask before choosing
How do you calculate ticket reopen rate?
One defensible version is unique tickets from a solved cohort that reopen within a fixed window divided by all tickets in that solved cohort, multiplied by 100. State the window and exclusions.
Is a reopened ticket the same as a reopen event?
No. One ticket can reopen several times. A unique-ticket rate and an event count answer different questions and should not be mixed.
Does every reopen mean an agent made a mistake?
No. A customer may add a related but new question, an automatic closure may fire, or a third party may change the outcome. Read the ticket before assigning cause.
Can a reopen rate be too low?
A very low rate is not proof of quality if customers start new tickets instead of reopening, or the system closes cases permanently. Watch repeat contact and CSAT as well.