WhatsApp Drip Campaigns: The Opt-In Rules That Decide What You Can Send

WhatsApp drip campaigns sound simple — a sequence of messages over days that warms a lead toward a purchase — and they are simple, right up to the point where the rules arrive. On WhatsApp, a drip is not an email sequence with a different logo: every message after the first day lives under rules about consent, timing, and message type, and a sequence that ignores them does not just underperform, it risks the business's ability to message at all. This post explains the rules first and the sequence second, because on WhatsApp the rules are the strategy. And one thing to state plainly at the start: Neksio is not a bulk or broadcast tool, and this post does not promise a drip or bulk feature — it explains how compliant sequences work so a business can judge any tool, including its own manual process, against the rules.

Rule one: opt-in is the foundation, not a formality

A drip sequence may only go to people who agreed to receive messages from the business, for the kind of messages being sent. Opt-in is specific: a customer who agreed to order updates has not agreed to a marketing sequence, and a customer who gave a phone number at checkout has not agreed to anything unless the business asked. Collect opt-in in the open — a checkbox with plain wording, a message the customer sends to subscribe, a form that says what will arrive and how often — and keep a record of it, because the first complaint about an unwanted message will ask for that record. Sequences built on bought lists, scraped numbers, or “they bought once so they opted in” are not drip campaigns; they are the fastest route to blocks, reports, and a damaged quality rating.

Rule two: the 24-hour window shapes every step

Inside 24 hours of a customer's last message, the business can reply freely — this is where the conversational part of a drip lives: answers, follow-up questions, clarifications, the back-and-forth that moves a lead forward. Once 24 hours pass without a customer reply, the business may only send approved template messages, and only of the categories those templates allow. That single rule redesigns the drip: each step must either arrive inside the window, or be a template worth approving, and the most important design choice in any sequence is what happens when the customer goes quiet — the sequence does not chase, it waits for a template-appropriate moment or for the customer to return. A sequence that assumes it can message on day three, five, and seven regardless of replies is an email sequence wearing a WhatsApp costume, and it will break on day two.

What a compliant sequence actually looks like

A compliant drip is gated at every stage on the customer's response, and each stage earns the next one. An illustrative example: a language school's sequence starts when a prospect asks about courses — inside the window, the school answers and sends a level-test link. If the prospect completes it, the next message offers a trial class. If the prospect replies with a question, the sequence pauses and the conversation takes over. If the prospect goes quiet, the only further message is an approved template — a reminder about the trial, sent once, in the template's category — and then the sequence stops until the prospect returns. Notice what the sequence never does: it never sends the second step to someone who ignored the first, never re-sends to someone who declined, and never treats silence as permission to continue. The gate is the feature — it is what keeps the sequence welcome instead of spammy.

The quality rating is the enforcement

WhatsApp enforces these rules through the business's quality rating, which falls when customers block, report, or ignore messages, and rises when they engage. A falling rating throttles how many people the business can message, which means a bad drip does not just annoy customers — it shrinks the business's reach for every other message, including order updates customers want. This is why the metrics for a drip are different from email: a high open rate with a rising block rate is a failing sequence, not a successful one, and the number to watch alongside replies is blocks and reports. Any sequence whose blocks climb week over week should be paused and redesigned, not scaled — scaling a sequence customers report is how a business messages itself into silence.

Designing a sequence that survives the rules

• Start from an opt-in tied to the sequence itself, recorded and specific about what will arrive and how often.
• Make every step conditional on the previous step's response: no reply, no next step, except one approved template where the category allows it.
• Write each message as if it were the only one the customer reads, because for the customers who stop at that step, it is.
• Give every message an exit: a plain way to stop the sequence, honoured immediately, without a retention pitch.
• Watch blocks and reports as closely as replies, and pause any sequence whose blocks climb instead of scaling it.

Course provider: “Our first drip sent seven messages whether people replied or not. Blocks tripled in a month. The rebuilt sequence sends three, each one gated on a reply — fewer messages, more trial bookings, and our rating recovered.”