Per-user marketing template message limits | Developer Documentation

When a WhatsApp marketing message is limited for one recipient

A marketing template can be approved while an individual message still fails to reach its recipient. When sending through ChatArchitect, check the result of the specific attempt before changing a template, increasing a plan or repeating a campaign.

Understand the recipient restriction

Meta can limit the marketing messages a person receives across businesses. This restriction adapts to recipient engagement and inbox activity; it is not a fixed daily allowance that you can calculate from your own campaign alone. Meta explains the mechanism in its per-user marketing limits guide.

Identify the failed attempt

1. In your CRM, help desk or other connected sending tool, find the attempt for the intended sender, recipient, template name and language. Record its time with time zone and any message or request reference.
2. Inspect the final status and exact error details if your integration exposes them. A queued or accepted request is not proof of delivery; an unavailable outcome remains unknown. The sending guide explains the checks.
3. If the result contains Meta error 131049, ask support to confirm the restriction and the retry plan for that attempt. Meta associates this code with recipient marketing limits and excessive retries to a limited recipient. Other failures require their own diagnosis.
4. If your tool does not show the error, contact ChatArchitect support with the attempt details. Do not assume every missing message has reached a recipient limit or that a failed attempt to one person proves a problem with the entire campaign.

Handle a confirmed limit before retrying

For 131049, Meta instructs businesses to wait at least 24 hours before resending the template. That minimum waiting period does not guarantee delivery on the next attempt. Repeated retries within that period can make further attempts to affected recipients unavailable for up to 24 hours.

Review any automatic retries in your connected workflow and agree with support on which attempt to stop or reschedule. If no retry controls are exposed, ask the workflow owner or support to check them. Keep the original result and later attempts separate in campaign reporting; do not count a resubmission as a new delivered message.

Before an agreed retry, check that the recipient still expects the promotion, has not opted out, and that the offer remains valid. Do not change a promotional message to Utility merely to avoid a marketing restriction; choose the category for its actual purpose using the category guide. Respect a request to stop marketing messages.

Check the recipient country

As checked on 2 October 2026, Meta states that marketing templates are not delivered to United States phone numbers, identified by +1 together with a US area code. Do not treat every +1 number as a US number. Check current country rules with support before scheduling the affected audience; waiting or raising a ChatArchitect plan does not establish eligibility.

Example: one contact does not receive an approved offer

A campaign contains an approved offer for several contacts, but one attempt reports 131049. Keep that contact's result separate, check any scheduled retries and confirm the next action with support. Review other contacts by their own results. If the offer ends before another permitted attempt, close that attempt rather than sending expired terms.

Information for support

Provide the connected tool, sender number, affected recipient through the support channel, template name and language, attempt time with time zone, available reference, status, error text and earlier retry times. Include whether other recipients were affected. Keep App key and Secret out of diagnostic screenshots and messages.