Does anyone track whether customers come back on a *different* channel after Fin marks a conversation resolved? | Community
Skip to main content
Question

Does anyone track whether customers come back on a *different* channel after Fin marks a conversation resolved?

  • August 18, 2026
  • 2 replies
  • 19 views

Hi all — I'm doing some research on how teams measure AI resolution quality, and there's one thing I can't find anyone talking about.

My understanding of the billing mechanic: a conversation counts as resolved either when the customer confirms it helped, or when they stop responding without asking for a human. The second case is the interesting one. Intercom does deduct the resolution if the customer reopens *that conversation* later, even across billing periods, which seems like a genuinely fair correction.

But it only catches people who come back to the same thread. If someone reads Fin's answer, decides it didn't help, and emails support@ three days later — or calls, or starts a fresh chat — that's a new conversation. Nothing connects it to the original, and from what I can tell there's no way to see that pattern from inside Intercom, because Intercom can only see the Intercom channel.

So my question: **has anyone here actually joined their email or phone support data against Fin's resolution log to see how often this happens?**

If you have, I'd love to know roughly what you found — even a rough sense of whether it's 2% or 20% would be useful. If nobody's measured it, that's a useful answer too.

Full disclosure: I'm exploring building something in this space, so I have a horse in the race. I'm not selling anything here and I'm not going to DM anyone — I genuinely just want to know if this is a real problem or something I've invented in my head.

2 replies

Aleksei O
Super User ✨
Forum|alt.badge.img+5
  • Super User
  • August 18, 2026

Hi ​@evidueMaker ! I would want to hope that the scenario you are explaining is rather and edger case, but I can understand that in some workspaces it would be more common than not. I haven’t measured it personally, but in my workspace I wouldn’t consider this data to be significant to support, but rather to customer success, where they could measure how frequently an account gets in touch with support :) 


  • Author
  • New Participant
  • August 19, 2026

That’s really helpful ​@Aleksei O — especially the point about this potentially being more of an account-level/customer-success metric.

Let me ask the broader version then: ignoring cross-channel recontact specifically, have you ever seen cases where Fin considers a conversation “resolved” but your team wouldn’t consider the underlying customer issue genuinely resolved?

Or in your experience are Fin’s resolution criteria aligned closely enough with your own that independently auditing the resolution count probably wouldn’t add much value?

I’m genuinely trying to figure out whether there’s a real verification gap here or whether I’m overestimating it.