Voiceflow PartnersVPVoiceflow Partners
Powered by
SuggestoS
Voiceflow Partners•7mo ago•
2 replies
Suggesto

Heeeeeeeeeeeeeeeelp

Subject: No Reply not triggering consistently in Capture and Button blocks

Hi Voiceflow team,

I’m having trouble getting the No Reply behavior to work consistently:
1. With a Capture block:
• I enabled No Reply, set inactivity to 5s, added a short reprompt, and wired the No Reply port.
• In test mode, sometimes the reprompt shows once but the No Reply path never executes.
• Most of the time, neither the reprompt nor the No Reply triggers.
2. With a Button (Listen) block:
• In the Voiceflow Studio test environment, No Reply works correctly (reprompt + No Reply port firing).
• But once I publish the project and embed the widget on another site, the No Reply never fires.
• The only way to make it work again is to refresh the chatbot and start a New Chat.

Expected behavior:
After 5 seconds of inactivity, the reprompt should appear (if configured), and after that the flow should follow the No Reply port automatically.

Actual behavior:
• Capture block → No Reply almost never works.
• Button block → works in Studio Test, but does not work once published on a site unless I manually reset the chat.

Could you clarify:
• Why the Capture block No Reply doesn’t trigger at all?
• Why the Button block No Reply works in Studio but not in a published webchat without refreshing?
• What is the correct way to handle No Reply in a published chatbot (do we need to send a no-reply event manually from the frontend)?

Thanks a lot for your help 🙏
Voiceflow Partners banner
Voiceflow PartnersJoin
Exclusive community for Voiceflow Solutions Providers & Content Creators.
13,076Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?
Recent Announcements
jacklyn

# Let your agents search the web 🔎 Hey everyone! We just released the web search tool for the agent step! Your agents can now automatically search the web for information, letting your agent supplement the LLM's knowledge and the data in its knowledge base with live, up-to-date information. Plus.... * You can restrict searches to specific domains, so your agent only searches sites that you own * This is a tool, so you remain in control of when the agent searches the web * Results are automatically summarized in a way that your agent can automatically understand Under the hood, we're using OpenAI's web search API. Give it a try, and let us know what you think! https://docs.voiceflow.com/changelog/native-web-search-tool

jacklyn · 4mo ago

jacklyn

jacklynbiggin's Thread

jacklyn · 4mo ago

hurt-tomato

connor_maclean's Thread

hurt-tomato · 4mo ago