Guide FloatChat

Floatchat- User Guid

Request User Data

Table of contents

1. Introduction #

The Request User Data data node allows the chatbot to collect user input and save it as an attribute or entity.

2. Setup #

There are two types of inputs that you can collect from users using the Request User Data Node.

The first type is “Standard,” which enables you to capture user input as an “Attribute.” The other type is “Entity,” which helps capture user input as an “Entity.”

2.1 Standard (as an Attribute)

User Prompt: Here, you add a message for the user that is relevant to the information you’re requesting.

Attribute: You provide a name for the attribute where the data entered by the user will be saved.

Validation: You can validate the data entered by the user. For example, if a user enters an incorrect email format, you can prompt them to enter a valid email. The following validations are available in a Request User Data node:

  •  Text: Valid for all types of input.
  • Password: Used to collect password inputs. The collected data is not persistent and can only be used in the next immediate flow step.
  • Number: Used to validate numeric input only.
  • Location: Allows you to store shared information in the form of longitude and latitude.
  • NPS (1-10): Enables the user to choose a number in the Net Promoter Score range of 1 to 10.
  • NPS (1-5): Enables the user to choose a number in the Net Promoter Score range of 1 to 5.
  • NPS (1-3): Enables the user to choose a number in the Net Promoter Score range of 1 to 3.
  • Email: Validates if the user input is a valid email address.
  • Mobile: Validates if the user input is a valid phone number.
  • Date: Validates if the user input is a valid date. It can also be set up to accept a date from a date picker.
  • Regex: Allows you to set a custom validation format using regex.
  • Update Username: This option allows you to update the username by enabling it in the Request User Data node.

2.2 Entity

Saving user input as an entity enables you to custom verify them. You can use entity values and metrics in the flow by referring to them within double curly braces notation (e.g., {{context.booking_date}}). To use an entity named booking_date, you need to include the prefix ‘context.’ (e.g., {{context.booking_date}}). For more details, refer to the document on Entities.

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

Entity: You can select an entity from the existing entities dropdown menu or create a new entity by selecting the “Create new entity” option. You can choose from existing types or add custom values.

2.3 Enable Skip

You can mark non-mandatory fields by enabling the Skip option in Request User Data nodes. If required, you can change the text on the skip button.

Additional attributes in the contact list (1)

Connect the Skip button to a node in the same path, and when the user clicks on the button, they will continue with the connected node.

For channels that don’t support buttons like WhatsApp, you can ask the user to type a configured word to skip entering the input. For example, users can either click on a button or type the words “Not Interested” on WhatsApp.

Verification 1 (1)

Note: If no node is configured in the “Trigger Node,” by default, the next node will be executed if the user chooses to skip the current Request User Data node.

If you encounter any issues, please reach out to

What are your feelings
Scroll to Top