Fin's flawed resolution assumption | Community
Skip to main content

Fin's flawed resolution assumption

  • May 27, 2025
  • 6 replies
  • 290 views

bosbeest
Forum|alt.badge.img+1

Hello everyone :)

I've discussed Fin's flawed assumption of resolved cases in this thread, but it was also about the billing that went with it. This has been graciously addressed in the May 21st Built for You presentation (when you reply after Fin thinks it "resolved" an issue, the ticket is now no longer counted towards your Fin resolution bill ($0.99 per resolution)). To get a clean discussion without having to read an essay's worth of replies, I thought I'd start a new thread. 

 

In the past 4 weeks, we've had 40 tickets where Fin got involved. 16 of those are marked as "resolved by Fin", giving Fin a 40% resolution rate. However, when looking at these tickets, 9 out of 16 are not solved by Fin at all (see screenshots, I didn't add longer Fin convo's). So that makes Fin's actual resolve rate 12.5%. 

Thus, the issue of incorrect assumption persists. And it is so significant that I will never be able to use any of the beautiful reporting and analysis functionality surrounding Fin. As far as I know, I cannot manually change the "resolved by Fin" stamp these conversations receive. So what to do? Either I need to be able to change this manually or better yet; Intercom should stop assuming Fin resolved an issue when an agent replies to the customer after Fin.
 

I would love to know whether this is on any kind of radar, roadmap or in the back of a product manager's mind.

The examples:

 

 

 

 

 

 

 

 

6 replies

  • New Participant
  • May 27, 2025

Try to force the user confirm “route to the team”. I think this is why these conversations are considered a resolution. Think with me: An user comes to your support, talk with "Fin AI", and they dont talk anymore else. You dont want to pay this conversation, so, the conversations has no routed to the team, and you just start to answer the user. Intercom dont want to lose money, so they will considerate that convesation as a resolution, apesar of the intervention of an human. Do you understand? I think that is happening.


bosbeest
Forum|alt.badge.img+1
  • Author
  • Active User
  • May 28, 2025

Hi ​@Matheus Lutz , thanks for thinking with me there. However, I feel like somehow “forcing” or steering customers to say a certain thing is A. error prone, B. solving an issue that is Intercom's to solve and C. not something someone in Customer Support should be doing. I guess I could create some guidance which states that Fin always asks whether they could pleeeaase respond. But yeah, point A, B and C 😅

 

I'm afraid I kinda lost you after “You don't want to pay this conversation”. To clarify, the finances are no longer the issue here - Intercom has fixed that (see the video in my original post). I just want them to improve the assumption system, which should go the same direction as the payment system really. Why would I ever contact a customer in the same chat if not to actually solve their issue?


Hi ​@bosbeest ,

Thank you for raising this,  There was a misstep in how we described how billing works during the Built for You event on May 21. 

We incorrectly said that if a teammate replied after Fin’s response, the conversation wouldn’t count as a Fin resolution—and wouldn’t be billed. That’s not accurate, and we want to clarify:

  • A conversation is billed as a resolution when the end user gets an answer and doesn’t ask for further help.
  • If the end user does ask to speak to a person—either by clicking “Get more help” or replying with a follow-up request—then the conversation is not billed.

We’ve updated our Help Center with more detail [link], and we appreciate you pointing this out. 

— The Intercom Team

 


bosbeest
Forum|alt.badge.img+1
  • Author
  • Active User
  • June 4, 2025

Hi ​@Aisling O'Reilly ,

 

I'm pretty shocked to hear that, as it's stated very clearly and unambiguously on a huge slide next to your Chief Product Officer Paul Adams. Doesn't really seem like a misstep in description don't you agree?

 

 


 Totally understand your reaction — hearing something different now is frustrating, and rightly so. We didn’t communicate the billing logic accurately during the event, and that’s on us. We made a mistake, and we really appreciate you holding us to a high bar.
We’ve since updated internal guidance and are closely watching feedback like yours as we consider changes to how we measure resolutions.
Thanks again for taking the time to raise this.


bosbeest
Forum|alt.badge.img+1
  • Author
  • Active User
  • June 5, 2025

Hi Aisling, 

It was an amazing initiative that born out of improving customer service for both your customers (me) and my customers.. I'm assuming this was viewed as an incentive for bad actors to misuse, by someone in leadership who is not involved with customer experience, only money - and projecting what they would do themselves to your entire client base. A real shame and a leap backwards for your company. Perhaps some people need to re-read this page, especially the 3rd yellow sentence: https://www.intercom.com/believe