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 reach outside a service window in a moving 24 hours.
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 deliver to outside a customer service window in a moving 24 hours, set per business portfolio. 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 unique recipients, 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 outside a service window. What consumes it is reaching someone who has not written.
Does it move downward?
Not since 7 October 2025. A quality drop no longer lowers the limit, which is now set per business portfolio at 250, 2,000, 10,000, 100,000 or unlimited.
Quality still matters, because it decides whether the limit grows. A number whose recipients block or report messages loses standing, and the portfolio stops scaling. That makes a falling quality rating the 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 unique recipients per day, the other messages per second.
- Counting replies against the tier. Messages inside an open window are not counted.
- Expecting a quality drop to lower the tier. Since October 2025 it only stops the tier growing.
EasyCoexistence records messaging tier alongside quality rating and throughput on every connected number, so a stalled tier 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 delivered outside a service window 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 TrialVerified on