Yes and no entities

Daria Zaboj
3 min read
updated: Jan 1, 0001

Recognize yes and no answers without creating endless User says lists.

There’re many ways users can confirm or negate information. We’ve pulled them all together and created Yes and No entities that you can reuse in your Stories. Thanks to that, you don’t need to predict how your users might express yes or no. 

The system Yes and No entities can help your chatbot recognize the correct answer. You can then save the collected data as an attribute and reuse in an ongoing chat or pass it to your web services.

Entity name

Description

Query

Returned data

Yes

Matches yes synonyms

yes, fine, sure, good, true, right, certainly

yes

No

Matches no synonyms

no, no way, never, none

no

System entities are supported only in English. If you need to use other languages, create custom entities.
System entities are supported only in English. If you need to use other languages, create custom entities.

How to use the Yes and No entitiesLink icon

Let’s create an example Story that allows the user to schedule a call. You can use the Yes and No entity to confirm the user information.

  1. Open a Story you want to use to book calls with your users. 

  2. Add a Bot response to your Story after the interaction where you collected information from the user. Name it as ConfirmationYes and No entities

  3. Add a Quick reply and ask the user to confirm the collected information before scheduling a call.Yes and No entities

  4. Now, add two User inputs after the Bot response. Name them as Yes and No.Yes and No entities

  5. Click on the Yes User input block to open the edit window. In the User says section, type double curly brackets {{ and click on the Save to attribute field. Yes and No entities

  6. Next, select the Add custom attribute, and set the attribute’s name to, for example, yes_no. To save it, click Add attributeYes and No entities

  7. Click on the {{yes_no}} attribute and select Yes from the Parameter validation list. Then, click Done.Yes and No entities

  8. Similarly, you can do it for the No User input, but select No in the Parameter validation field.Yes and No entities

  9. Now, assign responses or actions to our new interactions. The Yes query should redirect the user to the response with the booking confirmation. Yes and No entities

  10. The No query means that the user wants to make some corrections before scheduling a call. Use the Go to step action to collect information again in the Question block.Yes and No entities

  11. Save all your work and test the Story. It doesn’t matter whether you press a button or type your answer. Also, ChatBot will process both uppercase and lowercase letters. Yes and No entities

  12. You can reuse the collected yes_no attribute in your Bot responses later in the Story. Add a Bot response before the Go to step action. Then, add a Text response. Once again, type double curly brackets {{ or click on the curly brackets symbol to view the available attributes. Yes and No entities

  13. Select yes_no from the list of custom attributes.Yes and No entitiesYes and No entities

  14. Save all the changes and test the Story once again. Yes and No entities

Was this article helpful?

Got it!

Thanks for your feedback.

Thank you!

We’re happy to help.

Start a free ChatBot trial
and build your first chatbot today!

Free 14-day trial No credit card required

Discover our other products