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

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

  • August 18, 2026
  • 6 replies
  • 170 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.

6 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.


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

@evidueMaker in my experience with relatively high contact volume SaaS, where over 50% of the cases are either user errors or unwillingness to read documentation (which is partially a product issue as well), I would generally consider deflection to be of higher importance than resolution, and Fin did a great job with that by offering customer education materials. However, considering the cost of Fin, auditing the actual resolution count would still absolutely make sense. I can also confirm that occasionally, Fin did “resolve” the conversation while the customer was still clearly struggling, but I believe those cases were due to a misconfiguration of how Fin should interpret the answers. 


  • Author
  • New Participant
  • August 20, 2026

Thanks ​@Aleksei O  — that’s particularly useful coming from someone who’s both operated Fin internally and now works across different client implementations.

 

The fact that you’ve actually seen Fin mark customers resolved while they were still struggling, but also think auditing the resolution count would make sense given the cost, is exactly what I’m trying to understand better.

 

I’m exploring whether there’s a useful product here for teams using Fin: independently auditing billable outcomes against the customer’s own data. If it works, I could also see it being useful alongside the kind of Fin optimisation work you already do with clients — the audit identifies questionable outcomes or configuration issues, and someone still needs to fix the underlying setup.

 

Would you be open to a 20–30 minute call to compare notes? I noticed the booking link in your profile and I’m happy to use that if appropriate.


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

Sure, saw that you already booked the call, let’s chat :) 


  • New Participant
  • August 20, 2026

To add some additional examples here, I have done a few audits on Fin’s resolution. We have ~2k conversations/month and there are typically only a handful that are counted as a resolution, but the customer is still struggling. I will say, in most of these cases the customer is not following directions from Fin, or has abandoned the conversation and came back in a separate channel and immediately escalating the second conversation. Review almost always shows that Fin gave a good answer and gave viable solutions on the first time around, but the customer either did not follow the directions, or did not like the correct answer. We have kind of chalked the misresolution as mostly fault of the customer and typically just the cost of doing business. 🤷