WhatsApp Forms: How to Collect Customer Details in a Chat

A WhatsApp form is a way to collect customer details inside a chat, and Meta’s own feature for it is called WhatsApp Flows. A customer taps a button, fills in fields on screens that open in WhatsApp, and submits, without going to a website.

People also say “WhatsApp form” when they mean a chatbot that asks questions one at a time, or a lead form on an ad or website that feeds into WhatsApp. This guide explains each one, what works in Automate AI, which to pick, example fields, and what you must never ask for in a chat.

What people mean by “WhatsApp forms”

WhatsApp has no feature called “forms”. The phrase covers four different things:

Flows and chatbots both need the WhatsApp Business Platform (API). The free Business app has quick replies and greeting and away messages, but no form or chatbot builder.

WhatsApp Flows: Meta’s in-chat forms

A Flow is built from screens, and each screen holds components such as text inputs, dropdowns, date pickers and checkboxes. It collects several fields in one structured step, so there’s less typing and fewer typos.

Meta gives two ways to send one: as a button on an approved template, or as an interactive message in a conversation the customer started. A few things to know:

• Requirements: Meta asks for a verified business and high message quality.
• Building: you use the Flow Builder in WhatsApp Manager, or Flow JSON through the API.
• Servers: simple forms need none. Live data, such as free appointment slots, needs a data endpoint.
• Devices: Flows work on phones, not on companion devices such as WhatsApp Web.

Limits, publishing and costs are in our full guide to WhatsApp Flows.

Forms in Automate AI

Automate AI doesn’t have a visual Flow builder. Instead, you add a form to a Utility template. Open Templates, choose Create Template, pick the Utility category and tick Enable form to collect customer information. Then choose a form type:

Add the button text and a webhook URL. The URL is where submissions are sent, so point it at your own system. A Custom Fields form needs one.

The neatest setup is a keyword reply. In Automation › Basic Replies, choose Respond with template, so someone who types “BOOK” gets the form straight away. The chatbot builder has no form step, so use the questions below inside a chatbot.

Collect details with chatbot questions

For most small businesses this is the easiest place to start. It needs no Flow and no developer, and the answers land on the contact. Build it in the chatbot builder at Automation › Flows, included in Series 2, 3 and 4:

1. Start the flow on a keyword such as “enquiry”, or when a new contact messages you.
2. Ask one question in a text step, such as “What’s your name?”
3. Add an Update Contact step straight after it and pick the field, such as First Name. The flow waits for the customer’s next message and saves it there.
4. Repeat for each typed answer: email, city, company or a custom field.
5. Use buttons or a list for choices. Each option can have its own branch, where Add to Group records the choice, such as “Mumbai leads”.
6. Finish with a thank-you and what happens next.

Two more steps help. Collect Media asks for a photo or document. AI Validation can ask for a date and time, and keeps asking until it gets a real one that isn’t in the past.

Don’t save a reply into Phone Number, because that’s the number you reach them on. Put a second number in Notes. More on the options in WhatsApp buttons and lists.

Lead forms and website forms

Sometimes it’s better to collect details before a chat starts. In Automate AI, lead capture is included in Series 2, 3 and 4, and saves these as contacts automatically:

• Facebook Lead Ads: connect the Pages that run your lead ads, and each new submission becomes a contact, with an instant WhatsApp template if you want one. See Facebook Lead Ads to WhatsApp.
• Website forms: send submissions to a contact webhook with your API key, pick a group and status, and send a welcome message.

One rule catches people out. A lead who filled in a form hasn’t messaged you, so your first message must be an approved template. The form also needs opt-in wording that names your business. See WhatsApp opt-in.

Which one should you use?

Use cases and example fields

Ask for as little as you can. These are sample field lists to adapt:

What you must never ask for in a chat

WhatsApp’s Business Messaging Policy says not to share, or ask people to share, full payment card numbers, financial account numbers, personal ID card numbers or other sensitive identifiers. That applies to every option above, including Flows.

• Never ask for full card numbers, bank account numbers, national ID numbers or passwords.
• Keep health details out of chats. Clinics can confirm a date and time without asking what’s wrong.
• Take payments on a secure page. Send a link rather than collecting anything in the chat.
• Collect only what you need, and follow your local data rules. Meta reminds businesses to do this for Flows too.
• Say why you’re asking and what happens next.

Tips for forms people finish

1. Keep it short. Meta’s guidance is that a Flow should take no more than 5 minutes; a chatbot should feel quicker still.
2. Offer choices where you can. A tap is easier than typing.
3. Make extras optional, so a missing detail doesn’t stop someone.
4. Explain formats, such as how to write a date.
5. Confirm at the end. Meta advises replying after a Flow is submitted, with next steps and how to change or cancel.
6. Offer a person. WhatsApp’s policy requires a clear way to get help beyond the bot.