Stop on Response and Disable Voicemail Detect in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

Stop on Response (workflow-level) removes contacts who reply by SMS, email, or call. Disable Voicemail Detect (Call action) skips the audio analysis that distinguishes a person from a voicemail. Combining them controls whether voicemails stop the workflow and how fast calls connect.

Two settings determine how a Sparkforge workflow reacts when an automated call lands: Stop on Response at the workflow level and Disable Voicemail Detect on the Call action. Used together, they decide whether voicemails count as a response and how fast calls connect.

Note: in the Call action, what the Business does is irrelevant to Stop on Response. The Business is called first; whether they answer or not, the workflow continues to the Contact. Only the Contact (or their voicemail) is evaluated against Stop on Response.

Stop on Response (workflow setting)

When enabled, Stop on Response automatically removes a contact from the workflow if they respond to any communication — SMS, email, or call. It prevents the workflow from continuing to message a lead who already engaged.

Disable Voicemail Detect (Call action setting)

This advanced toggle on the Call action controls whether Sparkforge analyzes the call audio to identify a live person versus an answering machine. Detection adds a short delay because the system has to listen before connecting.

The four combinations

Stop on Response	Disable Voicemail Detect	Behavior
ON	ON	Voicemail counts as a response and stops the workflow. Set the Call Timeout below 20 seconds so the call doesn’t reach voicemail in the first place.
ON	OFF	Voicemail is detected, so a voicemail pickup does not trigger Stop on Response. The contact stays in the workflow.
OFF	OFF	The workflow continues regardless of responses or voicemail. Slightly slower because voicemail detection runs by default.
OFF	ON	The workflow continues regardless of responses or voicemail. Slightly faster because voicemail detection is skipped.

Pick the right combo

Maximum accuracy: Stop on Response ON, Disable Voicemail Detect OFF. Voicemail won’t prematurely stop the workflow.
Maximum speed: Stop on Response OFF, Disable Voicemail Detect ON. Calls connect faster, but the workflow keeps running through any voicemail or response.

Frequently Asked Questions

Why does my workflow stop after a call when no one answered?

Stop on Response is on and Disable Voicemail Detect is also on. The system treats voicemail pickup as a response. Either turn off Disable Voicemail Detect or set the Call Timeout to 20 seconds or less so the call ends before voicemail.

What causes the delay when voicemail detection is enabled?

Sparkforge listens for a few seconds after the call is answered to distinguish a person from a recorded greeting. That analysis time is the delay.

What’s the recommended Call Timeout to avoid triggering voicemail?

About 20 seconds. Most carriers ring longer than 20 seconds before forwarding to voicemail, so a 20-second timeout cuts the call before voicemail picks up.

Does Stop on Response apply to manual calls from the Conversations tab?

No. Stop on Response only applies to automated actions inside that workflow. Manual calls or calls from other workflows don’t trigger it.