Index:

1. Introduction 
2. How does it work?
3. Installation and configuration
   1. Installing the extension
   2. Setting up Flows
   3. Creating Flows in the Dashboard
   4. Testing Flow on WhatsApp
   5. About WhatsApp Flows Test (Meta)
   6. Steps to test Flow
   7. WhatsApp Flows Limitations
4. Tips and good practices
   1. Making a checklist of my Flow
   2. Creating a test environment
   3. Validation and Preview
   4. Security and Privacy Best Practices
5. Usage Examples
6. Support 

Introduction

A WhatsApp Flows extension integrates the Blip platform with Meta's Flows functionality (WhatsApp), allowing developers to create, configure and publish custom flows directly from the bot, without having to leave the Blip environment.

Furthermore, with this extension it is possible to create interactive journeys, such as: appointments, personalized forms, surveys, data collection, and others.

This extension is paid and developed by the company White Wall.

 

How does it work?

The extension has the following features:

• Personalization:creating custom interactive flows that reflect your brand identity and meet the specific needs of your business.
• Easier management:management and publication of your WhatsApp flows in a practical and efficient way directly on Blip.
• Agile development:Quickly design and launch WhatsApp flows, driving customer satisfaction and operational efficiency.
• Enriched Experience:richer, more engaging customer journey with dynamic interactions that drive customer satisfaction and loyalty.
  
  

Installation and configuration

Installing the extension

To use the extension, you must access the Blip website and log in. After that, access the Blip Store and search for WhatsApp Flows. Click on install and select the bot where you want to apply the extension.

Setting up Flows

Flows are structured in JSON, with support for multiple screens. Each screen can contain several interactive components (e.g. text, input fields, buttons, lists, and dropdowns). Navigation between screens is configured via internal actions in the JSON.

Attention! See the official Meta documentation for configuration in this link.

Creating Flows in the Dashboard

During creation, the Flow will be in the Draft state. You will be able to edit and review the code.

If there are syntax errors, they will be displayed in the extension panel:

If there are no errors, it will appear like this:

Attention! Once published, you will no longer be able to edit or delete the Flow. If you want to make changes, you will need to create a new Flow with the updated code. Deprecated Flows may be marked as Deprecated.

Testing Flow on WhatsApp

You can test Flow directly on WhatsApp by interacting with the bot.

Tests can also be done through Meta's playground. Access hereto meet them. 

About the of the WhatsApp Flows (Meta)

While developing a Flow in WhatsApp, it will remain in the Draft state. In this mode:

• All messages sent by Meta are considered tests, as described in the official WhatsApp Flows documentation;

• The system will display all Flow options with a clear indication that it is a simulation environment;

• You cannot personalize messages to the end customer in this state. Personalization will only be applied after the Flow is published, when it moves to the Published state.

Steps to test Flow

Access the WhatsApp number connected to your bot and trigger the Flow in one of the following ways:

• Sending a message that automatically triggers Flow;
• Manually executing the send action through the Builder;
• Using the shipping API.

Then, validate the Flow behavior:

• Check if navigation between screens is fluid;
• Confirm that the buttons and fields are working correctly;
• Test data entry validations.

Observation: For more realistic testing, it is recommended to publish the Flow. This way, the configured messages and logic will faithfully reflect the end-user experience in the production environment.

See more examples at playground da Meta.  

WhatsApp Flows Limitations

The limitations of Flows are:

• After publishing, you cannot edit the Flow.
• Some components may not render correctly on older versions of WhatsApp;
• Latency in mobile connections can impact the end user experience.

Tips and good practices

Making a checklist of my Flow

To make good use of Flows, try to follow the checklist below:

• Check if the JSON code has been validated and has no errors;
• Test the screens, that is, make sure they are navigable and working correctly;
• Check if all required fields have been filled in correctly;
• Check out the Visual Preview;
• Standardize the Flow Name and Version.

Creating test environments

It is recommended to create and test Flows in homologation bots before production. To do this, use the Playground da Meta for rapid testing.

 

Validation and Preview

The extension allows you to validate if the JSON code has errors before publishing. It is also possible to visually preview the screen structure before sending it to production.

Security and Privacy Best Practices

To have good security and privacy practices, always follow the guidelines below:

• Only request data that is really necessary;
• Inform the user about the use of their data (where applicable);
• Make sure the flow complies with LGPD and Meta guidelines.

Usage Examples

You can use WhatsApp Flows as:

• Support screen with ticket opening;
• Shipping confirmation screen;
• Scheduling or data collection forms;
• Consultations about status;
• Screens with NPS fields and dropdown selectors.

Support

If you have any questions or encounter any problems with the extension, please contact us via emailsupport@whitewall.dev.