Blog / API & technical

WhatsApp sending limits: how to scale the messaging tiers

If you've started sending campaigns on the WhatsApp Business API, sooner or later you've run into WhatsApp sending limits and the so-called messaging tiers. They are the reason why one day you can reach 1,000 contacts and the next day the platform tells you you've used up the available volume. Understanding how these tiers work, and above all how to grow them, is the difference between a strategy that scales and one that stays stuck at the first thousand messages. In this guide we look in detail at how the tiers are structured, what makes them go up, what makes them go down and how to organize sends so you never run short of capacity.

What WhatsApp messaging tiers are

Messaging tiers concern only the official Meta APIs (Cloud API), not WhatsApp Web. They are a limit on the number of conversations your business number can start in a 24-hour period. Note: the tier counts conversations initiated by the business toward the user, not the replies to users who write to you first, which remain unlimited. Meta assigns the tier automatically and updates it based on two factors: the volume of messages you send and the perceived quality of your number.

The four tiers: from 1K to unlimited

Every new number starts at Tier 1 with 1,000 conversations per day. That's not little to begin with: it means being able to contact 1,000 different people every 24 hours. As you send regularly and maintain a good reputation, Meta promotes you to the higher tiers, usually within a few days when the volume justifies it.

Quality rating: the real engine of the tiers

Volume alone isn't enough. Meta assigns each number a quality rating (green, yellow, red) based mainly on user feedback: blocks, spam reports and negative reports. A high quality rating lets the tier rise; a low one blocks it or makes it drop, and in the worst cases leads to suspension of the number.

• Green: high quality, the tier can grow freely
• Yellow: medium quality, there are friction signals to monitor
• Red: low quality, risk of downgrade or block

How to raise the tier without risks

Scaling the tiers is a process of trust: you show Meta that your contacts appreciate your messages. Here are the practices that really work.

• Send only to contacts who gave explicit consent (opt-in)
• Use approved and relevant templates, not generic cold messages
• Increase volume gradually, without sudden spikes
• Personalize with variables like name and information useful to the recipient
• Always offer a simple way to stop receiving messages
• Monitor blocks and reports to act before quality drops

If your number is new, don't start with a campaign to 1,000 unknown contacts on the first day. Warm up the number by first sending to those who have already written to you or to highly engaged lists: quality stays high and Meta promotes you faster.

What makes the tier drop

A downgrade is almost always a quality problem, not a volume one. The most common causes are: contacting people who didn't ask for anything, sending promotional messages disguised as notifications, a high percentage of blocks, content perceived as spam. A single day of red quality rating can be enough to halt growth. The good news is that reputation recovers: a few days of clean, well-received sends are enough to return to green.

How to manage tiers with SendApp

SendApp works on the two WhatsApp tracks: the official Meta APIs, with approved templates, green tick and anti-ban system, or WhatsApp Web via QR, which has no messaging tiers but must be used sensibly. With the official APIs, SendApp Agent lets you build broadcast campaigns with templates and variables like {name}, {phone} and {email}, manage contacts with tags and lists to send only to those genuinely interested, and monitor how sends perform. The CRM with tags is the key tool to protect the quality rating: you segment contacts, send to the most engaged and grow the tier naturally. SendApp starts at 19 euros per month; messages sent via Cloud API are billed directly by Meta with no markup from SendApp.