WhatsApp Broadcast Lists Explained: Broadcasts vs Groups
Businesses new to WhatsApp marketing often assume a "broadcast" works like a group chat — send one message, everyone sees it. In reality, broadcasts and groups behave completely differently, and at business scale the WhatsApp Business API layers in a further rule that trips up almost everyone the first time: outside a 24-hour window, only pre-approved templates go out. Here's how it all actually works.
Broadcast lists vs groups: not the same thing
A WhatsApp group is one shared conversation where every member sees every message and can see who else is in it, along with everyone else's replies. A broadcast list is the opposite: you send one message to a list of contacts, but each person receives it as an individual, private chat from you — they don't see the list, don't see other recipients, and any reply they send comes back to you alone rather than into a shared thread.
Broadcast lists vs groups
| Platform | Visibility | Replies | Best for | Contact limit |
|---|---|---|---|---|
| Broadcast list | Private — recipients don't see each other | Come back to you individually | Marketing messages, announcements, reminders | Business API broadcasts scale well beyond personal-app limits |
| Group | Shared — everyone sees everyone | Visible to the whole group | Communities, ongoing discussion between members | Limited membership, not designed for one-way business messaging |
Groups are the wrong tool for business messaging
Adding customers to a WhatsApp group exposes their phone number to every other member and turns your announcements into a visible thread anyone can reply into. Broadcast lists exist specifically to avoid this — use them instead.
How broadcasts work on the personal app vs the Business API
In the free personal or Business App, a broadcast list only reaches contacts who already have your number saved in their phone — anyone who hasn't saved you simply won't receive it. That's fine for a small list, but it doesn't scale, and it offers no reporting, scheduling or template system. The WhatsApp Business API removes the 'must have you saved' limitation and lets you broadcast to your full opted-in contact base, but in return it enforces Meta's template and session-window rules on every message you send.
The 24-hour window is the rule that changes everything
Whenever a customer messages you, a 24-hour window opens during which you can send anything — free text, images, links, offers. The moment that window closes, free-form messages stop working entirely. To reach a contact after the window has closed, you must send a Meta-approved message template instead. This is exactly the situation most broadcasts are in: you're proactively reaching out to a list of people, most of whom haven't messaged you in the last 24 hours, so the broadcast has to be built from an approved template rather than a plain message.
Running a broadcast outside the 24-hour window
Draft your message as a template
Write the content with any variable fields (name, order number, date) marked as placeholders rather than free text.
Submit it for Meta approval
Templates are reviewed before they can be used and can be rejected for promotional language or mismatched categories, so build in review time.
Select your opted-in list
Only include contacts who've explicitly consented to WhatsApp marketing messages — never an imported list without fresh permission.
Schedule and send the broadcast
Each recipient gets the message as an individual chat, which reopens a fresh 24-hour window if they reply.
Route replies into a shared inbox
Any responses land back as private one-to-one conversations your team can pick up and continue in free-form.
Approved broadcast template
Hi {{1}}, your {{2}} appointment is coming up on {{3}}. Reply CONFIRM to keep it or RESCHEDULE if you need a new time.Notice the placeholder fields — name, service and date — filled in per recipient at send time. This is the standard shape of an approved broadcast template: personal enough to feel direct, structured enough to pass Meta's review.
What gets templates rejected
Common template rejection reasons
Segmenting your broadcast list
A single broadcast list sent to everyone regardless of purchase history, location or engagement tends to underperform compared to smaller, segmented sends. Splitting a list by recency of last order, service type, or location lets each template's variables and content stay genuinely relevant, which keeps reply rates higher and opt-outs lower.
Havari handles both sides automatically
Havari manages template submission and approval status, builds and schedules broadcast lists against your opted-in contacts, and drops every reply into a shared inbox — so your team never has to track the 24-hour window manually.
Can I add customers to a WhatsApp group instead of a broadcast list?
You can, but it's not recommended — groups expose every member's number to each other and turn one-way announcements into a visible thread, which most customers don't want.
Do I need a template for every broadcast?
You need a template for any broadcast sent to contacts outside the 24-hour window since their last message to you, which covers the vast majority of proactive marketing broadcasts.
How long does template approval take?
It varies, but building in a few days' buffer before you need to send is safer than submitting a template the same day as a planned campaign.
What happens if a customer replies to a broadcast?
Their reply opens a fresh 24-hour free-form window, letting you respond with anything until that window closes again.
Broadcast lists give you WhatsApp's reach without the mess of a shared group thread, but only if the underlying template and session-window rules are respected. Get your templates approved ahead of time, keep lists properly segmented, and treat every reply as the start of a real conversation rather than an afterthought.