# WhatsApp Flow Form Fields in ZazzyAgent: Complete Guide

The quality of a WhatsApp Flow depends heavily on choosing the right input field.

A customer choosing one option should not have to type an answer.

A customer entering a long explanation should not be restricted to a short field.

ZazzyAgent's WhatsApp Flow builder provides several form components for collecting structured information. The current builder includes Text Field, Text Area, Radio Group, Checkbox Group, Select, Date Field, Header and Submit Button components.

## Text Field

Use a Text Field for short responses.

Good examples:

> Full Name

> Company Name

> Order Number

> Coupon Code

> Email Address

If the customer only needs to provide a short value, Text Field is usually the simplest choice.

## Text Area

Use Text Area when the response can be longer.

Examples:

> Describe your problem.

> Tell us what you need help with.

> Additional requirements

Don't use a Text Area when the answer is simply a name or order number.

## Radio Group

Use Radio Group when the customer should choose **one** option.

Example:

> Which plan are you interested in?

**Basic**

**Pro**

**Enterprise**

The customer selects one.

## Checkbox Group

Use Checkbox Group when customers can select multiple answers.

Example:

> Which services do you need?

☑ Installation

☑ Training

☑ Maintenance

A customer can select more than one.

## Select

Use Select when you have a list of options and want a compact selection interface.

Example:

> Select your city

*   Mumbai
    
*   Delhi
    
*   Bengaluru
    
*   Hyderabad
    
*   Pune
    

This is useful when there are several possible values.

## Date Field

Use Date Field when the customer needs to provide a date.

Examples:

> Preferred appointment date

> Demo date

> Delivery date

A date picker is easier and cleaner than asking:

> Please type your preferred date.

## Header

Headers don't collect customer information.

They help organize the form.

For example:

> Contact Information

followed by:

**Name**

**Email**

Then:

> Appointment Details

followed by:

**Service**

**Date**

This makes longer forms easier to understand.

## Submit Button

The Submit Button completes the form submission.

The current ZazzyAgent flow interface requires a Submit Button for saving a WhatsApp Flow form successfully.

## Example: Lead form

```text
Header
"Your Details"

Text Field
"Full Name"

Text Field
"Company"

Text Field
"Phone"

Header
"Your Requirement"

Radio Group
"Service"

Text Area
"Tell us about your requirement"

Submit Button
"Submit Request"
```

## Example: Customer support form

```text
Header
"Support Request"

Select
"Issue Type"

Text Field
"Order Number"

Text Area
"Describe the Issue"

Submit Button
"Send Request"
```

## Example: Appointment form

```text
Header
"Book a Consultation"

Radio Group
"Service Type"

Date Field
"Preferred Date"

Select
"Preferred Time"

Text Field
"Your Name"

Submit Button
"Request Appointment"
```

## Don't ask customers to type predictable answers

Bad:

> Type your preferred service.

Better:

**Consultation**

**Demo**

**Installation**

Structured inputs reduce unnecessary typing and make the resulting data easier to automate.

## Choose fields based on the data you need

Ask:

> What information will I use after the customer submits this?

If the answer is:

> Nothing.

you may not need the field.

## Design around the customer's decision

A good form follows a natural sequence.

For example:

**What do you need?**

↓

**When do you need it?**

↓

**Who are you?**

↓

**Submit**

The customer shouldn't have to jump randomly between unrelated questions.

## Don't collect information twice

If the customer already provided a value earlier and your workflow can reuse it, avoid asking the same question again.

For example:

> What's your name?

shouldn't necessarily be repeated later if the name is already available.

## Field choice affects automation

The type of information you collect determines what you can do afterward.

For example:

**Radio Group**

gives a controlled category.

**Date Field**

gives a date.

**Text Area**

gives a free-form explanation.

This makes downstream automation easier to design.

## A useful rule

Use:

**Text Field** → short answer

**Text Area** → long answer

**Radio** → one choice

**Checkbox** → multiple choices

**Select** → choose from a list

**Date** → date

**Header** → organize

**Submit** → finish

That's enough to choose the right component in most cases.