WhatsApp Flows: how to use forms inside the conversation to qualify, schedule, and quote without losing the customer

The six most effective uses

1. Lead qualification

The lead arrives via ad, website, or Instagram and receives a short Flow: interest, company size or need size, deadline, and investment range. The answers decide which salesperson the conversation goes to and with what priority.

2. Scheduling

Location, service, professional, date, and time. With an integration that checks the calendar in real time, the customer only sees truly available times. Without integration, the Flow collects preferences and the team confirms.

3. Quoting

For services that depend on technical information — measurements, quantity, model, installation address — the Flow collects everything before a quote specialist opens the conversation. The quote is faster and with fewer back-and-forths.

4. Registration and enrollment

Enrollment in trial class, event, webinar, waiting list, or referral program, with recorded consent.

5. Satisfaction survey and NPS

Rating, reason, and optional comment on one screen, right after service or delivery. The response rate is usually much higher than email surveys because it happens on the channel where the conversation took place.

6. After-sales and support

Ticket opening with problem type, order number, photo, and description. The agent receives the case classified and with what’s needed to resolve it.

How a Flow works behind the scenes

Without going into code, it’s worth understanding the parts because they define what’s possible:

• Screens and components. The Flow is a set of screens. Each screen has text and input components. The flow between screens can be linear or depend on previous answers.
• Creation. Flows can be built in the WhatsApp Manager builder from Meta or defined by a JSON structure via the platform the company uses. Once ready, the Flow must be published to be sent to customers.
• Static Flow or with data exchange. The static has fixed options defined at creation — list of locations, budget ranges. The dynamic queries a company server during filling, for example to show free times or calculate a value, with encrypted communication.
• Sending. Within the 24-hour service window, the Flow can be sent as an interactive message. Outside the window, it must be sent as a button inside an approved message template.
• Response. When the customer finishes, the company receives structured data, which the platform records in the conversation and contact record.

The Short Screen Method: how to design a Flow that people complete

A poorly designed Flow is just a boring form inside WhatsApp. Four rules make the difference between the customer completing or closing the screen:

Rule 1 — One decision per screen

Each screen answers one main question. "Which service?" on one screen, "Which date?" on the next. Screens with eight fields feel like work.

Rule 2 — Maximum four screens

If the Flow needs more than that, it’s probably asking for information that can wait for the agent conversation. Ask only what decides the next step.

Rule 3 — Option before text

Whenever the answer fits a list, use a list. Free text only for name, problem description, and truly open information — preferably as an optional field.

Rule 4 — Say what happens next

The last screen explains the result: "You will receive confirmation within 10 minutes" or "A specialist will contact you today with the quote." Without this, the customer finishes and waits not knowing what.

Complete example: evaluation scheduling Flow

An example for a clinic with two locations, which you can adapt for any appointment-based business:

• Initial message: "Hi, Ana! To schedule your evaluation, just tap the button below. It takes less than a minute." Button: Schedule evaluation.
• Screen 1 — Where: "At which location do you prefer to be served?" Options: Downtown Location, South Zone Location.
• Screen 2 — What: "What is your main interest?" Options: facial treatment, body treatment, harmonization, not sure yet.
• Screen 3 — When: date picker with the next 15 business days and list of periods: morning, afternoon, evening.
• Screen 4 — Confirmation: full name (auto-filled if already in record), consent checkbox to receive reminders via WhatsApp, and the text: "Our team will confirm the exact time within 10 minutes, right here."

When the clinic has integrated scheduling, screen 3 shows truly free times and confirmation is immediate. Without integration, the Flow already saves all the data collection, and the team just confirms the time.

The calculation: how much is it worth to replace loose questions with Flow

With illustrative numbers from a company that receives 600 leads per month via WhatsApp:

• Today: data collection is done by questions in messages. 55% of leads answer everything needed to schedule. That’s 330 possible appointments.
• Each collection takes on average 6 minutes of agent time spread throughout the conversation: 60 hours of work per month.
• With Flow: suppose 70% complete the form. That’s 420 possible appointments — 90 more per month.
• If 40% of those scheduled show up and 30% of them buy, with an average ticket of R$ 900, the 90 extra appointments represent about 11 sales and nearly R$ 9,700 per month.
• And the team recovers much of the 60 hours spent collecting data, which now goes to closing conversations.

Integration with CRM and automation

The Flow yields little if responses remain trapped in a message. The value appears when each field becomes useful data:

• Contact fields. Location, interest, budget range, and preferred date become contact attributes, searchable and filterable.
• Distribution. The answer decides who handles it: harmonization to the specialist, quote above a certain range to the senior salesperson.
• Funnel stage. Completing the Flow moves the lead to "qualified" or "appointment requested" automatically.
• Next messages. Appointment reminders, confirmations, and follow-ups are sent based on collected data, without anyone retyping anything.

Flow, question chatbot, or website link?

There are three ways to collect information via WhatsApp, and each has its place:

• Sequential question chatbot. Works for one or two simple questions and when the conversation needs to feel natural. With more than three, abandonment rates rise and answers arrive unstandardized.
• Link to form on website. Takes the customer out of WhatsApp, opens the browser, sometimes requires loading a slow page on mobile — and some people don’t return to the conversation. Makes sense for long registrations or payments.
• Flow. Best option when collecting three to ten pieces of information, with answers fitting options, and when keeping the customer inside the conversation matters.

In practice, the best automations combine all three: an open question to understand the topic, a Flow to collect data, and a link only when it’s time to pay.

How to measure if the Flow is working

• Open rate: how many tapped the button among those who received it.
• Completion rate: how many finished among those who opened. A sharp drop indicates a long screen or a question that blocks progress.
• Time to complete: if it takes more than two minutes, the Flow is asking too much.
• Conversion after the Flow: confirmed appointments, quotes sent, and sales from those who completed, compared to those served only by message.

Meta's rules and best practices

• The 24-hour window still applies. Outside it, the Flow can only be sent as a button in an approved template, with the correct category — a satisfaction survey Flow after a purchase isn’t the same as an offer Flow.
• Don’t request sensitive data unnecessarily. Meta restricts collecting information like full card data and passwords. And LGPD requires collecting only what’s necessary for the stated purpose.
• Clear consent. If the Flow also authorizes future messages, this must be explicit on the screen, not implicit.
• Number quality. Sending Flow to people who didn’t request it, in bulk, causes blocking and reports like any other message — which lowers the number’s quality.

Errors that prevent Flow completion

• Long form, copied from the website, with all possible fields.
• Asking what the company already knows — phone, name already in the record.
• Free text where a list would fit.
• Sending the Flow without context, without a message explaining its purpose and how long it takes.
• Not saying what happens next and leaving the customer without feedback.
• Response that reaches no one. The customer fills it out and the team isn’t notified, or the data doesn’t enter the record.
• Using Flow for everything. A simple question is better solved with a human response than a form.

Where to start

Choose the moment in the conversation when the team repeats the same questions most — usually qualification or scheduling. List only the information that decides the next step, turn each into options whenever possible, and design a maximum of four screens using the Short Screen Method. Publish, send to new leads for two weeks, and compare with the previous period: completion rate, appointments, and team time per lead. With these numbers, it’s easy to decide the second Flow.