Skip to main content
Build a sequence once and every person you add gets the same steps at the right time, in their own timezone. You only step in when a call, an email you send yourself or a to-do comes due. This page walks through it in order: create, add steps, set timing, write templates, choose what a reply does, then turn it on. The Sequencer is in early access, on Enterprise, Enterprise+ and Admin seats for teams in the early access program. Time: about 10 minutes. Before you start: connect a mailbox if your sequence will send email.

​
Build it step by step

1

Create the sequence

On Sequencer › Sequences, click New sequence. Or open a sequence you like and click Duplicate to start from its steps and settings. A new sequence starts turned off. It can hold up to 50 steps.
2

Choose the timing

Pick Days after the previous step (most sequences) or On specific dates. You cannot change this once the sequence has steps. See Timing.
3

Add steps

Click Add step (or press N) and pick a type. Set the wait before each step. See Step types.
4

Write your emails

For each email step, write one or more templates with merge fields such as {{first_name}}. See Templates and merge fields. For what to write, start from the cold email frameworks.
5

Choose what a reply does

In Settings, When they reply is set to Stop the sequence by default. See Reply actions.
6

Turn it on

Click the toggle to enable the sequence, then add people.
You’re done when: the sequence shows as on, with every step in place and no warning in the banner above the steps.

​
Step types

Call and to-do steps carry a note for the rep (What to do) and a priority: high, medium or low. Medium is the default. Priority sets the order in Tasks.
A sequence needs at least one step before you can turn it on or add people. If it has an email step, it also needs a mailbox that can send. See Connect a mailbox.

​
Timing

You choose the timing when you create the sequence:
  • Days after the previous step (the default). Each step waits a set time after the previous step finished, that is after the email was sent or the task was done. The first step waits from the moment the person is enrolled.
  • On specific dates. Each step has a calendar date. Use it when everyone should get the same email on the same day, such as an event invite.
Whatever the wait says, a step never runs outside the sending window. A step due at 2 AM in the prospect’s timezone moves to the next open hour.

​
Sending window

The sending window is the days and hours steps may run. Out of the box it is Monday to Friday, 8 AM to 5 PM. Change the team default under Settings › Sequencer settings › Default sending window. To give one sequence its own window, turn on Only send on certain days and hours in its settings. Once a sequence has its own window, you can edit it but not remove it.

​
Tasks nobody gets to

A call or to-do step can carry Skip if not done within (days). If the task is still open that many days after it came due, it expires and the person moves on. One busy week does not stall a whole group of prospects. Snoozing a task moves this deadline by the same amount.

​
Templates and merge fields

Email steps send templates. A step can hold up to 10 templates, each with a weight. Salesfinity picks one at random for each person, in line with the weights. That gives you an A/B test without a second sequence.
  • Weights are relative. Templates weighted 1 and 3 send the second one three times as often.
  • A weight of 0 takes a template out of rotation without deleting it.
  • Sends, opens, clicks, replies, bounces and opt-outs are counted per template and per step.
Merge fields go in double curly braces and fill in from the contact when the email sends: A field with no value comes out empty, and the send records which fields were missing. A field Salesfinity does not recognize, such as a typo, is sent exactly as written. Use Preview as a sample contact in the email editor to see a template filled in before anyone gets it.
Always preview. A typo such as {{frist_name}} is sent to the prospect as typed.

​
Threads

By default, every email step after the first one sends as a reply to the previous email (“Re:”), so the prospect sees one conversation. That step’s own subject is not used. Turn on Start a new email thread on a step to send a fresh email with its own subject. The first email always starts a thread.

​
Reply actions

When they reply decides what a reply does to that person’s sequence: This applies to replies read as interested, meeting requests, and replies that could not be read. Out of office, not interested, wrong person, unsubscribe and automatic replies are handled the same way whatever you pick. See Replies and auto-send. Your team’s rules of engagement run on top.
The settings also show When someone else replies. It has no effect yet. Every reply, from the prospect or a colleague on the thread, follows When they reply.
Track opens and Track link clicks are on for every new sequence. Turn either off for a sequence that should send plain, untracked email. A custom tracking domain is set per mailbox. Every sequence email ends with an unsubscribe link. Set its text under Settings › Sequencer settings › Unsubscribe footer.
Skip the unsubscribe footer removes the link. It also lets the sequence reach people on the do-not-contact list who unsubscribed or were added by hand. Addresses that bounced, complained or are marked do not contact are still never emailed. Use it only for email a person is entitled to get no matter what, such as a service notice.

​
Limit how fast people are added

These limits count per owner, that is per rep the enrollments belong to:
  • Max people added per day: how many new people one owner can add to the sequence in a day, counted from midnight in the sequence’s timezone.
  • Max people in the sequence at once: how many people one owner can have waiting, active or paused in the sequence.
  • Pause adding people: refuses everyone new until you turn it off, without turning the sequence off.
People over a limit are refused with Sequence at capacity or Daily add limit reached and show on the Not enrolled tab. The limits never touch people already in the sequence.

​
Turn on, turn off, archive, delete

Starts the sequence and moves everyone waiting in it to active. It is refused when the sequence has no steps, has an email step but no mailbox that can send, is archived, or has a sending window that never opens. The message says which.
Pauses every active person with the reason sequence disabled, holds their open tasks, and takes their call tasks off the dial list. Turning it back on resumes exactly those people. Someone a rep paused by hand stays paused.
Copies the steps and settings into a new sequence named “(Copy)”, turned off, with no people, owned by you.
Archive turns the sequence off and hides it from the list. Its steps, people and history stay. Restore brings it back, turned off.
Permanent. Refused while anyone in the sequence is waiting, active or paused. Finish them first, or archive instead.
You cannot delete or reorder steps while anyone in the sequence is active or paused, and that includes people paused by turning the sequence off. Adding a step at the end, or editing a step in place, always works. To restructure a live sequence, duplicate it, edit the copy, and move people across with bulk move.

​
See results

The Results tab shows delivered, opened, clicked, replied, bounced, opted out, failed and scheduled counts, how many people were contacted and replied, and how many are in each state. Click a number to see the people behind it. The counts refresh every 15 minutes, so they can trail the timeline a little. The Not enrolled tab lists everyone who was refused, and why.
Step types over the API are auto_email (Email), manual_email (Email (you send it)), call and task (To-do). Timing is interval (with interval_seconds) or date. The reply action is primary_reply_action (finish, pause or continue) with primary_reply_pause_duration in seconds. Limits are throttle_max_adds_per_day, throttle_capacity and throttle_paused; skipping the footer is transactional; the task deadline is task_autoskip_delay in seconds. See the Sequencer API quickstart.

​
Next steps

Enroll people

Add people from your CRM, a dial list or a CSV.

Work your tasks

Calls, emails and to-dos, in one list.

Set rules of engagement

Decide who may be contacted, and when to stop.

Handle replies

What each kind of reply does.