Last updated: Jun 19, 2026
Ticket Reopen Rate (RR) is the percentage of resolved support tickets that customers reopen, signalling the issue was not fully resolved. Tracking this metric gives support teams a direct measure of resolution quality. A rising reopen rate can point to gaps in agent training, product knowledge, or escalation processes. Left unaddressed, it erodes customer trust and increases support volume.
Alternate names: Reopen RateOver a given week, a technical support team resolves 450 tickets. During the same period, 25 of those tickets are reopened by customers.
25 / 450 = 0.055, or 5.5%
A 5.5% reopen rate means roughly 1 in 18 resolved tickets required a second look — a useful signal for coaching conversations and process reviews.
Use PowerMetrics, modern analytics platform, to monitor your data. Choose a service below to start tracking your Ticket Reopen Rate instantly.
A 2022 survey of 260 companies by Endsight found that 3.1% of tickets are reopened on average. Teams handling complex technical issues or enterprise accounts will typically see higher rates than those managing simple transactional queries. Use this as a directional baseline and track your own trend over time.
Ticket Reopen Rate is a lagging indicator of resolution quality. It does not tell you why a ticket was reopened, but it tells you that something in the resolution process fell short. That makes it a valuable diagnostic tool when paired with other metrics.
Paired with Customer Satisfaction Score (CSAT): A high reopen rate alongside low CSAT scores confirms a systemic resolution problem. If reopen rate is high but CSAT is average, customers may be accepting poor resolutions without pushing back initially.
Paired with First Contact Resolution (FCR): FCR measures whether an issue is resolved on first contact. Reopen Rate measures whether the resolution holds. Together, they give a fuller picture of resolution effectiveness.
Paired with Average Handle Time (AHT): If agents are closing tickets quickly and reopen rates are climbing, speed may be coming at the cost of thoroughness.
Reducing reopen rate requires understanding why tickets are being reopened in the first place. Auditing a sample of reopened tickets from the original inquiry through to resolution is the most direct starting point.
Audit reopened tickets systematically. Look for patterns: Are reopened tickets clustered around a specific product area, agent, or shift? Are customers reopening because the fix did not work, or because they did not understand the instructions?
Use post-ticket surveys. If your support platform includes a post-resolution survey, review free-form responses from customers who reopened tickets. Customers often describe exactly what fell short.
Segment by agent, tenure, and time of day. A team-level reopen rate can mask wide variation at the individual level. Newer agents may reopen more tickets than experienced ones, or certain shifts may be closing tickets too quickly under volume pressure.
Invest in agent training. Train agents on root cause analysis, not just symptom resolution. Agents who understand the product deeply and can anticipate follow-up questions are less likely to generate reopened tickets.
Review ticket closure criteria. If agents can mark tickets as solved without customer confirmation, consider adding a confirmation step or a short waiting period before auto-closure. Many reopen events happen because a ticket was closed prematurely.
Use automation to prioritize, not just close. Automation that routes high-complexity tickets to senior agents, or flags tickets that match common reopen patterns, can reduce the rate more effectively than blanket speed targets.
Inconsistent closure practices distort comparisons across agents or teams. Standardize what "solved" means before drawing conclusions from the data.
Some platforms count both customer-initiated and agent-initiated reopens together. Distinguish between the two: a customer reopening a ticket signals unresolved dissatisfaction, while an agent reopening one may reflect a workflow correction.
A ticket reopened weeks after resolution still counts. If your reporting window is too narrow, you may undercount reopens and underestimate the true rate.
If agents are evaluated on reopen rate, some may delay closure or create new tickets instead of reopening old ones. Monitor for unusual spikes in new ticket volume alongside a falling reopen rate.
Ticket Reopen Rate (RR) is the percentage of resolved support tickets that customers reopen. It is calculated by dividing the count of tickets reopened by the count of tickets solved.
A 2022 survey of 260 companies by Endsight found an average reopen rate of 3.1%. Teams handling complex or technical issues typically see higher rates. Use this as a directional baseline and focus on tracking your own trend over time.
Audit reopened tickets to identify patterns, use post-ticket surveys to capture customer feedback, segment results by agent and shift, train agents on root cause analysis, and review your ticket closure criteria to prevent premature closures.
