yes and no responses similarly to traditional intent matching, enabling a more natural and fluent conversational experience. A model trained with a small set of example sentences recognizes various yes and no phrases, enhancing an agent’s ability to understand user confirmations or denials.
The Question, Optional Question, and Code nodes support the yes/no intents feature.
Key benefits
- Improved natural language understanding. Unlike the earlier confirmation words feature, which required manual synonym definitions, yes/no intents use a preinstalled vocabulary that can be expanded. This approach makes it easier to detect diverse expressions.
- Enhanced user experience. Yes/no intents enable agents to respond accurately to a broader range of affirmative or negative responses, reducing misunderstandings and improving conversations.
Restrictions
- Yes/no intents don’t support the Intent Trainer.
- Yes/no intents don’t provide traffic light feedback during training, which may limit visibility into model performance.
How to use
To set up this feature, do the following:Select a locale
Select a locale
Each locale has its own yes/no intents model, requiring separate training. The Universal locale includes English examples, but you should add more examples for better accuracy in other languages.To configure a locale, do the following:
- GUI
- API
- To see the project’s configured locales, go to Manage > Localization.
- Select the locale and click
, then select Edit Yes / No Intents. - In the Edit Yes / No Intents pane, configure the following intents for the current locale:
- Yes Intent. By default, the setting is activated. When you deactivate the setting, the intent is excluded from the build.
- No Intent. By default, the setting is activated. When you deactivate the setting, the intent is excluded from the build.
- Reject Intent. By default, the setting is activated. You need to add examples manually. When you deactivate the setting, the intent is excluded from the build.
- Optionally, add rules for the Yes and No intents.
- Click Save & Build to build a model. The yes/no intents model is always built when you edit and save settings.
Use yes/no intents for specific or all flows
Use yes/no intents for specific or all flows
Select how you want to apply the yes/no intents feature: to the entire project or to the selected flow.
- Project-level settings
- Flow-level settings
To use yes/no intents for all flows, do the following:
- In the navigation menu, go to Manage > Settings.
- On the Settings page, click NLU Settings.
- In the General Flow Logic section, select one of the following options from the Yes/No Logic list:
- Yes/No Intents - with extended rules. Evaluates the standard confirmation words logic first. If the standard confirmation words logic fails to determine the input type, the yes/no intents model is evaluated.
- Yes/No Intents. Evaluates the yes/no intents logic for every user input. The standard confirmation words logic is only used as a fallback when no Yes, No, or Reject intents from the yes/no intents model are triggered.
- If you selected Yes/No Intents - with extended rules or Yes/No Intents, configure Yes/No threshold. The Yes/No threshold slider sets the minimum score required for yes/no intents to trigger. A Yes, No, or Reject intent is only triggered if the intent score is greater than or equal to this threshold. This value applies to yes/no intents models for all locales. You can change this value for a specific flow.
- Click Save to apply settings and build a model. The yes/no intents model is always built when you edit and save settings.
How to test
Check if the yes/no intents feature works as expected via the Interaction Panel:- In the existing flow, open the Interaction Panel by clicking the chat icon (
) in the upper-right corner of the page. - Run a flow.
- On the Info tab, select Input to view the Input object in JSON format. In the
yesNoIntentResultsobject, you’ll see the result of the yes/no intents model evaluation.
Examples of possible results
Examples of possible results
- Yes intent
- No intent
- Reject intent
- Fallback reject intent
FAQ
FAQ
Q1: What happens if the Yes/No Logic setting is set to Yes/No Intents, but both
yes and no intents have been individually deactivated in the locale settings?A1: The standard confirmation words logic is used.Q2: Are yes/no intents independent of standard intent scoring?A2: Yes, the yes/no intents are completely independent of standard intent scoring (input.intentScore or input.nlu.intentMapperResults). They specifically find the types nAnswer and pAnswer within the flow. These types are used for the Yes/No type in Question nodes and for confirming intents, similar to confirmation words.Q3: How are yes/no intents evaluated when the Execute Flow node is used with and without the Parse Intents setting activated?A3: Yes/no intent scoring behavior differs only if the yes/no intent settings are different in the two flows.For example:Prerequisites:- Flow A has Yes/No Intents and only one node, which is an Execute Flow node that executes Flow B.
- Flow B has Yes/No Intents - with extended rules and one Say node.
- The Parse Intents setting is deactivated in the Execute Flow node of Flow A.
- When the user sends
yesin Flow A, the Yes intent is triggered in Flow B. - Flow B inherits the Yes/No Logic setting from Flow A.
- The Parse Intents setting is activated in the Execute Flow node of Flow A.
- When the user sends
yesin Flow A, the Yes intent isn’t triggered in Flow B. - Flow B uses its own Yes/No Logic setting.