Frequency Capping
Frequency capping is the practice of deliberately limiting how many messages a single contact receives from your business within a given period — per day, per week, or per campaign. On the WhatsApp Business API it is one of the most direct levers you have over your quality rating, block rate and long-term deliverability. Send too often and recipients tap "Block" or "Report"; those signals feed Meta's quality scoring, throttle your throughput, and can push your number from a Green to a Yellow or Red quality tier. A well-tuned cap keeps you in front of customers often enough to drive results, without exhausting the goodwill that makes WhatsApp such a high-converting channel.
In one line
Frequency capping means limiting how often you message each contact so you protect your WhatsApp quality rating, keep block rates low, and sustain deliverability — while still reaching customers often enough to convert.What frequency capping actually means
Frequency capping is a rule you set — inside your broadcast tool, CRM, or automation logic — that stops a contact from receiving more than a defined number of messages in a defined window. A typical cap might be 'no more than one marketing template per contact per day' and 'no more than three per week'. Crucially, capping applies to messages you initiate: marketing and utility templates sent outside the 24-hour service window. Replies within an open service window are conversational and rarely need capping, because the customer is actively engaged. The point of a cap is not to send less for its own sake — it is to protect the finite attention and tolerance each recipient has, so that the messages you do send land, get read, and get acted on.
Why it matters on the WhatsApp Business API
WhatsApp is unusually protective of the user experience, and Meta measures how customers react to your business. Every message that triggers a block or a report degrades your quality rating; a poor rating lowers your messaging limit tier and can trigger warnings or restrictions on your number. Frequency capping is the single most controllable input into that scoring. It also matters for cost: since 1 July 2025, WhatsApp bills per delivered message by category (marketing, utility, authentication), so every unnecessary marketing send is a line item you are paying for — with InfiQ that is transparent ₹ pricing, ex-GST. Capping trims the low-value, high-annoyance sends that quietly inflate your bill while eroding trust.
- Protects your quality rating (Green / Yellow / Red) by keeping block and report rates low
- Preserves your messaging limit tier, which governs how many unique contacts you can reach per day
- Reduces wasted spend, since marketing templates are billed per delivered message
- Improves open and click rates by keeping each message feeling relevant rather than relentless
- Lowers opt-out and 'STOP' rates, protecting the size of your reachable audience over time
How to set a sensible cap
There is no universal number — the right cap depends on your category, your list quality, and how much genuine value each message carries. A d2c brand running weekly drops behaves differently from a bank sending transactional alerts. Start conservative and let engagement data guide you: watch read rates, block rates and opt-outs, and loosen or tighten from there. Separate your caps by message category, because a customer will happily receive an OTP and a delivery update on the same day they would resent a third promotional blast. Layer a per-contact daily limit, a rolling weekly limit, and a cooling-off period after any block or opt-out signal, and enforce them at the send layer so no campaign can accidentally override them.
- Cap marketing separately from utility and authentication — never lump them into one limit
- Use a rolling window (last 7 days) rather than a fixed calendar week to avoid weekend clustering
- Respect a cooling-off period for contacts who recently didn't open or engaged negatively
- Suppress anyone who has opted out immediately, and honour it across every campaign
- Review caps monthly against block rate, read rate and unsubscribe trends
Frequency capping vs. the per-user marketing limit
It is easy to confuse frequency capping with Meta's own per-user marketing message limit, but they are different mechanisms. The per-user marketing limit is enforced by WhatsApp itself: it restricts how many marketing template messages a person can receive across all businesses, and messages beyond that ceiling simply may not be delivered. Frequency capping is your own voluntary discipline, applied per business, that usually sits well below any platform ceiling. Think of the platform limit as a hard wall you rarely want to touch, and your cap as the comfortable lane you choose to drive in. Businesses that rely on the platform limit to save them from over-messaging have already lost the trust battle — by the time WhatsApp is dropping your messages, your recipients were annoyed long ago.
Common mistakes to avoid
The most frequent error is treating frequency capping as a global switch instead of a per-category, per-segment policy — which either over-restricts your transactional messages or under-restricts your promotions. Others forget that multiple tools or teams sending from the same number stack up: marketing, support, and an automation flow can each be 'within cap' while the customer receives five messages in an afternoon. Some businesses cap by campaign rather than by contact, so a person on three lists gets three sends. And many ignore engagement entirely, applying the same cap to a super-fan and a dormant contact who last opened a message months ago. The fix is to centralise capping at the contact level, count every outbound message regardless of source, and let engagement raise or lower the ceiling per person.
- Applying one blanket cap across marketing, utility and authentication categories
- Counting caps per campaign instead of per contact, so multi-list contacts get over-messaged
- Ignoring messages sent by other teams or tools from the same WhatsApp number
- Never adjusting the cap based on individual engagement or recency
- Forgetting to reset the audience after a quality-rating dip, and simply sending more
Frequently asked questions
What is a good frequency cap for WhatsApp marketing?+
Does frequency capping reduce my WhatsApp costs?+
How does over-messaging affect my quality rating?+
Is frequency capping the same as the per-user marketing limit?+
Do replies inside the 24-hour window count against my cap?+
Should transactional and marketing messages share the same cap?+
How do I stop different teams from over-messaging the same contact?+
Can InfiQ help me set up frequency capping correctly?+
Message often enough — never too often
Talk to an InfiQ specialist to set per-contact, per-category frequency caps that protect your quality rating and cut wasted spend, with transparent ₹ pricing.