fascinating-indigo•2y ago
is the built in fallback intent overpowering all other no matches?
Hi! I have defined path for no matches but also used the built in fallback intent in my project. the problem is, every no match leads to the built in fallback intent. Is there a documentation for the built in fallback intent, so i can read up the functionality of it?
2 Replies
The built-in fallback intent is designed to handle any user input that doesn't match any of the defined intents in your project. However, it should not be overpowering the No Match paths that you've set up.
In Voiceflow, the No Match path is triggered when the user's input doesn't match any of the intents in your Choice step. You can define what happens when the assistant detects a 'No Match'. You can choose to reprompt your users and/or configure a fallback path.
If you've set up a No Match path and it's not being triggered as expected, it's possible that there might be an issue with how the intents or the No Match path is configured.
As for the built-in fallback intent, it's a global intent that's designed to catch any user input that doesn't match any of the other intents. It's the last resort when the assistant can't match the user's input to any path, local, or global intent.
Unfortunately, there's no specific documentation for the built-in fallback intent. However, you can refer to the Voiceflow documentation on Choice steps and intents for more information on how they work and how to configure them.
Sources:
- Choice Step
- Capture Step
- Asking Open-Ended Questions vs Close-Ended Questions
fascinating-indigoOP•2y ago
cannot open the links