Follow-Up Engine
The days after the call, run on the same cadence engine as everything else, with a phone step in the middle of the mail. What makes it an outbound page rather than a marketing one is that the rep's logged outcome is what decides the next step.
Sequence: after the renewal call
activeProduct figures from the platform’s own defaults - not customer averages
How it works.
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. Mail tools cannot see that word at all, which is the whole reason this page exists.
What puts somebody in, and what steers them once they are
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 afterwards steers a cadence rather than starting one: its behaviour books the callback or sets do-not-call, and the branch downstream reads the outcome that was logged.
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.
What the reporting counts
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.
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.
- 01Number
the line it arrives on or leaves from
- 02Route
where the call is sent and to whom
- 03Dial
placing it, and how many at once
- 04Connect
the moment a person picks up
- 05Talk
while the conversation is happening
- 06Wrap
the code, the notes, the next step
- 07Record
what is kept, and where it is kept
The specifics.
8 facts- Enrolled 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
- 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 enrolled 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
What runs alongside it.
Volume calling is several controls working at once, not one dial turned up. These are the others.
More in Outbound & Compliance
2 capabilitiesBroadcasting, voice AI, QA scoring, calling rules and number health.
You write the rubric and the model scores the call. Weighted scorecards, instant-fail items, sampling rules, and coaching notes with the quote attached.
Answer rate per number, spam-label and CNAM status from carrier databases, a warm-up ramp for new numbers, and the thresholds that decide when one is rested.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
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.
14-day trial · no card · migration included