[Overview]
Phone is not a side channel anymore. Sequence call-task steps drop leads into the dialer queue when it is their turn; auto-call steps enqueue outbound legs. Wait-until nodes branch on connected, voicemail, or no-answer so the next step matches what actually happened.
Highlights
- Call-task steps for rep queues
- Auto-call steps for automated legs
- Wait-until on disposition
Outcomes
- Email, LinkedIn, and phone in one cadence
- Rep queues fed automatically from sequences
- Follow-up logic that respects call outcomes
How it works
- 01
Add a call step
Insert call-task or auto-call nodes on the sequence canvas.
- 02
Queue for reps
Call tasks appear in the dialer when prior steps complete.
- 03
Branch on outcome
Dispositions advance, delay, or branch the sequence.
[In the product]
Call tasks in context.
See how this capability sits next to lists, sequences, and inbox - the same surfaces your team already opens every day.
Maya Chen
VP Sales · Stripe
+1 (415) 555-0142
Outcome
[Integrations]
Stack for call tasks
Tools that commonly sit next to this capability - connect what you already use.
Salesforce
HubSpot
SlackLinkedIn
Gmail
Calendar
[Use cases]
Teams that lean on this
See the motion for your role or market - then jump back into the product surfaces that power it.
[More in Dialer]
Related capabilities
[FAQ]
Questions from call tasks users.
Try call tasks.
Try the feature in a workspace, or book a demo and we will wire it into your motion.

