Node Types
You can add the following nodes to dialog tasks based on your requirements:
User Intent Node
The user intent to be identified by the platform is based on the user utterance. Every dialog has one root intent with any number of sub-intents. For more information, refer to Working with the User Intent Node.
Entity Node
The user entity in the utterance. The platform supports 15+ entity types. Developers can define the prompt message to be shown, and this message can be channel-specific. For example, an amount, account number, time, or zip code. Entity nodes prompt the user for an input. For more information, refer to Working with the Entity Node.
Agent Transfer Node
Used to transfer communication from the VA to a live agent. This is usually the last node for a dialog task. For more information, refer to Working with the Agent Transfer Node.
Script Node
Used to write custom JS code in the dialog task. For more information, refer to Working with the Script Node.
Service Node
Allows you to call an API. You can also use cURL to build the API request. For more information, refer to Working with the Service Node.
Message (or VA Response) Node
Displays a message from the VAto a user, such as, Is there anything else I can help you with? For more information, refer to Working with the VA Response Node
Confirmation Node
Displays a query message from the VA to the user, and then waits for a user response. Conditions are defined to continue processing the dialog task flow based on the user input. For more information, refer to Working with the Confirmation Node.
WebHook Node
Used for server-side validation, executing business logic, or making backend server API calls. To use this node, you must have installed the SDK Tool Kit. For more information, refer to Working with the WebHook Node.
While any dialog starts at the Intent Node, it is advisable to end it with a Message Node to give a sense of closure to the user as well as to the VA internally.
Component Transitions
A Dialog Task builds a task flow with different nodes connected by transitions. Dialog Task transitions depend on conditions that use business-defined evaluation criteria to take the next steps within the Dialog Task flow.
In Kore.ai, you define If-then-else conditions using a set of predefined operators. For each component, you must specify a fallback condition. How you represent a transition depends on the component type you are defining, and component type-specific transitions are described in the topic for each component type.
You can use the following operators to write conditions:
- Exists
- Equals to
- Greater than equals to
- Less than equals to
- Not equals to
- Greater than
- Less than
- Contains
Context Object
The Context object for the platform is the container object that holds the data for the dialog execution. The Kore.ai Natural Language Processing (NLP) engine populates the intent identified, entities extracted, and history into this object. You can use the keys from the Context object for component transition conditions. For more information, refer to Context Object.