You can think of flows as a folder in which you can put bot dialogs that are related to the same topic.
Some tips in choosing how to split flows:
Group all flows that have a functional relation. In our Choo Choo example, you could group all bot dialogs that are meant to help book a ticket, all general questions about trains, and all support flows (e.g. I lost my bag on the train).
Reserve one flow for general questions, such as your offloading settings and your not understood bot dialog.
There are four kinds of bot dialogs, each with its own color and functionalities.
Everything message that a bot will send to a user is a bot message. This includes text messages, buttons, quick replies, etc.
If you want to add rules to determine how a user is routed based on the value of a variable, you can do it with this bot dialog type.
Actions allow you to configure the settings of a user session, such as the language that will be used to reply to your user, or the offloading of a user.
Use this bot dialog type to gather input from your users.
Every bot dialog type has a settings and NLP tab, which stay the same throughout the different types.
In Chatlayer you can have two views on your bot dialogs, where you configure what the bot will answer to a user.
The flow view: a visual representation of all your bot dialogs, where you can easily see which bot dialogs are related to each other.
The table view: the same information about your bot dialogs, but in a table, making it easier to filter, search and sort on bot dialogs.
View your flows as a tree representation. This view is helpful to see how your flows are constructed. The parent child relations between bot dialogs is being used to visually organise the bot dialogs. Changing the parent child relation will not change the way your conversation flows work: it is purely for organising the bot dialogs in a logical matter on the canvas. The user is only redirected by intent recognition or click on UI components such as buttons and quick replies.
View your bot dialogs in a table which is helpful for searching, filtering and sorting dialog states.
This is the ID associated with the dialog state. You can use this to debug the bot in the Emulator.
The name associated to this dialog state. This is also the label that is shown in the tree view, the list view or the translations module. You can enter any name you like and change it as often as you wish.
The bot dialog flow determines in which flow the bot dialog you're editing or creating will live.
The Parent Dialog State can be used to visually organise the dialog states. Changing the Parent Dialog State will not restrict the conversation flows: it is purely for organising the dialog states in a logical matter on the canvas.
Every bot dialog can be linked to an Intent. When a user is entering free-form text, it is analysed by the NLP model. If the NLP model recognises an intent with a high enough accuracy (above the threshold), the user will reach the bot dialog coupled to the intent. Multiple bot dialogs can reuse the same intent by using different
Context settings. A dialog state can only be linked to one Intent.
To restrict the usage of an intent in a bot dialog to certain points in the dialog flow, you can use input contexts. If you specify an input context and the linked intent is recognised, the bot will check if the input context is active and act accordingly: combine multiple required contexts for sub flows in flows.
If the required context is not active, this dialog state will not be reached, even though the intent linked to it was recognised.
If the required context is active, the dialog state will be reached.
To learn more about using context, see the Context concepts documentation
To set an output context for a certain bot dialog, click on the
New context button. Next, type the name of your new context. The number on the left of the context name is the lifetime of the context. For example if you specify a lifetime of 3, this context will remain active for 3 user messages. After the user has entered three messages, this context will not be active anymore. Combine multiple input contexts for sub flows in flows.