A WhatsApp broadcast to past guests is safe when four things are true: the message is a Meta-approved template, it goes only to the people you chose, it leaves slowly instead of all at once, and anyone who said "stop" is left out. Skip any one of them and you risk blocks, reports and a restricted number.
We run guest messaging for more than 100 homestay units in Johor Bahru, and a promotion to past guests is one of the few messages we send that nobody asked for. That makes it the message most likely to get our number reported. Below is what Google's first page says about WhatsApp broadcasts, then exactly how our own broadcast tool in AntlerChat sends, step by step, including the parts that still need a human.
What does Google's first page say about WhatsApp broadcasts?
Most results for "WhatsApp broadcast" and "WhatsApp blast" in Malaysia are written by companies that sell broadcast software (SleekFlow, Qiscus, YCloud and others). Their advice agrees on three points:
- The free WhatsApp Business app has broadcast lists, but these guides describe a cap of 256 contacts per list, and a broadcast only reaches people who have saved your number.
- Larger sends go through the official WhatsApp Business Platform (Cloud API), where business-started messages must use a template that Meta reviews first.
- Bans come from behaviour, not from the tool: sending to a whole database at once, sending without opt-in, and ignoring how many people block you.
What these guides rarely show is what the tool actually does between "send" and the last message. That is the useful part for an operator, so that is what the rest of this article covers.
How does our broadcast tool send a WhatsApp message to hundreds of guests?
Here is the flow in AntlerChat, in the order it happens:
| Step | What happens | Why it is there |
|---|---|---|
| 1. Pick content | WhatsApp: you choose an approved template from your template library. You cannot type free text. | Business-started WhatsApp messages outside a conversation must be templates. |
| 2. Pick audience | "Everyone" or "contacts with these tags" (up to 30 tags). | So a Desaru promotion does not go to someone who only stayed in town once. |
| 3. Preview | You see the head count, how many were left out for opting out, and the first five names. | A last chance to notice "1,800 people" when you meant 80. |
| 4. Snapshot | The recipient list is frozen at the moment you create the broadcast. | Tags you add afterwards do not change who receives it. |
| 5. Slow queue | Every 30 seconds the queue sends a small batch: by default up to 15 messages, 1.2 seconds apart. | Sending everything at once is the pattern Meta treats as spam. |
| 6. Result per person | Each guest ends as sent, failed (with the error) or skipped. | You can see who did not get it and why. |
| 7. Cancel | Cancel marks everyone still waiting as skipped. Messages already sent stay sent. | A stop button for a wrong template or wrong audience. |
Two more rules sit inside those steps. If one phone number has several chats with you (for example, it wrote to two of your lines), it receives the broadcast once, on the chat used most recently. And a template variable can carry the guest's name: the token is replaced with the name on file, or with "there" if we have no name.
How long does a WhatsApp broadcast to 500 guests take?
With the default settings, about 30 messages a minute. That means roughly 17 minutes for 500 guests and a little over an hour for 2,000. It is slow on purpose. A sudden burst of identical messages from one number is exactly what gets numbers flagged, and a promotion that arrives 40 minutes later loses almost nothing.
Which numbers and channels can receive a broadcast?
| Channel | Who is included | What is left out |
|---|---|---|
| WhatsApp on the official Cloud API | Every WhatsApp chat on that line, or only the tagged ones | Chats tagged stop, unsubscribe, optout or opt_out |
| WhatsApp Web line | Not included. Templates only go out on the Cloud API | Everything on that line |
| Facebook Messenger | Only people who wrote to you in the last 24 hours, checked again just before sending | Anyone whose 24-hour window closed between creating and sending (marked skipped) |
The second row matters for anyone comparing plans. Our plans include one WhatsApp Web number. Chats on a WhatsApp Web line are not part of a broadcast. If promotions to past guests are a big part of why you want a messaging tool, connect a Cloud API number for it.
What does Meta charge for a WhatsApp broadcast in Malaysia?
On the Cloud API, Meta charges for each delivered template message, by category. Meta's pricing page says businesses are charged only when a message is delivered, and that per-message pricing started on 1 July 2025. A promotion is a marketing template.
For Malaysia, respond.io lists Meta's rate effective 1 October 2026 as RM0.3467 per delivered marketing message and RM0.0564 for utility and authentication messages. Check Meta's own rate card before you budget, because rates change.
| Example list | Marketing messages delivered | Meta fee at RM0.3467 |
|---|---|---|
| 200 past guests | 200 | about RM69 |
| 500 past guests | 500 | about RM173 |
| 2,000 past guests | 2,000 | about RM693 |
These are worked examples, not a quote. The Meta fee is separate from what you pay for any software, including ours. The practical lesson: a tagged list of 200 people who actually stayed with you in the last year is cheaper and less likely to be reported than "everyone who ever wrote in".
How do you stop a broadcast from getting your number banned?
These are the rules we follow before pressing send:
- Send to guests who know you. Someone who stayed with you and chatted about check-in will recognise the number. Someone who asked one price question two years ago may not.
- Tag first, then send. Tag guests by area, by stay or by year. "Everyone" should be rare.
- One clear reason per message. A school-holiday date, a returning-guest rate, a new unit in the same building. Not a list of six offers.
- Make leaving easy. Put "Reply STOP to stop these messages" in the template.
- Watch the results. If many messages fail or people start blocking you, stop sending for a while and fix the list.
- Do not send at night. The queue starts on the next tick after you create a broadcast, so create it when you want it to arrive.
Malaysia's Personal Data Protection Act 2010 also gives people the right to ask you to stop processing their data for direct marketing. Keep a record of who asked to stop and when. This is general information, not legal advice.
What still needs a human in our broadcast tool?
Being honest about this is part of choosing any tool, so here are our gaps:
- A STOP reply does not yet remove the guest from broadcasts on its own. When a guest replies just "STOP" (or "unsubscribe", "berhenti", "停止"), our system withdraws their marketing consent in another part of the product. The broadcast audience, however, only checks the chat's tags. Until someone tags that chat "stop", the next broadcast can still reach them. Until that is joined up, search the inbox for STOP replies and tag those chats before every send.
- No consent filter. The tool does not ask "did this person opt in?". It includes every WhatsApp chat on the line unless you narrow it by tags. Choosing the right people is your job.
- No scheduled send time. You cannot set a broadcast for Friday 10am; it starts within about 30 seconds of creating it.
- No frequency limit. Nothing stops you from sending three promotions to the same guest in a week. Only your own rule does.
- WhatsApp Web lines are left out, as described above.
If you have fewer than a hundred past guests and send one promotion a year, the free WhatsApp Business app broadcast list may be enough. A tool earns its cost when the list is in the hundreds or thousands, when several staff share one number, and when replies to the promotion need to land in the same inbox as the booking.
Where does the broadcast fit with the rest of our guest messaging?
A broadcast is the only message we send that the guest did not trigger. Everything else is tied to a booking: the 9 automatic messages around a stay, the AI replies and when they hand over to a human, and the shared inbox rules for who answers which guest. When a guest replies to a promotion, the reply lands in that same inbox and follows the same assignment rules.
AntlerChat costs RM 450 a month, RM 4,860 for one year or RM 8,640 for two years, with one WhatsApp Web number included and RM 200 a month for each extra one, before SST. Meta's message fees are charged separately. See how it works at /chat.
Rates and rules quoted here were checked on 17 November 2026 and can change. This is not legal advice.