A template is the email body. A sequence chains templates into a multi-step outreach flow, up to five steps, each with its own delay and send window. Templates render the words; sequences decide when they go out.
Templates and tokens
Templates are written with Liquid tokens. These are available everywhere a template renders:
| Token | Example |
|---|---|
{{contact.first_name}} | Jordan |
{{contact.name}} | Jordan Buyer |
{{contact.title}} | Procurement Officer |
{{contact.email}} | [email protected] |
{{agency.name}} | Utah Department of Technology Services |
{{opportunity.title}} | Contact center modernization, 200 seats |
{{opportunity.deadline}} | May 28, 2026 |
{{sequence.step}} | 1 |
How a sequence gets picked
When the pipeline auto-enrolls a new opportunity, it picks the first sequence whose agency type matches the opportunity's agency. If no exact match exists, the first sequence in the workspace is used as a fallback.
A single generic sequence therefore works fine. Teams that want type-specific routing create one sequence per agency type and let the matcher do the rest.
Snapshot on enrollment
When a contact is enrolled, the sequence's current state is snapshotted onto the enrollment. Later edits to templates or steps never change in-flight enrollments; they keep sending whatever was true at enrollment time. This is deliberate: content should not change under the recipient's nose mid-conversation.
Templates and sequences are immutable once created. To change one, create a new version and let the old one age out; the list shows when each was last used.
Send windows and jitter
Each step has a UTC send window, by default 14:00 to 22:00 UTC, which is 8 AM to 4 PM Eastern, plus an optional jitter in minutes. The send run fires every 2 hours; when a due step's window is open, it sends after a random delay of up to the jitter, so your outreach never lands in mechanical bursts.
Steps and delays
Step 1 fires immediately on enrollment. Each later step waits its configured number of days after the previous step was sent. After the final step sends, the enrollment is complete. A reply at any point stops the sequence for that contact; see Bounces, replies, and unsubscribes.