WhatsApp Broadcast Account Restricted: Why Tier Limits Are Not the Whole Story

Every Malaysian SME that uses WhatsApp broadcasts for marketing eventually meets the question: how many is too many? The answer most platforms give you is "stay within your Meta tier limit". A Tier 1 number can broadcast to 250 unique recipients per 24 hours, so 250 must be safe — right?

We watched a real client learn the harder version of that answer. Within three days they sent 500 broadcasts total, well under Meta's tier cap, and their number got restricted anyway. Here is the full breakdown — what actually controls broadcast safety, and the warm-up plan that would have avoided it.

What happened (anonymised)

A Malaysian retail business signed up, connected their fresh WhatsApp Business API number, and imported their customer file. Their list was clean — no purchased numbers, no scraped contacts. All 500 recipients had bought from them in the past year.

• Day 1: Sent a marketing template to 250 recipients (a flash sale).
• Day 3: Sent another marketing template to a different 250 recipients (a follow-up to a different segment).
• Day 4: Outgoing template sends started bouncing. WhatsApp Manager showed a "Restricted" status.

Recovery took five days. They could only send to customers who messaged them first. No new broadcasts. Quality rating moved from Green → Yellow → Red → Yellow → Green over the recovery period.

Total damage: ~5 days of zero outbound visibility, plus a bruised quality rating that took three more weeks of careful sending to fully recover.

Why "within tier limits" did not save them

Meta runs two parallel systems on every WhatsApp Business API number:

1. The hard cap (tier limit) — how many unique recipients you can initiate template conversations with in a rolling 24h window. Tier 1 = 250, Tier 2 = 1,000, etc.
2. The quality rating — a hidden score derived from block rates, report-spam rates, and read rates on your template messages.

The tier limit is what every guide talks about. The quality rating is what actually gets numbers restricted. A new number can blow its quality rating well below the hard cap because the rating compounds across sends, and a bad rating triggers throttling regardless of the tier you are technically on.

The three things that hurt them

1. The number was too fresh

A WABA that has only ever sent templates and never received customer-initiated chats has no quality history. Meta's spam classifier treats this exactly like a list-buying spammer would behave: connect a number, send templates, hope for replies. The classifier sets the quality threshold lower for fresh numbers.

The fix is to build inbound traffic before you broadcast. Even running the WhatsApp API for a week with customers initiating chats (replying to your business card, scanning your QR poster, asking pre-sales questions) gives the number a baseline quality signal.

2. The cadence was too aggressive for the number's age

Two 250-recipient blasts in three days from a number with no history and no inbound traffic is the exact pattern Meta's classifier flags. It does not matter that the recipients were real customers. The pattern of sends — concentrated, high-volume, low inbound — is what looks suspicious.

A number that has been live for 6 months can do the same 250 + 250 sends in three days without issue, because it has accumulated quality signal in the meantime.

3. The recipients were not actively engaged

The list was technically clean — past customers, valid numbers — but many had not opened a chat with that business in 6+ months. So when the template arrived, block rates and "no response" rates were elevated. Meta interprets a low read rate as "this is unwanted message" even when the contact is on your list.

The warm-up plan that would have prevented this

If your WhatsApp Business number is fresh (or has only been on the consumer Business app, not the API), treat the first 30 days as warm-up. The goal is to build quality signal before pushing volume.

Days 1–7: utility messages only, to your most engaged contacts

• Send order confirmations, appointment reminders, delivery updates — utility category templates only
• Cap at 20–50 sends per day
• Pick recipients who have messaged you in the last 14 days
• Goal: build a "this number sends useful, expected messages" signal

Days 8–14: introduce a single low-key promotion

• Send one marketing template to 100 contacts, max
• Pick the most active customers (those who chatted in the last 7 days)
• Watch read rate. Aim for >70%. If lower, scale back.

Days 15–21: expand to 200 per send

• Two marketing sends max in this period
• Mix of marketing + utility templates
• Quality rating should still be Green at this point

Days 22–30: push toward your tier cap

• If quality stayed Green and read rates stayed above 70%, you can send up to your Meta cap
• Keep a 50/50 ratio of utility vs marketing if possible
• After day 30, you have a baseline of quality signal that can absorb occasional weaker-performing sends

What ForwardChat does automatically (and what it cannot)

ForwardChat's broadcast queue paces sends based on your WABA's tier — 1 message every 3 seconds for Tier 1, 5 messages per second for Tier 10K, with stricter caps if you have Coexistence mode enabled (consumer app on the same number). This prevents the "burst send" pattern that trips per-second rate limits.

But the platform cannot decide whom you should send to. That is a business decision. The single biggest lever you control is the quality of your send list. A 100-contact send to your most active customers will almost always perform better than a 250-contact send to your full file, especially in the first month.

What to do if your number gets restricted

1. Stop all outgoing template sends immediately. Continuing makes it worse.
2. Wait for inbound messages. Customers replying to existing conversations rebuilds quality fastest.
3. Check WhatsApp Manager → Quality Rating. It usually moves Red → Yellow → Green over 3–7 days if you stop the offending behaviour.
4. File an appeal in WhatsApp Manager if the restriction does not lift on its own. Be specific: how the contacts opted in, why the message was relevant.
5. Do not switch numbers. Meta cross-references display names and business accounts — a fresh number tied to the same business runs into the same issue faster.

The bottom line

Tier limits are a hard cap, not a safe limit. The number that sat under the cap and still got restricted was not unlucky — it was the predictable result of a fresh number sending bursty marketing to a list that had not been warmed up. Spend the first 30 days building quality signal, and the same list that bricked one number will work fine on the next.

If you want a deeper read on how Meta categorises and prices conversations, see how WhatsApp Business API cost works in Malaysia. If you want the full broadcast playbook including opt-in rules and cadence, see WhatsApp Broadcast Strategy Malaysia.