Aahfil.

the form never leaves the chat

WhatsApp Flows: forms and bookings inside the chat

WhatsApp Flows are forms that open inside the chat: one or more screens with text fields, dropdowns, date pickers and checkboxes, sent back with one tap. Kuwait businesses use them for lead forms, appointment bookings, delivery details and feedback. Basic forms come with every Gallabox plan; dynamic forms that change with each answer and pull live data need Advanced.

What a WhatsApp Flow is

A Flow is a small form that WhatsApp opens on top of the chat. The customer taps a button, moves through one or more screens — text boxes, dropdowns, single and multiple choice, a date picker — and submits. Your business gets the answers back as one structured reply instead of a string of loose messages someone has to read and retype.

It is Meta's own feature, so it looks and behaves the same on every phone and never sends the customer to a website. That matters for people who start on Instagram, tap through to WhatsApp and would rather not open a browser just to book an appointment or leave their details.

Flows sit between a chatbot and a web form. A bot is good at conversation and at deciding what happens next; a Flow is good at collecting several pieces of information cleanly. Most of the setups we build use both: the bot greets and routes, and a Flow does the collecting.

What Kuwait businesses use them for

Lead forms are the obvious start. A real-estate office asks for area, budget, bedrooms and move-in month on one screen; a car dealer asks for model, trim and whether there is a trade-in; a training centre asks for course, level and preferred days. The sales team opens a chat that already has the answers in it.

Bookings come next. A clinic or salon Flow lists the services, offers a date picker for the day and shows the times as options, then confirms. Where the free slots have to come from your calendar in real time, that is a dynamic form and needs the Advanced plan; a fixed list of times works on any plan.

Delivery details are the most Kuwaiti use of all. Instead of asking for an address in free text, the form offers the areas you deliver to as a list, then block, street, avenue, building and floor as separate fields, and the chat asks for a location pin before or after the form. Drivers make fewer calls asking where to go. Short feedback forms after a visit or a delivery round it out.

Bilingual screens, written for each language

Every screen in a Flow — the title, each label, each option, the button — is text you write. A Kuwait form needs an Arabic version and an English version, and the customer should get the one that matches the language they chose earlier in the chat.

Arabic screens read right to left, and labels that fit neatly in English often run long in Arabic. We write the Arabic for the fields that matter most first, keep labels short, and check every screen on a real phone in both languages before it goes live. Area names are spelled the way people in Kuwait write them, in both scripts, so the list is quick to scan.

Keep each screen short. Every extra field is another reason to stop. If a question doesn't change what your team does next, leave it out; you can always ask in the chat later.

Collect only what you need

A form makes it easy to ask for a lot, and that is exactly the risk. Civil ID numbers, dates of birth, medical details and salaries are sensitive, and a lead form almost never needs them. Ask for them only when the service really depends on it, say why on the screen, and limit who in your team can see the answers.

In Kuwait, handling personal data falls under rules such as CITRA's Data Privacy Protection Regulation. We are not lawyers and this is not legal advice, but the practical habits are the same everywhere: tell people what you collect and why, get a clear opt-in before you message them later, and don't keep what you no longer need.

A useful test: if the form's answers leaked tomorrow, would any field embarrass you or hurt a customer? If so, ask whether that field has to exist at all. A shorter form is also a form more people finish.

What a Flow costs to run

Meta charges for the message that carries the form, the same way it charges for any other message a business sends. Inside the 24-hour window that opens when a customer writes to you, the form goes out as a normal reply. Outside that window it has to travel inside an approved template, billed at that template's category rate.

From 1 October 2026 that reply stops being free in Kuwait: each number gets 1,000 free service messages a month, and after that each one costs Meta's Kuwait service rate of $0.044 before the provider's markup. A Flow helps here. One form that collects six answers replaces a bot that would have sent six separate questions, so the same job uses fewer paid messages.

If the customer arrived from a Click-to-WhatsApp ad and you replied within 24 hours, every message for the next 72 hours is free, templates included. A lead form sent inside that window costs nothing in Meta fees, which makes an ad followed by a Flow a tidy way to qualify leads.

How we set it up

  1. 01

    Pick the job

    One form per job: a lead form, a booking, delivery details or feedback. We list only the fields your team actually uses.

  2. 02

    Build from a template

    We start from a Gallabox Flow template, cut every field that isn't needed and decide where the answers go.

  3. 03

    Write both languages

    Arabic and English screens, written separately, with labels sized for a phone screen.

  4. 04

    Test, connect, launch

    We submit test entries from real phones, check they land in the inbox and your CRM or sheet, then attach the form to your bot or template.

Kuwait & the GCC

What’s different here

Area, block, street — not one address box

Kuwait addresses have parts people know by heart. Separate fields for area, block, street, avenue and building, plus a location pin in the chat, save the driver a phone call.

Booking lists that know your hours

Friday and Saturday slots, and Ramadan's changed hours, should only appear when you are open. A fixed list works on any plan; live availability from your calendar is a dynamic form on Advanced.

Sensitive fields need a reason

Don't ask for a Civil ID number unless the service needs it. In Kuwait, CITRA's Data Privacy Protection Regulation is the name to know; for what it requires of you, ask a lawyer.

Which plan?

From Basic

Basic forms are included on every plan, Basic too. Dynamic forms, which change with each answer and pull live data from your systems, need Advanced.

Connects with

  • Google Sheets
  • Zoho CRM
  • HubSpot
  • Calendly
  • Webhooks
  • Gallabox API

Integrations Gallabox documents. Kuwaiti gateways such as KNET have no built-in integration; we connect them with payment links or a custom build.

A question about your own business?

Send it on WhatsApp. We reply with a straight answer: whether you need the API at all, which plan, and which flow is worth building first.

Frequently asked questions

Do I need the WhatsApp API for Flows?
Yes. Flows are a WhatsApp Business Platform feature; the free Business app doesn't have them. On Gallabox you build them in the Flows builder and send them from your API number.
Can a Flow take payment in Kuwait?
Not inside the chat. WhatsApp's in-chat payments aren't available to businesses in Kuwait or anywhere in the GCC. A booking or order form can end by sending a payment link from your gateway, and a webhook from the gateway can confirm the payment.
What's the difference between basic and dynamic forms?
Basic forms show the screens and options you set in advance, and they are on every plan. Dynamic forms change with the customer's answers and can pull live data, such as open appointment slots, while the customer fills them in. Those need Advanced.
Where do the answers go?
Into the contact's record in Gallabox, where your team sees them next to the chat. From there they can be sent on to a CRM, a Google Sheet or your own system through webhooks or the API.
Ask us on WhatsApp