WhatsApp Broadcast vs. Status: Which Should You Use?

A WhatsApp Status is a photo, video or text update you post to the Updates tab that customers must open to see, and which disappears after 24 hours. A WhatsApp broadcast is a message pushed straight into each customer's chat list with a notification, which stays there until they delete it.

The difference is push versus pull, and it decides everything else: who sees it, how many see it, whether it costs anything, and whether you can measure it. This guide compares reach, attention, lifespan, cost and measurement, then shows how to run both together — because unlike broadcast versus group, this is not an either/or.

Push versus pull, precisely

A broadcast is a push. You choose the moment, the message arrives with a notification, and it sits in the chat list alongside messages from the customer's friends until it is read. Attention is the default; ignoring it takes an action.

A Status is a pull. You post it and wait. It appears on the Updates tab, and only customers who open that tab and tap your entry ever see it. Ignoring it is the default; seeing it takes an action.

Neither is better. They are different instruments, and the mistake is using a pull channel for something that needed a push — a flash sale ending at midnight that 90% of your customers never opened.

Side by side

The reach question, honestly

Status reach is capped twice over. First by the address book: a customer who never saved your number will not see your Status at all, the same structural limit that makes the phone app's 256-contact broadcast list unreliable (WhatsApp Help Centre, about broadcast lists). Second by attention: of the contacts who could see it, only the ones who open the Updates tab that day actually do.

Broadcast reach is capped by different things — your opt-in list size and your messaging tier, which starts at 250 unique recipients per rolling 24 hours for a new number and rises through 2,000, 10,000 and 100,000 to unlimited (Meta, WhatsApp messaging limits). Those caps are knowable in advance and they grow. The Status ceiling does not grow; it depends on how many people bothered to save you.

So Status is not a cheaper broadcast. It is a different, smaller, softer surface that happens to be free.

The cost question, honestly

Status genuinely costs nothing and you can post as often as you like. A broadcast through the Business API is billed by Meta per delivered template message — Meta states that "You are only charged when a template message is delivered" — with marketing templates charged on delivery and non-template replies inside an open customer service window free (Meta, WhatsApp pricing). Rates vary by country and are published on a separate rate card, so ignore any single per-message figure quoted without a country attached.

That price gap is the strongest argument for putting your routine content on Status and paying only for the messages that need to be seen. The breakdown for the paid side is in how much a WhatsApp broadcast costs.

What Status is genuinely good at

• Daily specials and restocks that would be irritating as a notification but are welcome if someone happens to look.
• Proof you are alive. A shop that posts three times a week reads as active to anyone who checks before ordering.
• Behind the scenes. Production, packing, a new delivery arriving — content with no call to action.
• Testing an offer cheaply before you commit to a paid send to the whole list.
• Anything you would post to an Instagram story. The format and the effort are the same.

What Status cannot do

• Reach a customer who never saved you — which is most one-time buyers.
• Guarantee a specific customer sees a specific thing, such as a delayed order or an expiring voucher.
• Personalize. One post goes to everybody, so no names and no order numbers — the opposite of a personalized broadcast.
• Segment. You cannot post only to lapsed customers; segments exist on the broadcast side.
• Survive the day. A 24-hour lifespan means anyone on holiday missed it entirely.
• Give you a report. A viewer list on your phone is not the per-recipient delivery data in delivery stats and reports.

What you can measure on each

Status gives you a viewer list: swipe up on your own post and you see the names of contacts who opened it. That is a real number, but it is a vanity one — it tells you how many people looked, not how many acted, and it vanishes with the post after 24 hours, so you cannot compare this week to last.

A broadcast gives you a per-recipient record that survives: who it was sent to, who it was delivered to, who read it, who failed, and which link each person tapped. That is what makes a second campaign better than the first, because you can send the follow-up only to the people who did not respond rather than to everybody again.

If you are choosing between the two for a campaign you intend to repeat, the measurement gap matters more than the price gap. A free channel you cannot learn from stays the same quality forever.

Which one for a given message?

Ask one question: if nobody sees this, does something go wrong?

• "Your order shipped" — yes, something goes wrong. Broadcast.
• "Sale ends midnight tonight" — yes. Broadcast.
• "We are shut on Monday" — yes, if people will turn up. Broadcast.
• "Fresh batch of the blue mugs" — no, it is nice-to-know. Status.
• "Here is today's bake" — no. Status.
• "We repacked the whole studio, look" — no. Status.

Deadline or consequence means push. Ambient interest means pull.

Running both together: a weekly rhythm

1. Post to Status three to five times a week. Low effort, no approval needed, free. This keeps you in front of the customers who already saved you.
2. Reserve broadcasts for moments that earn a notification — realistically two to four a month for most stores, not two a week.
3. Prepare the template in advance. Meta reviews templates before they can be sent in bulk, so write it days before the launch, not on the morning of it. Start at how to send your first WhatsApp broadcast.
4. Trail the campaign on Status first. Post the teaser free, then broadcast the announcement — the people who saw both arrive already warm.
5. Follow up only the people who did not engage, using retargeting by delivery outcome, instead of broadcasting to the whole list again.
6. Cap your marketing frequency so the broadcasts stay rare enough to matter, using the controls in opt-outs and frequency.

Why the pairing protects your number

Every broadcast you send is a small withdrawal from your customers' patience, and blocks and reports feed the quality rating that governs how many people you may message. Moving your low-stakes content to Status means the messages that do arrive with a notification are the ones worth having. Fewer, better sends keep the rating healthy, which is what lets you climb the tiers described in messaging limits and tier caps.

Status also costs nothing when you get it wrong. A dull Status post is invisible; a dull broadcast is a paid notification interrupting someone's evening. Use the free channel to find out what people respond to.

How this compares to the other options

Status, broadcast, broadcast list and group are four different shapes. A group exposes every member's number to every other member and is compared in broadcast vs. group. A broadcast list in the phone app is private like a broadcast but capped at 256 contacts who must have saved you, compared in broadcast vs. broadcast list. Of the four, only an API broadcast reaches a customer who never added your number, and only Status is free and unlimited.