Escalation Rule triggering batch testing. | Community
Skip to main content
Answered

Escalation Rule triggering batch testing.

  • April 24, 2026
  • 2 replies
  • 148 views

Forum|alt.badge.img+1

Hopefully I can describe this as simply as possible to see if this is expected or if anyone has run into this.

I have an escalation rule set and live for audience A. I have batch testing setup in the test section and for each batch I set an audience B-H, one at a time or a single one (doesn’t matter). But batch testing is never tested as audience A. 

For any batch test that I run for any audience B-H, the escalation rule is triggered, meaning that it automatically escalates so that I cannot test my content or other guidance. I must turn off escalation rule for Audience A, test in the batch section as Audience B to get my answers, and then turn on escalation rule for Audience A. This does not seem like desired behavior.

If I just skip the batch testing and test directly in my product via the messenger, the Escalation Rule is not triggered and works properly.

Does anyone know what could be causing this? Is there another setting I am not aware of? 

 

An example of escalation rule being turned off and getting the correct batch answers:
 

 vs turning the rule on for only audience A, batch testing as audience b, and getting this answer:
 

 

screenshots clipped for privacy.

Best answer by Sean Meade Forum Support Lead

Hi ​@Heather Willson, Seán here from the Fin technical support team 👋 I see Symone has answered this in the chat for you!

Just wanted to post here to explain to others in case they run into the same issue to explain that this is expected behaviour.

What’s happening is that the escalation check runs before Fin gets to the part where it evaluates other guidance or content. So if an escalation rule is triggered early in batch testing, Fin will stop there and offer escalation instead of continuing on to test the rest of the guidance.

That’s why the escalation rule is firing in batch tests, even when trying different audiences, while testing in Messenger can behave differently depending on the conversation flow and context.

So in short: once Fin decides the conversation should escalate, it won’t continue on to the later guidance steps. That part is working as designed.

2 replies

Forum|alt.badge.img+1

I also do not understand Fin’s answer when I ask it. 

 


Forum|alt.badge.img+6

Hi ​@Heather Willson, Seán here from the Fin technical support team 👋 I see Symone has answered this in the chat for you!

Just wanted to post here to explain to others in case they run into the same issue to explain that this is expected behaviour.

What’s happening is that the escalation check runs before Fin gets to the part where it evaluates other guidance or content. So if an escalation rule is triggered early in batch testing, Fin will stop there and offer escalation instead of continuing on to test the rest of the guidance.

That’s why the escalation rule is firing in batch tests, even when trying different audiences, while testing in Messenger can behave differently depending on the conversation flow and context.

So in short: once Fin decides the conversation should escalate, it won’t continue on to the later guidance steps. That part is working as designed.