ZazzyAgent User Input | Collect User Information in Whatsapp
Sometimes a customer conversation needs more structure than a normal chat.
You may need to ask:
What is your name?
then:
What service do you need?
then:
What is your preferred date?
ZazzyAgent User Input lets you build these structured question-and-answer experiences inside your automation.
The collected responses can be stored in supported fields and used later in the conversation or other workflows.
What is User Input?
User Input is a way to collect structured information from customers through a series of questions.
It can be used for:
Lead forms
Surveys
Appointment requests
Quotation requests
Feedback
Customer onboarding
Product requirements
Support requests
The current implementation supports free-text and multiple-choice style inputs and can store responses in system/custom fields or supported external destinations.
When should I use User Input?
Use User Input when you know exactly what information you need.
For example:
Lead form
Name
Company
Requirement
Budget
Use a normal AI conversation when customers need freedom to explain something in their own words.
You can also combine both.
Create a User Input flow
Open the User Input section in ZazzyAgent.
Create a new User Input campaign.
Give it a clear name.
Good:
New Lead Form
Appointment Request
Customer Feedback
Avoid:
Form 1
Test
Add your first question
Create a question such as:
What is your name?
Choose the appropriate input type.
Save the response to a suitable field.
For example:
Name → Name field
Free Keyboard Input
Free Keyboard Input allows the customer to type their own response.
This is useful for:
Names
Companies
Requirements
Comments
Addresses
Other text-based information
Example:
What product are you interested in?
Customer:
Running shoes
Multiple Choice
Multiple Choice gives customers predefined options.
Example:
What type of customer are you?
Individual
Business
Reseller
Multiple Choice is useful when you want the customer's answer to remain within a known set of choices.
Save the response
A response can be stored in an appropriate system or custom field.
Example:
What city are you in?
↓
City custom field
Customer:
Pune
Now the customer record contains:
City = Pune
Build a multi-step form
You can connect several questions.
Example:
Question 1
What's your name?
↓
Question 2
Which product are you interested in?
↓
Question 3
What's your budget?
↓
Question 4
Would you like a callback?
This creates a structured lead-collection workflow.
Don't ask everything at once
Avoid sending a huge message such as:
Please provide your name, phone number, email, city, budget, product category and preferred date.
Instead, break it into manageable questions.
Customers are more likely to understand what you are asking when each step has one clear purpose.
Required vs optional information
Only make information required when you actually need it.
For example:
Name: Required
Product: Required
Budget: Optional
This prevents unnecessary friction.
Validate customer responses
Where supported, use validation to make sure the information is usable.
For example:
Enter your email address.
The workflow can validate whether the response has the expected format.
Validation is especially useful for:
Email addresses
Phone numbers
Numbers
Dates
Other structured inputs
Use collected information later
Suppose User Input collected:
Name = Priya
Product = Sofa
Budget = ₹50,000
Your next flow step can use that information.
Example:
Thanks, Priya. I'll help you find sofas within your ₹50,000 budget.
Send collected data to Google Sheets
Supported User Input workflows can send collected information to Google Sheets.
This is useful for:
Lead lists
Survey responses
Appointment requests
Customer enquiries
Send collected data to a webhook
You can also use supported webhook functionality when your information needs to be sent to another application.
For example:
Customer completes form
↓
Webhook
↓
CRM
This allows your form to become part of a wider business process.
User Input vs AI
Use User Input when you need structured answers.
Use AI when customers need to communicate naturally.
Example:
Structured
Select your preferred appointment day.
User Input works well.
Natural
I can come any day next week except Wednesday.
AI is better suited to understanding the message.
User Input vs WhatsApp Flows
Both can collect customer information, but they provide different experiences.
User Input is useful for conversational question-and-answer flows.
WhatsApp Flows are designed for structured form experiences within WhatsApp.
Choose the option that best matches the experience you want to create.
User Input troubleshooting
Customer response isn't saved
Check:
Correct field selected
Input step is connected
Response type matches the field
Customer actually completed the step
Validation rejects valid information
Check the validation configuration and expected format.
Form stops halfway
Check that each input step correctly connects to the next step.
Data isn't reaching Google Sheets
Check:
Google Sheets connection
Sheet permissions
Field mapping
Required columns
Workflow configuration
Example: Lead Qualification Form
A simple lead flow could be:
What's your name?
↓
Save Name
↓
What are you interested in?
↓
Save Product Interest
↓
What's your budget?
↓
Save Budget
↓
Condition:
Budget ≥ ₹20,000
↓
Premium lead path
Otherwise:
↓
Standard lead path
This is a simple example of how User Input, Custom Fields and Conditions can work together.
zazzyagent.com