WhatsApp Broadcast: The Complete Operator's Guide

Most WhatsApp broadcast advice stops at "get opt-ins and don't spam." That's table stakes. The gap between a broadcast program that quietly prints revenue and one that gets a number flagged within a quarter comes down to operational discipline: who you send to, how often, with what template, and what you do in the 48 hours after the send.

We see this across accounts: two businesses with the same list size and the same product category can end up with a 3–5x difference in revenue per broadcast. The difference is rarely the copy. It's segmentation, cadence control, and whether anyone is actually watching the quality rating between sends.

This is the operator playbook — the version we wish every team had before their first big send. It covers list building that survives an audit, an RFM-lite segmentation model you can run in a spreadsheet, template strategy by lifecycle stage, frequency caps that protect your number, the metrics that actually run the program, and the follow-up plays that typically add 15–30% on top of the initial send.

Build the list before you need it

A broadcast program is only as good as its opt-in base, and opt-in collection is a background process, not a campaign. The businesses that do this well have three to five collection points running permanently, each with a documented consent trail — and they review the mix quarterly, because the sources drift.

Website widget

A chat widget with an explicit "get updates on WhatsApp" checkbox converts a small but steady share of visitors — typically 1–3% of traffic, more on high-intent pages like pricing or order tracking. The key detail: the opt-in language must mention marketing messages specifically, not just "chat with us." Support consent and marketing consent are different things, and Meta's policies treat them differently. A visitor who ticked a box to track their order did not agree to a weekly offers blast, and they will tell you so with the block button.

QR codes at physical touchpoints

For retail, restaurants, clinics and salons, a QR at the counter, on the bill, or on packaging is often the highest-volume source. A Bengaluru café chain we work with prints a QR on every receipt with "Scan for this week's menu + offers" — the framing gives customers a reason beyond "join our list." In-store QR opt-ins tend to be higher quality than web ones because the person has already transacted with you. If you run multiple locations, use a distinct QR (or a location parameter) per outlet; six months in, knowing which store built which slice of the list is worth real money when you plan location-specific offers.

Checkout and order confirmation

The single best moment to ask. The customer is mid-transaction, trust is at its peak, and the value exchange is obvious: order updates now, offers later. Whether it's a checkbox on your e-commerce checkout or a verbal confirmation logged by staff at a billing counter, capture it here and you'll build a buyer-heavy list rather than a browser-heavy one. Buyer-heavy lists behave differently: higher click rates, dramatically lower blocks, and far better tolerance for a third or fourth monthly touch.

What not to do: never upload a purchased or scraped list, and never migrate an SMS database wholesale without fresh WhatsApp-specific consent. Block rates above roughly 1–2% on a send are enough to start dragging your quality rating, and purchased lists routinely block at several times that. One bad import can undo six months of careful warm-up.

Store the proof — timestamp, source, and the consent text shown — for every contact. If Meta ever reviews your account, "we have opt-ins" is not an answer; records are.

Segment with RFM-lite

Full RFM analysis (recency, frequency, monetary) is standard in email marketing but overkill for most WhatsApp programs. A simplified version — RFM-lite — gets you 80% of the value with a spreadsheet and an order export.

Score every contact on two axes:

• Recency: days since last order (or last meaningful interaction if you don't sell online). Buckets: 0–30, 31–90, 91–180, 180+.
• Value: lifetime order count or lifetime spend. Buckets: one-time, repeat (2–4 orders), loyal (5+).

That yields a manageable grid. In practice, four segments cover most sends:

1. Active buyers (ordered in the last 30 days) — highest intent, lowest tolerance for irrelevance. They just bought; don't pitch them the same category again.
2. Warm (31–90 days) — the core broadcast audience. Most campaign revenue comes from here.
3. Cooling (91–180 days) — needs a stronger hook: a genuine offer, new arrivals, a reason to come back.
4. Dormant (180+ days) — send sparingly, expect blocks, and treat every send to this segment as a controlled experiment with its own budget line.

The value axis earns its keep inside those recency bands. A loyal customer who's gone quiet for 100 days deserves a personal-feeling win-back — they've proven they'll spend. A one-time buyer at the same recency gets the standard offer template, and if they don't respond in two attempts, they age out. Spending your best offers uniformly across a recency band is leaving margin on the table.

The discipline that matters most: rebuild segments before every send. A contact who bought yesterday should not receive the win-back message that was queued when they were dormant. Stale segments are the most common self-inflicted wound we see in broadcast programs — usually it shows up as a customer screenshot of a "we miss you" message sent two days after their order arrived.

Match templates to lifecycle stage

Every business-initiated broadcast on the WhatsApp Business Platform goes out as a pre-approved template. The mistake is writing one "monthly offer" template and sending it to everyone. Template strategy should mirror your segments:

• Active buyers get cross-sell and replenishment templates. "Your order shipped — customers who bought X often add Y" performs; a generic discount to someone who paid full price last week mostly generates annoyance and the occasional refund request.
• Warm contacts get your core promotional templates: new collection, seasonal offer, restock alerts. This is where carousel and catalog formats earn their keep.
• Cooling contacts get incentive-led win-back templates. Lead with the offer in the first line — it's what shows in the notification preview, and the preview is the whole battle for this segment.
• Dormant contacts get a single, honest re-permission template: "We haven't messaged you in a while — want to keep getting offers?" with quick-reply buttons. A "No" here is a gift; it's a silent block you avoided and a delivery cost you stop paying.

Two craft notes that apply across all stages. First, use quick-reply buttons rather than bare links wherever the flow allows — button taps typically run 1.5–2x link click rates and open a service window for free-form follow-up. Second, write templates in the language your customers actually message you in; Hinglish outperforms formal English for a large share of Indian D2C audiences, and regional-language templates routinely beat both in tier-2 and tier-3 cities. A Surat saree retailer running Gujarati templates against an English control is not running a gimmick; that's usually the highest-leverage A/B test available.

Keep two to three approved variants per lifecycle stage rather than one. Templates can be paused by Meta on negative feedback, and festival weeks are the worst possible time to discover your only win-back template is under review. Our marketing template library has approved-format examples for each of these stages, including button and carousel variants you can adapt.

Cadence and frequency caps

Frequency is where broadcast programs die. Not from one bad send — from an unexamined habit of sending "whenever there's something to announce," which quietly becomes eight touches a month once the founder, the marketing hire, and the agency each schedule their own campaigns.

The sustainable zone for marketing messages is typically 2–4 touches per contact per month, weighted by segment:

Three rules make the caps stick:

1. Enforce them in software, not in memory. Your platform should hard-stop a contact from receiving a fifth marketing message in a month regardless of which campaign it belongs to. Manual tracking fails the first time two teams schedule sends in the same week.
2. Count all marketing, across teams. The festival campaign, the new-launch announcement, and the "quick flash sale" all draw from the same monthly budget of attention.
3. Exclude utility from the cap. Order updates, delivery notifications and payment confirmations are expected and welcomed; capping those helps nobody.

Timing matters less than frequency, but it isn't nothing. For most Indian consumer audiences, late morning (10:30–12:00) and evening (19:00–21:30) windows outperform; avoid the 08:00 blast that lands while people are commuting. Your own click-by-hour data will beat any generic guidance within three or four campaigns — which is one more reason to instrument early.

If you're planning a multi-send month, sketch it in the WhatsApp campaign planner first — seeing four campaigns land on the same warm segment in one view is usually all the persuasion a team needs.

Protect your quality rating like revenue depends on it

Because it does. Meta assigns each phone number a quality rating (High / Medium / Low) based on recipient feedback — blocks and reports foremost. A falling rating can reduce your messaging limits or restrict the number; a sustained Low rating puts the whole channel at risk.

Operational protections worth building in:

• Warm up new numbers. Fresh numbers start with lower daily conversation limits that upgrade with sustained volume and quality. Ramp over two to three weeks, starting with your most engaged contacts; don't blast the full list on day one.
• Stagger large sends. Sending 50,000 messages over 4–6 hours instead of ten minutes lets you halt mid-send if blocks spike. Treat the first 10% of any large send as a canary.
• Send dormant campaigns from a slot you can afford to lose. Isolate risky segments in time (and in review cadence) from your bread-and-butter warm sends, so one bad win-back experiment can't contaminate the read on your core program.
• Review template quality signals. Retire templates whose block rates run consistently above your account average — the template is telling you something the copy review missed.

Assign the rating check to a named person as a post-send ritual, same as checking the revenue number. Programs where "everyone" watches quality are programs where nobody does.

Measure past the read rate

Read rates on WhatsApp are structurally high — often 70–90% on healthy opted-in lists — which makes them a flattering but nearly useless KPI. Every campaign looks like a winner if reads are the scoreboard.

The metrics that actually run the program:

• Click / button-tap rate — the first real intent signal. Healthy promotional sends typically land somewhere in the 8–20% range depending on segment and offer strength; your own baseline matters more than any benchmark.
• Reply rate — for conversational campaigns, replies open a service window and a selling opportunity. A campaign built around a question ("Which colour should we restock?") can monetise replies better than clicks.
• Attributed orders and revenue per send — via coupon codes, UTM-tagged links, catalog orders or CRM matching. This is the number that justifies (or kills) the program.
• Block rate and opt-out rate per send — your cost side. A campaign that drives ₹80,000 in orders but burns 400 contacts in blocks may be net-negative once you price in list replacement and rating risk.
• Cost per attributed order — Meta bills marketing conversations per delivery, so every send has a hard cost. Run the numbers in the broadcast cost calculator before a large campaign; the economics of a full-list blast versus a segmented send are usually decisive on their own.

One reporting habit worth stealing from mature programs: report revenue per send by segment, not just per campaign. The moment a team sees that warm contacts produce most of the revenue at a fraction of the blocks, the full-list blast argument dies on its own.

The 24-hour non-reader resend play

Here's the follow-up sequence that most teams leave on the table. After any promotional send, your audience splits into four behavioral groups — and each deserves a different next touch:

The non-reader resend deserves emphasis because it's counterintuitive: messages go unread for mundane reasons — notification buried, phone on silent, bad timing — far more often than from disinterest. A single resend to non-readers 24–48 hours later, with a rewritten first line so the notification preview looks fresh, typically recovers a meaningful share of the original send's clicks at zero incremental list cost. Sending it at a different hour than the original covers the "bad timing" failure mode too. We generally see the follow-up wave add 15–30% to campaign totals when the sequence above runs properly.

Two guardrails: follow-ups count against the monthly frequency cap, and each behavioral group gets one follow-up, not a drip. The play works because it's restrained — the moment it becomes a three-message chase sequence, block rates climb and the math flips.

Plan the festival calendar in advance

In India, the broadcast year is not evenly distributed. Raksha Bandhan, Ganesh Chaturthi, Navratri, Diwali, Christmas, and the wedding seasons around them concentrate both demand and message volume — which means concentrated opportunity and concentrated block risk. Your customer's inbox in Diwali week is a war zone; every jeweller, apparel brand and electronics store they've ever bought from is in it.

Plan a quarter ahead:

• Reserve the frequency budget. If Diwali week needs three touches, the two weeks prior need to be quiet. Contacts who received four promos in October will block the fifth in Diwali week — precisely when a block hurts most.
• Submit templates early. Template review is usually fast, but festival weeks see volume across the ecosystem. Get seasonal templates approved 2–3 weeks out, with a backup variant in case one is rejected.
• Sequence the season, don't blast it. A teaser to warm contacts, the main offer to warm plus cooling, a last-day reminder only to clickers and non-readers. Three coordinated waves outperform three identical blasts, and the last-day wave rides on the follow-up matrix you already run.
• Book the post-festival window. The two weeks after a major festival are underrated for win-back sends — attention is cheaper and dormant contacts are unusually responsive to "we missed you during the rush" framing.

The same logic scales down to regional calendars: Onam for a Kochi retailer, Pongal in Tamil Nadu, Durga Puja in the east. If your list is tagged by city or store — another payoff of source-tagged opt-ins — regional festival sends to the relevant slice routinely outperform the national calendar.

Putting it together

None of this requires a big team. It requires a system: permanent opt-in collection with consent records, segments rebuilt before every send, templates mapped to lifecycle stage, caps enforced in software, quality metrics reviewed after every campaign by a named owner, and one disciplined follow-up wave.

As a Meta Business Partner, InfiQ builds this system into the platform — opt-in records with consent trails, segment-aware broadcast audiences, frequency caps, quality-rating monitoring with automatic alerts, and the follow-up matrix as reusable automation. If you're running broadcasts today and any of the above sounded like manual work, see how promotional broadcasts work on InfiQ, or start a 7-day free trial and run your next campaign through it.