What’s the difference between broadcasts in the Business app and the Cloud API?
WhatsApp broadcast messages work in two completely different ways. The WhatsApp Business app allows you to send messages to only 256 contacts, requires a dedicated phone that stays connected at all times, and does not integrate with other systems. The WhatsApp Cloud API, on the other hand, is infrastructure that Meta provides to businesses that want to send messages at scale, connect WhatsApp to a CRM or lead management system, and build automated processes that respond to customers according to rules you define.
The API does not require a physical phone. It operates through a business number that Meta verifies, and connects to your system via webhook. Every incoming message reaches your system in real time, and every outgoing message is sent through an API call. We build this connection in n8n, so it interfaces with Google Sheets, with a CRM, or with any other system the business works with.
The most significant difference is in scale: the API has no limit on the number of contacts, but Meta has strict policy about what you may send, when, and to whom.
What are you allowed to send in broadcast messages under Meta’s policy?
Meta allows you to send broadcast messages only to customers who have given explicit consent to receive messages from your business. Consent must be specific – “I agree to receive updates on WhatsApp” – not general. You may not buy phone lists, send to numbers that did not request it, or send marketing messages to anyone who did not explicitly agree.
The first message you send to a customer must be a template pre-approved by Meta. You write the template, submit it for approval, and Meta checks that it complies with policy. A template can contain variables – customer name, order number, date – but the general structure is fixed. Only after the customer replies to you does a 24-hour window open in which you can send free-form messages.
Meta divides messages into three categories: marketing, utility, and authentication. A marketing message is a promotion, discount, or update about a new product. A utility message is an order confirmation, delivery update, or appointment reminder. An authentication message is a one-time code. Pricing varies by category, and policy is stricter on marketing messages.
We build systems that record consent, store it in the CRM, and send only to those who approved. The system also automatically handles anyone who asks to be removed from the list.
How much does it cost to send broadcast messages via WhatsApp Cloud API?
WhatsApp Cloud API charges per conversation, not per message. A conversation is a 24-hour window that opens when you send a message to a customer or when the customer sends to you. All messages within those 24 hours count as one conversation. If you sent a customer a message at 10:00 and again at 15:00 on the same day, that’s one conversation. If you sent again the next day, that’s a second conversation.
Pricing varies by country and by message category. In Israel, currently, a utility conversation costs less than a marketing conversation. A conversation the customer opened – meaning they sent you a message first – is cheaper than a conversation you opened.
The first thousand conversations each month are free. That’s enough for a small business starting out, but not for a business sending hundreds of messages a day. Beyond that, you pay per use. Meta publishes rates on its site, and they change from time to time.
It’s important to understand that the true cost also includes the infrastructure that connects the API to your systems. We build this in n8n and connect it to a CRM or Google Sheets. The cost of n8n depends on monthly execution volume, and it is significantly lower than other platforms.
| Conversation type | Who opens | Example | Relative cost |
|---|---|---|---|
| Customer-initiated | Customer sent first | Customer asks about product | Lowest |
| Utility message | Business sends first | Order confirmation, delivery update | Medium |
| Marketing message | Business sends first | Promotion, discount, new product | Highest |
How do you build a system that sends broadcast messages correctly?
A proper broadcast message system starts with a managed contact list. We build this in Google Sheets or in a CRM, with columns that record the phone number, consent date, the category the customer belongs to (active customer, lead, former customer), and status – whether they agree to receive messages or not.
The second step is creating message templates in WhatsApp Business Manager. You write the template, define the variables (name, order number, date), and submit for Meta approval. Approval takes between a few hours and a day. After the template is approved, you can use it.
We build a workflow in n8n that links the list to the API. The workflow reads the list, filters only contacts who consented, fills in the variables in the template, and sends the messages. It also records every send, so you know who received a message and when.
The system includes error handling: if a phone number is invalid, if the customer blocked the business, or if Meta rejected the message for any reason, the workflow logs it and updates the list. We also build an automatic opt-out mechanism: if a customer sends “stop” or “unsubscribe”, the system removes them from the list immediately.
The systems we build operate on a schedule you define – once a day, once a week, or in response to a specific event (new order, payment received). They also interface with other systems: if you work with an accounting system like Green Invoice, you can send an automatic message when an invoice is issued.
For more on building such systems, see our chatbot and WhatsApp automation solutions page.
What happens when Meta rejects a message or blocks an account?
Meta tracks the quality of the messages you send. If customers block you at a high rate, or report your messages as spam, Meta lowers the quality rating of the account. A low rating leads to restrictions: first Meta limits the number of messages you can send per day, and in extreme cases it blocks the account entirely.
The way to prevent this is to send only to those who requested, send relevant content, and provide a clear option to be removed from the list. We build systems that track the quality metrics Meta provides in the API, and alert if the rating drops.
If a specific message is rejected, the API returns an error code that explains why: invalid number, customer blocked the business, template not approved, or the account reached the daily send limit. The systems we build log these errors and update the list, so you don’t keep trying to send to numbers that don’t work.
Account blocking is rare if you work according to policy, but if it happens, the process to reopen is long and requires proof that you fixed the problem. So prevention is far more important than repair.
Can you send broadcast messages with file attachments?
WhatsApp Cloud API supports sending files: images, PDF documents, video files, and audio files. The template you submit for approval can include an attachment, but the file itself must be stored on an accessible server and sent as a URL. You cannot attach a file directly from your computer at send time.
We build systems that upload files to a server (for example Google Drive or another storage server), generate a public link, and send it through the API. This is useful for businesses that send catalogs, invoices, or presentations to customers.
It’s important to know that large files slow down sending and cost more in data volume. Meta limits the maximum file size by type: image up to 5MB, document up to 100MB, video up to 16MB. If you’re sending heavy files to thousands of customers, consider sending a link to a web page instead.
Another system we build is automatic invoice sending: when the accounting system issues an invoice, the workflow downloads the PDF file, uploads it to a server, and sends the customer a message with the link. All this happens without manual intervention.
For more on connecting WhatsApp to CRM systems, see our guide to WhatsApp CRM integration.
Frequently asked questions
Can you send WhatsApp broadcast messages without prior customer approval?
No. Meta's policy requires explicit consent from every customer before sending messages. You may not buy phone lists or send to numbers that did not request it. Violating the policy can lead to account blocking. Consent must be specific – "I agree to receive updates on WhatsApp" – not general.
What happens if I send a broadcast message to a customer who hasn't opened WhatsApp in a year?
The message will be sent just like to any other customer, and you'll be charged for a conversation. But if the customer is inactive, the chance they'll block you or report the message is higher, and that hurts the quality rating of the account. It's worth cleaning the list periodically and removing customers who don't respond.
Do I need a separate phone number for sending broadcast messages via Cloud API?
Yes. WhatsApp Cloud API requires a dedicated phone number that is not used for anything else. This number will appear to customers as the sender of the messages. You cannot use the same number for both the regular WhatsApp app and the API. The number must be verified by Meta before you can start sending.
How long does it take to set up a broadcast message system connected to a CRM?
The technical setup – connecting the API, building the workflow in n8n, and connecting to a CRM or Google Sheets – takes between one and two weeks. But before that you need to get Meta approval for the phone number, create message templates and get approval for them, and prepare the contact list. In total, from start to first send, it's between three and four weeks.