Flows
Last updated
Last updated
Let's talk about the first part of the knowledge base, the one built from conversational flows.
The sequences of cells inside the Workspace are called conversational flows. They're part of your virtual agent's knowledge base. Before building your flow, it's important to learn about all the components that are part of the dialog.
Inside the Dialog Manager, you can find the following sections:
Workspace: where the flows are built
Repositories: store the flows and cells (Intents, Entities, Services, and Answers) created in the Workspace
Training: place to train the virtual agent and check previous trainings.
To start building your virtual agent, you will have to choose a flow. These are the four types available in eva:
Let's learn more about them!
This is an optional flow with one or more cells. For starters, you may find it easier to open a dialog with greetings in a welcome flow.
You can start your Welcome flow with a simple Answer (that can be evaluable or transactional), Rule, Code, or Service cell. After these, you can add any of the cells available in the Dialog Manager, including Intent, Entity, Input, Jump, and the End cell, as it may be a reusable flow.
The Welcome flow can be useful in different ways, depending on the channel being used and the business needs.
If your virtual agent is using an app channel, where the user is already logged in, this flow can help segment different user groups through rule cells, for example, which will allow you to deliver a different welcome message for each group.
Now, if the channel doesn’t start the dialog and depends on the user input to start a conversation (like in the WhatsApp case), the welcome flow can aim to query, using a service cell, the customer's telephone number, identify its segment and disambiguate it to deliver different answers.
In web channels, the welcome flow can aim to change the behavior of the channel, using cell code, and store user information from open to hidden context. In sequence, the virtual agent delivers sequential responses to the user.
The not expected flow is a fallback answer (also known as idk) executed when the virtual agent doesn’t understand the user’s context. It works as a miniflow with one or more cells. It’s mandatory and cannot be deleted.
You can set your virtual agent to deliver different Not Expected answers for different segments of customers using Rule cells.
It’s also possible to query the costumers' segment to custom the answers by its segment (if it’s a regular costumer or premium, for example) using a Service cell.
You can also use Code cells to remember how many times the user has gone through a certain flow and then use Rule cells to disambiguate and deliver variable answers.
Learn how to create variable answers with Code and Rule cells.
More robust option for building the dialog with all the conversational tools that eva has to offer. It must start with an Intent cell, whether it is new or from the list, in this cases eva searches on the repository for intents that had already been created.
For a better performance, we recommend to not exceed 100 cells in one dialog flow. If you need to add more cells, you can either create new flows and use the Jump function. 😉
This can be a complementary flow. Some flows may use a common journey, like for example when you need to validate or register a user, which may be needed in different flows such as open a ticket, follow its status, to cancel it, or even to leave a suggestion or a complaint.
Instead of repeating the same cells in all these flows, you can simplify it by just adding a Jump cell that will lead to the Jump flow “user_validation”. After what, it will go back to the original flow, by default, and continue from there.
Example: In the image below, we used a Code and Rule cells to disambiguate the flow when users try to reach for a human assistance during business hour and after that.
In the first case, an End cell was added after the "talk_agent" answer cell. If users follow this route, the flow stops there. Whereas, if they go through the other path, they will go back to the origin flow.
If you don't want the conversation to go back to the origin flow after the jump cell, simply add an End cell to the Jump flow where you want it to end. Important: if you have other cells in your origin flow after the jump cell, they won't be delivered.
When you jump to a User Journey flow, the first cell, an Intent, is ignored. If you need to use this Intent, add it to the origin flow.
Any flow can be edited (pencil icon) and deleted (trash can icon).
Important: Deleting a flow is an irreversible action.
These two functions are very useful for improving the visualization of flows with many branches.
On the right side of each cell, there is a colored sidebar. Yellow for Intent, blue for Answer and pink for the others (Entity, Code and Rule).
Click on the sidebar of any cell to make all the following cells after it disappear, click again to make it appear again, as shown in the image below:
Important: This function does not occur in End, Not Expected cells and some types of Jump (only those located at the ends of the flows), simply because they are always positioned at the end of the flows.
Once you are familiar with the most important features of Dialog Manager, it's very easy to create dialogs and requires just a few steps:
You can start a flow with an Intent, a Welcome message, or a Not Expected Cell.
If you start with an Intent, you can create one or use one from the repository. Always Remember: you need at least 5 Intents registered to start your flow. And also have at least 5 Examples/Utterances registered on each Intent.
Flows that don’t start with Intents can only be accessed through jumps from other flows.
When you move your mouse over the cell, you will see 3 buttons: plus (+), a pen and a trash (as shown in the image below)
5. When you click the plus (+) button, a modal opens showing cell types you can add to your flow. You cannot add an intent after another intent. You can, however, insert an Answer, an Entity, or a Service.
6. The pen button, allows you to edit that cell.
7. Clicking on the trash button, you will delete that cell.
Important:
Every flow must end with an answer. If a flow ends with a jump to another flow, the other flow must end with an answer
After the second intent, comes a second answer and so on
If you need to delete one or a sequence of cells, hover the cell you want removed and click on trash can icon.
The cell for Not Expected answer might disappear depending on the cells you are removing. They reappear when reconnecting the cells again.
If you choose to remove only the selected cell and not their subsequent siblings, the flow will have disconnected cells that you will have to reconnect.
To reconnect those cells, you will have to link them. To see if the link is possible, click on one of the magnets that appear. Possible links will appear as green magnets. In this case, just click on the two magnets to connect two cells, or select the third cell to go in the middle. Impossible links will appear as red magnets. In this case, you will have inserted a cell between them to reconnect the flow.
To reconnect cells, you should:
1) Click on the “add cell” button (plus icon) of the first cell.
2) After that, you can create a cell or select one from the repository.
3) If there is an available endpoint, the link will happen automatically.
4) If there is any branch that is not connected, you can link it to an available endpoint or remove it.
