WhatsApp Not Sending — Blocked, or Limits and Quality? (Hong Kong & APAC)

Published 2026-11-12 Updated 2026-11-13

On this page

Still on manual broadcast? Check whether the number is really banned
How platform sending answers those problems (UFOSEND)
Already on the platform but seeing failed or Flagged
Four ways sends stop — do not lump them together
Rolling limits: what is being counted?
Quality: blocks are the signal
Hong Kong note: DNC vs WhatsApp consent
FAQ
Further reading

Key takeaways

Manual broadcasts (app lists, unofficial plugins) during a promotion are the highest-risk path — blocks and reports spike, often with no Meta error code.

Official Cloud API + platform scheduling does not bypass Meta, but folds opt-in, suppression, approved templates, pacing and failure webhooks into one governable flow.

Failed or Flagged on the platform path usually maps to limits, quality or opt-in — traceable rules, not a silent permanent ban.

Still on manual broadcast? Check whether the number is really banned

During a promotion, the easiest move is often a WhatsApp Business app broadcast or an unofficial bulk plugin. After sending: mass undeliveries, spam complaints, the line feels “collectively blocked” — and no official Meta reason code in any dashboard. The team assumes the number is dead and rushes to swap tools.

That is usually not a permanent ban. Manual blasts concentrate compliance and quality risk:

Mixed consent — transactional, cold and unsubscribed contacts in one list.
No suppression sync — opted out on SMS or email, still messaged on WhatsApp.
Uncontrolled pace — whole spreadsheet in minutes; blocks and reports pile up.
Outside templates and API rules — app blasts and plugins are not the approved marketing template path; failures are hard to map to Meta’s docs.

If you are searching “WhatsApp broadcast blocked” or planning a bulk send during a promotion, this is the danger zone. The fix is not another plugin — it is a governed official send path.

How platform sending answers those problems (UFOSEND)

WhatsApp Cloud API with scheduled sends in one dashboard still faces Meta limits and quality. The difference: controls manual blasts lack, and visibility when something fails.

Manual blast problem	Platform send response
Unsubscribes still reached	Shared suppression with SMS and email before send (WhatsApp service)
Promotion without clear opt-in	Approved marketing templates + auditable consent
One-night full list	Staggered schedules — pacing, lower throughput spikes
Failures are guesswork	Delivery / failure webhooks — pause the next wave, no blind retries

We cannot rewrite Meta quality scores or promise “never blocked”. The platform filters lists before send, paces during send, and surfaces failed after send. Ops detail: How to send WhatsApp reliably.

Already on the platform but seeing failed or Flagged

You are past the “manual blast” stage. Next, read four stop reasons on the official path — limits, template quality, throughput and opt-in. Hong Kong, Taiwan and APAC share the same rules; align IT and marketing below.

Outside the 24-hour customer service window, proactive messages need templates; reach is capped by messaging limits (unique users in a rolling 24 hours), usually shared at Business Portfolio level. See Meta: Messaging limits.

Four ways sends stop — do not lump them together

What you see	Likely cause	What to do
Scheduled send, mass failed	Rolling reach limit or another number in the portfolio consumed quota	Spread campaigns; check Manager; adding numbers ≠ automatic extra reach
One marketing template suddenly unusable	Template quality red or Disabled	Revise copy and audience; see template quality
API errors like 130429	Throughput (messages per second) too high	Slow bursts; avoid hammering the API in seconds
Complaints “why am I getting promos?”	Opt-in or list hygiene	Audit consent; align with SMS and email suppression

None of these is fixed by “finding a BSP to unlock you”. Meta-owned rules need content and discipline; the rest is operations — see sending reliably.

Rolling limits: what is being counted?

Outside the service window, Meta counts how many distinct WhatsApp users you reached in a rolling 24-hour window. Since 2025, that cap is often shared across the portfolio, not per +852 or +886 number.

New portfolios usually start lower; verification and high-quality template volume unlock higher tiers. Further upgrades depend on recent usage and quality — follow Manager and official docs.

A common mistake: “We have 80k members” = one-night full blast. Rolling reach stops you first, not spreadsheet row count.

Quality: blocks are the signal

Meta uses blocks, reports, mutes among other signals. Templates show green / yellow / red in WhatsApp Manager; poor quality leads to Flagged or Disabled.

Official guidance: contact opted-in users only, send useful messages, do not hammer the same people daily. Promoting to people who only opted in to order updates drives reports — and stalls limit upgrades.

Opt-in rules: Getting opt-in. Hong Kong teams align PDPO and unsubscribe flows; Taiwan teams align local privacy wording — channel split in our SMS vs MMS vs WhatsApp guide.

SMS marketing may need OFCA Do-not-call checks; WhatsApp marketing needs its own WhatsApp consent. Copying an SMS list into WhatsApp without separate consent is a common mistake. Operations that keep one suppression list across channels are covered in sending reliably.

FAQ

Limit full vs dead template?

Limit: many templates fail at once near the cap. Template: usually one marketing template flagged or disabled.

Will switching BSP unblock us?

Quality and portfolio limits follow the business, not the inbox SaaS. Migration is about numbers, templates and webhooks — not bypassing Meta. See Wati & Sleekflow alternative.

Should OTP move to WhatsApp?

Keep must-deliver OTP on SMS; use WhatsApp for opted-in service and promos. See the Hong Kong practical guide.