Steps & sequences

A campaign's steps are the actual emails in the sequence — step 1 sends first, then each following step sends after its own wait period, as long as the contact hasn't replied.

Adding steps

From the campaign detail page, click Add step and set:

  • Subject (step 1 only — see below)
  • Body — the message content
  • Wait days — how long after the previous step to send this one
Campaign step editor with subject, body, and wait days fields
Adding a step to a campaign

Why only step 1 has a subject

Steps after the first are follow-ups in the same email thread, not separate emails — that's what makes threading work. Every step beyond step 1 automatically reuses step 1's subject with a Re: prefix, so the subject field only appears on step 1; it wouldn't do anything on later steps.

HTML source

The step body editor accepts raw HTML source directly — useful if you're pasting in a formatted signature or already have HTML from another tool, rather than being limited to a plain rich-text box.

Merge tags

Personalize any step with merge tags pulled from the contact being sent to:

Hi {{name}},

Noticed {{company|your team}} might be a fit for...

Supported tags: {{name}}, {{email}}, {{company}}, and any custom field you've defined, by its key. Add a fallback with a pipe — {{company|your team}} — to render that text instead when a contact has no value for that field, rather than leaving a blank.

Preview before sending

From a step, click Preview and pick a real enrolled contact to see exactly what they'd receive — subject and body fully rendered with that contact's actual data, not a generic mockup.

Campaign step preview showing rendered subject and unresolved merge tag warning for a contact
Previewing a step for a real contact

The preview flags two things worth catching before you activate a campaign:

  • Unresolved merge tags — a {{tag}} with no matching field and no fallback, which would otherwise render as an empty gap
  • Spam warnings — content patterns that commonly trigger spam filters