Intent not Identified
Triggered when the AI Agent cannot understand the user’s intent. Choose one of the following responses:- Show a standard message from the standard responses library. Learn more
- Automatically run a dialog task — select the task from the dropdown.
Ambiguous Intents Identified
Triggered when the NLP engine detects multiple intents with similar confidence. By default, the AI Agent presents the list of ambiguous intents to the user for selection. This event fires when:- Two or more “definite” intents are identified.
- Two or more “possible” intents are identified within the proximity threshold.
- Only low-confidence Knowledge Graph intents are found and no other engine identifies an intent.
koreUtil.getAmbiguousIntents() to retrieve ambiguous intents and their confidence scores. Learn more
Configure the Event
- Go to Conversation Intelligence > Events > Intent Events.
-
Click Configure to enable the event.
Note: If not enabled, the list of ambiguous intents is presented to the user.
-
Select a configuration option:
- Present all qualified intents to the end-user for disambiguation — Default. Shows the standard ambiguous-intent response. Learn more
- Automatically run a Dialog Task — Select a dialog with custom logic for handling ambiguous intents. Learn more
-
Click Save & Enable.
Note: When ambiguous intents are detected during testing, the Debug Log shows: Multiple intents are identified — Ambiguous Intents Identified event is initiated.
Interruption Management
When this event is enabled, interruption behavior follows the configured node, dialog, or app-level settings — with one exception: if Continue the current task and add a new task to the follow-up task list is selected, the interrupting task is not added to the follow-up list. Learn moreVariable Namespaces
Go to More Options > Manage Variable Namespaces at the top of the Events screen to associate variable namespaces with events. This option is visible only when Variable Namespace is enabled for the AI Agent. Learn more