1. Home
  2. Actions
  3. How to use an entity’s value
  1. Home
  2. Conversational UX
  3. How to use an entity’s value

How to use an entity’s value

An entity’s value can be used to jump directly to the right step, without having to ask another question to the user.

We will use an example to show you how this works.

Here, we have an intent “Customer service”, containing the entity “contact” in required and “contact_channel” in non-required.

Here is the entity “contact_channel”

All right, buckle up, this is where it gets interesting.

We want the chatbot to understand “I want to contact you” and go to a step asking which contact channel they prefer.

However, if they already said which channel, we don’t want to ask again.

So, I constructed my story like this:

In the first step, not only did I put the question “Which channel do you prefer?”, but I also put a Jump to action, before this question.

This jump will avoid asking the channel question if the user already provided the information.

In the configuration of the Jump To, I put three conditions, depending on the value given to the parameter “contact_channel”. 

⚠️⚠️In the “jump to” configuration, remember you use the parameter’s name, not the entity’s name. ⚠️⚠️

If the entity is present in the user’s question, the information will be taken into account, and used to jump directly to the right step.

Isn’t it great?

You can also use the values of the entities to re-use in the conversation. In the same context, we could say this.

This allows you, for example, to check with your users on the information they gave you. You could have to do that in a contact form.

I hope this was useful, don’t hesitate to contact us if you have more questions about this feature. You might, it’s not that trivial! 😉

Updated on September 7, 2020

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
More help

Leave a Comment