Who This Is For / When to Use
Use the Call action if you want to:
Instantly notify users of important events by phone
Prompt fast follow-ups on leads or appointments
Combine calls with voicemail, SMS, or email actions in workflows
This action is commonly used for time-sensitive workflows.
What the Call Action Does
The Call action:
Places an automated call during a workflow
Plays a whisper message before connecting the call
Detects answered calls vs voicemail (optional)
Can require a keypress before connecting the call
The call behavior depends on workflow settings and action-level toggles.
Step 1: Open or Create a Workflow
Go to Automations.
Select Workflows.
Click Create Workflow, or open an existing workflow to edit.
Step 2: Add or Confirm Workflow Triggers
Add one or more workflow triggers, or leave the workflow without triggers.
Any trigger type can be used with the Call action.
Note:
A workflow without triggers will not run automatically.
Step 3: Add the Call Action
Click the + icon below a trigger (or at the start of the workflow).
Open the Actions menu.
Search for and select Call under Communication actions.
Step 4: Configure Call Action Settings
Action Name
Internal label for the workflow builder only
Does not affect call behavior
Call Whisper
Message played to the user before the call connects
Supports custom fields using the tag selector
If left blank, the default whisper plays:
“You have a new lead. Press any button to connect.”
Call Timeout (Seconds)
Time the call rings before routing to voicemail
Example: 30 or 60 seconds
Advanced Call Settings
Disable Voicemail Detection
Enabled (default): System detects voicemail vs answered calls
Disabled: Faster call handling with no voicemail detection
Recommended use cases:
Disable if the next action is a prerecorded voicemail
Enable if workflow logic depends on detecting real responses
Connect Call After Keypress
Enabled (default): User must press any key to accept the call
Disabled: Whisper plays three times, then call auto-connects
Step 5: Save and Publish the Workflow
Click Save Action.
Click Save in the workflow header.
Toggle workflow status to Publish when ready.
Use Test Workflow to confirm behavior.
How Call Action Interacts With Workflow Settings
Stop On Response
If enabled, an answered call counts as a response and removes the contact from the workflow
With voicemail detection enabled, voicemail does not count as a response
With voicemail detection disabled, voicemail does count as a response
This setting directly affects follow-up actions like SMS or second call attempts.
Example Workflow Configuration
Trigger: Appointment Confirmed
Action: Call
Call Action Settings:
Action Name: Appointment Call Reminder
Call Whisper:
“You have a new appointment with [Contact Name] at [Appointment Time]. Press any key to confirm.”Call Timeout: 30 seconds
Disable Voicemail Detection: Enabled
Connect Call After Keypress: Enabled
Outcome:
The assigned user receives an immediate call when an appointment is confirmed.
Common Issues and Fixes
Call Does Not Connect
Confirm a valid phone number exists in settings
Verify workflow is published
Check call timeout value
Workflow Stops After Voicemail
Check Stop On Response setting
Enable voicemail detection if follow-ups are required
Whisper Message Sounds Incorrect
Review custom field formatting
Test workflow with sample contacts
FAQs
What is the Call action used for?
It automates phone calls during workflows to notify users or prompt immediate action.
Can I personalize the whisper message?
Yes. Use custom fields to include contact or appointment details.
Can I use the Call action without a trigger?
Yes, but the workflow will not run automatically.
Can the Call action be followed by other actions?
Yes. It can be followed by voicemail, SMS, email, wait steps, or conditional logic.
How does voicemail detection affect workflows?
It determines whether a call counts as a response and whether the workflow continues.