Skip to content
Adoptiv

Follow-Up Engine

A mail tool cannot see how the call went, so it sends the next thing as though it never happened. Here the word a rep picks at hang-up chooses the next step, and the days after the call run on the same cadence engine as everything else.

See pricing

Sequence: after the renewal call

active
Dana Whitlowactiveon this step now
The call went
An open is a fork in the road here, not the figure the report leads on. It decides which step comes next and nothing else.
0
words a rep can close a call with, each with its own branch
0
days a late reply still gets matched to the run
0
channels timed against each other, not reconciled after

Product figures from the platform’s own defaults - not customer averages

The mechanism

How it works.

01

The phone is a step, not a separate tool

A call step puts a task on the record's owner part-way through the cadence. The rep rings, closes it with one of five words, and that word is written back against the run, where a fork further down the canvas reads it. No mail tool has that word, so its next send goes out the same for the person who answered and the person who never picked up.

02

What enrollls somebody, and what steers them after

A record being created, a stage moving, a tag landing, or somebody adding them by hand or from a list. The wrap-up code a rep picks afterward steers a cadence rather than starting one: its behavior books the callback or sets do-not-call, and the branch downstream reads the outcome that was logged.

03

Two channels, timed against each other

Email and SMS sit as steps on the same canvas rather than in two tools somebody reconciles. Mail departs on whichever outgoing server this workspace configured; the text lands in the thread the rep can already see on the record. A text at ten and a mail at four are one plan with one set of waits between them.

04

What it counts, and what it will not claim

Sends, opens and clicks per sequence, and the branch each person took, all read off the run itself. It is engagement per step rather than a claim about which call a touch produced, because the run knows what it did and not what somebody else's phone did next.

Where it sits

One moment in every call.

Every call passes through the same seven. Follow-Up Engine is the lit one, and everything either side of it is a different page in this category.

  1. 01
    Number

    the line it arrives on or leaves from

  2. 02
    Route

    where the call is sent and to whom

  3. 03
    Dial

    placing it, and how many at once

  4. 04
    Connect

    the moment a person picks up

  5. 05
    Talk

    while the conversation is happening

  6. 06
    Wrap

    the code, the notes, the next step

  7. 07
    Record

    what is kept, and where it is kept

The specifics.

8 facts
Enrollled by
Record creation, a stage moving, a tag landing, a manual add, a list action, or a call-flow node
Steps available
Send mail, pause, ask what they did, split, raise a call task, send a text, tag, goal, end
Branching on a call
One of five words the rep picks when closing the task: answered, voicemail, busy, wrong number, nobody picked up
Reply window
Thirty days from the send, matched on the person rather than on message headers
Email
Departs on the workspace's configured outgoing server, carrying a pixel and rewritten links
SMS
A step like any other on the canvas, and its message joins the conversation the rep reads in the inbox
Opt-out
The suppression roll, checked when somebody is enrollled and again inside the send
Not the same as
Email Sequences is this same engine described from the canvas. This page is the case for putting the phone inside it

Outbound & Compliance

See follow-up engine on your own floor.

Thirty minutes, your numbers and your data. We will set follow-up engine up live and you can decide from the thing itself rather than from this page.

See pricing

14-day trial · no card · migration included