Sequences

Outreach that runs on every channel

Email, LinkedIn, WhatsApp, texts, calls and X in one sequence, with delays, conditions and branches. Build once, enroll many.

Sequences

A sequence is a series of steps that runs per enrolled person. Email on day zero, LinkedIn connect on day two, and if they accept, a LinkedIn message. If they do not, a follow-up email instead. Build it once. Enroll a person, a list, or everything a filter matches.

The builder

A canvas for a sequence that forks, and a list for the ones that do not. Same sequence, two drawings. One plus adds the next step, and the cards face the direction the flow runs. Ask the agent to build it, and the canvas redraws while you watch.

The canvas
Each card is a step. Click one to edit what it sends and when.
Canvas and list
The same steps, as a list, and back.

Steps span every channel

Email
Automatic or manual, with A/B variants and a subject line per variant.
LinkedIn
Connect, message, InMail, voice note, video, post engagement. Through your session.
WhatsApp, iMessage, SMS
Texts from the business number, or through your Mac.
X and Reddit
DM, follow, post, engage. Reddit as manual steps.
Calls
A scripted manual task, queued for the dialer.
Logic
Delays, conditions that branch, and an Ask the Agent step that branches on its own answer.
Adding a step
The channel picker. Every channel the workspace has connected.

Auto and manual

Auto steps fire on their own. Manual steps queue as tasks in your To-do, which is the right shape for calls, personalized touches, and every Reddit step. The stats bar at the top of a sequence shows the split.

The stats bar
Auto against manual, and the channel mix.

Merge fields

Templates take the usual names, plus fallbacks and conditionals. Your own custom fields are merge fields too: a contact column named Trial Phase becomes a variable you can drop into a subject line. Preview merged shows exactly what one person will receive.

Enrolling

  1. 1From a list: select people, or everything a filter matches, and enroll.
  2. 2From a record: enroll this person. From the assistant: enroll everyone from the June import.
  3. 3From a workflow: a form submission or a stage change enrolls automatically.
  4. 4Exit rules: leave the sequence when they reply, book, or change status.

Health

The enrollments view shows who is at which step, who finished, who replied, and who failed with the reason. A failed step can be retried in place. Sender groups rotate mailboxes and retry a send that bounced off a limit.

Per sequence
Active, done, contacted, per sequence, on the list page.

Replies

A reply pauses the sequence for that person and lands in the Inbox with the intent read: interested, not now, wrong person, out of office. Out of office waits and resumes; the rest hand the thread to you.

Around sequences

The parts of the workspace this one works with.

Personalize a step for one person

Rewrite any step of a sequence for one named prospect, before it fires, without forking the sequence.

Copy is no longer fixed at the sequence level. You can rewrite a single step for a single person, and everyone else still gets the template. Tier-one accounts get a hand-written opener inside the same automated sequence.

A step, opened

Templates, snippets and components

Three layers of reusable copy. Sharpen a snippet once and every template and step using it improves.

Copy that works should be written once and used everywhere. Templates are the message. Snippets are the reusable pieces inside it. Components are the structured blocks the pieces are made of. Change one and everything built on it changes.

Messaging and Contracts

LinkedIn activity limits

Hourly caps and working hours for anything automated on LinkedIn, so an account keeps looking like a person.

LinkedIn throttles aggressive accounts, and a soft block does not look like an error. It looks like empty profiles and empty results for a while. The limits exist so you never find out.

LinkedIn steps in sequences

Schedule a message

Any channel, any time. A queue you can review, reschedule or cancel before it fires.

An email, a LinkedIn message or a text can go out tomorrow at nine instead of now. It sits in a queue until then, and the queue is a page you can read, reorder and cancel from.

The composer

Questions

How many sequences can a person be in?+

One at a time by default, so two reps never write on the same day. An admin can allow more.

Can a step send from a different mailbox?+

Yes. A sequence pins a mailbox or a sender group.

What happens at the weekend?+

Steps respect working days and the timezone of the person when it is known.

Does personalizing affect A/B stats?+

A personalized step is counted with the variant it was based on.

Can I personalize a LinkedIn connect note?+

Yes. Any step with copy: email, LinkedIn message, connect note, text.

Can a template be private?+

Templates are shared with the workspace. A draft stays yours until you publish it.

Do variables have fallbacks?+

Yes. {{first_name | there}} and conditionals for a line that only appears when a field is set.

What is a safe number?+

Depends on the account’s age and history. The defaults are safe for most. Do not exceed what you could do by hand in a busy day.

What happens if LinkedIn does throttle?+

Searches return empty and sends fail. Pause automation from the panel, wait a day, and lower the limits.

Where is the queue?+

Scheduled messages are listed from the Inbox and on each record under the channel they will go out on.

Can the assistant schedule?+

Send it Monday morning is enough. It picks nine in your zone.

Try sequences on your own data

Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.