What Meta is actually measuring
The quality rating on your number is built from how recipients react — blocks, reports, and messages that go unanswered. It is not a measure of how much you send.
That distinction matters. A number sending thousands of expected order updates a day can sit comfortably at high quality, while one sending a few hundred unwanted promotions gets marked down quickly.
When quality falls, the messaging limit drops first. Restriction follows if nothing changes. The warning is visible well before the penalty, which is why nobody using the API properly should be surprised by a ban.
The things that actually get numbers restricted
- Messaging lists that were bought, scraped, or collected for something else entirely
- Ignoring opt-outs, so the only way to stop you is the block button
- Marketing templates sent to people who only ever asked for a delivery update
- Unofficial bulk-sending tools that bypass the API — grounds for a ban on their own
- A brand new number sent straight into a large campaign with no history of real conversations
What a well-behaved setup does for you
Most of the defence should be enforced by the software rather than remembered by a person. In Waphie the 24-hour service window is enforced server-side, STOP replies opt a contact out and campaigns skip them automatically, sends are throttled per minute instead of dumped at once, and the quality rating and current messaging tier are on the dashboard.
The habit that matters most is still yours: start from conversations customers began. Inbound-first traffic is the cheapest and safest volume there is, because those people already expect to hear from you.
Where we sit
We build Waphie, so this is not a neutral page — but no platform can promise you will not be banned, and one that does is telling you what you want to hear. The recipients decide.
What software can honestly do is make the safe path the default one and show you the warning early. That is what we have built for.