Call Tasks in Sequences
A step that puts the phone in the middle of a mail cadence. It raises an assigned task on the record, and the outcome the rep logs against it travels back as something the next fork can read.
A phone step in the middle of a mail cadence
the row that gets writtenProduct figures from the platform’s own defaults - not customer averages
How it works.
It lands on whoever owns the record
Unless the step names a person, the owner of the record gets it. Where the step names nobody and the record has no owner either, no task is raised at all, because the column will not take an empty one, and the walk carries on to whatever comes next.
The title is personalised; the script is not
A first name is substituted into the title before the row is written. The script goes into the description exactly as typed, tokens intact, so anything you wanted filled in belongs on the title line.
It does not stand there waiting for the call
Raising the task takes no time and the walk continues immediately. If what comes next should depend on how the call went, put a pause between the step and the question, long enough that somebody has actually picked up the phone.
Closing it feeds the fork downstream
Logging an outcome completes the task, looks up which run raised it through the identifier kept on the step record, and writes that outcome back. An outcome box further along the cadence can then send them down whichever arm carries that word.
One moment in every run.
Every run passes through the same seven. Call Tasks in Sequences is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
7 facts- What gets created
- A task of type call against the record, with a title and a description, credited to the assignee
- Assignee
- The person named on the step, or the record owner where the step names nobody. Neither one nor the other means no task at all
- Merge fields
- First name, in the title. The script body is stored word for word
- Outcomes accepted
- Answered, voicemail, busy, wrong number, or nobody picked up. Five, and the list is fixed
- How the outcome finds its way back
- The task identifier is kept on the step record when the task is raised
- Not set by the step
- Due date, priority and reminders. The task is raised without any of them
- Not the same as
- This raises work for a person. Wrap-up codes a floor closes calls with are Disposition Behaviours
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and webhooks that act without being asked.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Enrol a lead once and the sequence carries them: sends, waits, branches and exits, with a ledger that makes a duplicate send structurally impossible.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
One do-not-contact roll per workspace, checked when a lead is enrolled and again inside the send, straight after that send has taken its own claim.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Six event types a CRM rule fires from: stage change, field update, new record, reassignment, schedule and inactivity, agreed in four places at once.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
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.
Automation & Flows
See call tasks in sequences on your own floor.
Thirty minutes, your numbers and your data. We will set call tasks in sequences up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included