{"id":904,"date":"2026-10-29T13:45:01","date_gmt":"2026-10-29T13:45:01","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-broadcast-frequency\/"},"modified":"2026-10-29T13:45:09","modified_gmt":"2026-10-29T13:45:09","slug":"whatsapp-broadcast-frequency","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-broadcast-frequency\/","title":{"rendered":"WhatsApp broadcast frequency: how many messages per week without losing quality"},"content":{"rendered":"\n

Updated on October 29, 2026<\/em><\/p>\n\n\n\n

There’s no fixed number of messages per week allowed on WhatsApp: Meta doesn’t publish a cap per business, but it limits how many marketing templates each person receives based on their recent engagement, and it lowers your number’s quality rating when blocks and reports pile up. The right frequency is the one that keeps reads and replies stable across your list. Start low, segment by engagement and slow down as soon as signs of fatigue appear, such as more blocks, “stop” requests and 131049 errors.<\/p>\n\n\n\n

This guide covers the limits Meta applies, the signals that indicate overload, practical rules for setting your cadence and how to build frequency control into your system with the official WhatsApp Business API<\/a>.<\/p>\n\n\n\n

What Meta limits (and what it leaves to you)<\/h2>\n\n\n\n

Three Meta mechanisms react to frequency, each in a different way:<\/p>\n\n\n\n

Mechanism<\/th>What it measures<\/th>What happens<\/th>Where it shows up<\/th><\/tr><\/thead>
Per-user marketing limit<\/td>Each person’s recent engagement with marketing messages<\/td>Marketing template isn’t delivered<\/td>Status webhook failed<\/code> with error 131049<\/code><\/td><\/tr>
Phone number quality<\/td>Feedback from recent days: blocks, reports and other signals<\/td>Rating drops and limit growth stalls<\/td>WhatsApp Manager and quality webhooks<\/td><\/tr>
Template pausing<\/td>Quality of a specific template<\/td>Template paused for 3 h, then 6 h, and disabled the third time<\/td>Template status webhook<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The per-user limit is the one most tied to frequency. According to the per-user limits documentation<\/a>, it adapts automatically to the person’s recent engagement, considering how often they read marketing messages and how crowded their inbox is with messages from personal contacts and businesses. Meta doesn’t publish a number. The same page says WhatsApp currently doesn’t deliver marketing templates to US phone numbers. Marketing messages sent inside a customer service window opened by the customer don’t count toward this limit. The article on the per-user marketing limit<\/a> explains the error in detail.<\/p>\n\n\n\n

Everything else is up to you: how many campaigns per week, to whom and at what interval. Meta doesn’t do that control for you, and the cost of getting it wrong shows up later, in quality.<\/p>\n\n\n\n

Why sending too much is expensive<\/h2>\n\n\n\n

High frequency hurts in three ways that add up:<\/p>\n\n\n\n

    \n
  1. Less delivery.<\/strong> People who receive a lot and read little tend to hit the per-user limit sooner. Messages fail with 131049<\/code>, and resending in less than 24 hours makes things worse: the documentation says repeated attempts can make sending to those people unavailable for up to 24 hours.<\/li>\n\n\n
  2. Lower quality.<\/strong> Blocks and reports drag down your number’s rating. The article on phone number quality rating<\/a> shows how to read green, yellow and red.<\/li>\n\n\n
  3. A smaller list.<\/strong> Each person who turns off your business’s offers stops receiving your marketing until they turn it back on themselves.<\/li>\n\n<\/ol>\n\n\n\n

    There’s also a direct cost. Each marketing template delivered to Brazil costs R$ 0.3217 (Brazilian reais) since October 1, 2026. One extra weekly campaign to 10,000 delivered contacts adds up to R$ 3,217.00 on Meta’s rate card, even if nobody buys.<\/p>\n\n\n\n

    Signs of list fatigue<\/h2>\n\n\n\n

    Track these signals per campaign and per segment. When two or more get worse at the same time, frequency has probably gone too far.<\/p>\n\n\n\n

    Signal<\/th>How to measure<\/th>What it indicates<\/th><\/tr><\/thead>
    More 131049<\/code> errors<\/td>Status webhook failed<\/code><\/td>People receiving more marketing than they read<\/td><\/tr>
    More 131050<\/code> errors<\/td>Status webhook failed<\/code><\/td>People turning off your business’s offers<\/td><\/tr>
    More taps on the opt-out button<\/td>Message webhook with type: \"button\"<\/code><\/td>Explicit opt-out<\/td><\/tr>
    Replies like “stop”, “unsubscribe”, “no more”<\/td>Text message webhook<\/td>Opt-out by text, which must also be honored<\/td><\/tr>
    Falling read rate<\/td>read<\/code> \u00f7 delivered<\/code> per campaign<\/td>Message ignored<\/td><\/tr>
    Change in number or template quality<\/td>WhatsApp Manager and webhooks<\/td>Accumulated negative feedback<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Error 131050<\/code> appears when the person used WhatsApp’s “Offers and announcements” setting to stop marketing messages from your business. The marketing templates documentation<\/a> says the API accepts the request but doesn’t deliver the message, and that you can subscribe to the user_preferences<\/code> webhook to learn when the person stops or resumes.<\/p>\n\n\n\n

    Practical frequency rules (a starting point)<\/h2>\n\n\n\n

    The numbers below don’t come from a Meta rule or a study. They’re a conservative cadence to start with, which you should adjust using the signals in the table above.<\/p>\n\n\n\n