Branching rules let you define multiple action paths from a single trigger, depending on different scenarios so you can consolidate and manage more dynamic workflows within a single rule. For example, you can route conversations based on tags, account owner, business hours, etc. With branching rules, you can also leverage Connectors to check 3rd party systems in conditions and actions and tell Autopilot exactly how to handle complex inquiries with repeatable workflows. When a conversation matches multiple branches, the rule will prioritize the highest path in the list. Learn more.
+9As a heavy internal user of Front rules, this thing is a game changer!
Hello,
got a silly question: Would you be able to use the branching rule with a ‘Rule set data’ to assign one branch to different people depending on the keyword?
and the other branch with another ‘rule set data’? 😅
Login to the community
No account yet? Create an account
Use your Front credentials
Log in with Frontor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.