Send Flows to eligible WhatsApp contacts
Trigger a Flow from a chatflow, an automation, a support agent, or a template send. The customer sees a single button that opens the full Flow experience. Submission lands back in Zena and syncs to your CRM.
Feature · WhatsApp Flows
Send WhatsApp Flows from Zena
Native, in-chat interactive forms for UAE businesses. Zena sends WhatsApp Flows to eligible contacts, opens dynamic Flows that read live CRM data, and attaches Flow buttons to marketing templates. All on your existing WABA and phone number.
Send Flows to eligible contacts
Dynamic endpoint for live data
Template Flow buttons
Start here
What is a WhatsApp Flow?
A native, in-chat form on the WhatsApp Business Platform. The customer opens it inside WhatsApp, moves through one or more screens of fields, and submits without leaving the chat. No redirect. No web form. No app switch.
Think of it as a small mini-app that lives inside a WhatsApp message. Text inputs, dropdowns, radio buttons, checkboxes, date pickers and image uploads render exactly like the ones your customer already sees on WhatsApp. The data collected lands in your business system the moment they hit submit.
Comparison
Flows vs chatbots vs web forms
Three ways to collect structured information from a WhatsApp lead. Flows keep the whole task inside the chat, which is why completion rates run materially higher than either alternative.
| Dimension | WhatsApp Flow | Chatbot Q&A | Web form (link out) |
|---|---|---|---|
| Where the task happens | Inside the WhatsApp chat. | Inside WhatsApp, but as separate messages. | External browser tab. |
| Typical completion rate | 2 to 5 times higher than a web form for equivalent fields. | Middle. Drops with each additional back-and-forth message. | Baseline. Web form abandonment runs 60 to 70 percent for lead forms. |
| Data quality | Structured, validated at field level. | Free-form parsing. Higher clean-up cost. | Structured, but session cost is higher. |
| Friction | Zero switch. Native UI. | Multiple message exchanges. | Redirect, load, sometimes login. |
| Works for | Fixed intake, appointment booking, KYC, quotes, surveys. | Conversational qualification, small data collection. | Long complex forms, uploads with heavy attachments. |
Completion-rate figures aggregate published benchmarks from multiple BSP studies (Meta, Wati, Splashify, WA.expert) across 2025 and 2026. Ranges are indicative, not guaranteed for a specific campaign.
Zena's product
What Zena's Flow support actually does
Use sending, dynamic-data and template-button capabilities as parts of a configured workflow. Confirm account eligibility, permissions and any external connection before publishing the Flow.
Dynamic endpoint for live data
The Flow calls a Zena endpoint at open time. Show available appointment slots, in-stock catalog items, personalised quotes, region-specific pricing or the customer's own historical data. The Flow updates its screens with what your business knows right now, not what it knew last week.
Template Flow buttons
Attach a Flow to a marketing template. The customer opens the template message, taps the button, and lands directly in the Flow. Complete the intake, the RSVP, the booking, or the KYC step inside the same conversation. No redirect.
Built for UAE workflows
What UAE businesses build with Flows
Five verticals where Zena's Flow support removes the "one more step" that costs conversions today. Every use case sits inside a WhatsApp conversation and submits directly into Zena's CRM.
Lead capture for brokers
Buyer budget, preferred emirate, community shortlist, target move-in date, Ejari status. Broker gets a scored lead in the CRM with the right context to reply in Arabic or English.
Appointment booking
Collect service, optional doctor preference and a preferred appointment time. Live availability requires a tested scheduling connection; confirm the booking only after the diary accepts it. Keep sensitive identifiers and clinical records in an approved separate channel.
In-chat order intake
Menu selection with pricing, delivery zone check, address capture with a saved-address fallback, order-confirmation screen. Cash on delivery or online payment routing on submit.
Product configurator
Colour, size, engraving text, gift-wrap add-on, delivery date. The Flow renders live in-stock options only, based on your inventory feed. Cart lands ready for payment.
Onboarding and KYC
Collect the minimum administrative information needed for onboarding and explain its purpose first. Use an approved separate verification process for sensitive identifiers or documents; the presence of a Flow does not establish regulatory compliance.
Feedback and surveys
Post-service CSAT, NPS, complaint intake with structured fields. Submissions score into a Zena dashboard with segmentation on channel, region and language.
Field types
Flow components Zena supports
Every native WhatsApp Flow component renders inside Zena Flows. Arabic and English labels supported side by side. Right-to-left rendering handled automatically for Arabic content.
T
Text inputSingle or multi-line
D
DropdownSingle choice from list
R
Radio buttonsVisible single-choice
C
CheckboxesMulti-select
📅
Date pickerCalendar UI
★
RatingStar or numeric scale
↑
Image uploadID, receipts, evidence
✓
Opt-in confirmConsent capture
Which do you need
Static Flows vs dynamic Flows
The rule is simple. Static if the form content is fixed for every customer. Dynamic if the Flow needs to read from your CRM, catalog or scheduling system at open time. Zena supports both.
Every customer sees the same content
Feedback surveys, event RSVPs, opt-in forms, complaint intake, warranty registration. No live data lookup required. Fastest to build, easiest to maintain, works for the majority of standard intake forms.
Content changes based on the customer or live data
Appointment booking with real availability, product picker from your live inventory, personalised quotes, region-specific pricing, order lookup with the customer's own history. Zena calls your endpoint on open and renders the Flow with the response.
Workflow integration
How Flows fit inside your Zena setup
Flows are one moment inside a longer customer journey. Zena wires them into the automation, the inbox, the CRM and the team so the submission drives real business outcomes, not a form sitting on a dashboard.
-
Trigger from a chatflow
Send the Flow at the right point in your Zena chatflow. Use it for lead qualification, booking, KYC or intake at exactly the step it belongs to.
-
Sync submissions to the CRM
Every field maps to a CRM property in Zena's WhatsApp CRM. Submissions land as records, not as unstructured chat transcript.
-
Score and route the lead
Combine Flow inputs with your existing scoring rules. Pass to the team inbox or a specific agent. The lead arrives with the right context and the right owner.
-
Feed downstream automations
A completed Flow triggers the next automation: booking confirmation template, welcome sequence, payment link, or follow-up nudge. All inside Zena.
Cost context
Plan for the messages that carry your Flows
Meta message fees are separate from the Zena subscription. Review the current category, recipient-market and conversation-window rules before estimating campaign costs.
Check current fees and your configured workload
Sending a Flow, receiving its submission and triggering a follow-up are different steps. Check the message rules and measure the automation and API workload for your implementation.
Use the WhatsApp pricing guide as context, confirm rates against Meta's current official schedule, and review Zena's current plan allowances separately.
Common questions
WhatsApp Flows FAQ
Answers to the questions UAE teams ask before enabling Flows on their WABA. Verified 28 September 2026 against Meta developer documentation.
What is a WhatsApp Flow?
A WhatsApp Flow is a native, in-chat interactive form built into the WhatsApp Business Platform. Customers open it inside a WhatsApp conversation, fill out multiple screens of fields (text, dropdown, radio, checkbox, date, image upload) and submit without leaving WhatsApp.
Does Zena support WhatsApp Flows in the UAE?
Yes. Zena supports three Flow capabilities natively: sending Flows to eligible WhatsApp contacts from your automation, dynamic endpoint Flows that pull live data from your CRM or catalog, and template Flow buttons that attach a Flow to a marketing template. All three run on your existing WABA and phone number.
What is the difference between a static Flow and a dynamic Flow?
A static Flow shows the same content to every customer. Use it when the form data is fixed (a feedback survey, an event RSVP). A dynamic Flow calls your endpoint at open time and shows content based on the customer or your live data (available appointment slots, in-stock catalog items, personalised quote). Zena supports both.
Do WhatsApp Flows work under Coexistence?
Yes for API-sent Flows. Under Coexistence a single WhatsApp number is shared between the Business App and Cloud API. Flow messages sent through the API on that number work normally. Business App interfaces do not send Flows themselves.
How much does it cost to send a WhatsApp Flow message in the UAE?
Meta message fees are separate from the Zena subscription. Check the current official rate card for the message category, recipient market and applicable conversation window. Do not assume every Flow message is free. See the WhatsApp pricing guide for context.
Do WhatsApp Flows support Arabic?
Yes. Flow content, labels and validation messages accept Arabic input and can be authored in Arabic. Bilingual Arabic-English forms are common for UAE businesses. Confirm right-to-left rendering in the Meta Business Manager preview before publishing.
How does PDPL apply to data collected through a WhatsApp Flow?
Assess the data and rules applicable to your business before collecting it. Explain the purpose, obtain the required permission, minimise fields and agree access and retention arrangements. A form or CRM does not establish PDPL compliance. Healthcare and other regulated workflows require review of their additional obligations.
Talk to Zena
Plan your first WhatsApp Flow
Map the fields, consent, CRM destination and staff handoff before publishing. Where live data is needed, validate the endpoint and selected integration with your team. Use the automation planner to scope the workflow.