input
I have connected Voiceflow with WhatsApp, and because of this, my operation is exposed to user messages at any time. Today, a client first sent "ok" and then, 24 seconds later, sent a question. Since my no-reply timeout is set to 15 seconds, their question was not captured. I’d like to know if it’s possible to always redirect any new incoming input to the component that handles user messages.
1 Reply
Because WhatsApp is an async chat channel, we generally don’t use Voiceflow’s global “No-Reply” timeout.
That feature was designed for real-time voice calls; once the timeout fires the flow follows the No-Reply path (or even ends the session), so the very next message the user sends never reaches the block that was waiting for input. What to do instead: • Remove the global No-Reply setting (or raise it to something much longer).
– Project settings ▸ Global No-Reply ▸ disable / delete.
– If you still need a reminder for truly idle users, add a No-Reply on specific User-Input steps and choose a larger delay (e.g., minutes or hours). • Keep the conversation in a “listening” state.
Your last step before waiting for the user should be a User Input (or a Choice/Intent step) that is set to “Always on” so any message—“ok” or a long question—routes to that block. • Session length.
DM-API chat sessions stay active for 30 days unless you deliberately send an END trace, so the user can come back at any time and their next WhatsApp message will be processed by the current state of the flow. In short, disable the global 15-second No-Reply and rely on standard User Input steps; that way every new incoming WhatsApp message is picked up by the component that’s waiting for it.
Docs: https://docs.voiceflow.com → “No Reply handling”
That feature was designed for real-time voice calls; once the timeout fires the flow follows the No-Reply path (or even ends the session), so the very next message the user sends never reaches the block that was waiting for input. What to do instead: • Remove the global No-Reply setting (or raise it to something much longer).
– Project settings ▸ Global No-Reply ▸ disable / delete.
– If you still need a reminder for truly idle users, add a No-Reply on specific User-Input steps and choose a larger delay (e.g., minutes or hours). • Keep the conversation in a “listening” state.
Your last step before waiting for the user should be a User Input (or a Choice/Intent step) that is set to “Always on” so any message—“ok” or a long question—routes to that block. • Session length.
DM-API chat sessions stay active for 30 days unless you deliberately send an END trace, so the user can come back at any time and their next WhatsApp message will be processed by the current state of the flow. In short, disable the global 15-second No-Reply and rely on standard User Input steps; that way every new incoming WhatsApp message is picked up by the component that’s waiting for it.
Docs: https://docs.voiceflow.com → “No Reply handling”
Voiceflow
Welcome to Voiceflow's docs
Build, manage, and deliver chat and voice agents for customer support and beyond.