Call Tasks in Sequences
The Call Decides What They Get Next.Call tasks in sales sequences, so a real phone call sits between the emails.
Put a phone call in the middle of your sequence. The lead’s owner gets a call task with the lead’s name in the title and your script attached. When they log how it went (answered, voicemail, busy, wrong number or no answer), that outcome picks the lead’s next step.
- Goes to the lead’s owner
- Script attached
- Outcome picks the next step
How it works
- Emails go outThe sequence runs as planned
- A call task appearsFor the lead’s owner, with your script
- The rep callsAnd logs how it went
- The outcome steersVoicemail, answered or busy: each its own path
Your Sequence Gets a Human Voice.
Drop a call between emails at the point a conversation matters most, and the right rep gets it.
Tasks go to the person you name on the step, or to whoever owns the lead.
Your script rides along in the task, with the lead’s first name already in the title.
The outcome the rep logs sends the lead down the matching path: voicemail, answered, busy and more.
A Call Step in Three Steps.
Add a Call Step
Drop a call task into the sequence, write the title and the script, and pick a rep or leave it to the owner.
Add a Wait, Then a Branch
Give the rep time to call, then add a call outcome question with a path for each outcome.
Reps Call and Log It
The rep makes the call and logs the outcome. That closes the task and sends the lead the matching way.
Why Put Call Tasks in Sales Sequences?
Call tasks in sales sequences put a real phone call between your emails. When a lead reaches the step, Adoptiv creates a call task for a rep, and the outcome the rep logs decides what that lead gets next.
This is what makes a multichannel sales cadence work: a call step in an email sequence that the rest of the sequence listens to. The task goes to the rep named on the step, or to the lead’s owner if nobody is named, so you assign call tasks to the lead owner by default. The title fills in the lead’s first name, and your call script rides along word for word.
The sequence doesn’t stand still while the rep dials. It creates the task and moves on, so put a wait after the call step, then a call outcome question. When the rep logs answered, voicemail, busy, wrong number or no answer, the task closes and the branch sends the lead down the matching path: a voicemail might get a text, an answered call the proposal.
Reps make these follow-up calls from the browser, on the same system as the sequence. The step doesn’t set a due date, priority or reminder on the task. And outcomes at the end of everyday calls can trigger actions on their own, outside any sequence: see after-call work automation.
A Phone Call, Planned into the Follow-Up.
A phone call between emails, created the moment a lead reaches the step.
Or to the rep you name on the step.
Your script is attached to the task word for word.
The lead’s first name is filled into the title.
Answered, no answer, voicemail, busy or wrong number.
For Teams That Sell on the Phone and by Email.
Call Tasks in a Sequence vs a Separate Call List.
| What | Email tool plus a call list | With Adoptiv |
|---|---|---|
| When to call | Email tool plus a call list: Someone checks a list and guesses | With Adoptiv: A task appears when the lead reaches the step |
| Who calls | Email tool plus a call list: Whoever has time | With Adoptiv: The rep on the step, or the lead’s owner |
| What to say | Email tool plus a call list: Notes in another document | With Adoptiv: Your script attached to the task |
| After the call | Email tool plus a call list: The emails carry on regardless | With Adoptiv: The logged outcome picks the next step |
| Due dates and reminders | Email tool plus a call list: Set by hand | With Adoptiv: Not set by the step either; the task is created without them |
Call Tasks in Sequences Questions, Answered.
What is a call task in a sequence?
A step that hands a rep a phone call to make partway through a sequence, instead of sending another email. The outcome they log can then choose the lead’s next step.
Who gets the call task?
The person named on the step. If the step names nobody, the lead’s owner gets it. If the lead has no owner either, no task is created and the sequence moves on.
Does the sequence wait for the call?
No. It creates the task and moves straight on. If the next step depends on the call, put a wait between the call step and the outcome branch so the rep has time to call.
Which call outcomes can steer the sequence?
Five: answered, no answer, voicemail, busy and wrong number. Each can lead to its own next step.
Can I personalize the call script?
The task title fills in the lead’s first name. The script is saved exactly as you type it, so put anything personal in the title.
Can a call task have a due date or reminder?
Not from the step. The task is created without a due date, priority or reminder.
How long should the wait be after a call step?
Long enough for the rep to actually make the call. The outcome question only sees outcomes logged by the time a lead reaches it.
Is a call task the same as a call outcome action?
No. A call task gives a rep a call to make inside a sequence. Call outcome actions run things like callbacks and Do Not Call marks whenever any call is wrapped up.
Where does SIYA fit in?
After a call, SIYA can put the next step in your feed, like a callback, a meeting or a follow-up email, the way your best rep would. A person accepts or rejects each one.
Still have a question? A real person replies in under 60 seconds in US business hours. Talk to our team →
14-day free trial
Put a Real Call in Your Sequence.
Add a call task to your first sequence in the free trial. Free for 14 days, no credit card.
14-day trial · no card · migration included