WhatsApp rate limiting and best practices
How to protect your number's quality rating, stay within Meta's messaging limits and avoid getting your WhatsApp channel blocked.
What this article is for
WhatsApp Business is not an open firehose: Meta scores the quality of your number and assigns it a messaging limit and a maximum send rate. Ignore them and your number can drop to low quality (red), get restricted, or be blocked. This guide is for admins running broadcasts or automations at volume.
The three concepts to know
- Quality rating: green (high), yellow (medium), red (low). It is computed from blocks and reports your recipients trigger over the last 24 hours.
- Messaging limit: how many new contacts you can start per day (1,000, 10,000, 100,000 or unlimited). It only goes up if you keep quality high.
- Throughput: messages per second Meta accepts. Omnifox queues and spaces sends so you never exceed it.
Best practices to protect quality
- Only message people who opted in. A clear opt-in is the single biggest difference between a healthy channel and a banned one.
- Respect the 24-hour window. Outside it you can only send approved templates — don't try to force free text.
- Use the correct template category (utility, marketing, authentication). Tagging marketing as utility triggers reports and reclassification.
- Warm up the number. Start with low volume and ramp gradually; don't jump from 50 to 10,000 messages in one day.
- Segment. Don't blast your whole base — inactive contacts generate more blocks.
- Make opt-out easy. A "reply STOP to unsubscribe" reduces reports, which hurt far more than an unsubscribe.
How Omnifox handles it for you
- Broadcasts are queued and paced automatically to respect Meta's throughput.
- Every channel runs a periodic health check; under Channels you'll see Connected status or alerts if the token or quality drop.
- If a bulk send hits many 131049/131050 errors, Omnifox throttles it to protect your number.
Verification
Open Channels, select your WhatsApp number and check the channel status. In Meta's WhatsApp Manager, confirm quality is green and your messaging limit is what you expect.
If something goes wrong
- Quality yellow/red: pause marketing broadcasts for 24-48h; quality recovers on its own once reports drop.
- Mass "not delivered": usually a depleted daily limit or a flagged number; wait for the limit reset (midnight UTC) and lower volume.
- Restricted number: check Meta for a temporary restriction; don't retry in a loop — that makes quality worse.
Tips
- Keep one category and one language per template so its quality is measured cleanly.
- Favor customer-initiated conversations: the 24-hour window lets you reply in free text without spending templates.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.