← All docs

Sequences

Multi-touch cadences with auto-pause on reply, sending windows, conditions, and per-step stats.

Sequences at <yourcompany>.satua.io/sequences are multi-touch email cadences — a series of emails sent to a lead over days, with conditions on each step (skip if they replied, skip if they opened, etc.). They're how you turn a one-shot pitch into a follow-up rhythm without manually scheduling every email.

Sequences are available on Growth and higher plans. If you're on the Launch plan and want sequences, contact your account manager about upgrading. Reply detection (the auto-pause feature below) needs to be enabled for your account — your account manager turns it on once when you're set up.


What a sequence is

A sequence is a named template of email steps:

  • Step 1 fires immediately when a lead is enrolled.
  • Step 2 fires after wait_days + wait_hours from step 1, IF its condition is met.
  • Step 3 fires after its own wait, IF its condition is met.
  • ...up to 10 steps.

Each step has:

FieldNotes
SubjectPlain text. Supports {{first_name}}, {{last_name}}, {{email}} merge tags
BodyPlain text. Same merge tags. Rendered to HTML on send
Wait days / hoursHow long to wait after the previous step before this one fires
ConditionWhen to evaluate the wait timer expires

Conditions:

  • always — send no matter what. Use for the first step.
  • no_reply — send only if the lead hasn't replied yet. Most common follow-up pattern.
  • no_open — send only if the lead hasn't opened any prior step. "Hey, did you see my last email?"
  • no_click — send only if the lead hasn't clicked any link in a prior step. Useful when step 1 had a clear CTA.

Auto-stop: when a lead replies, bounces, or unsubscribes, their enrollment is marked replied / bounced / unsubscribed and no further steps fire. This is non-negotiable — you can't accidentally keep emailing someone who said no.


Creating a sequence

From /sequences click + New sequence. The dialog asks for:

  1. Name — internal label. "3-touch intro for VPs of RevOps" is more useful than "Sequence 1."
  2. Description — optional team note.
  3. Steps — at least one. Add up to 10. Each step gets a subject + body + (for steps 2+) a wait + condition.

Hit Create as draft. The sequence is saved but not active — leads enrolled won't get anything until you switch it to active.


Editing steps after creation

Click any sequence row in the list to open the detail page (/sequences/{id}). The Steps tab is a full editor:

  • Drag the up/down arrows to reorder.
  • Edit subject, body, wait, condition inline.
  • Save replaces the entire step set atomically — old enrollments mid-flight will continue with their current step number, but step content updates affect the next send.

The Enrollments tab lists every lead enrolled in this sequence with their current step, status (active/paused/replied/bounced/etc.), and next send time. Pause and resume individual enrollments from here.

The Per-step stats tab shows sends, opens, clicks, and skipped counts per step so you can see which step is dropping people off.


Activating and pausing

  • Draft — created but won't send. Leads can still be enrolled; they'll start sending the moment you activate.
  • Active — Satua picks up enrollments every few minutes and fires steps on their schedule.
  • Paused — Satua skips this sequence. Existing enrollments wait; new enrollments queue up until you resume.
  • Archived — terminal state. Existing active enrollments continue running, but no new leads can be added.

Toggle from the detail header (Activate / Pause buttons) or the list page (play/pause icons).


Enrolling leads

Today, enrollment happens through your account manager or via direct API integration. The dashboard "enroll multiple leads" UI is on the roadmap. A lead can only be enrolled once in the same sequence — duplicates are silently ignored.


Sending windows

Each sequence respects a sending window so cold emails don't hit prospects' inboxes at 3am:

  • Weekdays only by default (Monday–Friday).
  • 9am–5pm by default in the sequence's configured timezone.

If a step would be due outside that window, Satua pushes it to the next valid send time. Your account manager can adjust the window per-sequence on request.


What happens on a reply

When a prospect replies, Satua matches the reply back to the right lead, classifies it (positive, negative, neutral, out-of-office, unsubscribe, bounce, or auto-reply), and:

  1. Marks the lead's enrollment as Replied (or Bounced / Unsubscribed) so no more steps fire.
  2. Logs the reply on the lead's timeline.
  3. Notifies the lead's owner with a bell-icon notification.

Out-of-office replies are classified separately and don't auto-pause the sequence — a vacation auto-reply shouldn't kill an outreach cadence.


How sequences count against your plan

Every step that successfully sends counts as one email against your monthly email allowance. Once the allowance is exhausted, overage draws from your Satua Credits balance at the per-email rate shown on My Plan. When credits run out, sequence sends pause and resume automatically once you top up.

If your account billing is on hold, sequences pause across the board and resume automatically once billing is back in good standing.


Common gotchas

  • Edit-while-active is allowed but tricky. If a lead is on step 2 when you change step 3's body, they'll receive the new step 3 — that might or might not be what you want. Pause first if you want a clean cutover.
  • No A/B testing yet. If you want to test two subject lines, run two sequences and split your leads between them.
  • Reply detection needs to be enabled. Your account manager turns this on once during setup; without it, replies don't auto-pause and the cadence runs to completion regardless.
  • Sending windows are currently UTC. The "weekdays + 9-5" check uses UTC, not your local timezone. If your team operates outside UTC, sends may land slightly off-window. Full timezone support is on the roadmap.
  • Merge tags with no value render empty. If a lead has no first name, Hi {{first_name}}, becomes Hi , — fix at the lead-data level by adding the missing field.