No matching route for AI steps with buttons
Business problem
When AI routing in a journey uses buttons, the 'no matching route' option is missing. If a user types their own message instead of selecting a button, the chatbot still tries to match the input to an existing path, which often results in repeating the original question and a frustrating user experience.
Desired outcome
The ability to add a 'no matching route' to AI routing steps that contain buttons. This would allow users who don't choose the suggested options to be naturally guided to an alternative path to handle edge cases correctly.
Reminder: Insights help guide our direction. Votes and discussions help us understand demand, but don't guarantee development. Every insight receives a response within 30 days.
Discussion (1)
Sign in to join the discussion