A customer submits a ticket asking for help with their monthly bill. The agent sends a link to an article covering common billing questions, then marks the ticket as solved. The customer reads the article but it doesn't resolve their specific issue, so they write back to support. The ticket reopens. This ticket now has a Ticket Reopens count of 1.
Ticket Reopens
Last updated: Aug 17, 2026
What is Ticket Reopens?
Ticket Reopens is a count of how many times closed support tickets are reopened after a customer responds with an unresolved issue. When a customer replies to a ticket marked as solved, the ticket automatically reopens and receives an open status. Each reopen increments the count by one. A high Ticket Reopens count signals that resolutions aren't sticking — either because agents are closing tickets prematurely or because the underlying issue isn't being fully addressed.
Ticket Reopens Formula
ƒ Count(Ticket Reopens)
How to calculate Ticket Reopens
Start tracking your Ticket Reopens data
Use PowerMetrics, modern analytics platform, to monitor your data. Choose a service below to start tracking your Ticket Reopens instantly.
More about Ticket Reopens
Why Ticket Reopens matter
A reopen isn't just an inconvenience. It means a customer had to reach out again, wait again, and explain their problem again. That erodes trust and increases support costs.
Tracking Ticket Reopens helps support leaders identify two distinct problems:
- Agent behaviour: Tickets closed before the customer's question is fully resolved
- Product or content gaps: Answers that are technically correct but don't solve the real problem
Both drive dissatisfaction. Monitoring this metric alongside Customer Satisfaction Score (CSAT) and First Contact Resolution (FCR) gives a more complete picture of support quality.
How to reduce Ticket Reopens
Reducing reopens requires changes across training, content, and process.
Improve agent resolution practices. Agents should confirm resolution before closing a ticket — not assume it. A brief closing message that asks "Does this fully resolve your issue?" can catch gaps before the ticket is marked solved. Regular quality reviews of reopened tickets reveal patterns in how agents are handling common query types.
Strengthen your self-service content. Many reopens happen when a customer is sent to a knowledge base article that doesn't actually answer their specific question. Audit your FAQ and help content regularly. If the same question keeps generating reopens, the article needs to be rewritten or expanded.
Review your product and service experience. Recurring reopens on the same topic — billing, onboarding, a specific feature — often point to a product or process issue, not a support issue. Use reopen data to flag these themes for product and operations teams.
Track patterns over time. Log reopened tickets by category, agent, and issue type. Over time, this data reveals whether reopens are concentrated in specific areas, making it easier to target improvements rather than applying broad fixes.
Ticket Reopens Frequently Asked Questions
What does a high Ticket Reopens count indicate?
A high Ticket Reopens count typically means tickets are being closed before the customer's issue is fully resolved, or that self-service content isn't answering the real question. It can also point to a recurring product or service problem driving repeated contacts.
How is Ticket Reopens different from First Contact Resolution?
First Contact Resolution (FCR) measures whether an issue is resolved on the first interaction. Ticket Reopens measures how many times a previously closed ticket is reopened. A ticket can pass FCR checks but still generate reopens if the customer returns with the same unresolved issue.
Contributor
