Request User Data

1. Introduction 

The Request User Data data node enables the chatbot to read input from the user and save them as an attribute or entity. Therefore, facilitating use cases like Lead Generation, personalizing user experience, and much more.

1.1 Availability 

You can access this node in the Add a Node Modal.

2. Setup

There are two types of inputs that you can collect from users using the Request User Data Node. The first, “Standard” allows you to capture user input as an “Attribute” and the other is “Entity” that helps capture the user input as an “Entity”. Both of these can be used subsequently in your workflows in a very similar manner in other nodes including “Send Message”, “Send Message with Options”, “Send Carousel”, “Randomize Message”, “Script” and any other nodes that allow you to refer Attributes. 

2.1 Standard (as an Attribute)

User Prompt: A message for the user is added here. This should be relevant to the information being requested from the user.  

Attribute: Add a name for the attribute where the data entered by the user is saved. 

Validation: You can validate the data entered by the user. For example: if a user enters a wrong email format you can prompt for a valid input. Following validations are available in a request user data node 

  • Text is valid for all input.
  • Password is used to take password inputs. Data collected over this validation type is not persistent and can only be used over the next immediate flow step.
  • Number validation is used to validate numeric input only.
  • NPS (1-10) is an option that allows the user to choose a number in the Net Promoter Score of 1 to 10.
  • NPS (1-5) is an option that allows the user to choose a number in the Net Promoter Score of 1 to 5.
  • NPS (1-3) is an option that allows the user to choose a number in the Net Promoter Score of 1 to 3.
  • Email validation is used to check if user input is a valid email address.
  • Mobile validation is used to check if user input is a valid phone number
  • Date is used to validate user input is a valid date. It can also be set up to accept a date from a date picker.
  • Regex : It allows you to store the set the validation type of the attribute into any regex format of your choice.

Update Username: You can select this option if this value needs to be used to refer to this user in the bot flow ahead. 

2.2 Entity

Saving user input as entity enables you to custom verify them. You can use values and their metrics in the flows just like you would use an attribute by referring to it within a double braces notation. For using entity values in the flow though you also have to add the prefix ‘context.’ to the entity name. As an example to use an entity named booking_date, you can use it by specifying {{context.booking_date}}. For more details refer to the document on Entities. 

User Prompt: This is the message shown to the user when information is requested in the bot flow. 

Entity: An Entity can be selected from existing entities from the drop-down menu or a new Entity can be created from the create new entity option, where you can select the Entity type as any of the existing types or add Custom values. 

Was this article helpful?

Related Articles

Leave A Comment?