How to Send WhatsApp Reliably — Lists, Unsubscribe, and Pace
Published Updated
On this page
Key takeaways
- Manual blasts leave you guessing; platform sends use suppression, staggered schedules and failure webhooks to handle the limits, quality and opt-in risks from the previous article.
- Stability is not a hack to “unblock” — it is right audience, visible failures, no one-night full-list blasts.
- WhatsApp, SMS and email share one suppression list where configured — unsubscribe once, respect everywhere.
- Schedule in waves, watch webhooks; pause when failure codes spike.
- UFOSEND does not change Meta quality ratings; we help day-to-day ops avoid easy mistakes.
The previous article: manual broadcasts during promotions are highest risk and hardest to diagnose; platform sends answer with suppression, templates, pacing and webhooks. This article is the hands-on half — what to do daily in the UFOSEND dashboard.
If you still rely on app broadcasts or plugins, read WhatsApp not sending — limits and quality first.
Start with WhatsApp not sending — limits and quality if you have not read it.
What the platform can and cannot do
| Situation | Platform helps | You change |
|---|---|---|
| Unsubscribed on SMS, still on WhatsApp | Suppression sync, pre-send filtering | Who updates CRM |
| 50k cold members in one hour | Staggered scheduling | Campaign strategy and copy |
| Template quality yellow/red | Surface failures, pause reminders | Segmentation, frequency, opt-in source |
| Portfolio at reach cap | Usage visibility, reschedule advice | Meta upgrade criteria |
We do not sell “guaranteed never blocked” — Honest Delivery means stating boundaries clearly.
List hygiene: suppression is not paperwork
Classic self-inflicted wound: CRM unsubscribed, email suppressed, WhatsApp list is last week’s export.
We keep SMS, EDM and WhatsApp under one account with shared suppression — one channel opts out, the others filter before send (see WhatsApp service — WABA onboarding). Hong Kong SMS promos may need OFCA DNC; WhatsApp needs WhatsApp opt-in records — not interchangeable.
Checklist:
- New members: record which channel they consented to — marketing, transactional, support separately.
- Before a campaign: sample 10 recent unsubscribes — all channels suppressed?
- Bought lists: SMS consent ≠ WhatsApp consent.
Full omnichannel playbook: EDM + SMS + WhatsApp on one platform.
Pace: do not clear the list in one hour
Meta enforces rolling reach and throughput. Even with quota left, bursting tens of thousands in minutes triggers throttling.
Practical approach:
- Split big promos into 2–4 scheduled waves; watch failures between waves.
- New templates: pilot on a small segment before full rollout.
- Multiple promos per user per day drive reports — favour fewer touches and in-window FAQ flows (FAQ chatbot design).
Scheduling is available in the dashboard; API scheduling fits automated systems.
Delivery receipts: failed ≠ “send again”
Official API statuses include sent, delivered, read, failed with Meta reason codes — unregistered number, template state, window rules, etc.
Operations:
- Wire webhooks to CRM or dashboards — not just “submitted”.
- When one code spikes, pause the next wave and fix list or template — do not blind-retry the same batch.
We expose DLR-style status callbacks; you define which failures auto-stop a campaign — that is operational visibility, not a black-box optimiser.
Permissions: who can press “send to everyone”
Retail and finance teams often need maker-checker and squad-scoped lists — see team permissions.
Taiwan and other markets
Meta rules are global; consent copy and privacy law are local. Taiwan SMS API setup: Taiwan SMS quickstart. WhatsApp still needs its own opt-in — do not treat Hong Kong DNC logic as WhatsApp consent.
FAQ
Can UFOSEND “warm up” our limit automatically?
Limit tiers are Meta’s, based on behaviour and quality. We help you send cleanly — suppression, scheduling, visible failures — so ops mistakes do not drag quality down.
Mix OTP and promos in one schedule?
Route OTP and passwords on SMS; WhatsApp for opted-in service. Mixing in one blast blurs consent — see the Hong Kong guide.
Accounts feel messy after the WABA split?
Meta now separates phone presence from templates and billing. See WABA vs Messaging Account.
Further reading
Want a list and schedule review? Contact us or see WhatsApp service.