WhatsApp Error 131049: The Per-User Limit Quietly Dropping Your D2C Broadcasts in India

Every Indian D2C brand treats WhatsApp the same way at festival time: load the whole list, write one offer, hit send, watch the orders come in. The send report says the broadcast went to everyone. What the report doesn't say is that Meta quietly declined to deliver a chunk of it — specifically to the people who've been ignoring you — and handed back a error code most founders have never heard of. Your reach leaked, your least-engaged contacts never saw the offer, and nothing in your broadcast tool told you plainly.

The mechanic behind this is Meta's per-user marketing template limit, and the error it throws is 131049. It's an engagement-based frequency cap that throttles marketing messages to people who don't read them — and India is not on the list of markets exempt from it. That single fact reshapes how WhatsApp should work for a D2C brand: reach is no longer something you buy with volume, it's something you earn per contact through engagement. This post covers what the limit does, why blasting your whole list now actively wastes spend, and how to run WhatsApp as an engagement-gated channel instead.

What the per-user limit actually does

Meta's own developer documentation describes an adaptive limit on marketing template messages, applied per recipient. It adjusts over time based on a person's recent behaviour — Meta's docs point to signals like recent marketing message read rate and how many messages the person currently has in their inbox. Read your messages, and you get more headroom. Ignore them, and your headroom shrinks.

When you send past that limit, the message fails. The webhook returns error code 131049, and the message isn't delivered. Meta's guidance is to wait at least 24 hours before resending to that user. BSP documentation (from providers like WANotifier and ChatOnDesk) records the user-facing framing of the drop as being to "maintain a healthy ecosystem engagement" — which is exactly what the cap is for. Meta is stopping promotional messages from piling up unread in inboxes.

India is not exempt — and that's the whole story

Here's the line that makes this urgent for local brands. Meta's documentation states the per-user marketing limits are not currently active for the European Economic Area, the United Kingdom, Japan and South Korea. India appears nowhere on that exemption list. So while a UK brand can broadcast without this particular throttle, an Indian brand can't. The contacts most likely to be dropped are your least-engaged ones — the dormant buyers a festive win-back is supposed to reactivate. The mass blast doesn't just underperform on them; it never reaches them.

Tier limits versus per-user limits: two different ceilings

A lot of the confusion here comes from mixing up two separate limits. Getting them straight is what lets you diagnose a leaking broadcast correctly.

The trap is assuming a bigger tier solves everything. It doesn't. You can sit comfortably inside your 2,000-recipient tier and still have messages dropped with 131049 because specific contacts are throttled for not engaging. Tier gives you capacity; per-user limits govern whether that capacity actually delivers.

Why spray-and-pray now costs you

For years, blasting the whole list was merely inefficient — you paid per message and annoyed some people. Now it's worse than inefficient, because the per-user limit means the sends most likely to fail are the ones to your coldest contacts, and per-message billing means you may still be charged for attempts that don't land the way you hoped. You're spending effort and money precisely where it's least likely to reach anyone, while training Meta's algorithm to see your account as one that messages unengaged people.

Engagement is the currency

The flip side is the opportunity. Because a reply opens a 24-hour customer service window, and marketing messages sent inside that window don't count toward the per-user limit, engagement directly restores your ability to reach someone. A contact who replies is a contact you can message freely for a day. That turns the entire game from "how many can I blast" into "how many can I get to reply" — a far healthier question for a retention channel, and one that maps cleanly onto how good CRM already works.

Running WhatsApp as an engagement-gated channel

The fix isn't to send less for its own sake. It's to send to the right people, in a way that earns you continued access to the rest. Here's the shape of it.

Segment by engagement, not just by list

Stop treating your list as one blob. Split it by recent engagement — active openers, lapsing, dormant — and send your best-engaged segment the straightforward broadcast, since they have the headroom. For lapsing and dormant contacts, don't blast a fourth ignored promotion into a capped inbox; change the approach entirely.

Use a reply-to-unlock mechanic on cold contacts

For the segment that isn't engaging, lead with something that asks for a reply rather than another one-way offer — "reply YES to unlock your festive code", a quick this-or-that question, a poll. A reply opens the 24-hour window and buys back your ability to message them, so you're rebuilding access instead of burning it. This is the core of turning WhatsApp from a broadcast megaphone Meta throttles into an engagement-gated CRM engine, and it's exactly the kind of segmented, reply-driven lifecycle our CRM team builds for D2C brands so festive sends land where spray-and-pray leaks.

Keep your list clean and your cadence honest

Respect opt-outs immediately, don't retry a dropped message inside 24 hours (excessive retries can make a user undeliverable for up to 24 hours), and don't send a fourth promo to someone who ignored the first three. Every ignored message pushes that contact's per-user limit down. Fewer, more relevant messages to people who actually open them protect your deliverability across the whole list.

The takeaway

Meta turned WhatsApp reach into something you earn, not something you blast. The per-user marketing template limit throttles sends to people who don't engage, dropping them with error 131049, and India is squarely inside its scope while the EEA, UK, Japan and South Korea sit outside it. It's a separate ceiling from your account tier, so a bigger tier won't save you. The brands that win here stop treating the list as one broadcast target and start managing engagement: segment by recent activity, send clean broadcasts to your warm segment, use reply-to-unlock mechanics to rebuild access to cold contacts, and keep your cadence honest so you don't throttle yourself. Do that, and the festive send that used to leak reach on the people you most wanted to reactivate finally lands.

Sources: Meta for Developers — "Per-user marketing template message limits" (adaptive limit based on recent marketing read rate and inbox fullness; failed delivery returns error code 131049; wait at least 24 hours before resending; limits not currently active for the European Economic Area, United Kingdom, Japan and South Korea; a user reply opens a 24-hour customer service window and messages sent within it do not count toward the limit; excessive retries within 24 hours can make a user undeliverable for up to 24 hours; marketing templates not delivered to United States phone numbers). Meta for Developers Changelog (8 October 2025 — messaging limits moved to business-portfolio basis; scaling up to 2,000 unique recipients per 24 hours). WANotifier and ChatOnDesk BSP documentation restating the 131049 error text "This message was not delivered to maintain a healthy ecosystem engagement" and recommended segmentation/retry practices. Turn.io Learn — interpretation of the roughly one-marketing-template-per-user-per-24h baseline and how engagement opens additional sends.