Core metrics

What is reopen rate?

Also known as: ticket reopen rate, reopened tickets, ticket reopens, reopen ratio

Published September 10, 2026 · Last updated September 28, 2026 · Reviewed by the Fidiora team

Definition

Reopen rate is the share of tickets marked resolved that are subsequently reopened, either by the customer replying or by a new contact about the same issue. It is the cheapest available check on whether your resolution numbers describe reality.

Why it matters

Every support metric that can be gamed is disciplined by reopen rate. Fast handle times, high resolution rates, and impressive automation numbers all become suspect if reopens rise alongside them. It is the metric that makes the others trustworthy, and almost nobody puts it on the dashboard.

What to know

Count cross-channel reopens. A resolved chat followed by an email about the same issue is a reopen.
Set a window, usually seven to fourteen days, and keep it fixed so the number stays comparable.
Reopen rate by topic points precisely at where your documentation or process is failing.
Reopens on AI-resolved contacts should be tracked separately from reopens on human-resolved ones.
A low reopen rate combined with low satisfaction usually means customers gave up rather than came back.
Worked example: 1,000 tickets resolved in a month, 60 reopened within fourteen days. Reopen rate is 60 / 1,000 x 100 = 6 percent. Your own trend matters more than any single figure.

How to calculate it

Reopen rate = (tickets reopened within the window / tickets resolved) x 100

An example

Example: an automation programme reports resolution rate rising from fifty to seventy percent. Reopen rate rises from four to fifteen percent over the same period. The real resolution rate barely moved and the customer experience got worse.

Common causes of ticket reopens

Most reopens trace back to one of these five causes, and each has a different fix.
Cause	What it looks like	Fix
Incomplete first answer	The customer replies with a follow-up question on the same issue	Rewrite the article or macro to cover the next step
Closed too early	The ticket closed before the customer confirmed the fix worked	Use a pending state with an automatic close window
Wrong diagnosis	The answer addressed a different problem	Better triage and a clarifying question before answering
Dependency not finished	A promised fix from engineering or billing never landed	Link the ticket to the internal task and update the customer proactively
Reply to a closed thread	A thank-you or an unrelated question reopens the ticket	Exclude courtesy replies and split unrelated questions into new tickets

Common mistakes

Not tracking reopens at all, which is the most common state
Ignoring reopens that arrive on a different channel
Changing the measurement window and comparing across the change
Reading reopen rate without satisfaction, which hides silent give-ups

Where Fidiora fits

Fidiora treats reopens as the audit on its own billing. Because a resolution is defined by the issue genuinely closing, a conversation that comes back is not the outcome the model was paid for, and the gap it exposes gets reported to you.

See Pricing

FAQ

Questions

What is reopen rate in customer support?

Reopen rate is the percentage of tickets marked as resolved that are reopened within a set window, usually because the customer replies that the problem is not fixed. It is calculated as reopened tickets divided by resolved tickets, times 100. It is the simplest check on whether your resolutions were real.

What causes tickets to be reopened?

The usual causes are an incomplete first answer, closing the ticket before the customer confirmed the fix, a wrong diagnosis, and a promised fix from another team that never landed. Courtesy replies such as thank you can also trigger reopens in some tools, so exclude those before reading the number.

What is a good reopen rate?

Lower is better, but a rate of zero usually means you are not detecting reopens rather than that you have none. What matters most is the trend and whether specific topics are far above your own average.

Why is reopen rate important for AI support?

Because it is the only cheap way to verify that claimed AI resolutions were real. A resolution rate with no reopen check is a self-assessment, and self-assessments run high.

How do I reduce reopen rate?

Find the topics with the highest reopens and read those conversations. Almost always the first answer was incomplete rather than wrong, and the fix is a documentation change rather than a training one.

Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a Demo

No credit card · Live in under an hour · Read the setup guide