How to handle users avoiding or circumventing Fin? | Community
Skip to main content
Answer

How to handle users avoiding or circumventing Fin?

  • November 18, 2025
  • 1 reply
  • 13 views

Adam Bengal
Forum|alt.badge.img

Hi Community! 

We are still newish to Intercom, launching in earnest in April of 2025, and have been slow-rolling it out to our users. We currently have Fin enabled for ~100 of our customers, with plans to double, then triple that number in the upcoming weeks.
Overall, Intercom has been great and Fin is performing even better than our initial expectations. That said, the one reoccurring issue we continue to see is users shortcuttong/circumventing Fin--when the chat starts, their first question is “Talk to a person” or “create a case,” and since Fin is frictionless, he will not fight them and defers to the case handover process (we use ServiceCloud). Issue is, since no question or context is present, none of the AI-detection fields fill in, and the case just is sent to a ‘triage’ queue until our reception team can reach out to determine what the users’ question/issue was so they can then place them into the correct Support queue (we do not currently offer live-chat support). 

We’ve bounced this off of different people at Intercom, but nobody has been able to provide suggestions or a fix to this issue. We created a Task to try and intervene in these situations, but it does not work consistently. 

Has anyone else ran into this? Any suggestions or setup changes we could try?

Thank you!

Best answer by Sean M

Hi ​@Adam Bengal, Seán here from the Intercom engineering support team 👋

I have just tested this myself and you can use Escalation guidance to ask the customer to clarify their query before escalating here is a very simple example:
 

Hope this helps!

1 reply

Forum|alt.badge.img+4
  • Intercom Team
  • Answer
  • November 25, 2025

Hi ​@Adam Bengal, Seán here from the Intercom engineering support team 👋

I have just tested this myself and you can use Escalation guidance to ask the customer to clarify their query before escalating here is a very simple example:
 

Hope this helps!