Difference between revisions of "Conversation Flows"
| Line 16: | Line 16: | ||
The Start Event is usually connected to a message node, that contains the welcome message. This means that when the user opens the chat he will instantly receive the welcome message. | The Start Event is usually connected to a message node, that contains the welcome message. This means that when the user opens the chat he will instantly receive the welcome message. | ||
After sending the welcome message, the virtual agent will wait for user input. When receiving the user input it will detect the intent and continue on that branch. If for example the agent couldn't detect the intent it will select the "default fallback" intent, that is configured as a fallback; thus it will send the user the message from the "mesaj fallback" and will wait for user input again. The "messaj fallback" node is connected to all the intents from the previous state, creating a loop. | After sending the welcome message, the virtual agent will wait for user input. When receiving the user input it will detect the intent and continue on that branch. If for example the agent couldn't detect the intent it will select the "default fallback" intent, that is configured as a fallback; thus it will send the user the message from the "mesaj fallback" and will wait for user input again. The "messaj fallback" node is connected to all the intents from the previous state, creating a loop. | ||
| + | |||
| + | |||
| + | The topics bellow describe the mechanics of the conversation flows. | ||
| Line 21: | Line 24: | ||
In more complex scenarios that also contain scripts and services the agent might pass through multiple nodes in the flow before generating the response for the user. | In more complex scenarios that also contain scripts and services the agent might pass through multiple nodes in the flow before generating the response for the user. | ||
| + | The agents stops and returns a message in 3 situations: | ||
| + | 1. It reached the end of the flow | ||
| + | 2. It reached a node that is followed by intents, thus user input is required | ||
| + | 3. It reached an entity node that requires user input | ||
| + | |||
| + | |||
| + | == Component library == | ||
| + | |||
| + | Every node on the canvas holds a reference to a component. The node receives the name and the configuration of the component but it is only a reference to it. This means that when deleting the node the component is not deleted and also that we can reference the same component on different branches of the conversation. | ||
| + | All component can be browsed in the component library. | ||
Revision as of 10:51, 18 November 2019
Dialogs based on conversation flows are guided dialogs. With conversation flows you create a dialog tree where you define all the branches of the conversation. Here you can also connect different services and scripts to match business logic requirements.
Conversation flow are trigged either by an event or by another flow. Flows are build using 6 building blocks. Read more about each building block on it's dedicated page:
- Events
- Intents
- Messages
- Entities
- Scripts
- Services
In the example above we have a flow that is triggered by the Start Event. The Start Event is the most common type of event and is triggered when the user opens the chat or calls in. The Start Event is usually connected to a message node, that contains the welcome message. This means that when the user opens the chat he will instantly receive the welcome message. After sending the welcome message, the virtual agent will wait for user input. When receiving the user input it will detect the intent and continue on that branch. If for example the agent couldn't detect the intent it will select the "default fallback" intent, that is configured as a fallback; thus it will send the user the message from the "mesaj fallback" and will wait for user input again. The "messaj fallback" node is connected to all the intents from the previous state, creating a loop.
The topics bellow describe the mechanics of the conversation flows.
Stop conditions
In more complex scenarios that also contain scripts and services the agent might pass through multiple nodes in the flow before generating the response for the user. The agents stops and returns a message in 3 situations: 1. It reached the end of the flow 2. It reached a node that is followed by intents, thus user input is required 3. It reached an entity node that requires user input
Component library
Every node on the canvas holds a reference to a component. The node receives the name and the configuration of the component but it is only a reference to it. This means that when deleting the node the component is not deleted and also that we can reference the same component on different branches of the conversation. All component can be browsed in the component library.
