Onboarding Sequences
Multi-step welcome flows that fire automatically when a host is hired — with a run history showing what each one actually did.
Onboarding sequences are automated, multi-step message flows that run when a new host joins — so every hire gets a consistent welcome.
Defining a sequence #
A sequence is an ordered list of steps. Each step has:
- a channel (WhatsApp and/or email),
- a delay in hours after the previous step,
- a reference to a reusable message template.
If your agency has no messaging channel connected yet, the sequence editor says so outright — a sequence with nothing to send through will record every step as skipped. Connect WhatsApp or email in Agency Settings first.
How it fires #
When an application is accepted and creates a brand-new contact, the sequence dispatches automatically. Steps send in order, spaced by their delays.
Run history #
Open a sequence and you get a Run history tab. Every dispatch is logged: when it ran, what triggered it, how many steps were evaluated, and how many succeeded, were skipped, or failed. The list column on the sequences page shows the last run at a glance.
Open a run and you see it step by step — which step, what happened, and why, in plain words. A step that could not send is recorded as Skipped with its reason rather than disappearing:
| Reason | Meaning |
|---|---|
| No messaging channel connected | The agency has neither WhatsApp nor email set up. |
| Step has no message template | The step points at nothing to send. |
| Host has no email address | An email step for a host you have no address for. |
| Host has no phone number | A WhatsApp step for a host you have no number for. |
That is the point of the log: "the host never got the welcome message" now has an answer on the screen instead of requiring a support ticket.
Two things worth knowing about how the numbers read:
- One run is recorded per host being onboarded, and its counts are that host's steps — not a count of hosts. A sequence that welcomed ten hires has ten runs.
- If you work in a sub-agency scope, host names outside your access are withheld from the per-step list while the totals stay agency-wide, and the page tells you how many were held back.
Runs are kept for about 90 days.
Channel skipping #
If a step targets a channel the contact doesn't have (for example, an email step for a host with no email address), that step is skipped — the rest of the sequence still runs, and the skip is recorded in the run history with its reason.