Your number's limit does not reset at midnight: each send occupies a slot for 24 hours and releases it automatically, in the same order it was used. Those unaware of this spend the next day waiting for a reset that never comes. This article explains how the tier ladder works, what causes a number to upgrade, how to plan a send within capacity, and the cost of forcing the limit.
In this article
- How the limit really works
- What causes the number to upgrade tiers
- How to plan a send within the limit
- What to do when you hit the limit
- The cost of forcing, with numbers
- Operating well within TIER_250
- Three planning mistakes that cost tiers
- Applicable material: the capacity spreadsheet
- Frequently Asked Questions
How the limit really works
Every official number has a cap on how many conversations it can start within a 24-hour period. The tiers follow a known ladder: 250, 1,000, 10,000, 100,000, and at the top, unlimited. New numbers start at the first tier.
Two details completely change the planning for senders, and almost no one knows them until they hit a wall.
The limit counts conversations you start, not messages. If the customer replies and you exchange forty messages, that still counts as one conversation. Responding to someone who initiated contact does not consume any quota.
The window is rolling, not daily. This is the most confusing point. There is no "midnight reset": each send occupies a slot for exactly 24 hours and releases it automatically. If you sent 250 messages spread throughout an afternoon, the quota returns gradually over the following afternoon, in the same order and pace it was used.
Those who don’t understand the second rule spend the entire next day waiting for a reset that never comes, concluding that "Meta didn’t release it" when in fact the release was happening drop by drop all along.
What causes the number to upgrade tiers
Upgrading is not requested, it is earned—and depends on two simultaneous factors.
Maintained quality. Numbers with average or low quality do not upgrade, no matter the volume. It is a prerequisite, not a tiebreaker.
Consistent use of the current tier. The platform checks if you really need more. A number in TIER_250 using 40 conversations per day does not show need; one that regularly uses near the limit without generating complaints does.
Add to this the verification of the business account, which is a condition for higher tiers. Unverified businesses remain stuck at the bottom regardless of behavior.
The typical upgrade pace is from days to a few weeks when both factors are in order. And there is a two-way path many ignore: the tier also downgrades. Poor quality reduces the limit, and it is the same mechanism described in number quality acting in reverse.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
How to plan a send within the limit
The calculation that avoids most problems is done beforehand, not during. An example with numbers.
You have 2,300 contacts with opt-in to contact, and three numbers: two in TIER_250 and one in TIER_1000.
Total daily capacity: 250 + 250 + 1,000 = 1,500 conversations per day.
The temptation is to divide 2,300 by 1,500 and conclude it takes two days. Here lies the most costly mistake: using 100% of capacity is the fastest way to burn quality, because there is no margin left to serve those who reply—and replying is what you want to happen.
The correct plan uses 70% of capacity: 1,050 per day. The 2,300 contacts go out in three days, leaving room for returning conversations.
Also distribute within the day. One thousand fifty messages sent in twenty minutes is a pattern that draws attention; the same 1,050 spread over six hours, with variable intervals, looks like what it is—a working operation.
What to do when you hit the limit
Hitting the limit is not an accident: it is the expected result of an operation using its capacity. What matters is the reaction.
Stop trying. Persisting against the limit causes repeated rejections, and repeated rejections are a negative signal. The queue should stop on its own and wait.
Don’t switch numbers to continue. This decision turns a temporary limit into a permanent problem. If you use a second number to bypass the first’s limit, the pattern the platform observes stops being volume and becomes circumvention.
Wait for the window to release. Since the release is gradual, the queue can resume slowly a few hours later—you don’t need to wait the full 24 hours to send the next batch.
Use the time to serve those who replied. Useful irony: the moment you cannot start new conversations is exactly the moment to work on those already started. And those don’t consume quota.
If hitting the limit becomes a weekly routine, the problem is not the limit—it’s sizing. You either need more numbers, more days, or a more qualified list.
The cost of forcing, with numbers
An operation with 2,300 contacts and a capacity of 1,500 per day decides to send everything in one day, distributing the excess among the numbers.
What happens: the 800 that exceed the limit return as rejections. But the damage doesn’t stop there—the pattern of trying against the limit, combined with the atypical volume, lowers the quality of all three numbers.
• Conversations lost due to rejection: 800
• Limit reduction in following days: capacity drops from 1,500 to about 600
• Estimated recovery time: 2 to 4 weeks
• Revenue interrupted during the period, in an operation earning R$ 4,000/day via the channel: R$ 40 thousand to R$ 80 thousand
Compare with the alternative: wait two more days and send the same 2,300 contacts without losing anything. The cost of rushing is tens of thousands of reais; the cost of patience is 48 hours.
It’s worth noting what this calculation teaches about priority: the capacity to start conversations is an asset that takes weeks to build and hours to destroy. No monthly goal justifies spending it—and that’s why the decision to force should not be in the hands of those responsible for the goal, but those responsible for the channel.
Operating well within TIER_250
Many companies treat the first tier as a limitation to overcome. It’s worth reversing that: 250 conversations started per day, with real opt-in, is quite a lot—5,500 per month on business days. The problem is almost never the limit; it’s the quality of the list you want to burn against it.
Three moves that yield more than upgrading tiers.
Prioritize warm contacts. If you can only start 250, let them be the 250 with the highest chance of response. Sort the list by recency and source before sending—contacts from two weeks ago convert much better than those from eight months ago.
Make the customer start. Conversations started by them do not consume quota. Click-to-WhatsApp ads, QR Codes on materials, links on websites and email signatures turn the limit into a non-issue. An operation receiving 300 conversations started per day operates above TIER_250 without touching the limit.
Improve conversion, not volume. Increasing the response rate from 12% to 20% is equivalent, in results, to nearly doubling the limit—and with no associated risk.
Three planning mistakes that cost tiers
Testing capacity on campaign day. Discovering the real limit of the number in the middle of an important send is the worst possible time. Do a controlled test on a normal day, with increasing volume, and note where rejection starts—that number is your starting point for planning, and it’s not necessarily the one on paper.
Confusing delivered messages with started conversations. Reports usually show messages; the limit counts conversations. In a campaign where many people reply, these two numbers diverge significantly, and planning by the first leads to underestimating how much quota remains.
Leaving volume decisions to those responsible for the goal. It’s not a lack of trust in the team: it’s recognizing that incentives point in different directions. Those who need to hit the monthly number will always have an argument to send more today, and the cost of that choice appears weeks later, spread across the entire operation. Set the campaign limit before the campaign exists, and treat it as a rule, not a suggestion.
Applicable material: the capacity spreadsheet
One row per number, updated before each campaign: number · current tier · quality · conversations started in the last 24h · remaining capacity · time when the first slot returns.
And a second tab for campaign planning: total contacts · summed daily capacity · usable capacity (70%) · days needed · contacts per number per day · sending time window.
Two rules worth more than the entire spreadsheet. First: never plan above 70% of capacity—the margin ensures service for those who reply and absorbs the unexpected. Second: if the campaign doesn’t fit capacity, change the campaign, never the limit. Cut the list to the warmest contacts, extend the days, or reduce the scope. Every attempt to fit the limit to ambition ends the same way, and its price arrives weeks later, when the channel supporting the entire operation is running at half capacity.
Frequently Asked Questions
Does the sending limit reset every day at midnight?
No, and this is the most common confusion. The window is rolling: each conversation started occupies a slot for exactly 24 hours and releases it automatically. If you sent 250 messages spread throughout an afternoon, the quota returns gradually over the following afternoon, in the same order and pace it was used. There is no reset hour, and those waiting for it conclude the release didn’t happen when it was actually happening drop by drop.
What causes the number to upgrade tiers?
Two simultaneous factors: quality maintained at a high level and consistent use of the current tier. Numbers with average or low quality do not upgrade, no matter the volume—it’s a prerequisite, not a tiebreaker. The platform also checks if you really need more: those using 40 conversations per day in TIER_250 do not show need. Add business account verification, which is a condition for higher tiers. The tier also downgrades when quality drops.
Can I use another number when the first hits the limit?
Not to bypass the limit. Legitimately distributing volume among healthy numbers is cadence planning and works; using a second number to continue a send that exceeded the first’s limit is circumvention, and the platform’s pattern changes from volume to evasion. When the limit is reached, the correct action is to stop, wait for the window to gradually release capacity, and use the interval to serve those who replied—conversations started by the customer do not consume quota.
Centralize service without changing your number
Connection via QR or official API, single queue with defined responsibility, client history that stays with the company, and sales funnel on the same WhatsApp panel.