This is Part 2 of a six-part series exploring the findings of Meta's State of Business Messaging 2026 report and what they mean for businesses using HubSpot and WhatsApp.
In Part 1 of this series, we established the headline finding from Meta's State of Business Messaging 2026 report: 73.3% of consumers prefer messaging as their primary channel for business communication. The commercial case is clear.
But here is where many businesses go wrong. They hear "consumers want WhatsApp" and respond by doing what they have always done, just in a different channel. They take their email marketing playbook, swap the delivery mechanism and start sending WhatsApp broadcasts.
The result? A new kind of inbox noise. And the data shows consumers have very little patience for it.
According to the Meta report, 69.9% of online adults feel frustrated when they receive irrelevant messages from a business.[1]
Nearly seven in ten. And this is not frustration with the channel; consumers love messaging. This is frustration with how businesses are using it. The report's framing is precise: customers do not dislike marketing. They dislike bad marketing.
The distinction matters. Three out of four online adults say they value receiving personalised messages about products, services, discounts and sales.[1] They want to hear from you. They just want the communication to be relevant, timely and personal.
When you send a blanket WhatsApp broadcast to your entire contact list, you are treating WhatsApp like email. And you are likely frustrating a significant portion of your audience in the process. If your CRM still relies on email as the default outreach channel, it is worth asking whether you even have enough customer WhatsApp numbers to make the switch effectively.
The report reveals something that should reshape how we think about business messaging: 75.1% of consumers want to communicate with businesses the same way they do with friends and family.[1]
This is a much higher bar than "use their first name in the subject line." When someone messages a friend, the conversation is contextual, responsive and two-way. There is memory. There is relevance. There are no mass blasts.
Meanwhile, 72.1% of online adults find messaging more personal than other forms of communication, and 77.3% feel more connected with a business when they can message them directly.[1] Consumers are telling us that the channel itself carries an expectation of intimacy and relevance. Violating that expectation with generic content does not just miss the mark; it actively damages the relationship.
Systematic personalalisations are no longer sufficient. Consumers perceive true personalisation through natural conversations that feel connected and contextual.
Here is the cycle we see with many businesses that have adopted WhatsApp for marketing:
This is the broadcast trap: using WhatsApp to send at scale without having the infrastructure to receive and process at scale. You have created a new channel for generating work, not automating it.
The natural response to the volume problem is "let us add a chatbot." And the Meta report shows that consumers are broadly open to this: 67.7% agree that getting a response from an AI chatbot is helpful, and a similar percentage believe AI-powered chatbots will be a useful way to get help in the future.[1]
But chatbots introduce a different problem: unstructured data.
When a customer interacts with a chatbot, they type in natural language. The chatbot interprets, responds and (hopefully) moves the conversation forward. But what you are left with at the end is a conversation transcript, not clean, structured data that your CRM can reliably act on.
If a customer tells a chatbot "I'd like to book for four people next Thursday, one of us is vegetarian and it's my wife's birthday," that is rich, useful information. But it is buried in a sentence that needs natural language processing to extract, and the confidence level on each data point varies.
Chatbots are brilliant for answering questions. They are less reliable for collecting data you need to automate against.
There is a better approach, and it is built into WhatsApp itself.
WhatsApp Flows allow businesses to create guided, form-based interactions directly inside a WhatsApp conversation. Instead of asking customers to type free-text responses, you present them with structured input fields: dropdowns, date pickers, radio buttons, text inputs with validation.
The customer's experience stays conversational; they are still in WhatsApp, tapping through screens that feel native to the app. But the data that comes back is clean, validated and structured. Every field maps to a property in your CRM. Every response can trigger a specific workflow action.
This is the shift from messaging to automation. You are not just sending messages and hoping for useful replies. You are collecting structured data that powers the next step in the journey, automatically. If you are new to this concept, our Flows, Campaigns and Use Cases guide walks through the practical details.
Consider the difference:
| Step | Broadcast Approach | Structured Flow Approach |
|---|---|---|
| Outreach | Generic message to all contacts | Targeted message with Flow button |
| Response | Free-text reply requiring manual reading | Guided form with dropdowns and validation |
| Data | Unstructured text in an inbox | Clean CRM properties, instantly actionable |
| Automation | Manual follow-up, often delayed | Workflow triggers automatically |
The Meta report includes a fascinating dataset on the types of messaging-based activities consumers enjoy. The top-scoring activities are all transactional and structured in nature:[1]
These are not conversational activities. They are transactional ones. And they all map naturally to structured WhatsApp Flows rather than free-text exchanges.
Consumers are telling us, through their behaviour, that they want guided, structured interactions on messaging channels. They do not want to type paragraphs; they want to tap through a clean, quick form and get on with their day.
The businesses that will win in this new era of messaging are not the ones sending the most WhatsApp broadcasts. They are the ones building workflows that run on structured data.
That means moving from "send and hope" to "send, collect, automate." It means thinking about WhatsApp not as a marketing channel, but as a data collection and customer journey platform.
At Flowella, this is exactly the problem we have built for. Flowella lets you turn the forms you already use in platforms like HubSpot into WhatsApp Flows, so customers complete a guided form in WhatsApp, and the answers are returned to your CRM as clean, structured data. No custom endpoints. No encryption plumbing. No messy free-text parsing. You can get started in minutes.
That one shift, from free-text chatting to structured responses, unlocks fully automated workflows. You can trigger actions, apply branching logic, update CRM properties and only involve a human when it genuinely matters.
In the next article in this series, we will make this tangible with a real-world example: how a single WhatsApp Flow can transform a restaurant's entire customer experience, from booking confirmation through to post-meal feedback and review generation.
See how Flowella turns your forms into automated WhatsApp Flows. Start your free trial or learn more about WhatsApp Flows.