WhatsApp error 131048 (spam rate limit): what causes it and how to recover

Updated 2026-10-22 · 4 min read · By the Convo360 team

What error 131048 means

Meta's error code reference describes 131048 like this: the message failed because there are restrictions on how many messages can be sent from this phone number, and this may be because too many previous messages were blocked or flagged as spam. Meta's suggested fix is to check your quality status in WhatsApp Manager and review your template quality.

In practice it usually appears in the middle of a broadcast. The first few hundred messages go through, then failures with 131048 start piling up. That pattern tells you the campaign itself is generating the negative feedback, and every extra message you push adds to it.

Meta's opt-in guidance says the same thing in general terms: its systems will rate limit businesses whose quality is low for a sustained period. 131048 is what that rate limit looks like in your delivery report.

131048 compared with similar limit errors

Only 131048 points to a problem with how people are reacting to your messages. The others are about speed or about an individual customer. If you see a mix, deal with 131048 first, because it affects everyone on your list.

What usually triggers a spam rate limit

• Messaging people who never opted in. Bought lists, old exhibition data or numbers scraped from directories produce blocks very quickly. Meta's policy requires opt-in that names your business.
• A sudden jump in volume. A number that normally sends a few hundred messages a week and then sends 8,000 festive offers in an hour invites reports.
• Messages that do not look like you. If the display name, profile photo or first line does not tell people who is writing, they block first and ask later.
• No easy way to opt out. When the only way to stop your messages is the block button, people use it.
• Too many offers. Daily promotions to the same list wear out goodwill even among real customers.

Your quality rating in WhatsApp Manager is the early warning. A move from high to medium is your cue to slow down before 131048 appears.

How to recover, step by step

1. Stop the campaign. Every message sent while restricted either fails or adds more feedback.
2. Check WhatsApp Manager. Look at the phone number's quality rating, any template marked low quality or paused, and the messaging limit under Account tools.
3. Find the cause. Which list, which template, which day? Compare the failing campaign with ones that went well.
4. Clean the list. Remove contacts without a clear opt-in and anyone who has not engaged in months.
5. Fix the template. Make the sender and purpose clear in the first line, and add a quick-reply button such as Stop offers.
6. Restart small. Send to your most engaged customers first, then widen over several days.

Meta does not publish how long a 131048 restriction lasts, so be wary of anyone who promises a fixed timeline. What is published is that a drop in phone number quality no longer lowers your messaging limit. You keep your tier, but a poor rating still pauses templates and can keep sending restricted, so the fix is behavioural, not technical.

How Convo360 helps you avoid 131048

On Convo360 the broadcast tools in WhatsApp Studio are built around this problem:

• Automatic pause. When Meta returns a spam or quality limit, the campaign pauses itself, keeps the remaining contacts queued and tries again later, instead of firing the whole list into a restriction.
• Pacing controls. Each campaign has speed presets, a send window and a daily cap at 80% of your messaging limit, so a festive list goes out over hours, not minutes.
• Opt-out handling. STOP keywords mark a contact as opted out, and opted-out contacts are left out of broadcasts. Add a Stop offers button to your template so people have an easier choice than blocking.
• Number health. The Manage panel for your WhatsApp number shows its messaging limit and quality, so you can check before a big send.
• Clean imports. CSV import checks numbers before they are added, so obviously broken data does not reach a campaign.

You pay Meta directly for delivered messages, with no markup from Convo360. Read the campaigns documentation for the settings, and the compliance guide for opt-in capture.

Habits that keep a number out of trouble

• Collect opt-in at the point of sale, on your website form or with a keyword, and record it.
• Grow volume gradually. Let a new number build history with utility messages and replies before big promotions.
• Segment. A Surat saree buyer and a Bengaluru corporate client should not get the same offer.
• Make every marketing message easy to act on and easy to decline.
• Review the delivery report after every campaign, not only when something breaks.

For the full picture of what can stop delivery, see six reasons WhatsApp messages are not delivered.

Step by step

1. Stop the campaignPause the broadcast as soon as 131048 failures appear, so you stop adding negative feedback.
2. Check quality in WhatsApp ManagerReview the phone number's quality rating, paused or low-quality templates and the messaging limit.
3. Remove unconsented contactsDrop numbers without a clear opt-in and contacts who have not engaged in months.
4. Fix the templateMake the sender and purpose clear in the first line and add a Stop offers quick-reply button.
5. Restart with engaged customersSend to your most engaged contacts first and widen the audience over several days.

Example conversation

Frequently asked questions

Official sources

• Meta: WhatsApp Cloud API error codes (checked 22 October 2026)
• Meta: Messaging limits (checked 22 October 2026)
• Meta: Template pausing (checked 22 October 2026)
• Meta: Get opt-in for WhatsApp (checked 22 October 2026)

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.