WhatsApp Flow
Supported Platform: WhatsApp
WhatsApp Flows is a feature introduced by Meta that enables users to design and deploy interactive forms directly within WhatsApp. It streamlines customer interactions by allowing tasks to be completed without switching to external apps or websites, ensuring that the entire process remains contained within WhatsApp.
With WhatsApp Flows, you can design step by step journeys where customers can:
Share feedback quickly and easily
Fill out and submit forms
Sign up for events or promotions
Choose and send specific support requests to your team
Complete surveys
Book appointments
Log in to their accounts
Get details about your services, like pricing or terms
Beyond these examples, WhatsApp Flows provides additional capabilities, enabling organizations to manage a broad range of customer interactions directly within WhatsApp.

In the following sections, we’ll look at how to set up and manage WhatsApp Flows, connect a Flow with a Bot Builder Card to send it seamlessly to customers, and identify which roles have access to manage WhatsApp Flows.
Roles with Access to WhatsApp Flows
Here are the different roles and WhatsApp Flow permissions:
Administrator
✔️
✔️
✔️
✔️
Manager
✔️
✔️
✔️
✔️
Marketing Staff
✔️
✔️
✔️
✔️
Customer Service Manager
✔️
✔️
✔️
✔️
Customer Service Staff
✔️
X
✔️
X
Sales Manager
X
X
X
X
Sales Staff
X
X
X
X
Marketing & Customer Service Staff
✔️
✔️
✔️
✔️
Set Up and Manage WhatsApp Flows
Step 1: Set up WhatsApp Flow form
Please refer to this guide to set up your Flow form.
Step 2: View Flow List on Omnichat Platform
Once the flow is published in WhatsApp Manager, it will appear in the Omnichat platform under Channels > WhatsApp Flows. You can then set up the response flow and interaction content.

The list is updated hourly via the WhatsApp Flow API (at 5 minutes past the hour, e.g., 12:05, 13:05, etc.).
The information you can view on the list:
Name: Not duplicated, maximum 200 characters. The name is not displayed to the customer.
Flow ID: Used to identify each Flow.
Category: Used to identify the type of Flow. A Flow can have multiple categories, including the following:
Sign up
Sign in
Appointment booking
Lead generation
Contact us
Customer support
Survey
Other
Status:
Draft: Flow content can be edited. Flows at this stage cannot be sent to users.
Published: Flow content cannot be edited.
Deprecated: Deprecated Flows cannot be deleted, sent, or reverted to the published state. Messages sent out cannot be reopened.
Paused: Detected abnormalities by WhatsApp Flow, so the status is changed to paused. In this state, sending or opening is not allowed.
Restricted: Detected abnormalities by WhatsApp Flow, so the status is changed to restricted. In this state, sending or opening is allowed, but it is limited to 10 Flow messages per hour.
Total Responses: The total number of responses for each flow
Action
Edit: Navigate to edit the flow responses
Response Record: View customer response logs and content
Available actions vary depending on flow's status:
Draft
✔️
✔️
X
X
Published
X
X
✔️
✔️
Deprecated
X
X
X
X
Paused
X
X
X
X
Restricted
X
X
✔️ (10 per hour)
✔️
Step 3: Set Up Actions upon Receiving the Response and Response Storage Settings
Click "Edit" under "Action" to open this page.
1. Actions upon Receiving the Response

Success Message
When a customer completes the flow, the system replies with a default message: "Thank you for completing the response form!"
You can also customize it to include emojis and contact names.
Attached Message
Do not send (default setting)
Text
Chatbot Block (WhatsApp chatbot only)
Tags
Applying tags when the customer completes filling out the flow.
2. Response Storage Settings

By clicking "Select Fields" at the bottom of the page, you can choose what to store in Omnichat.
Responses can be saved as custom attributes or as system default fields such as name and email.

Step 4: Share WhatsApp Flow to Customers via Chatbot & WhatsApp Message Template
Chatbot
WhatsApp Flow Card can only be used on WhatsApp.
There are four editable sections in the card:

Title
None
Text: Up to 80 characters
Media:
Image: Accepted formats are .jpg, .jpeg, and .png, up to 5 MB. Files over 5 MB will be automatically compressed.
Video: Accepted format is .mp4, up to 10 MB.
Body
This section is required and supports up to 550 characters. You can include emojis and variables.
Footer
This section is optional and supports up to 60 characters. Emojis and variables are not supported.
Button

Button Name: Required, up to 20 characters (emojis are not supported).
Flow ID: Required, select from flows with a status of "Draft", "Published", or "Restricted".
Screen ID: Defaults to the first screen in the flow and cannot be changed.
Only one button can be added.
Adding WhatsApp Flows in a WhatsApp Message Template
You can add the WhatsApp flow inside your Omnichat WhatsApp Message Template as a CTA button.
We have added a new CTA button type called "Flow" where you can link your button to open a flow for the customer upon clicking on it.
Each template supports only one Flow button, which cannot coexist with other CTAs.
New Flow type for WhatsApp Flow CTA buttons:
Button Name (Required): Limited to 20 characters (each Chinese character is considered as 3 characters).
Flow ID: Only available for flows in the Published or Restricted status.
Screen ID: Defaults to the first set of Screens and cannot be changed.

You can share these WhatsApp Message Templates or Chatbot Blocks with customers in your one-on-one conversations, Broadcasts, Mass Messages (OMO plan), and Journeys.

Step 5: View or Export Response Records
To view all responses submitted through a particular Flow, go to Action > Response Records.

View Response Records
Search and Filter
Search: Supports searching by name or phone number.
Filter: Supports filtering by specified date range, with no limit on the length of the date.
List Fields:
Name: Customer's name on WhatsApp.
Phone: Customer's WhatsApp phone number.
Response Time: the time when the customer completed the Flow form, format: yyyy-MM-dd HH:mm:ss.
List Display and Sorting: Displays response data for all dates, sorted from newest to oldest based on response time.
List Actions
View Response Content
Label: Represents the title, which is the field set in the Flow (on WhatsApp manager backend) as the label.
Response Content: Content of the customer's response.
Delete Response
Exporting the responses
You can export responses to a CSV file by selecting a time period, or by searching and filtering a list of responses, then clicking the Export Response Record button in the top-right corner.
By default, the export includes all response data of the Flow.
If a time filter is applied, the export will include only responses within the specified time range.
If a search filter is applied, the export will include only responses that match the search criteria.
Exported file name: Flow name
Exported CSV fields:
customer_name: Customer's name, default field.
customer_phone: Customer's phone number, default field.
customer_response_time: Time of customer's response, default field.
Other fields will be displayed based on the Flow settings.

In some WhatsApp Flows, customers may be required to provide images, videos, or files. These responses can be viewed, exported, or sent to a third-party backend through the Omnichat Webhook.

The related features include:
Displaying files: Images and files uploaded by customers can be viewed directly within the WhatsApp Flow > Response Records section in Omnichat console.



Exporting records: Go to WhatsApp Flow > Response Records > Export Response Records to generate a CSV file that includes any images, files, or videos submitted by customers when completing the Flow.
Webhook file support: WhatsApp Flow Webhook supports the transfer of images, files, and videos to your own third-party platform.
This feature requires integration by your Engineering team, and is recommended only if technical support is available.
Webhook Setting: You can create a new webhook and select the newly added topic
whatsapp_flow/flow_createon the "Webhook" page.Trigger Timing: When a customer completes the Flow, the data is stored in the Omnichat system and simultaneously sent to the specified Endpoint URL through the webhook.

Response Format:
For further instructions on setting up WhatsApp Flows, please refer to the documentations below:
FAQ
Why don’t the customer responses I receive include the full question and answer?
A: Most likely, the Flow format has not been fully configured. ‣ and check the settings. Alternatively, check if there are any duplicate “Labels” for each question.
Does Flow support saving customer answers to custom attributes in real time?
A: Yes, you can include custom attribute variables in the “Post-Response Trigger.” Once the customer completes the Flow, the system will instantly save their answers to the custom attributes. The card sent at that moment will display the latest data, allowing the customer to view their responses immediately.
Why can’t I find the original question in the Omnichat response content?
A: This is because Omnichat only accepts "label" as the question title. If you use the "Text" type for a question, Omnichat cannot receive that type of Webhook. Since there is a character limit for "label," it may not fully describe the question; you can use "Text" to provide a detailed description of the question.// add agent instructions
Example of an error
Using "Small heading" as the title
e.g. Have you tried the Enfagrow A+ Step 3 product sample you received?

Using a single-choice “label” as a placeholder prevents the system from recognizing the corresponding question (or storing it correctly)
e.g. Select one answer

Correct example
Small heading as the full question description (for customers to see)
e.g. Have you tried the Enfagrow A+ Step 3 product sample you received?

Single-choice “label” used as the question identifier (for internal recognition)
e.g. Did you try the sample?

Last updated