On this page
Meta has paused all MARKETING-category WhatsApp template messages to United States (+1) phone numbers since 1 April 2025, and as of this writing the pause remains fully in force with no announced end date. VGraple CRM checks every recipient's country code before attempting a marketing send and blocks a US number at audience-build time, so the suppression happens before Meta ever sees the attempt, not as a failure you discover afterward.
US marketing pause: first 5 of 6 steps
- 1Every broadcast's audience is checked against the
- 2US recipients are marked suppressed, not attempted
- 3Utility and Authentication sends to the same
- 4Segment your audience by category need before
- 5Check the suppression breakdown after a campaign
Before you start
- Know that this affects MARKETING-category templates only. Utility templates, Authentication templates, and free-form replies inside an open 24-hour service window are unaffected and continue to work normally to US numbers.
- If your business has US customers and relies on marketing broadcasts to reach them, plan around this restriction now rather than discovering it mid-campaign; there is no VGraple CRM setting to disable the check, since it reflects a real Meta policy, not a configurable safety rail.
- Nothing needs to be turned on to receive this protection; it runs automatically on every plan, for every campaign, without configuration.
Steps
Understanding how VGraple CRM handles this automatically
Every broadcast's audience is checked against the pause before sending. When a campaign's audience includes a MARKETING-category template, VGraple CRM checks each recipient's country code as part of the same pre-flight suppression pass that checks opt-outs, blocks, and marketing-stopped status.
US recipients are marked suppressed, not attempted. A +1 number in the audience of a marketing broadcast never reaches Meta's API for that send; it is recorded as suppressed with the US marketing pause named as the specific reason, visible in the campaign's recipient table.
Utility and Authentication sends to the same numbers proceed normally. The check is specific to MARKETING-category content; if the same US contact is also enrolled in, for example, an appointment-reminder sequence using a Utility template, those sends are unaffected.
Planning campaigns that include US contacts
Segment your audience by category need before building a broadcast. If a campaign genuinely needs to reach US contacts, consider whether the message can be reframed as account-activity or transactional content and sent as a Utility template instead, since Meta's category rules (not VGraple CRM's) determine what qualifies. See template categories and pricing for what separates the categories.
Check the suppression breakdown after a campaign sends. The broadcast's analytics show suppressed recipients broken out by reason, including the US marketing pause specifically, so you can see exactly how many US contacts were excluded and confirm nothing else caused the suppression instead.
Do not attempt to route around the pause. There is no approved way to reach a US number with marketing content during this restriction, including sending from a different WhatsApp number, since the pause is based on the recipient's country code, not the sender's.
What is actually still allowed to US numbers?
| Message type | Affected by the pause? | Notes |
|---|---|---|
| MARKETING template (promotions, announcements, sales) | Blocked, suppressed before send | The only category this pause targets |
| UTILITY template (order updates, appointment reminders, account activity) | Not affected | Sends normally, billed at the utility rate outside the free service window |
| AUTHENTICATION template (OTP, login codes) | Not affected | Sends normally |
| Free-form reply inside the 24-hour service window | Not affected | A human agent or the AI assistant can reply to a customer's own message normally, at no charge |
| Marketing template to a US number who already replied recently | Still blocked | The exemption for free-form replies covers replies, not template sends; a Marketing template to that same number is still suppressed regardless of recent engagement |
Why does VGraple CRM block this before sending, rather than letting Meta reject it?
Blocking at audience-build time, rather than letting each send fail individually at Meta, exists for a concrete reason: a failed send at Meta still costs a delivery attempt Meta records against the account, and repeatedly attempting sends Meta has already made clear it will refuse is exactly the retry pattern Meta has enforced account-level penalties against since 30 April 2026. Suppressing the recipient before the attempt keeps the campaign's real failure rate honest (a genuinely broken template or a bad audience is still visible) while never contributing a wave of guaranteed-to-fail attempts that would otherwise look identical to a real delivery problem in your funnel.
What you will see
A broadcast sent to an audience containing US numbers, using a Marketing template, shows those specific recipients in the Suppressed tab of the campaign's funnel, with "US marketing pause" as the stated reason rather than a generic failure. The broadcast's cost estimate at compose time already excludes suppressed recipients from the projected charge, since a suppressed send is never billed by Meta.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| US marketing pause check | Blocks MARKETING-category sends to +1 numbers before they reach Meta | Always on; not configurable, since it reflects Meta's own restriction |
| Suppressed recipient reason | Names the specific cause (US marketing pause, opt-out, block, frequency cap) on each suppressed row | Always shown in the recipient table and export |
| Category-aware exemption | Utility and Authentication templates to US numbers are never blocked by this check | Automatic, based on the template's actual category |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| US recipients missing from a marketing broadcast's sent count | The US marketing pause suppressed them before the send attempt, by design | Expected; check the Suppressed tab for the exact count and reason |
| A US customer says they never received a promotional message | It was suppressed by the pause; this is Meta's restriction, not a delivery failure | Send the offer as an in-app notification, email, or another channel instead for US customers, or reframe as Utility content if it genuinely qualifies |
| Confusing this with error 131049 (per-user frequency cap) | Both suppress marketing sends, but for different reasons | Check the specific reason named on the recipient row; 130472/US pause is country-based, 131049 is per-recipient frequency-based |
| Wondering when this will lift | Meta has not announced an end date as of this writing | VGraple CRM will remove the block automatically if Meta lifts the restriction; no manual update needed on your part |
| Utility reminders to US numbers also being blocked | This would not be caused by the US marketing pause, which is Marketing-only | Check the template's actual category; a template recategorised to Marketing by Meta would then be affected, see template recategorised from utility to marketing |
Related reading
For the complete list of reasons a recipient can be suppressed, see why a recipient was suppressed. For how message categories are decided and what each costs, see template categories and pricing, and for the five reasons a whole campaign can pause, see broadcast paused: every reason and what to do.