A reopened conversation is Intercom's built-in record of a customer returning to a thread after it was closed — one of the strongest signals available that a problem didn't stay solved. It's also a narrower signal than most reporting treats it as: it only catches the case where the customer returns to the same thread. A repeat problem that shows up as a brand-new conversation looks, on paper, unrelated.
What a reopened conversation means
Intercom marks a conversation as reopened when a customer replies after it was closed, and its own guidance already treats this as a potential signal of a recurring issue or an unfinished follow-up. That's a fair read. A customer who closed a thread and then came back to it, unprompted, usually has a reason — either the original fix didn't hold, or something new turned up while the thread was still fresh in their mind.
Reopened conversations are the easiest repeat-problem signal to see, and the narrowest one. We're exploring a Supportman layer that also catches a repeat problem when it arrives as a brand-new conversation instead of a reopen — tell us how you currently catch those.
Free trial · no card · about 2 minutes to set up
Where this differs from a plain "the ticket wasn't resolved" reading: a reopen can also be a customer adding a follow-up question on a genuinely separate topic, using the same thread because it's the last one they had open. Read the message before treating every reopen as a resolution failure.
What reopens catch, and what they miss
| Scenario | Shows up as a reopen? |
|---|---|
| Customer replies to the closed thread saying the fix didn't work | Yes |
| Customer starts a new conversation about the same problem | No |
| Customer contacts a different channel (email vs. chat) about the same problem | No |
| Customer replies to the old thread with an unrelated new question | Yes, but not a repeat issue |
The second and third rows are the common failure mode: a customer who gives up on a thread rarely goes hunting for the exact same conversation to reply to. They start over. That new conversation won't show up in a reopen count at all, which is why repeat contact rate — matching the same customer and the same underlying issue across separate conversations — catches cases reopen rate structurally can't.
How to read reopen data in Intercom
- Pull reopened conversations for the period from Intercom's reporting.
- Read each one rather than trusting the count alone — separate genuine same-issue reopens from unrelated follow-ups riding the same thread.
- Tag the root cause: wrong information, incomplete fix, customer needed more time, or a new issue entirely.
- Cross-check the customer's other recent conversations. A reopen plus a second, separate new conversation on the same intent is a stronger signal than either alone.
Split Fin-closed and human-closed reopens the same way you'd split FCR — a bot that closes on an assumed resolution and reopens overnight is a different problem from a person's fix falling short. See how to QA Intercom Fin for the audit framework that separates the two.
Reopen rate isn't a standalone target
A team can drive reopen rate toward zero just by discouraging customers from replying to closed threads, which would make the number look better while doing nothing for the underlying problem. Read reopen rate alongside CSAT on the same conversations and alongside repeat contact rate, which catches the repeats that never made it back to the original thread. None of these three numbers alone proves a problem actually went away — together, they're a reasonable proxy until a team is tracking outcomes at the problem level directly.
Frequently asked questions
What is a reopened conversation in Intercom?
A conversation the customer replies to after it was marked closed. Intercom tracks this natively and flags it as a potential sign of a recurring issue or unfinished follow-up.
Does a reopened ticket always mean the issue wasn't resolved?
No. Some reopens are a genuine same-issue failure; others are an unrelated follow-up sent to the same thread out of convenience. Read the message before classifying it either way.
What does reopen rate miss?
A repeat problem that arrives as a brand-new conversation instead of a reply to the old one. That's the more common shape once a customer has stopped checking the original thread, and it won't appear in a reopen count at all.
What is a good reopen rate for customer support?
There's no portable target — it depends on product complexity and channel mix. Watch the trend and the root-cause split rather than chasing an external benchmark.
How do you reduce reopened tickets without hiding real problems?
Fix the underlying cause behind the most common reopen reasons — usually a wrong or incomplete first answer — rather than discouraging customers from replying to closed threads, which lowers the number without fixing anything.