How to build a WhatsApp drip sequence with Wait steps days apart

Updated 2026-09-19 · 5 min read · By the Convo360 team

Prerequisites and what makes a drip sequence different

Have your WhatsApp number connected and at least one approved template ready for any drip message likely to land outside the 24-hour window (see our template approval guide). Decide your entry point in advance: a keyword, a form submission, or a group-join event trigger, since that decides how contacts actually enter the sequence.

A normal flow responds immediately, message by message, as the customer replies. A drip sequence deliberately spaces messages out over time, with a day-3 check-in, a day-7 offer or a day-14 reminder, even if the customer never replies in between. This is the pattern behind onboarding nurtures, abandoned-cart follow-ups, and post-purchase check-ins.

The key design shift is thinking in calendar time rather than conversation turns. A normal flow assumes the next message happens the moment the customer responds. A drip sequence assumes the opposite: that most contacts won't respond at all, and the automation needs to keep working anyway, quietly, in the background, until either a reply arrives or the sequence naturally ends.

The Wait / Delay block: seconds vs longer units

The Wait / Delay block has two distinct uses:

• Seconds: a short pause that mimics natural typing, used inside a normal live conversation so replies don't feel instant and robotic.
• Minutes, hours or days: a real drip delay. This is persisted on the server, meaning the wait continues running in the background for up to 30 days, independent of whether the customer or your team has the chat open.

For a drip sequence, always use the minutes/hours/days mode.

Building it on Convo360: a simple 3-message drip

On Convo360, a drip sequence is built entirely in the Flow Builder using ordinary blocks, no separate 'automation' tool required:

1. Choose an entry trigger, commonly a keyword (e.g. 'interested'), a form submission, or a group-join event trigger (see our group trigger guide).
2. Send the first message immediately with a Send Message block.
3. Add a Wait / Delay block set to, say, 2 days.
4. Before the next message, add a Condition block checking 'has the contact replied since the last message?'. If yes, branch to a live-conversation path instead of continuing the script.
5. If no reply, send the second drip message with a Send Template block if more than 24 hours have passed since their last reply.
6. Repeat the wait-check-send pattern for further steps, e.g. day 7, day 14, then Publish the flow.

A worked example: a coaching institute's admission drip

An institute in Lucknow tags every website enquiry into a 'Prospective Student' group, which triggers a drip: day 0 sends a welcome message with the course brochure link, day 2 sends an approved template highlighting a placement statistic-free testimonial from the syllabus page, and day 5 sends a template nudging them to book a counselling call. At each step, a Condition checks whether the student replied — about a third do, at which point the flow branches into a live handoff to the admissions counsellor instead of continuing the scripted messages, so nobody who's already engaged gets an irrelevant scripted nudge.

Respecting the 24-hour window inside a drip

WhatsApp's 24-hour customer-service window resets each time the customer replies. In a drip sequence, the customer often hasn't replied in days, so by the time your day-3 or day-7 message is due, you're outside that window. That means it must be sent as an approved template, not a free-form message. Design your drip content as templates from the start rather than discovering the block fails at send time.

A practical habit: submit every planned drip message for template approval before you start building the flow itself, not after. That way you're never stuck redesigning a sequence around a rejected template mid-build, and you can adjust wording during the approval wait rather than after the whole flow is already wired together.

Troubleshooting common issues

Why CSV imports don't trigger a group-based drip, and what to test

If your drip's entry point is a group-join event trigger, note that adding contacts through a CSV import does not fire that trigger. The event only fires for group additions that happen through live actions in Convo360, like an Add to Group block or a manual add from Contacts → Groups, not bulk imports. If you're migrating an existing list into a drip, use the Add to Group block in a short onboarding flow instead of relying on the import itself to start the sequence. Before going live, test the whole sequence by adding a test contact to the group manually, replying mid-sequence to confirm the branch works, and checking that a message scheduled past 24 hours actually renders as a template.

Step by step

1. Choose an entry triggerUse a keyword, form submission, or group-join event trigger to start the sequence.
2. Send the first messageDeliver an immediate welcome or acknowledgement message.
3. Add a Wait / Delay blockSet it to days (not seconds) for the gap before the next drip message.
4. Check for repliesAdd a Condition block to see if the contact replied since the last message.
5. Branch on the reply checkIf they replied, route to a live conversation path; if not, continue the drip.
6. Send the next drip message as a templateUse an approved WhatsApp template since you're likely outside the 24-hour window.
7. Repeat for further stepsAdd more Wait / Condition / Send pairs for day 7, day 14 and beyond, up to 30 days.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.