cIntent: followed by the intent name.
This feature overrides the default intent mapping process, giving you precise control over the flow’s next steps based on user input, such as a message or button click.
Use the trigger intent feature when you need to:
- Skip NLU processing and direct the flow to a specific intent.
- Ensure consistent navigation in response to button clicks or system actions.
- Improve the user experience by minimizing errors from misinterpreted user input.
Key benefits
- Precise flow control. Ensures the correct intent drives the flow forward.
- Postback support. Triggers a specific intent smoothly when a user clicks a button with a postback value.
Prerequisites
Before using this feature, ensure the following:- You set up your flow with specific intents for the scenarios you want to trigger.
- You have a Say, Question, or Optional Question node in the flow editor.
Restrictions
- This feature bypasses full NLU processing, preventing default replies from triggering and automatically setting the intent score to 1. Don’t use this feature for general NLU analysis.
How to use
- In the navigation menu, go to Advanced > NLU and identify the intent needed to continue your flow, for example,
Continue Booking. - In a Say, Question, or Optional Question node, use the syntax
cIntent:Continue Bookingas a postback value in output types that support postbacks. Follow these syntax rules:- Don’t add a space after the colon, though spaces within the intent name are allowed. For example,
cIntent:Continue Booking. - (Optional) Add text for slot parsing after a pipe symbol (
|). For example,cIntent:Continue Booking|book tomorrow.
- Don’t add a space after the colon, though spaces within the intent name are allowed. For example,
How to test
Test the feature in the Interaction Panel:- Open the Interaction Panel and activate Debug Mode.
- Test your flow with the
cIntent:Continue Bookingpostback value. The system debug message shows: - Test your flow with the
cIntent:Continue Booking|book tomorrowpostback value to verify slot extraction, for example,tomorrow. The system debug message shows: