Ask A Question
Collect user input and save to the CRM
Last updated
Was this helpful?
Collect user input and save to the CRM
Last updated
Was this helpful?
This step helps you ask a question to the user, collect the answer, and save it to the flow-specific CRM fields or any other modules in the CRM. The bot will proceed to the next step only upon receiving input from the user.
The Answer Step possesses the following features:
Validates the user input with specified conditions and sends relevant error messages.
Allows users to skip the question and proceed to the next step.
Redirects the user to a separate step if the validation fails a number of times, as configured by you.
Sends a reminder step if the user does not provide an answer within the timeframe configured by you.
Saves user input into the CRM or a runtime variable for future reference.
The Answer Step facilitates user input validation, sending an error message if the validation fails. To validate user input, click on 'Settings' in the step, and from the left side menu, select the user input type according to your requirements. Below are the input types that you can validate:
Text: The user can input alphanumeric text.
Name: The user can input only alphabets; numerics are not allowed.
Phone Number: The user must input a valid phone number.
Email: The user must provide a valid email address.
Number: The user must input a number to pass the validation.
File: The user must upload a file, such as a PDF or video.
Location: The user must share a location.
URL: The user must share a URL.
Website: The user must share a website.
Date & Time: The user must provide a date and time in a format selected by you.
You need to select the correct input type based on your requirements and provide a relevant error message. If the validation fails, the system will send an error message to the user.
You also have three more optional features to configure, as shown below:
Send the last block again to the user along with the error message. If enabled, the user will receive two messages: the configured error message and then the last block once more.
Skip to the next block after a certain number of failures. If enabled and given a value like 3, the user will automatically skip to the next step after three instances of incorrect input.
Show the "Skip" option as a button. If enabled, the user will get a button to skip this question and move to the next step. You can customize the text for the skip button as well.
Beyond the basic input type validation, you can enable advanced validation to scrutinize user input with multiple conditions. Based on the user input type, you will get different conditions to validate the input.
Here are a few use cases for Advanced Validations:
Postal Code Validation: Check whether the user's inputted postal code falls within your serviceable area.
Proximity Validation: Verify if the user's shared location is within a defined radius.
Domain-Specific Email Validation: Confirm that the user's email comes from specific domains, particularly useful if you wish to accept company domain emails only.
File Type and Size Validation: Check the type and size of the file uploaded by the user. For example, you might want the user to share a PDF, but they send a file in a different format. Or, you might want the user to send a file smaller than 5 MB.
Date Range Validation: Validate whether the user's inputted date falls within a specified period.
If you wish to capture the user's response and save this data into your CRM, or reuse the input in subsequent steps, you can use this feature.
Save to an Existing Attribute: An attribute refers to fields in a CRM module. You can save values to an existing attribute used in the flow.
Add New Attribute: This method allows you to create a new data field in the respective flow module or in the contact module and save the data into it.
Save to Run Time Variable: You can save the response as a runtime variable, which is available only when the user is in that specific conversation. The runtime variable value will be discarded after the conversation ends.
Don't Save User Input if the Attribute Value Already Exists: Enabling this feature ensures that you won't overwrite any values that already exist in that particular field of the CRM.
The Reminder Step is an optional feature that allows you to remind the user if they have not responded within the time you configured in the step. This aids in maximizing interactions. For instance, if a user is in the process of booking a table and gets a call at the final step, causing them to forget about the conversation, the Reminder Step can be useful to bring the user back into the flow.
Each flow also has global reminder settings. You should use the step-specific reminder feature only if you wish to customize the reminder time depending on each situation. Otherwise, the global reminder block is a perfect choice for you.
Click on the Reminder button as shown below;
Here, you can customize the frequency and link to another step as per your requirements. If you wish to resend the previous step, simply link the Reminder Step back to the original step as demonstrated below:
The Dynamic Button Generation feature in Flow Builder is like a powerful tool that makes creating interactions easier and improves user experiences. This feature allows you to easily create dynamic buttons, simplifying the process of making interactive elements. In other words, it helps you create buttons that make your conversations more engaging and user-friendly.
This feature makes it easy to create interactive elements and improve user interactions in flows. By using Trigger HTTP API, Data Lookup, and Webhook capabilities, users can easily make dynamic buttons that fit their conversations, making the chat more engaging and efficient. In Flow Builder, you can use these three sources for dynamic button generation: Trigger HTTP API, Data Lookup, and Webhook.
The trigger HTTP API Action is like a special tool for developers. It lets you connect your chatbot with other apps easily. Through the use of the HTTP API action, users can dynamically create buttons in response to inputs from third-party sources.
For Example, With the help of the HTTP API action, you can fetch data about products from Shopify using their API. Once you have this data, Using the Dynamic button generation feature you can organize it neatly in the Send List menu message. In this List menu, each product's name is listed, along with its description or details.
In Flow Builder, Data Lookup Attributes is a useful tool. It helps users take data(addresses, email IDs, Phone Numbers etc) from their CRM and use it for making buttons that fit their needs. This data can make the chat more interesting and interactive.
For example, if a user has multiple addresses for product delivery, such as a home address and an office address, and they need to choose one for delivery, they can use the Data Lookup Attributes step. This allows users to map data from their CRM and then, using the Dynamic Button Generation Feature, send this mapped data through a Send List Menu Message.
By utilizing Webhook Request Data, users can access responses from third-party applications triggered by specific events. This means that when certain actions or occurrences take place, users can fetch information or responses from external apps. Additionally, by using the Dynamic Button Generation Feature, users can easily send this information as Interactive messages.
For example, users can retrieve daily meeting details from Calendly through webhook requests. By using the Button Generation Feature, users can send the meeting details via a Send List Menu message, where the meeting time is placed in the Section Name and corresponding details in the Choice Description. This simplifies actions for users, allowing them to easily confirm, reschedule, or perform various tasks according to their requirements.
Users can easily send dynamic buttons in their chats using three main message types: List Menu, Quick Reply Button, and Choice Message. This flexibility lets them show options and info in different ways, making chatbots more interactive and engaging for everyone.
Here the user is able to add up to 3 quick reply buttons ,you can quickly offer users response options in the form of dynamic buttons. These buttons adapt to the conversation context, allowing users to make choices that guide the flow.
Step 1 : Click on the Map Dynamic Replies button (see the picture below).
Step 2 : Then Click on Select Dynamic Array button (see the picture below)
Step 3 : Then here you can select the Source Array you want according to your requirements (see the picture below)
Here,you can show users up to 10 choices and their descriptions as dynamic buttons. These buttons adapt to the chat, offering options that fit what users want or talked about before. It's like giving users a custom menu of choices.
Step 1 : Click on the Map Dynamic Replies button (see the picture below).
Step 2 : Then Click on Select Dynamic Array button (see the picture below)
Step 3 : Then here you can select the Source Array you want according to your requirements (see the picture below)
Here, users can add up to 10 choices based on their specific needs, such as listing today's meeting times, available products name etc.
Step 1 : Click on the Map Dynamic Replies button (see the picture below).
Step 2 : Then Click on Select Dynamic Array button (see the picture below)
Step 3 : Then here you can select the Source Array you want according to your requirements (see the picture below)
After selecting the source array, the user can Map Dynamic attributes in message blocks. What we map here will dynamically append as buttons.(See the Picture below)
NB: Quick Replies and Send List Menu is Only Available for Whatsapp Official and Whatsapp Cloud API Channel
