WhatsApp Business

Messaging limits and quality rating: why your brokerage number gets throttled at month-end

Half the premium reminders did not send. What a WhatsApp messaging limit counts, how tiers and quality rating work, and how to run a month-end batch safely.

Published on 7 min readFCB.ai
Contents
  1. What a messaging limit actually counts
  2. The tiers, and why they belong to the portfolio rather than the number
  3. Quality rating: what makes it fall
  4. Error 131049: the limit that is not yours
  5. Running a month-end batch without hitting the ceiling
  6. Frequently asked questions

It is the 25th, the unpaid-premium report is out, and someone in the office queues a reminder to eleven hundred clients. Four hundred go out. The rest sit there with an error nobody in the brokerage can decode. Nothing is broken and nobody has been banned — the firm has simply run into two separate ceilings that the WhatsApp Business Platform applies to every business on it, and neither of them appears anywhere in the brokerage's own procedures.

This is the part of setting up WhatsApp Business for a brokerage that only becomes visible once the book is big enough to matter, which is to say once it is worth doing at all.

What a messaging limit actually counts

A messaging limit is the maximum number of unique client phone numbers you can deliver messages to, outside an open customer service window, in a moving 24-hour period. Three things follow from that definition, and each one surprises somebody.

  • It counts people, not messages. Sending four follow-ups to the same client during the same 24 hours costs you one, not four.
  • It only counts business-initiated messages. Replies inside an open 24-hour service window do not touch the limit, so the inbox work your team does all day is free of it.
  • It is a moving window, not a calendar day. A batch fired at 16:00 is still occupying capacity at 09:00 the next morning.

For a brokerage this is mostly good news. Conversational service — claims, queries, document collection — is essentially unconstrained. It is the batch, the month-end premium reminder run, that meets the ceiling.

The tiers, and why they belong to the portfolio rather than the number

Meta's documentation sets out the progression as follows.

TierUnique recipients per 24 hoursHow you get there
Starting250Where every newly created business portfolio begins
Second2,000Verify the business, be verified by a partner, or deliver 2,000 messages to unique numbers outside service windows over a moving 30-day period using high-quality templates
Third10,000Automatic scaling
Fourth100,000Automatic scaling
TopUnlimitedAutomatic scaling

Two details in that table cause most of the confusion in broking firms. First, the limit is calculated and set at business portfolio level and shared across every business phone number in the portfolio — so a group with a short-term number, a life number and a funeral number does not get three allowances. Second, the increases are automatic rather than requested: Meta looks at whether you are sending high-quality messages across your numbers and templates and whether you used at least half your current limit in the last seven days, and it can raise the tier within six hours of you qualifying. A firm that never uses more than a third of its allowance will sit on the same tier indefinitely, wondering why nothing moves.

Quality rating: what makes it fall

Every business number and every template carries a quality rating — high, medium or low — derived from how recipients reacted over roughly the last seven days, with recent messages weighted more heavily. The inputs that matter are the ones the client controls: blocking the number, reporting the business, and simply not opening what you send. Meta's template quality guidance is explicit that low read rates count against a template alongside negative feedback.

Three habits push a brokerage's rating down faster than anything else:

  1. Messaging the whole book at once. A list that includes lapsed clients, people who left three years ago and numbers copied from an old spreadsheet will generate blocks, because a meaningful share of those people do not recognise you.
  2. Sending marketing when the client expected service. A client who agreed to hear about their policy did not agree to a promotion for a new product. The mismatch is what gets reported.
  3. Repeating a template that nobody reads. Rating is per template as well as per number, so one badly written reminder that goes out every month drags the whole account down with it.

If a number's rating stays flagged, the messaging limit can drop by a level — which is how a firm that was comfortably sending ten thousand finds itself back at two thousand in the middle of a renewal season.

Error 131049: the limit that is not yours

There is a second ceiling that has nothing to do with your tier. Meta applies a per-recipient cap on marketing template messages: if a person has already received a certain volume of marketing on WhatsApp that day — from any business — further marketing templates to them are simply not delivered, and the sender gets error 131049, "this message was not delivered to maintain healthy ecosystem engagement". Meta does not publish the number, and it is not a penalty against your account. Utility and authentication templates are not subject to it.

The practical consequence for a broker is worth stating plainly, because it changes how you categorise messages. A premium reminder, a renewal notice, a failed debit order notice and a claim update are genuinely utility content: they concern an existing policy and a transaction the client is already in. Categorised correctly, they are not competing with a retailer's promotion for space in the client's inbox. Written as a sales pitch and submitted as marketing, the same message can silently fail to arrive on exactly the day it mattered. If you are unsure which side a message falls on, the template categories are worth reading before you draft rather than after a rejection.

Running a month-end batch without hitting the ceiling

  1. Know your tier before you queue anything. It is visible in the WhatsApp Manager, and it belongs to the portfolio, not to the number you happen to be sending from.
  2. Split the run across days. Eleven hundred reminders against a 1,000 allowance is two days of sending, not one failed batch. Segmenting by due date usually splits the list naturally, and it makes each message more relevant anyway.
  3. Send to people who will recognise you. Filter on opt-in and on recent activity. In ORIS that means building a segment rather than exporting everyone — engagement score and days since inception exist precisely so the batch is not the whole book.
  4. Keep utility content in utility templates. One template per purpose, categorised honestly, so that the reminder that must arrive is not queued behind somebody else's promotion.
  5. Mind the local clock. A reminder that lands at 06:00 or at 21:00 earns blocks in any market. Set a send window and respect public holidays and payday patterns.
  6. Watch the rating after each run, not once a quarter. If a template slips to medium, rewrite it before the next cycle rather than sending it again unchanged.

The uncomfortable truth is that messaging limits mostly punish behaviour that was already a bad idea. A brokerage that sends fewer, better-targeted, correctly categorised messages to clients who asked to hear from it will climb the tiers automatically and never think about any of this again. One that treats WhatsApp as a bulk SMS gateway will keep meeting the ceiling, and eventually meet it from below.

Frequently asked questions

Does replying to a client count against our messaging limit?

No. The limit only counts business-initiated messages sent outside an open customer service window. Once a client messages you, the 24-hour window is open and your replies in that window are outside the limit entirely. This is why conversational service work — claims, queries, document collection — almost never runs into it, and why batches do.

We have three WhatsApp numbers. Do we get three allowances?

No. Messaging limits are calculated at business portfolio level and shared across all the business phone numbers in that portfolio. Splitting a large send across numbers in the same portfolio to dodge a ceiling does not work, and spreading poor-quality sending across several numbers can drag the quality rating on all of them.

How do we get our limit increased?

Beyond the first step, you do not ask — it happens automatically. Verifying the business moves a new portfolio off the starting tier; after that, Meta raises the limit when you are sending high-quality messages across your numbers and templates and have used at least half your current limit in the preceding seven days, with the increase applied within about six hours of qualifying. Consistently under-using your allowance keeps you where you are.

What should we do when a message returns error 131049?

Do not retry immediately — the cap belongs to the recipient and will still be in force. Check whether the message really needed to be a marketing template: policy and claim communications about an existing contract usually belong in a utility template, which is not subject to the per-recipient marketing cap. If it genuinely is marketing, reduce how often you send it and improve who receives it.

Our quality rating dropped after a campaign. How long until it recovers?

Rating reflects recipient feedback over a rolling recent period, so it improves as newer, better-received sends replace the bad ones — but it will not recover if you keep sending the same template to the same list. Pause that template, rewrite it, tighten the audience to clients with a live relationship and a clear opt-in, and let a few good cycles pass before scaling volume again.

See ORIS in action

Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.

Book a demo
Book a demo