Sequences & workflows

Outreach on a schedule, automation on a trigger.

Two different engines. Sequences send multi-step email to enrolled contacts when each step comes due. Workflows watch for events — a lead reaching Closed/Won, a scheduled progress check — and run their conditions and actions without anyone remembering to.

contacts per sequence
24contacts per sequence
enforced exit
1enforced exit
steps per workflow
5steps per workflow

Q3 roofing outreach

Contact enrolled on a sequence

Resolved through the linked person record

Step 1 — intro email

Renders {{first_name}}, {{sender_name}}

Wait until step 2 is due

Scheduled job or manual process-due

Step 2 — follow-up email

Sent over SMTP, written to the send log

Unsubscribe stops all future sends

Public link, no login required

To tom@blueskyroofing.com

Following up, Tom

Hi Tom — we spoke about routing for your two crews.

I put together the depot breakdown you asked for. Worth 15 minutes this week?

Priya Nandan · Fieldstone

Merged{{first_name}}{{sender_name}}

Send log

Today, 09:14

  • tom@blueskyroofing.comStep 2Delivered
  • maria@greenvalley.coStep 2Delivered
  • aisha@sunrisedental.comStep 1Unsubscribed
How it works

The path a record actually takes.

  1. 01

    Enroll a contact

    The recipient resolves through their linked person record, so the address comes from the account, not a paste.

  2. 02

    A step comes due

    Either the scheduled job picks it up, or you trigger process-due by hand when you want it out now.

  3. 03

    The email renders and sends

    Merge fields resolve per recipient, the message goes over SMTP, and the send is written to the log.

  4. 04

    Unsubscribe ends it

    A public link, no login required. It blocks every future send to that recipient permanently.

Workflows

Triggers that fire on real events.

A lead reaching Closed/Won, or a scheduled progress check on a project. Each run works through its conditions and actions, and logs the steps it had to skip.

Closed/Won → delivery

Active
WHEN

Lead status changes to Closed/Won

AI

Read the conversation, draft a plan

ACTION

Create the project, milestones, and tasks

CHECK

Is Slack connected for this company?

YesCreate channel, invite team, post kickoff
NoSkip the step and log it
ACTION

Notify the assigned rep

Last run 8 days ago6 runs this month

What you get.

Multi-step sequences

Intro, wait, follow-up — each step with its own subject and body.

Merge fields

Rendered per recipient, previewable before a single message goes out.

Send log

Every send recorded with recipient, step, and outcome.

Enforced unsubscribe

The one exit condition the engine acts on, and it is absolute.

Event triggers

Status changes and scheduled checks start a workflow run.

Conditions and branches

A workflow can check state and take a different path — including skipping safely.

Worth knowing

Reply and meeting detection is not automatic

Those exit criteria can be stored on a sequence, but the engine does not detect them for you. Unsubscribe is what it enforces.

Keep going.

Companies & people

The contacts sequences send to and updates reach.

Read more

Notifications

In-app and browser push from a single dispatch.

Read more

Projects & tasks

Built automatically the moment a lead is won.

Read more
Start hereYour next won deal

Never rebuild the same project twice.

We set up your workspace and your first admin. Your team joins by invite, and the next deal you close arrives as a project that is already moving.

  • We set up your workspace
  • Your team joins by invite
  • Bring the pipeline you have

Prefer to talk first?

  1. Deal marked Closed/Won

    One status change

    01

  2. Project, milestones, 5 tasks

    Drafted from the conversation

    02

  3. #harborview-onboarding

    Channel opened, kickoff posted

    03

  4. Owner notified

    In-app and browser push

    04

Every step above runs from one status change.