Home/Help Center/Sequences

Automation

Set Up Drip Sequences and Enrolment

Build a multi-step WhatsApp follow-up sequence, enroll leads by stage or source, and read the Enrollments view to see who is stuck at which step.

By Chirag Darji · Updated 16 Oct 2026 · 7 min read

On this page
  1. Before you start
  2. Steps
  3. What you will see
  4. Settings and options
  5. Troubleshooting
  6. Related reading
Sequences list in VGraple CRM with two multi-step follow-ups, their steps and how many contacts are enrolled

A drip sequence sends a lead or contact a series of pre-written WhatsApp messages spaced out over time, without anyone on your team clicking send for each one. This walkthrough covers building a sequence step by step, enrolling contacts into it, and reading the Enrollments view once it is running.

Sequences: first 5 of 6 steps

  1. 1Open Sequences and start a new one
  2. 2Add your first step
  3. 3Add a delay before the next step
  4. 4Repeat for as many steps as the
  5. 5Enroll leads
The steps on this page, in order.

Before you start

  • Sequences are available on every plan, including Free, with no separate cap on how many you can build. Conversations are unlimited on every plan, so no enrollment is paused by conversation volume; what a plan sets is agent seats and how many contacts you can store.
  • Any step scheduled to send more than 24 hours after the last customer message should be a template step, since only an approved template can reach someone outside WhatsApp's 24-hour service window.
  • To enroll leads automatically rather than manually, build a flow with the New lead arrives trigger and an Enroll in sequence step. Create the sequence first; the step picks an existing one.
  • Sequences send over WhatsApp, so a sequence built for leads captured from a website chat widget, Calendly, or a Meta DM depends on that lead having, or later gaining, a usable phone number.

Steps

  1. Open Sequences and start a new one. In the sidebar, open Automation, then Sequences, and click New Sequence. Give it a name describing its purpose, such as "New enquiry nurture" rather than a date.

Booking bot in the Flow Builder canvas: a trigger, a greeting, quick replies that lead to a booking message, an AI answer or a human handoff

  1. Add your first step. Choose Text for a free-form message you write directly, or Template for a Meta-approved template with its language and variable mapping. The first step typically has no delay, since it is meant to send as soon as someone enrolls.
  2. Add a delay before the next step. Every step after the first has a wait duration in hours or days, shown as a "Wait" chip between steps on the timeline so the full schedule is visible at a glance. The default wait is 24 hours.
  3. Repeat for as many steps as the sequence needs. A typical nurture sequence runs 3 to 5 steps across a week to ten days; there is no fixed limit on how many steps a sequence can have.
  4. Enroll leads. Once the sequence is active (click Activate on its card), click Enroll leads on the card and choose a pipeline stage or a lead source to add everyone currently matching in one action, or leave enrollment to a flow with an Enroll in sequence step, started by the New lead arrives trigger, so every new matching lead enrolls automatically going forward.
  5. Watch it run. Click the "N enrolled" count on the sequence's card to open the Enrollments view and see every contact who has ever run the sequence, their status, and how many steps have actually reached them.

A coaching institute running a 5-step enquiry nurture, for example, might send an instant welcome text on step one, a testimonial template two days later, a course brochure on day five, and a call-to-book template on day nine. Each step is edited independently, so tightening the wording on step three never touches the timing or content of any other step.

What you will see

Once enrolled, a contact is resolved to a WhatsApp conversation (a new one is created if none is open) and the step chain begins running with its delays, exactly like any other flow execution. The Enrollments view shows each contact's progress as "N of M steps," calculated from the actual tagged messages sent to them rather than their raw position in the underlying node graph, so a contact stuck at "1 of 4" tells you step two is worth reviewing. A contact who sends STOP mid-sequence, at any step, never receives the remaining messages; their enrollment is marked cancelled.

Behind the scenes, every sequence is stored as a real flow: a trigger node, alternating Delay and Send Message or Send Template nodes, and an End node, built automatically when you save the sequence editor's simpler step list. This is why a sequence gets every protection Flow Builder gives any other flow, the 24-hour window guard and the per-node opt-out check included, without you having to configure either one yourself.

Settings and options

Setting or fieldWhat it doesDefault
Step typeText (free-form) or Template (Meta-approved)Text
Wait before stepDelay in hours or days before this step fires, shown after the first step24 hours
Enroll leadsManually enrolls every lead currently at a chosen pipeline stage or from a chosen sourceManual action
Enroll in sequence flow stepEnrolls the flow's lead the moment the step runs, for example in a flow started by New lead arrivesOff unless a flow uses this sequence
Enrollment statusRunning, completed, cancelled, or pending (waiting for a resolvable WhatsApp contact)Running on successful enrollment
STOP handlingChecked before every step, not only at enrollment; cancels the run immediately on matchAlways on, not configurable
Duplicate sequenceCopies every step and delay into a new draft you can retarget or editThe copy button (Duplicate sequence) on the sequence's card

Troubleshooting

SymptomLikely causeFix
A contact's enrollment sits at "pending" indefinitelyThe lead has no phone number, so there is no WhatsApp contact to send toAdd the phone number to the lead, or wait: it resolves once that person messages your connected WhatsApp number
A step scheduled for day 3 never sentIt was a text step and the 24-hour service window had closed by the time the delay elapsedSwitch that step to a template step, since only an approved template reaches a contact outside the window
A contact keeps receiving steps after replying to ask a questionThis is expected; a reply does not cancel a sequence, only STOP doesAdd a Human Handoff or Resolve Conversation step if you want replies to end automation, or move the contact out of the sequence's enrollment trigger manually
Enrolling by pipeline stage enrolled fewer contacts than expectedSome leads at that stage have no phone number and their enrollment deferred to pending instead of failing outrightCheck the Enrollments view for pending rows; they will resolve once those leads gain a usable WhatsApp contact
A duplicate sequence sent messages before you finished editing itThe duplicate copied the original's active status along with its stepsConfirm a duplicated sequence is in draft, or has no flow step or manual enrollment targeting it, before you finish editing
The same phone number without a country code created a second contactThis should not happen; enrollment tries a suffix match against existing contacts before creating a new one, but a very short or malformed number can fail that matchConfirm the lead's phone field holds a real, complete number; numbers under 7 digits are not eligible for the suffix match

Start a sequence from a flow with the New lead arrives trigger and an Enroll in sequence step so new leads enroll the moment they arrive, or use Flow Builder directly if a follow-up needs to branch on the contact's answer rather than run a fixed, linear script.

Frequently asked questions

What is a WhatsApp drip sequence?
A sequence is a set of WhatsApp messages sent to a contact over time, each one separated by a delay you set from minutes to days. VGraple CRM builds each sequence internally as a chain of Delay and Send Message or Send Template steps, the same engine that runs Flow Builder.
How do I enroll leads into a sequence?
Click Enroll leads on an active sequence's card and choose to enroll everyone currently at a pipeline stage or from a specific lead source, or add an Enroll in sequence step to a flow, for example one started by the New lead arrives trigger, so new matching leads enroll the moment they arrive with no manual step.
Does a sequence stop if the contact replies?
No, not by itself. A reply is a different signal from an opt-out, so a sequence keeps sending its remaining steps on schedule even after the contact answers. Only STOP and its variants, or the contact being blocked, cancel a running sequence.
What happens if a lead has no WhatsApp contact yet?
A lead with a phone number gets a WhatsApp contact created at once and the sequence starts. A lead with no phone number is marked pending; the moment that person messages your connected WhatsApp number, enrollment resumes automatically and the sequence starts from its first step.
Can a sequence mix free text and approved templates?
Yes. Each step is either a text step or a template step. A text step is checked against the 24-hour service window before it sends and is skipped with a logged reason if the window has closed; a template step is unaffected, since a template is exactly what Meta requires outside the window.
How does VGraple CRM handle a phone number typed without the country code?
Enrollment tries an exact match on the normalized WhatsApp ID first, then a suffix match against existing contacts, so a lead's phone stored as "9876543210" still resolves to an existing contact stored as "919876543210" instead of creating a duplicate.
Can I see who is enrolled and how far along they are?
Yes. The Enrollments view lists every contact ever enrolled with their status (running, completed or cancelled), when they started, and how many of the sequence's steps have actually been sent to them, calculated from the real tagged messages rather than just their node position.

Run your WhatsApp on VGraple CRM

Free forever plan, official Meta WhatsApp Business API, set up in 15 minutes. No card needed.