---
title: WhatsApp Frequency Capping
slug: whatsapp-frequency-capping
icon: ⚠️
docTags: 
createdAt: 2026-03-10T09:01:54.835Z
---

**WhatsApp Frequency Capping** is a user-centric feature introduced by Meta to limit the number of **marketing template messages** a user receives within a specific timeframe. Unlike business-specific tier limits, these caps are enforced at the **user level** across all businesses trying to reach them. 

## Core Mechanism

- **Targeted Content**: The cap applies strictly to **Marketing Template Messages** that open new conversations.
- **Exemptions**: Utility, authentication, and user-initiated "free-form" messages are generally **not capped**.
- **Dynamic Limits**: Meta does not publish a fixed threshold; limits are adjusted dynamically based on user engagement and the number of messages a user receives from *all* brands.



## Key Impact for Businesses

When a user hits their limit, any further marketing messages sent to them will **fail to deliver**. 

- **Error Codes**: Failed messages may return Cloud API error code **131026** (often listed as "The message was not delivered to maintain healthy ecosystem engagement").

**First-Come, First-Served**

Delivery depends on whether your message reaches the user before they hit their dynamic cap for that period. 

**Best Practices to Manage Capping**

To maintain high delivery rates despite these restrictions, consider these strategies:

- **Prioritize Engagement**: Use templates that encourage a user reply. Once a user responds, you enter a 24-hour "session window" where messages are not capped.
- **Scheduled Retries**: If a message fails due to capping, wait **24–48 hours** before retrying. Some platforms offer automated retry features to catch users after their limit resets.
- **Segmentation**: Avoid bulk "cold" broadcasts. Target users who have explicitly opted in and are most likely to interact.