Use a broadcast when you want to send the same private message to many saved contacts at once, and use 1-to-1 when the conversation needs a personal or private reply. The right choice comes down to three things: how private the exchange must stay, how many people you need to reach, and whether you expect a back-and-forth conversation or a one-way update.
TL;DR:
- A broadcast reaches only contacts who have saved your number; direct messages can reach anyone whose phone number you have.
- Each list holds up to 256 contacts, and larger audiences require multiple lists that need regular maintenance as numbers change or people opt out.
- Recipients cannot see one another, but every reply arrives as a separate private chat, so businesses should tag and triage responses promptly.
- Consider the WhatsApp Business Platform when you need scheduled, high volume messaging or outgrow manual lists, but keep clear opt in records for every contact.
WattleKeep customer conversations togetherWattle brings calls, website chats, WhatsApp calling, and SMS into one workspace, with tools for bookings and staff handoffs.Explore Wattle
Table of Contents
- How broadcasts work versus single 1-to-1 messages
- Who sees replies and what happens after recipients respond
- Reach, limits and platform support
- Decision checklist: when to use broadcast, when to message 1-to-1
- Alternatives and scale: Business API, templates and scheduling
- Operationalising broadcasts for service businesses
- Author’s perspective on choosing the right message model
- How Wattle helps you manage WhatsApp replies and bookings
- FAQ
- Sources
How broadcasts work versus single 1-to-1 messages
A broadcast list lets you send one message to a group of contacts, but WhatsApp delivers it as a separate, individual chat to each person rather than as a shared thread. Nobody on the list sees who else received the message, and each recipient can only reply to you, never to the group. According to the WhatsApp Help Centre, a broadcast only reaches contacts who have saved your number in their own address book. If someone hasn’t saved you, the message simply doesn’t arrive, no error, no warning.
That saved-contact rule is the single biggest difference between how broadcasts and 1-to-1 messages behave. A direct 1-to-1 message goes through as long as you have the person’s number, regardless of whether they’ve saved yours. That’s why a cold outreach message or a one-off customer reply works as a direct message but fails silently as a broadcast.
Routing differs too. A 1-to-1 chat is a continuous thread where both sides can see the full history and respond freely. A broadcast message lands in the recipient’s chat list looking like an ordinary message from you, but from your side, each reply comes back into its own separate chat, as if you’d messaged that person directly all along.
Typical use cases make the contrast clearer:
- Broadcast: sending the same appointment reminder, promotion or opening-hours update to a list of existing customers who’ve saved your business number.
- 1-to-1: confirming a specific booking detail, answering a billing question or handling anything that involves personal information.
- Broadcast: notifying a client base about a service outage or a seasonal closure.
- 1-to-1: following up after a complaint, a refund request or any conversation that needs context from earlier messages.
The pattern holds across most business use: broadcasts suit announcements, 1-to-1 suits anything with nuance.
Who sees replies and what happens after recipients respond
One of the most common misunderstandings about WhatsApp broadcasts is whether recipients can see each other. They can’t. Every reply to a broadcast message arrives as a private chat with you alone, and recipients never see each other’s replies, phone numbers or even the fact that they were on the same list.
This is very different from a group chat, where every member sees every message, every reply and every other member’s number by default. If customer privacy matters, a group is the wrong tool for distributing an announcement to people who don’t know each other, and the WhatsApp Help Centre is explicit that a group is for conversations where people are meant to participate together, while a broadcast list stays one-to-many.
Practical implications for managing replies:
- Replies land as individual 1-to-1 chats, so each one needs to be tracked and answered like any other direct message.
- Nothing distinguishes a broadcast reply from a normal message in your chat list, so you need your own way of tagging which conversations started as a broadcast.
- High-volume broadcasts can produce a sudden spike of individual replies that’s easy to lose track of without a system for triaging them.
Pro Tip: Tag or label broadcast-originated replies as soon as they land, so you can tell at a glance which conversations need a personal follow-up versus a quick acknowledgement.
For a business sending to even a modest list, this reply pattern means every broadcast is really the start of dozens of separate 1-to-1 conversations, not one group conversation. Planning who answers those replies, and how quickly, matters as much as planning the broadcast message itself.
Reach, limits and platform support
Broadcasts have hard technical ceilings that shape how far a single message actually reaches, and they’re worth knowing before you build a customer communication plan around them.
- A 256-contact cap per list. The WhatsApp Help Centre confirms each broadcast list holds up to 256 contacts, though you can create multiple lists to cover a larger base.
- Platform differences exist. Some broadcast management features behave differently between the mobile app and WhatsApp Web or Desktop, so features you rely on daily on your phone may not be available the same way in the browser.
- The saved-contact rule remains the main point of failure. Even with a list under the cap, any contact who hasn’t saved your number won’t receive the message, and this is the first thing to check when a broadcast under-delivers.
- Multiple lists add management overhead. Running several 256-contact lists to cover a larger customer base means keeping each one current, which becomes its own ongoing task as customers change numbers or opt out.
For a business planning to message its full customer base, these limits usually mean a real reach that’s smaller than the contact count suggests, because not every customer has your business number saved. Building that save-my-number step into onboarding, an invoice footer or a booking confirmation is the most reliable fix, and it’s worth treating as a standing operational task rather than a one-off ask.
Decision checklist: when to use broadcast, when to message 1-to-1
Most of the confusion about which method to use disappears once you ask a few direct questions before you hit send.
- Does this message need a personal or confidential reply? If yes, use 1-to-1.
- Have these contacts explicitly opted in to receive updates from you? If yes, a broadcast is appropriate.
- Do you expect a high volume of individual replies you’ll need to triage? Plan for that before sending, not after.
- Is the goal a shared discussion where people respond to each other? Use a group instead of either option.
Three rules of thumb cover most everyday decisions. A one-off personal matter, like confirming a specific appointment time or handling a complaint, always goes to 1-to-1. An opt-in update sent to many people at once, like a reminder or a seasonal notice, fits a broadcast. An open discussion where participants need to see and respond to each other belongs in a group, not a broadcast list.
Pro Tip: The moment a broadcast reply asks a specific question about that customer’s own booking, account or order, move the conversation to a clearly 1-to-1 footing in your own records, even though WhatsApp already treats the reply as private.
Escalation matters here too. A broadcast reply that starts generic (“thanks for the reminder”) can stay as-is, but one that raises a specific issue needs the same care as any other direct message, including a human reading it rather than a templated response. Treating every broadcast reply as a potential 1-to-1 conversation in waiting keeps customers from feeling like they’ve been filed into a list.
Alternatives and scale: Business API, templates and scheduling
Broadcast lists work well for a few hundred opted-in contacts managed from one phone, but they weren’t built for scheduled, regulated or high-volume outbound messaging. That’s the point where businesses usually look at the WhatsApp Business Platform, often called the API, and template messages.
Template messages are pre-approved formats that let a business send structured, scheduled notifications, like booking confirmations or shipping updates, outside the constraints of a manual broadcast list. Automation built on the Business Platform removes the 256-contact cap, the saved-contact dependency and the need to manually manage multiple lists, which is why it becomes relevant once a customer base outgrows what a phone-based broadcast can handle.
A few signals suggest it’s time to consider that shift:
- Your contact list regularly exceeds what a handful of 256-contact broadcast lists can realistically manage.
- You need messages to go out on a schedule rather than whenever someone is free to send them manually.
- You’re sending the same type of update often enough that a templated, automated version would save meaningful time.
The trade-off is that automation and template messaging come with their own compliance requirements, most importantly keeping clear opt-in records for every contact you message this way. Our guide to compliant WhatsApp automation walks through what that transition looks like in practice, and for businesses weighing automated reminders generally, automating service reminders by SMS shows a parallel approach worth comparing against a WhatsApp-based setup.
Operationalising broadcasts for service businesses
Running broadcasts responsibly as a business comes down to a handful of habits that keep the list clean and the replies manageable.
- Keep a simple opt-in record for every contact on a broadcast list, noting when and how they agreed to receive messages.
- Review your contact list periodically to remove numbers that bounce, never saved you back, or have asked to stop receiving updates.
- Route every incoming reply into one place rather than leaving it scattered across a phone’s chat list.
- Use quick-reply templates for predictable responses so routine replies don’t eat into time needed for the ones that require real attention.
Our opt-in recordkeeping guide outlines the specific details worth keeping on file if a broadcast list is ever questioned. A unified inbox that pulls broadcast replies, booking requests and payment confirmations into one customer thread makes this far easier to manage than toggling between a phone’s chat list and a separate booking system, and it’s the difference between treating each reply as an isolated message and treating it as part of one customer’s ongoing history.
Quick wins worth adopting early: tag replies by source, keep a short list of quick-reply templates on hand, and move any reply that mentions a specific booking or account detail into a dedicated 1-to-1 conversation rather than leaving it filed under the original broadcast.
Author’s perspective on choosing the right message model
Default to 1-to-1 unless you have a clear opt-in list and a genuine one-to-many need. It’s tempting to treat broadcasts as a shortcut for anything you’d otherwise type out individually, but the saved-contact rule and the silent delivery failures it causes mean broadcasts punish sloppy contact lists far more than direct messages do.
Used well, broadcasts are a respectful way to update people who’ve already said yes to hearing from you, not a way to avoid writing personal messages. The real measure of success isn’t how many messages went out, it’s how many were delivered, how many replies came back, and how many of those replies turned into an actual booking or action. A broadcast that nobody opens or responds to isn’t working, no matter how big the list.
— Christopher
How Wattle helps you manage WhatsApp replies and bookings
Once a broadcast list starts generating real reply volume, the bottleneck usually isn’t sending the message, it’s keeping up with what comes back. We built a unified inbox to pull WhatsApp replies, website chats, calls and SMS into one customer thread, so a reply to a broadcast doesn’t get lost between a phone’s chat list and whatever booking tool you run separately.
Our system supports WhatsApp Business Calling alongside phone, web and SMS, and connects those conversations directly to calendar bookings and payment requests, so a customer who replies to a broadcast can go from “yes, I’m interested” to a confirmed appointment without you manually copying details across tools. Opt-in records, reply routing and booking confirmation all sit in the same workspace instead of three different apps.
If your broadcast lists are outgrowing what a phone can manage, our features page covers how the inbox and integrations work, and our pricing page lists the Starter, Pro and Max plans if you’re ready to see what fits your call and message volume.
FAQ
Do people know they are in a broadcast list on WhatsApp?
No, recipients aren’t notified that they’re on a broadcast list, and the message simply appears in their chat as if sent directly to them. They have no way to see who else received the same message.
What are the limitations of WhatsApp broadcast?
Broadcasts only reach contacts who have saved your number, cap out at 256 contacts per list, and generate individual replies that need separate tracking. Some management features also differ between mobile and web versions of WhatsApp.
Do recipients see each other on a broadcast list in WhatsApp?
No, recipients never see each other’s names, numbers or replies on a broadcast list. Each person receives the message as a private chat and can only reply to you, never to the group.
What is the 24 hour rule on WhatsApp?
The 24 hour rule refers to a WhatsApp Business Platform policy that limits certain free-form business replies to a limited time window after a customer’s last message, after which template messages are required. It applies to the Business API rather than to personal broadcast lists or standard 1-to-1 chats.