The business_capability_update webhook
business_capability_update reports a change to what the account may do, most usefully the messaging limit. It carries the current limit, which is how many unique customers you may start conversations with per day. It moves in both directions.
- Carries the messaging limit
- A daily count, not a rate
- Moves up and down
Nothing charged for 7 days. Cancel anytime.
Field carrying the new value: current_limit.
The separate error for exceeding throughput, which is a rate rather than a daily count.
Events our handler treats identically: this one and messaging_limit_update.
What is the messaging limit actually limiting?
How many unique customers you may start a conversation with in a rolling day. Not how many messages you may send, and not how fast.
This is the distinction that causes trouble. Throughput is a rate, measured per second, and exceeding it returns 130429. The messaging tier is a daily count of new conversations, and exceeding it is a different condition. A number can be well within its tier and still be rate limited, or the reverse.
Replies inside an open customer service window do not consume the tier, because they are not starting a conversation. What consumes it is reaching someone who has not written.
Why does it move downward?
Because the tier follows quality, and quality follows how recipients react.
A number whose recipients block or report messages loses standing, and the tier is one of the things that adjusts. That makes a downward move a useful early signal: it usually arrives before anything stops working, while there is still time to change what is being sent and to whom.
The upward direction is slower and is earned by sustained good reception. Neither direction is announced anywhere a business would see, which is why recording this event rather than only reacting to failures is worth the small effort.
Common mistakes
- Confusing the tier with throughput. One is conversations per day, the other messages per second.
- Counting replies against the tier. Messages inside an open window do not start a conversation.
- Ignoring a downward move. It arrives before anything breaks, which is the whole value of it.
EasyCoexistence records messaging tier alongside quality rating and throughput on every connected number, so a downward move is visible as a trend rather than as a surprise.
Frequently asked questions
How do I raise my tier?
It follows quality over time rather than a request. Sending well to people who want it is the mechanism.
Does a template send always consume tier?
A template that starts a conversation does. One sent inside an open window does not.
Is messaging_limit_update different?
Meta sends both names for related changes. Our handler treats them the same because the useful content is the same.
Does this apply on a Coexistence number?
Yes. What is fixed on Coexistence is throughput, not the messaging tier.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on