WhatsApp drip campaigns: what they are, and where they go wrong

A drip campaign is a sequence of messages sent automatically over days or weeks, triggered by something the contact did rather than by a date on a calendar. Somebody downloads a catalogue, and over the next fortnight they receive three messages spaced out and relevant to what they looked at. Nobody sends them manually.

The concept came from email. Moving it to WhatsApp changes it more than most businesses expect, and copying an email sequence across is the most common way to lose an audience.

What makes it a drip rather than a broadcast?

Three things.

It is triggered, not scheduled. A broadcast goes to everyone on Tuesday. A drip starts when a person does something — an enquiry arrives, a stage changes, a quotation is sent — so each contact experiences it relative to their own moment.

It has deliberate gaps. The delay between messages is the design, not a scheduling detail. Two days feels attentive. Two hours feels automated.

It branches. A contact marked as a serious enquiry should not receive the same sequence as one who is browsing. In practice this means routing on a field — lead stage, product interest, region — so the messages match the situation rather than the calendar.

Why do drips work at all?

Because most sales are lost to silence rather than to competitors.

An enquiry arrives, someone responds, and then nothing happens for a fortnight because the sales team is busy with orders that are already closing. By the time anyone follows up, the customer has bought elsewhere — not because the alternative was better, but because it was in front of them.

A drip removes the dependency on somebody remembering. It also removes the awkwardness: a salesperson often does not follow up because they have nothing new to say, whereas a sequence is designed in advance to have something to say each time.

How is WhatsApp different from email?

	Email drip	WhatsApp drip
Where it lands	An inbox already full of marketing	Beside messages from family
Cost per message	Effectively nothing	A real per-message charge
Message freedom	Write anything	Pre-approved templates outside the 24-hour window
Consequence of annoying someone	They ignore it	They block you, which harms your account
Sensible sequence length	Five to eight messages	Three to four, at most
Sensible gaps	Two to three days	Three to seven days

The fourth row is the one that matters. An email nobody wants gets deleted. A WhatsApp message nobody wants gets the sender blocked — and blocks lower your quality rating, which reduces how many people you may message at all. A badly judged drip can quietly shrink your reach across every campaign you run afterwards. We have written about that in what lowers your quality rating.

What does a sensible WhatsApp drip look like?

Short, branched, and with an obvious exit.

For a building materials enquiry, something like: an immediate acknowledgement with the specific thing they asked about, a few days later something genuinely useful — a catalogue, a quantity estimate, the nearest dealer — and after another week, one message asking whether they want to proceed. Then stop.

Branching is where it becomes worth building rather than doing by hand. A contact whose stage has been set to a serious enquiry gets a shorter, more direct sequence pointed at a conversation. One marked as early-stage gets slower, more informative messages. Same automation, different path, decided by a field your team already updates.

Buttons matter more here than in email. A message ending with a tappable “Send me the price list” or “Talk to someone” converts far better than one asking the person to type a reply, and it also tells the automation what to do next.

Where do WhatsApp drips actually fail?

No exit when someone replies. The most damaging failure by a distance. A customer answers message one and starts a real conversation with your team — and message two arrives on schedule two days later, ignoring everything that was said. It reads as though nobody was listening, because nobody was. Any reply must stop the sequence.

Too many messages. Sequences designed for email get carried across intact. Six messages in a fortnight is normal in an inbox and intolerable in a chat app.

Promotional content in a utility template. Templates are categorised, and one promotional line reclassifies the whole message. This gets templates rejected and, once approved, priced differently than expected. See why your template was rejected.

Running it on a list with no opt-in. Automation applies the same mistake to a thousand people at once. A manual follow-up to a bad list is a bad afternoon; an automated one is an account restriction.

Never reviewing it. A drip built once runs indefinitely. Businesses discover eighteen months later that step three references a product they discontinued.

What does this cost to run?

More than it used to, and the change is worth planning for.

Marketing templates have always carried a per-message charge. From 1 October 2026, messages sent inside the 24-hour customer service window also become chargeable — which affects any drip that continues after someone has replied. We have covered that in what changes on 1 October.

There is also a limit that money cannot solve. Meta caps how many marketing messages an individual receives across all businesses, adjusted to how much they engage. A four-message sequence to a disengaged list will not simply cost more — part of it will not be delivered.

Both point the same way: fewer, better-targeted messages outperform longer sequences, on cost and on results.

Running this on our platform

Our WhatsApp panel includes an automations builder for exactly this: workflows triggered by a field change in the CRM, routing into branches based on the value, template messages with personalised variables and buttons, and configurable delays between steps.

In practice that means your team continues to update a lead stage as they always have, and the follow-up sequence attached to each stage runs itself. Several separate flows can run against different fields or triggers.

If you want to talk through what a sequence should say before building one, tell us what you are trying to fix. The message design matters considerably more than the configuration.

Common questions

How many messages should a sequence have?

Three or four. If you cannot say something worth reading in four messages, the problem is the content rather than the length, and adding a fifth will not help.

Do we need consent for drip messages?

Yes. Automation does not change the requirement — it multiplies the consequence of not having it. See getting opt-in that holds up.

What happens if someone replies mid-sequence?

The sequence should stop and the conversation should go to a person. Any drip that continues after a reply will damage the relationship it was built to create — this is the single most important rule in the article.

Can we use a drip for dealers rather than end customers?

Yes, and it often works better — onboarding a new dealer, walking someone through a scheme, or a reminder sequence before a claim window closes. Transactional relevance is higher, and dealers are less likely to treat it as marketing.

How do we know whether it worked?

Replies and conversions, not delivery or read rates. A sequence with high read rates and no replies is being tolerated rather than working, and tolerance turns into blocks eventually.

More on this: sending fewer messages without reaching fewer people and connecting WhatsApp to your CRM. For how we build on the platform, see WhatsApp Business API.