WhatsApp campaigns and broadcasts that are checked before the first send
A WhatsApp broadcast goes wrong in the first minute: a list nobody checked, a template Meta had paused, a number already past its daily limit. Linkubit runs the outbound gate across the whole audience before message one, picks only templates Meta has approved, sends up to the number's limit and no further, and stops a sequence the moment somebody replies.
Build an audience from filters over anything you know about a contact or from a spreadsheet, choose an approved template, set a start time, and run pre-flight: every contact is checked for consent, suppression and a usable number, and the refusals are named before the campaign starts. Sends go out at Meta's own per-message rate, with nothing added, and a reply on any channel stops the rest of that person's sequence and opens a conversation.
Deliverability, protected up front
Pre-flight before the first send
The same gate that guards every outbound message runs across the audience before anything goes out: who has consented, who unsubscribed, who is missing a number, who is blocked. You see who would be refused and why, because the first send is where a number's quality rating is lost.
- Refusals are named before the campaign starts, not found in a report
- STOP on any channel suppresses a person everywhere, and nothing reaches them after
Pre-flight across 1,241 contacts
1,183 will send
consent and identity checks passed37 skipped — no marketing consent
service messages only21 suppressed — unsubscribed earlier
refused permanentlyA campaign, not a blast
Sequences stop on reply
A campaign is steps with waits between them. A reply — on WhatsApp, by email, anywhere — cancels the remaining steps for that person, opens a conversation with an owner, and starts qualification from the words they actually wrote.
- Nobody gets step three after they already said yes
- A campaign whose replies vanish is a campaign nobody answered — every reply lands in the inbox
Step 1 · Introduction
Sent · opened twiceStep 2 · Case study
Sent · repliedReply received
“Interested — can you call Tuesday?”
Step 3 · Break-up email
cancelledThe rest of it
Only templates Meta has approved
Write a template, submit it, and its status arrives from Meta as it changes — approved, rejected, paused. A campaign can only pick one that is approved, so a send never fails on a template you thought was live.
It stops at the number's limit
Meta caps how many people a number can start conversations with in a day. The campaign sends up to that limit and holds the rest until it lifts, and the screen says "waiting on the number" rather than reporting a failure that is not one.
Your WhatsApp bill, before Meta sends it
Meta bills per message, days late. The dashboard shows what it has charged and what the unbilled days will cost, drawn dashed so you can tell them apart, beside the credits the campaign spent.
Audiences from filters or a spreadsheet
Filter on anything you know about a contact — your own qualification fields included — and watch the count update, or import a sheet. Deduplicated before it lands, not after.
What it is made of
Pre-flight before the first send
A campaign is checked across the whole audience before anything goes out: who has consented, who unsubscribed, who is missing a number. You see who would be refused and why, because the first send is where deliverability damage happens.
WhatsApp templates, synced with Meta
Write a template, submit it, and its status arrives from Meta as it changes — approved, rejected, paused. A campaign can only pick one that is approved, so a send never fails on a template you thought was live.
Sequences stop on reply
A reply stops the remaining steps, opens a conversation and starts qualification. Nobody gets step three after they already said yes.
Your WhatsApp bill, before Meta sends it
Meta bills per conversation, days late. The dashboard shows what it has charged and what the days it hasn’t billed yet will cost, drawn dashed so you can tell the two apart — beside ad spend and your credits.
Questions people ask
Do I need a WhatsApp Business API number?
Yes. Broadcasts to people who have not messaged you first can only be sent as approved templates on the API, and Linkubit connects a number through Meta's own Embedded Signup in a few minutes. A number already on the API is connected as it is.
What does a campaign message cost?
Meta's per-message rate, billed by Meta to your WhatsApp Business Account, with nothing added by Linkubit — plus a tenth of a credit per message on your plan. The cost calculator shows a month's bill on your own numbers.
Can I schedule a campaign?
Yes — a start time, and waits between the steps. A member who is due while the number is at its daily limit is held, not dropped, and sent when the limit lifts.
Will this get my number blocked?
The things that get numbers blocked — messaging people who did not opt in, people who asked you to stop, templates that were rejected — are refused before the send. Pre-flight shows you every refusal, and a STOP reply is honoured across every channel at once.
Read next
Ready to put your sales on autopilot?
Start freeNo coding required. No credit card required.