Escalation rule should evaluate and run before inital Fin intro message | Community
Skip to main content
Submitted

Escalation rule should evaluate and run before inital Fin intro message

Related products:Tickets
  • September 4, 2026
  • 1 reply
  • 51 views

Our workflow is setup so that Fin’s initial response begins with an introductory message (something like “Hi, I’m Fin Support’s AI Agent….you can ask to talk to the team at anytime.” Currently this message is also sent when a ticket requires immediate escalation (e.g. inquiry indicates a deadline within the next Xhrs) followed by escalation messaging indicating the ticket is being routed to the team. It sounds odd and is aggrevating for customers to receive two separate ticket updates, one with simply an intro saying Hi, I’m Fin Support’s AI Agent….you can ask to talk to the team at anytime, immediately followed by “I’ve routed you to the team, help is on the way...”. 

It has been suggested to remove the generic intro message however this is not viable, in the majority of tickets that are not escalated customer need to know they are communicating with an AI Agent and that they can request to get routed to the team. 

Prior to the the last few weeks Fin used to validate escalations before sending the intro message so customers immediately received the “I’ve routed you to the team, help is on the way...” immeidately, no other genenric intro message. 

1 reply

Forum|alt.badge.img+2
  • Connector
  • September 9, 2026

​@Judy Correia This is a really important point. The bigger issue with cases like this is that it can be difficult to consistently identify when Fin gives a response that should have been escalated or stopped.
We’ve been working on ChatShield.cloud, which monitors AI support conversations and flags potentially risky or incorrect responses after they happen. This kind of escalation failure is exactly the type of behavior we’re interested in catching.