Sequences

Outreach that knows when to stop.

Multi-step email sent from your own mailbox, to recipients drawn from your book rather than from a spreadsheet. A reply, a booked meeting or an unsubscribe takes that person out, without anyone watching the inbox.

Sequences examples

Draft it, release it, enrol into it. A sequence ships the way the rest of your configuration ships, and anyone already moving through it keeps the version they started on.

[01]

Steps and waits.

Order the emails and set the days between them. Write each one inline, or pull a saved template into the step.

[02]

Nothing sends off a draft.

The working copy is yours to edit all week. A sequence only enrols and sends once the release holding it is live.

[03]

Recipients are records.

Point the sequence at a view of people and enrol up to a thousand at once, or let a workflow enrol them one at a time.

[04]

Pinned at enrolment.

Each enrolment locks the version it started on, delivery settings included. New copy reaches new recipients only.

“We used to keep a spreadsheet of who had been chased and when. Now the sequence keeps it, and it stops the moment someone writes back.”
Head of distributionRegional wholesaler · 12 states

Three campaigns worth running. One engine behind producer follow-up, renewal outreach, and the long chase for the document that never arrives.

Producer follow-up.

A submission lands, the underwriter has questions, and the producer goes quiet. Three emails across a week from the underwriter's own address, ending the moment a reply comes back.

Sent the way a person would send it. From your own mailbox, inside the hours you set, under the limits your provider allows.

Your own mailbox

Connect Gmail or Microsoft once. The message comes from a real address and the reply lands in your inbox.

Sending windows

Set the hours and the timezone. With weekdays only, a delay landing on a Saturday waits for Monday.

Mailbox rate limits

Daily and per-minute caps on every connected mailbox, so a thousand enrolments never overrun your provider.

Variables that resolve

Insert a field from the recipient's record with a fallback, or generate the line from a prompt at send time.

Delegated sending

Send on a colleague's behalf once they accept the invite. Switching it off does not need a new version.

One unsubscribe link

Choose the wording once and it renders at the foot of every email in the sequence.

One recipient, start to finish. Follow a single person through the campaign and you can see every send before it happens, and every reason it might end.

Enrolled.

The moment a record joins, every step is scheduled with its own send time. Nothing waits on someone remembering to hit send.

In flight.

Each email is queued, sent, and written to the recipient's timeline. Pause a person and they hold their place; resume and they pick up on the same step.

Exited.

A reply, a meeting booked on your calendar, an unsubscribe or a bounce ends it. The reason is recorded against the enrolment and anything still queued is cancelled.

See a sequence run on your own book.

Bring the follow-up list you keep in your inbox. We will build it as a sequence and show you exactly what stops it.

Usually 30 minutes, with an underwriter on the call.