Skip to main content

​
WhatsApp Meta Policy Cadence & Tenant-Owned Posture

Meta’s WhatsApp Business policies are not static: the rules that govern template categories, marketing frequency, and regional enforcement change several times a year. Orbit submits templates and sends on your behalf, but every content decision, category assignment, and enforcement action is Meta’s. This page tracks the enforcement-level shifts that most often affect tenants on Orbit, framed as a posture checklist rather than a guarantee. Every claim below carries an “as of” date and a live verify-link. Use this page to plan around known Meta behaviour; always confirm the current rule against Meta’s live documentation before launching a new use case. For the evergreen content rules, see WhatsApp Restricted & Prohibited Content Policy.

​
The 2023-2026 Meta content-policy timeline

​
From four template categories to three

  • As of April 2025, Meta moved WhatsApp Business message templates from four categories to three: Marketing, Utility, and Authentication. The previous “Service” category was retired.
  • What changed in practice: templates previously classified as Service were expected to map to Utility or, in some cases, to Marketing if their body contained promotional intent.
  • Why it matters for Orbit tenants: a template that once billed as Utility could be reclassified as Marketing by Meta reviewers or by automated reclassification, changing the per-message conversation price. Orbit syncs the category Meta returns, but does not decide the category.
  • Verify the current categories against Meta’s live documentation: Meta template categories.

​
Utility vs. Marketing re-categorization

  • As of April 2025, Meta tightened how Utility templates are judged. A template submitted as Utility that contains any promotional language, cross-sell, coupon, discount, or “buy now” framing is routinely reclassified as Marketing during review or after a period of live traffic.
  • What a tenant should expect: the template name stays the same, but the category field in Meta’s response changes. The approval status may remain approved, but the billing category and conversation-rate rules now follow Marketing.
  • Orbit’s role: the synced template record reflects Meta’s returned category. Orbit does not rewrite categories and does not pre-approve Marketing content as Utility.
  • This is the most common cause of “my marketing template category flipped” symptoms. For the fix workflow, see Troubleshoot WhatsApp templates.
  • Verify against Meta’s live guidance: Meta Business Messaging Policy.

​
Per-user marketing-template frequency caps

  • As of May 2024, Meta began enforcing per-user frequency limits for Marketing templates in select markets, and expanded the behaviour through 2025. A single WhatsApp user can receive only a limited number of Marketing template messages from any business within a rolling window. The exact cap varies by market and is not published as a fixed number.
  • What a tenant should expect: a Marketing template that is approved and otherwise healthy can still be throttled at send time if the recipient has already received too many Marketing messages in the window. Meta returns a rate-limit response; Orbit surfaces it as a send failure rather than queueing it indefinitely.
  • Orbit’s role: Orbit forwards Meta’s refusal. It does not maintain a separate per-user Marketing cap; any cap that appears in the send log is Meta’s.
  • Planning implication: high-frequency campaigns should split audiences and cadences so that no single user receives repeated Marketing templates in a short window.
  • Verify current guidance: Meta quality and rate limits.

​
Marketing Messages Lite / per-user frequency caps

  • As of late 2024, Meta introduced a “Marketing Messages Lite” experiment in some markets. The experiment reduced the per-user frequency ceiling for certain Marketing templates, effectively tightening the cap described above for traffic that Meta labelled low-value or high-frequency.
  • What a tenant should expect: sends that previously passed began failing with rate-limit or quality-related refusals even though the template itself was approved and the WABA was healthy.
  • Orbit’s role: Orbit records the refusal code Meta returns. It cannot bypass the cap or whitelist a sender for the experiment.
  • Planning implication: treat Marketing templates as a constrained resource per recipient. Prioritize high-intent segments and reserve Utility templates for transactional notifications.
  • Verify current status: Meta Business Messaging Policy changelog.

​
Regional pause experiments: United States, India, and Brazil

  • As of 2025, Meta ran phased experiments that paused or restricted Marketing template sends in the United States, India, and Brazil at different times. The experiments were not global and were not announced with fixed end dates.
  • What a tenant should expect: Marketing sends to users in an affected market were refused at Meta’s edge during the experiment window, while Utility and Authentication templates generally continued. The refusal code and message pointed to a Meta-side restriction.
  • Orbit’s role: Orbit relayed Meta’s refusal and logged the market-level block. It did not impose the pause independently.
  • Planning implication: if a campaign sees sudden, market-wide Marketing refusals on an otherwise healthy WABA, check Meta’s status and policy changelog before assuming a connection, template, or billing problem.
  • Verify current regional status against Meta’s live pages: Meta Business Manager status and Meta WhatsApp business updates.

​
Authentication-template sunsets in some regions

  • As of 2025, Meta began phasing out traditional one-tap and zero-tap Authentication templates in some regions in favour of newer authentication message formats. Existing approved Authentication templates continued to work in most markets during the transition, but new submissions in affected regions were required to use the updated format.
  • What a tenant should expect: an Authentication template that submitted successfully in one market could be rejected or require additional credentials in another. The code_expiration_minutes and button-type rules remained strict.
  • Orbit’s role: Orbit enforces the structural rules Meta requires for Authentication templates before submission. It does not decide regional availability or format sunsets.
  • Planning implication: if your use case depends on OTP over WhatsApp, verify the current Authentication-template format for each target market before launch, and keep a fallback channel ready.
  • Verify current rules: Meta Authentication templates.

​
What a tenant observes in Orbit when Meta acts

When Meta changes a policy or enforces a limit, the effect appears in Orbit through Meta-synced signals. The job is to tell Meta’s action from an Orbit-side throttle.

​
Template-status changes

The WhatsApp template list under Channels > WhatsApp > Templates and the GET /api/v1/whatsapp/templates endpoint reflect Meta’s returned state:
  • approved but with a new category — Meta reclassified the template.
  • paused — Meta’s quality metrics for that template dropped.
  • rejected — Meta returned a policy or formatting reason.
  • submission_failed — Meta refused the create call before the template entered review.
These statuses come from Meta. Orbit runs a structural pre-flight check before submission, but the final verdict is always Meta’s. For the full status workflow, see Troubleshoot WhatsApp templates.

​
Quality-pause surface

When Meta reports a RED quality rating on a phone number, Orbit’s campaign gate auto-pauses new sends with WHATSAPP_QUALITY_RED. The dashboard banner and campaign metadata name the Meta-side cause.
  • This is a Meta-side pause mirrored by Orbit, not an Orbit-initiated hold.
  • Recovery happens in Meta Business Manager: fix the content that recipients are reacting to, wait for the rating to recover to YELLOW or GREEN, then resume the campaign.
  • See Troubleshoot WhatsApp quality-red campaign pause.

​
Billing surface

Meta error 131042 (WHATSAPP_BILLING_ISSUE) blocks every send from the WABA because of a payment-method problem at Meta. Orbit returns HTTP 409 with the code. The fix is entirely in Meta Business Manager; the Orbit connection and wallet are unaffected.

​
Send-gate record: Meta-side decline vs. Orbit-side hold

The compliance send-gate log distinguishes between Orbit-side gates and Meta-side refusals:
  • Orbit-side hold — a gate Orbit owns, such as quiet-hours or tenant-configured suppression. These appear with Orbit error codes like OUTSIDE_QUIET_HOURS or SUPPRESSED.
  • Meta-side decline — a refusal returned by Meta’s Graph API. These carry a Meta error code such as 131042, 131009, or a rate-limit response, and the send-gate record logs the upstream code.
For the send-gate model, see Send Gates. For the list of Meta error codes Orbit maps, see Error codes.

​
Tenant-owned posture actions

Meta’s enforcement cadence is outside any BSP’s control. The tenant-owned actions below reduce surprise and keep sends running.

​
Cadence planning against per-user caps

  • Treat Marketing templates as a per-recipient, per-window resource. Avoid sending multiple Marketing templates to the same user within a short window.
  • Use Orbit’s frequency-cap and campaign-throttling settings to enforce your own ceiling below Meta’s unpublished cap. That way a Meta cap lands as a safety net, not a sudden failure.
  • Read more: Frequency caps and Campaign limits and quiet hours.

​
Split Utility and Marketing templates cleanly

  • Reserve Utility templates for purely transactional events: order confirmations, appointment reminders, delivery updates, payment receipts, and account alerts.
  • Remove upsell, cross-sell, discount codes, and brand-promotion language from Utility templates. Even a small promotional line can trigger reclassification to Marketing.
  • Build Marketing templates in a separate workflow so that category, pricing, and frequency planning stay explicit.

​
Verify the send-gate record before escalation

When a send fails:
  1. Read the error code in the message record or DLR webhook.
  2. If the code is a Meta error such as 131042, 131009, or a WhatsApp rate-limit, the fix is at Meta.
  3. If the code is an Orbit gate such as OUTSIDE_QUIET_HOURS or SUPPRESSED, adjust the tenant config or recipient state.
  4. If the code is a structural issue such as TEMPLATE_NOT_APPROVED, work the template layer first.
This distinction prevents re-running sends that Meta will refuse again and protects the WABA’s quality rating.

​
Verification habit: quarterly checklist

Meta updates its policies, category rules, and regional experiments quarterly or faster. Make this check part of your quarterly compliance review:
  1. Re-read Meta’s Business Messaging Policy.
  2. Re-read Meta’s Commerce Policies if you sell goods or services.
  3. Check Meta’s template-category documentation for any new category or format changes.
  4. Check Meta’s quality-rating and rate-limit guidance for updated thresholds.
  5. Review your WABA’s quality rating and recent template rejections in Meta Business Manager.
  6. Compare your Orbit template list against Meta’s template list for category drift.
  7. Confirm that your Marketing-template frequency and audience splits still match your target markets.
Orbit’s compliance posture quarterly review guide covers the broader cadence for tenant-owned controls.

​
See also