Sequences

Follow up until they answer.

Write the steps once. Matiks sends each one on your delay, inside your hours, from your own mailbox — and stops the moment somebody replies.

Enrolled fromSpring intake
Your application is inSent · Tuesday 9:02
After 2 business days
One thing we still needSent · Thursday 9:02
Dana replied — sequence ended
Last call on this oneNot sent

Step inside a sequence.

A list of emails, a delay between each, and the conditions that end it early.

Nobody has to remember.

The runner keeps track of who is due, and skips anyone who already answered.

Enrol one, or a list.

Start a person from their record, or put a whole list into the sequence at once.

Send inside your hours.

Delays in hours or days, business days only if you want, within a window you set.

Stop on a reply.

A response ends the sequence for that person. Step three never arrives after step two worked.

Exit criteria

The part most follow-up gets wrong

A sequence that keeps sending after somebody answers is worse than no sequence. Matiks checks before every step, and ends the enrolment when any of these is true.

  • They replied

    Any response on the thread the sequence started.

  • A field changed

    The status you are watching moved to a value that means done.

  • Somebody stopped it

    Pulled by hand, from the record or the enrolment list.

  • It finished

    The last step sent and there is nothing left to send.

Written like one email.

Every step is the same composer you already use, with the same merge fields.

The composer you know.

Each step opens the editor from the Email page — formatting, signatures, attachments and all. Nothing about a sequence step is a special case.

Fields fill themselves.

Drop in a first name, a date, or any field on the record, and every recipient gets their own version resolved at send time.

Paperwork rides along.

Attach a filled PDF or a share link, so the thing you are asking them to sign is in the message rather than in a follow-up.

All of it on the record.

Enrolment, every send, every reply and the reason it ended — in the activity feed.

[01]

Every send, logged.

Each step lands on the record it was sent about, in the same feed as everything else.

[02]

Replies thread.

The answer arrives on the conversation the step started, not as a new loose email.

[03]

Pause or pull anyone.

Stop a person, restart them, or take them out — one at a time or from a selection.

[04]

Draft until you publish.

A sequence sends nothing until it is Live, so a half-written step cannot go out.

Sequences are one part of it.

They read the same records, and write to the same feed, as the rest of the workspace.

Set up your first sequence today.

Bring a mailbox and a list. The first step can go out this afternoon.