Review, test-send and publish a broadcast
Check who will receive it, send one test to yourself, then send now or pick a time.
Quick start
- As an owner or admin, click Next in the broadcast to reach the review.
- Read Recipients and each Excluded — … count.
- In Test broadcast, type your own number, then click Send test. It sends a real message.
- Choose Send now, or Schedule for and pick a date and time.
- Click Publish — send now or Publish — schedule. Each recipient passes the current sending checks.
Watch out
- A test send is a real message. Opted-out, blocked and deleted numbers are refused; one that never agreed is not. Use your own number.
- Publishing cannot be undone. Only a broadcast that is still scheduled can be cancelled.


Details
Getting here
Broadcasts → open the broadcast → Next at the top right. The back arrow returns you to the setup.
Before you start
- Next stays greyed out until a channel and a message are both in place.
- Sending depends on your plan, and scheduling for later is a separate question from sending now; see pricing.
- Any paid plan may send now. Scheduling for later needs a higher plan.
- A test send is a real WhatsApp message, and it costs what a message costs.
Fields
- Recipients
- People queued for sending, subject to the checks before each send.
- Messages
- How many messages that is.
- Excluded — no channel
- Matched the segment but has no usable number.
- Excluded — no consent
- Matched, but marketing consent is not active.
- Limits: Shown only when it stopped somebody.
- Excluded — opted out
- Matched, but they withdrew marketing consent, on this record or on another record with the same number. A contact with consent on their own record, held back by another record, is listed under the tiles with a link to that record.
- Limits: Shown only when it stopped somebody.
- Excluded — blocked
- Matched, but the contact is blocked.
- Limits: Shown only when it stopped somebody.
- Excluded — data deletion
- Matched, but they completed a data-deletion request. They stay out of every broadcast.
- Limits: Shown only when it stopped somebody.
- Excluded — never messaged this channel
- Removed by the previously-interacted rule on the setup.
- Limit send rate
- An optional cap of so many messages per second, minute or hour.
- Limits: Applied as a per-minute cap, so expect roughly rather than exactly the rate you typed.
- Timing
- Send now, or Schedule for with a date and time.
How it works
- The counts are worked out the same way publishing works them out, so the review is a preview rather than a separate calculation.
- A broadcast sends to at most 1,000 people. When the audience is larger, a notice under the counts says that only the first people who can receive it are included and the rest will not get this one. Split the segment to reach everyone.
- A WhatsApp number may have less of its daily limit left than this broadcast sends on it. Then a notice under the counts says how many it has left, how many go out there and up to about how many days it takes. The rest go out as the limit frees up. Workflow and API template sends use the same limit, so it can take longer.
- Test broadcast sends this exact message to one person immediately. It is not counted as a recipient and never appears in the report.
- The search box finds a contact by name or number. Typing a number that matches nobody still sends to that number, which is how you test with your own phone. That number is then added as a contact, and the test appears as a conversation in your inbox.
- With several numbers selected you also choose which number's message to test with.
- Limit send rate paces the send. The worker checks itself about once a minute, so a per-second or per-hour rate is applied as the matching per-minute cap.
- Send now and Schedule for both publish. Publishing takes the audience as it is at that moment and writes the list of recipients; a send that is due goes out on the next tick, about a minute later.
- Publishing fixes the recipient list. A scheduled broadcast cannot be edited: its setup page says so, so cancel it back to a draft before you change it.
- Before each person's send, their current contact, number, blocking and consent are checked. Deleted, erased, changed-number or blocked contacts are skipped, so any broadcast can reach fewer people than the review counts.
- A segment using Time Since Last Outgoing Message adds a note under the counts. Its complete published rules are checked before each batch and each person's send; anyone who no longer matches is skipped.
- Only one publish can win. A second attempt on the same broadcast is refused with This broadcast has already been published.
- A refusal about the setup appears here as a banner with Go to Configuration or Go to Message Content, which takes you to the exact row that is wrong.
- Save at the top writes any pending edit immediately, and says Saving… then Saved.
- The back arrow returns to Configuration and Message Content; Back to broadcasts leaves, saving first.
When it fails
- Schedule for chosen with no time picked: Pick a date and time, or choose “Send now”.
- A time already past: The scheduled time is in the past.
- A plan that may send but not schedule: the refusal names the plan needed and adds You can still send this one now.
- No channel: Choose a channel. No message: Choose a channel and a message first.
- A segment that matches nobody: This segment matches no contacts.
- Nobody in the segment has consented: No one in this segment has given marketing consent, with the number that matched.
- Everybody removed by the previously-interacted rule: the message says so, and on Specific channel it names the switch.
- A test send with nothing to send to: Search for a contact, or enter a phone number, to test-send to.
- A successful test says Test message sent.
- An unavailable sending check holds the unattempted batch or person for another tick. When the failure counter is available, failed checks count once per broadcast per tick, across people and channels; the tenth failing tick within an hour stops affected rows.
- The report names segment could not be re-checked at send time for a batch check or recipient could not be re-checked at send time for a person's check. Retry failed checks them again after completion; another failure in that hour gives up immediately.
- The channel and workspace check right before each send counts the same way. At the limit, its unsent rows show channel or workspace could not be checked at send time — not sent.
Limits
- A test send is not held to marketing consent: a number with no contact record, or a contact who never agreed, still receives it, so you can test on your own phone. A number that opted out, is blocked or whose data was deleted, on any record of that number in this workspace, is refused with the reason on screen. Name yourself.
- A test send does not appear in the report, and does not use up the schedule.
- Publishing cannot be undone from here. A scheduled broadcast can be cancelled back to a draft; one that has begun sending cannot.
- The audience is resolved when you publish. Contact identity, number, blocking and consent are checked again for each person as it sends. Only segments using Time Since Last Outgoing Message also re-check their published rules.
- Already accepted messages are never automatically re-sent. Failed rows with message ids or the exact known unknown-outcome marker are withheld from manual retry too. Current ambiguous or thrown sends say send outcome unknown — provider acceptance could not be confirmed; expired claims on an attempted send say send outcome unknown — claim expired. A claimed row never handed to WhatsApp goes back to pending.
- Older raw errors and variable unknown-outcome details are not fully classified and can still be manually retried without a message id. Retrying an unknown outcome can send twice. Read each report reason first.
- The time you pick is read from your own device's clock, while the line below it repeats that moment in the fixed zone
Asia/Kuala_Lumpur. On a device set to another zone the two read differently. - The rate limit is approximate, because the pacing is re-checked about once a minute.
Best practices
- Always send one test to your own number, and read it on a phone. The preview cannot show you a broken picture or a button that goes nowhere.
- Read Excluded — no consent before you publish. It is the number that tells you whether your list was ever asked.
- Schedule rather than sending now when the audience is large, so you can still cancel.
- Use Limit send rate on a first big campaign to spread it out. A send that has started cannot be stopped, so read your test message first.
Use cases
- A festival campaign: test to yourself, then schedule it for the morning.
- A flash offer: test, then Publish — send now.
- A first large send: cap the rate, publish, and watch In Progress.
- A refusal you do not understand: click Go to Message Content, and the offending row is pointed at.
FAQ and troubleshooting
- Does a test send count as a recipient?
- No. It is sent immediately to whoever you name, and it is not in the report at all.
- Can I test-send to somebody who has not consented?
- The test does not check consent, so it will go. Use your own number: sending marketing to somebody who has not opted in is exactly what the consent rule exists to prevent.
- I pressed Send now. Why has nothing arrived?
- Publishing hands the broadcast to the sender, which picks it up on its next tick, about a minute later. Watch Sent on the report.
- Can I edit the message after publishing?
- Cancel it back to a draft first, which only works while it is still scheduled. A scheduled broadcast cannot be edited, because Publish froze its message and audience. Cancelling clears the time, so choose the timing again before you republish.
- The scheduled time I see is not the time I typed.
- You pick on your device's clock, and the confirmation repeats it in the fixed time zone the product schedules in. If your device is set to another zone, expect the difference.
Reading this with an AI assistant? Plain Markdown version.