Basic Concepts
A summary of eva's features ranked in order of importance

Main concepts

In a nutshell, everything you need to know to build a bot

Dialog Manager

The Dialog Manager is the main feature, the canvas where you create the dialogs and build your bot knowledge base.
The Dialog Manager has 7 (seven) main sections:
    Training (if you are using Clever, eva’s NLP)
For more information, click here


The flows in eva are composed of elements called cells. Each cell enters the flow for a specific purpose.
There are 10 cells (in order of importance)
    Not Expected Answer
For more information, click here


When you connect Intents, Entities and Answers, you form a flow.
A bot probably will have more than one flow.
For more information, click here

Intent cell

When designing a conversational flow you need to predict the user interactions and the bot responses.
An intent cell will represent the users' interactions. It is the representation of a user's will, in other words, an action.
Usually it is associated with a verb. For example, when the user says he wants to buy something he is expressing a will, that is, an intention.
Since users can express the same will in different ways, the intention cell is composed of examples. The examples are all the possible ways the user can express the same will.
Examples of a purchase intention:
    I want to buy
    I want to acquire
    I want to make a purchase
For more information, click here

Entity cell

Entities represents a user interaction, but unlike the Intent, it is usually associated with an adjective, noun, product, services, etc. In most cases, entities complement intentions.
For example, if the the user says: "I want to buy an Apple phone"
The terms "cell phone" and "Apple" will be Entities, because they represent a product and a brand.
Entities can also represent a very specific user interaction, such as an email. In cases where it is impossible to map all possible user interactions, such as an email list, we design a standardized term that will cater for this type of interaction. And for this we use standard type entity.
For more information, click here

Answer cell

As the name suggests, the Answer cell will bring a bot's feedback to a user's input.
In eva, you can also make your response evaluable. In the bottom corner, you can put a thumbs up and a thumbs down. This way you will know whether the user's feedback was positive or negative.
eva has six types of responses:
1) Simple Answers: the bot predicts answers to user questions
b) Not Expected Answers: the answer given by the bot to an unidentified user demand
c) FAQ: flows built based on answers to intentions
d) Dynamic Answers: through simple codes, brings personalized answers
e) Transactional Answers: when the answer will depend on an API
f) Channel-based Responses: responses that vary according to the channels
For more information, click here

Jump cell

As the name suggests, the Jump function allows you to go from the last cell created to any other cell in any flow.
This is perfect to avoid repetition, as well as shortening and simplifying flows.
For more information, click here

Service cell

Often, a response to a user demand will require information that will necessarily be outside the eva, on other servers.
For example, informing a customer's balance, credit card account, closing a purchase on an ecommerce bot...
Here comes the Service cell, which connects the user to eva and the customer.
In it, there is a field to put Webhook. If you have never heard of this expression, it is a protocol used so that an application (APP) on the internet receives real-time information as soon as an event occurs in another web-based application.
For more information, click here

Input cell

"What is your birth date?", "write your name here", "put your account number here". The Input cell will be responsible for storing this information in the eva.
There are three types:
a) Date Template: allows the insertion of dates.
b) Time Template: allows the insertion of time (hour and minutes)
c) Customizable templates: you can enter locations, zip codes, among other data
For more information, click here

End cell

The End Cell works like an end point in a flow. By placing this feature, the bot stops communicating at that point. That is, it will only resume the dialog if the user (the bot's interlocutor) interacts again.
The End Cell is always used in a Jump flow, never in the User Journey (the main one).
For more information, click here

Code cell

The Code Cell allows you to perform some services without relying on APIs. It offers immense advantages in a flow.
Through the Code Cell it is possible to
    Manipulate objects
    Anticipate executions and actions
    Perform services without the need for APIs
    Reduce time and cost
For more information, click here

Rule cell

Imagine two users that have the same intention: checking their bank balance. However, one is already logged into the bank and the other is not. In cases like this, the Rule Cell comes in, to steer each user in the right direction.
This is a feature to make your dialog more assertive and much more precise, especially when Intentions and Entities can bring up multiple scenarios.
The language used is JavaScript.
For more information, click here


Is the first and the main tab of Dialog Manager, since it is the area where it is possible to view and also design the flows.
The Workspace is where you will build your bot knowledge base.
Here, you will create cells and string them together to form flows.

Other concepts

See eva glossary HERE.
Last modified 28d ago