Published in Guides

How to send WhatsApp bulk messages without getting your number restricted

By Lyle Timotheus · 8 min read

Share this post

Most WhatsApp numbers that get restricted weren't doing anything shady. They sent a big campaign to an old list, a few hundred people tapped block, and the quality rating fell overnight.

This guide is what we walk new Syncli customers through before their first broadcast: how Meta decides who you can message, what drags a number down, and the checks worth doing before you press send. Everything here is from Meta's developer documentation as at November 2026, unless we say otherwise.

What actually gets a number restricted

Meta doesn't watch the content of each campaign. It watches how people react to it. The signals that matter most:

  • Blocks and reports. Each one tells Meta the message wasn't wanted. A burst of them after one send is the fastest way to lose quality.
  • Low engagement. Meta uses how people read and react to business messages when it sets limits, so campaigns that go unread don't help you.
  • Template feedback. Meta rates each template. One that keeps getting poor reactions can be paused, and you can't use it until it recovers.

Your number's quality rating, shown in WhatsApp Manager, rolls these up. While it's high, your limits grow. When it drops, they stop growing, and in bad cases Meta restricts the number. Our guide on how to avoid a WhatsApp ban covers every kind of restriction and how to appeal.

Know your messaging limit before you plan a campaign

Meta limits how many different people your business can start a conversation with in a rolling 24 hours. Replies inside a conversation the customer started don't count. Since the latest change, the limit applies to your whole Meta business portfolio, so two numbers under one portfolio share it.

Limit (unique people per 24 hours)How you get there
250Where every new portfolio starts
2,000Verify your business, or deliver 2,000 good-quality template messages outside the 24-hour window within 30 days
10,000Automatic, while quality is high and you've used at least half your limit in the last 7 days
100,000Same rule as above
UnlimitedSame rule as above

Meta says an upgrade happens within about 6 hours of you qualifying. You can check your current limit in WhatsApp Manager under Account tools, then Messaging limits.

In practice this means a 20,000-person campaign isn't something you can send in week one. Plan the first month around growing the limit: verify the business early and send to your most engaged customers first.

The cap nobody tells you about

On top of your own limit, Meta caps how many marketing messages each person receives from businesses in general. The cap adapts to the person. Someone who reads and replies to a lot of business messages gets more than someone who ignores them. Meta doesn't publish the number.

When a message hits this cap it isn't delivered, and the API returns error 131049. Don't retry straight away. Meta asks you to wait at least 24 hours, and repeated retries count against you. Marketing messages you send inside a conversation the customer opened don't count towards the cap.

It's also why a campaign's delivery rate can be lower than you expect even when your list is clean. Some of your customers simply had a busy week.

Get opt-in that holds up

Meta requires opt-in before you message anyone on WhatsApp. The opt-in has to make clear the person is agreeing to receive messages from your business. It doesn't have to be collected on WhatsApp: a website form, a checkbox at checkout, a QR code in store or a signed form all count.

POPIA adds its own rule for South African businesses. Direct marketing by electronic message needs consent, with a narrow exception for existing customers who bought something similar and were given the chance to opt out. If in doubt, ask your legal adviser. This isn't legal advice.

  • Record it. Keep when and where each person opted in. If someone complains, that record is your answer.
  • Ask per purpose. Order updates and promotions are different things. Separate opt-ins mean fewer surprises.
  • Honour opt-outs at once. Add an opt-out button to marketing templates and remove people the moment they use it.

The riskiest list is the one you already have: a spreadsheet of every customer since 2019. Some will remember you. Many won't, and they're the ones who tap block. Send those people a single, useful message first, and only keep marketing to the ones who respond.

Write templates that get approved and get read

Every bulk message on the API is a template that Meta has approved. A few habits save a lot of resubmitting:

  • Pick the honest category. A discount is marketing, even if it's attached to an order update. Meta re-categorises templates that get this wrong.
  • Mind the variables. Don't start or end the text with a variable, and don't put two variables side by side.
  • Say who you are in the first line. People decide in a second whether to read on.
  • One message, one ask. Shop the sale, book a slot or confirm a time. Not all three.
  • Use buttons. A quick-reply or link button gets more responses than "reply YES".

Personalising with the customer's name and something they actually bought makes a bigger difference to read rates than clever copy.

Segment and pace your sends

Sending everything to everyone is how good numbers get hurt. Start with the people most likely to welcome the message: recent buyers, customers who've replied before, people who opted in this month. Their engagement lifts your quality rating, which raises your limit for the wider sends.

Split large campaigns over a few hours or days instead of one blast, so a weak template shows up in the numbers before it reaches your whole list. And leave space between campaigns. A weekly promotion to the same segment wears out faster than you'd think.

Watch the right numbers after you send

  • Delivery rate. A sudden drop can mean the per-person cap is biting, or that your list has stale numbers.
  • Read rate. If it falls campaign after campaign, you're sending too often or to the wrong people.
  • Replies. The best sign a campaign worked. Make sure someone, or an AI agent, is ready to answer them.
  • Opt-outs and blocks. If these jump after a send, stop and look at the template and segment before the next one.

In Syncli, each broadcast shows its delivery, read and reply numbers, and replies arrive in the shared inbox with the customer's order history next to them.

What a campaign costs

Meta charges per delivered message. From 1 October 2026, a marketing message to a South African number is $0.0379 and a utility message $0.0095. A promotion to 10,000 people therefore costs about $379, roughly R6,800 at R18 to the dollar, before your platform fee. Messages that aren't delivered, including those held back by the per-person cap, aren't charged.

Our South African WhatsApp API pricing guide has the full rate card and worked examples, and the pricing calculator will price your own campaign in rand.

A quick check before you press send

  • Everyone on the list opted in, and you know when.
  • The template is in the right category and has an opt-out button.
  • The segment fits inside today's messaging limit.
  • You're starting with your most engaged customers.
  • Someone is ready to handle the replies.
  • Your quality rating in WhatsApp Manager is high.

If you'd like a second pair of eyes on your first campaign, talk to us. See how campaigns work in Syncli on the WhatsApp bulk messaging page.

Frequently asked questions

It depends on your messaging limit, which counts unique people you start conversations with in a rolling 24 hours. New businesses start at 250. Verification takes you to 2,000, and good quality takes you to 10,000, 100,000 and unlimited. The limit is shared across every number in your Meta business portfolio.

Keep reading

All posts

See how Syncli works for your business.

Book a 20-minute demo and we'll show you how to sell, take bookings and get paid on WhatsApp.

  • Personalised walkthrough
  • Official WhatsApp API
  • No commitment
Booking an appointment in WhatsApp with Syncli