Call Tasks in Sequences
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever outcome they log when the call ends is what decides where that person goes next.
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 already owns them
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 personalized; 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.
What the rep logs decides where they go next
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 Behaviors
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 outside triggers that act without being asked.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
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