Skip to main content
The Dynamic Intent node lets you dynamically trigger any of the flows in the AI Agent by defining the intent’s display name using variables. The target intent can be either a Dialog Task or a FAQ. You can use this node to proactively disambiguate an intent and choose different intents based on the user or conversation context. In the case of linked apps associated with Universal Apps, you can also use this node to trigger flows present in any other linked apps of the corresponding Universal Apps. This feature allows you to invoke reusable or utility flows in one linked app from another, for example, user authentication, OTP verification, etc. It simplifies switching between tasks in different linked apps of a Universal App.

​
Key Points

  • The target task can be within the current app, or if connected to a Universal App, it can be in any of the other linked apps of the Universal App.
  • You can define the display name of the target intent using Context or Environment variables.
  • The platform resolves the context or environment variable during runtime to identify the target intent.
  • If the variable fails to provide a valid Dialog Task or FAQ Name, the current task will be discarded, and the Task Failure Event will be triggered.

​
Add the Node

  1. Open the dialog task to which you want to add the dynamic intent node.
  2. Use the ”+” button next to the node after which you want to add the dynamic intent node, choose + New Node > Dynamic Intent.
The Dynamic Intent window is displayed with the Component Properties tab selected by default.

​
Configure the Node

​
Component Properties

The settings made within this section affect this node across all instances in all dialog tasks.
  1. Enter Name, Display Name, and Description for the node. The node name cannot contain spaces.
  2. Target Intent Name In this section, you can define the display name of the intent (Dialog Task or FAQ) that you want to switch to. Use context variable or environment variable to define the display name as follows:
    • Context Variable — {{context.targetTaskName}}
    • Environment Variable — {{env.targetTaskName}}
    Where targetTaskName is a variable that contains the target intent’s display name as the value. Example Scenarios:
    • If the target intent is present within the same app: The variable must use a valid display name of an intent within the app. The target intent can be associated with a Dialog Task or FAQ. Consider the following intent display names — reset_password, apply_paid_leave, or how often should I reset my password. In the Target Intent Name field, you can use either the display name reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name reset_password as the value.
    • If the target intent is present in a different linked app (the target app and the current app are linked to a common Universal App): The variable must refer to the target linked app name and the display name of the intent within the target app, separated by a ‘dot’. Consider the following intent names — HRBot.apply_paid_leave, ITBot.reset_password, or ITBot.how often should I reset my password. In the Target Intent Name field, you can use either the display name ITBot.reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name ITBot.reset_password as the value.
  3. Target Intent Error Transition In this section, you can select the flow of execution to be followed in case the Platform fails to resolve the defined target intent:
    • Ignore this node and continue with the execution of the following node in the transition — this option is selected by default.
    • Trigger Task failure event.

​
Instance Properties

Under the Instance Properties tab, you can configure the instance-specific fields for this Dynamic Intent node. These settings are applicable only for this instance and will not affect any other instances of this node.

​
Entity Pre-Assignments

In this section, you can assign values for the entities or context variables of the target dialog task. Provide the name of the entity or context variable of the target intent and define the value to be assigned from the current task’s context. Key/Value should prefix with context for getting values from the context object.
  • Key: Entity name
  • Value: context.path of the value which needs to be assigned to the entity
Use the flag 'reuseEntityWords: true' as part of the pre-conditions to enable entity values extracted in a parent dialog to be automatically available and reused in downstream dialogs without needing to prompt the user again. If multiple entities of the same type are captured in a dialog before the Dynamic Entity Node is triggered, only the first entity value is carried forward to downstream dialogs. Example: Entities:
  1. Departure City
  2. Destination City
After both entities are collected, if a Dynamic Intent Node triggers a child dialog, the Departure City (the first captured value) is reused in the child dialog, even though the Dynamic Intent was triggered after the Destination City was captured.
This setting is ignored if the target intent is FAQ.

​
Entity Post-Assignments

In this section, you can assign values for the entities and context variables of the current task after returning from the target task. Provide the name of the entity or context variable of the current task and define the value to be assigned from the target task’s context.
  • Key: Entity name
  • Value: context.path of the value which needs to be assigned to the entity

​
Transition Options

In this section, you can select the flow to be followed once the task completes. You can choose from two options:
  • Initiate the target intent execution from within the current context.
  • End the current task and initiate the target task.

​
Advanced Controls

In this section, you can add Custom Meta Tags to the conversation flow to profile AI Agent-user conversations and derive business-critical insights from usage and execution metrics. You can add tags for the following:
  • Message — Define custom tags to be added to the current message in the conversation.
  • User — Define custom tags to be added to the user’s profile information.
  • Session — Define custom tags to be added to the current conversation session.
For more information on custom tags, see Custom Meta Tags.

​
Connections Properties

Connection properties can be seen and accessed only if this is the bottommost node of a sequence.
Click the Connections tab and set the transition properties to determine the node in the dialog task to execute next. You can write conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions. See Adding IF-Else Conditions to Node Connections for a detailed setup guide.
These conditions apply only for this instance and will not affect this node when used in any other dialog.
The Connection Path property offers three default variants:
  1. Not Connected — No specific next node is defined.
  2. End of Dialog — Explicitly ends the current dialog.
  3. Return to Flow — Terminates the Dialog Task and returns control to the Flow Builder. The Flow Builder resumes from the next node.
    • Enable the Deflect to Chat option to create conversation flows that transition from voice to chat-based interactions within the same context. It has two deflection types: Automation and Agent Transfer.
Deflect to Chat works only with Kore Voice Gateway Channels (Phone number or SIP Transfer).
Related Links