Workflow Action: Call in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Call action auto-dials the assigned user (or a default number) when a workflow trigger fires, with optional whisper messages, voicemail detection, and keypress confirmation before connecting.

The Call workflow action initiates an outbound call to the assigned user — or a default company number if no user is assigned — when a trigger fires. You can play a whisper message before the call connects, set a timeout, control voicemail detection, and require a keypress before the call links to the contact.

Field reference

Field	Description	Required
Action Name	Internal name for this call action.	Yes
Call Whisper	Short message played to the receiver before connection. Supports custom values. Plays up to three times.	No
Call Timeout (s)	Max seconds to wait for connection before terminating.	Yes
Disable Voicemail Detect	Turns off voicemail detection. Reduces connection delay but may treat voicemail as a live answer.	No
Connect Call After Keypress	Connects only after the receiver presses a key. Confirms a live person answered.	No

Note: The Call Whisper uses Text-to-Speech, billed at $0.00084 per 100 characters.

How to configure

Add the Call action.
Name it (e.g., Appointment Call Reminder).
Type a whisper message. Custom values like {{contact.first_name}} personalize it.
Set the call timeout in seconds.
Toggle Disable Voicemail Detect if you need faster connect times.
Toggle Connect Call After Keypress if you require a live answer.
Save.

Disable Voicemail Detect & Stop on Response

By default, Sparkforge tries to detect whether a person or voicemail answered. This adds a small connection delay. If Stop on Reply is on and voicemail is detected, the contact continues in the workflow.

Disabling voicemail detect removes the delay, but with Stop on Reply on, the workflow stops whether a person or voicemail answers — the system can't tell them apart.

What the Business does when called doesn't affect Stop on Response. The Business is dialed first; if the Business doesn't answer, the workflow continues. If the Business answers and the Contact then doesn't, the workflow continues. Only the Contact (or Contact's voicemail) influences Stop on Response.

Example: appointment confirmation

Trigger: Appointment Confirmed.
Action: Call.
Action Name: Appointment Call Reminder.
Whisper: You have an appointment with {{contact.name}} at {{appointment.time}}. Press any key to confirm.
Timeout: 30 seconds.
Disable Voicemail Detect: on.
Connect After Keypress: on.

The assigned user gets a heads-up call, hears the whisper, and only connects to the contact after pressing a key.

Frequently Asked Questions

Who gets called — the contact or the user?

The Call action dials the assigned user (or a default number if unassigned). The whisper plays to that user, and after keypress the call connects to the contact.

How is the whisper message billed?

Whisper messages use Text-to-Speech at $0.00084 per 100 characters. Calls themselves are billed at standard usage rates.

Should I disable voicemail detect?

If you have short timeouts and want faster connections, disable it. If you rely on Stop on Response logic to skip voicemails, keep it enabled.

What happens if no one is assigned to the contact?

The system dials a default company number set in your phone configuration. If no default is set, the action skips.