The aggression detected scenario action is a way to jump to a sub-flow if it's detected that the contact is becoming aggressive.

As with custom scenario, default behavior after the sub-flow completes is to return to the main flow where we left off. However, you'll probably want to use this sub-flow to turn your agent off.

The most common use case for the aggression detected scenario is to turn the agent off and add tags so we know why the agent disengaged on the CRM (source) side.

Let's start by adding the aggression detected scenario action.

Then if we detect aggression let's add a tag on the contact aggressive and stop the conversation from continuing.

We can see in testing that we are able to trigger the aggression detected scenario and the actions in that sub-flow are executed in order 💪

Aggression detected can be used if your agent commonly encounters aggressive scenarios like with database reactivations! Try using this yourself and let us know use cases you've found in our Facebook Community 👏 Other users love to see ideas on how to use CloseBot actions.