Write it once. Send it consistently.
Reusable email templates with merge fields keep your wording consistent, and multi-step drip sequences carry the follow-up so nothing falls through.
Templates are reusable subject/body pairs with merge fields — {{contact.first_name}}, {{contact.company}}, {{sender.name}} — so a follow-up reads as personal without being retyped every time. Drip sequences take that further: a named sequence of steps, each with its own delay, that runs against an enrolled contact automatically. A step can send an email, create a follow-up task, or log a call — not just email — and a background worker checks every 20 seconds for enrollments that are due, advances them one step, and schedules the next one based on that step's delay_days. Enroll a contact once and the sequence carries itself forward.
Templates with merge fields
A template is a name, subject, and body saved once and reused from the composer or a campaign. Merge fields like {{contact.first_name}} and {{contact.company}} get filled in per recipient, so one template produces a personalized email for every contact it's used on.
- Merge on contact fields (first name, company, display name) and sender identity
- Organize templates with an optional category badge
- Delete a template you no longer use without touching past sends
Drips are multi-step, multi-channel sequences
A drip sequence is an ordered list of steps, each with a delay_days offset and a channel — email, task, or call. That means a sequence can mix an automatic email on day 0, a rep task on day 3, and a logged call reminder on day 7, all from one definition.
- Each step sets its own delay from the previous step, not just from enrollment
- email steps send through the same Mailjet connector as campaigns
- task steps create a real Task; call steps log a CrmActivity — both visible on the contact
Enroll a contact, and the sequence runs itself
Enrolling a contact creates a DripEnrollment that tracks which step it's on and when the next one is due. A background worker polls for due enrollments, applies the current step, advances the pointer, and — if there's a step left — schedules the next run for that step's delay from now.
- A sequence must be active for its enrollments to advance
- An enrollment completes automatically once the last step runs
- View every enrollment on a sequence — contact, current step, and status — at a glance
One record of what a contact received
Every email a drip step sends is logged as a tracked EmailMessage on the contact's timeline, right alongside campaign sends and one-off emails — so there's a single history to check before you reach out manually.
- A 4-touch new-lead nurture: welcome email, 3-day check-in task, 7-day follow-up email
- A standard onboarding sequence enrolled the moment a deal closes
- A consistent re-engagement template used across every campaign send
Templates & drips — common questions
A template is a single, reusable email — subject and body with merge fields — used one send at a time. A drip is a whole sequence of timed steps, enrolled once per contact, that runs on its own.
Yes — a step's channel can be email, task, or call, so a sequence can create a follow-up task or log a call reminder alongside (or instead of) an automatic email.
A background worker checks for due enrollments roughly every 20 seconds, so a step runs close to its scheduled delay, not on a slow nightly batch.
Contact fields like {{contact.first_name}} and {{contact.company}}, plus sender fields like {{sender.name}} — filled in per recipient at send time.
Yes — marking a sequence inactive stops its enrollments from advancing without losing the sequence definition or history.