A sequence is a named list of ordered steps, each pairing a WhatsApp template with a delay, sending to a contact over time instead of all at once. Enroll a contact manually, from a segment, or by CSV, and an hourly sweep advances each enrollment when its next step comes due, pausing on a reply and stopping on opt-out.
Create a sequence and add steps in order: each step is a WhatsApp template plus how long to wait after the previous step before sending it (for example, send step 1 immediately, then wait 24 hours before step 2). Enroll contacts into the sequence manually, from a segment, or by uploading a CSV with column mapping. From there, an hourly sweep checks every enrollment and sends whichever step is due, then schedules the next one.
A reply from the contact pauses the sequence: the enrollment stops advancing until you resume it manually. A contact who never replies keeps moving through the remaining steps on schedule. This means a sequence never talks over a contact who's already engaging in conversation.
An opt-out exits the enrollment entirely, and it does not resume. If a contact's marketing consent is revoked partway through a sequence, the next step is blocked by the same consent check that governs every other outbound message on the platform, not a separate rule specific to sequences. Consent is always the last word on whether a message goes out.
Yes. A frequency cap applies per contact across your campaigns and sequences together, so someone enrolled in several sequences at once can't be messaged more than your configured ceiling in a given window. When a step is skipped for hitting that cap, the skip is counted and shown, never a silent drop.
Retargeting lets you re-send to a slice of contacts from a campaign that already finished, based on how they responded:
| Slice | Contacts included |
|---|---|
| Delivered, not read | Message delivered but never opened |
| Read, not replied | Opened but no reply |
| Replied | Contact sent a reply |
This is a separate action from a sequence: you pick a finished campaign, choose a slice, and it goes out as its own send, still subject to consent and your frequency cap.
Yes. A broadcast campaign can be scheduled for a future date and time instead of sending immediately; it fires automatically once that time arrives, using the same hourly sweep that drives sequence steps. This is separate from enrolling contacts in a multi-step sequence, it's a single send at a set time.
Sequences live under Campaigns, alongside Broadcasts and Recovery, so you can compare one-off broadcasts and abandoned-cart recovery sends in the same place. The enrollments table on each sequence shows every contact's status: active, paused, or exited.
Note that in the current version, sequence steps send the template as-is without per-step personalized variables (personalized variables are available on one-off broadcasts today). Your plan also caps how many sequences you can run and how many contacts you can have enrolled at once; see current plans for details.