Broadcast lists vs the Cloud API: when the free option stops working

Most businesses start the same way. Someone saves a few hundred customer numbers in their phone, makes a broadcast list, and starts sending offers. It works for a while. Then it doesn't, and it's worth knowing why before you get there.

Where broadcast lists fall short

• A list holds a limited number of contacts (256 at the time of writing).
• Only people who have saved your number in their phone will receive the message.
• Everything is tied to one phone and one person. If that person is away, nobody else can send or reply.
• There's no proper reporting. You get ticks on the screen, not data you can export or compare.
• Personalisation means typing each name yourself.
• The regular apps aren't meant for bulk sending, and heavy use can get the number flagged.

What changes with the Cloud API

You stop being limited by list size and by who has saved your number. Messages go out as approved templates, so recipients see a verified business message they can trust. You can fill in names or other details per contact, and every message has a status you can look at afterwards.

You also gain something less obvious: a team can share the work. One person builds the campaign, another sends it, a third answers the replies, all from one dashboard and one WhatsApp number.

What it costs you

Broadcast lists are free. The Cloud API isn't, because Meta charges for template messages by category and destination country, and a platform like Notivo has a monthly fee on top. For a business sending a few messages a week to a small list, broadcast lists may be enough. If sending is part of how you run the business, the cost is usually small next to the time and the numbers you'd otherwise lose.

A simple rule of thumb

If you're hitting the list limit, if more than one person needs to send or reply, or if you'd like to know how a campaign actually performed, it's time to move.