https://retellai.com/?utm_source=discord&utm_medium=seo logo
Custom-LLM WebSocket agent (agent_1c71408607b44528...
# ❓・ai-evy-support
m
@AI Evy Custom-LLM WebSocket agent (agent_1c71408607b44528d264346046, web_call). 1-word user replies like "No." (0.24s) get transcribed but don't trigger response_required. 2-word "Okay. Yes." (0.56s) works. Webhook for call_48c9529a6ca09ce353821003256 shows latency.llm.num=3 for 4 spoken turns — both "No." utterances dropped. Eagerness 0.95, Interruption 0.92, Dynamic OFF, Backchannel ON, Denoising "Remove noise". Is there a minimum-utterance-duration threshold for response_required? Should we move denoising to "No denoising" per your docs? What else controls promotion of short turns?
a
Thanks for tagging me @mannankhan. I'll look through relevant sources and get back to you shortly.
### Answer Retell AI's turn-taking model determines when to send
response_required
events by analyzing conversational cues including tone shifts, pauses, and sentence patterns [(1) ]() [(2) ]() . The model uses predictive timing to ensure smooth transitions between speakers [(2) ]() . For Custom LLM WebSocket agents, Retell continuously assesses when it's appropriate for the agent to speak and sends
response_required
when determined suitable, though not all responses requested will be spoken if the user continues speaking [(3) ]() . The system sends
update_only
events for transcript updates when users or agents speak, and sends
response_required
or
reminder_required
events when responses are needed . Your configuration shows high responsiveness (0.95) and interruption sensitivity (0.92) [(4) ]() [(5) ]() . The
responsiveness
parameter controls how responsive the agent is, with values ranging from [0,1] where higher values mean faster exchanges . The
interruption_sensitivity
parameter controls how sensitive the agent is to user interruptions, with higher values making it easier for users to interrupt . Regarding denoising, the
denoising_mode
parameter can be set to different values . The documentation doesn't specify a minimum utterance duration threshold for
response_required
events or explicitly state that denoising mode affects turn-taking promotion for short utterances. The turn-taking model combines acoustic signals with semantic
understanding to determine whether a user is pausing or finished speaking [(1) ]() . It waits patiently if the user hasn't finished talking to reduce interruptions . For your specific issue with 1-word utterances not triggering
response_required
, I recommend checking your agent's responsiveness and interruption sensitivity settings, and verifying your denoising configuration. The sources don't document a specific minimum duration threshold.
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
​ To learn more, see the sources I considered: [[1] VAD vs. Turn-Taking Endpoints in Conversational AI | Retell AI](https://www.retellai.com/blog/vad-vs-turn-taking-end-point-in-conversational-ai) [[2] Retell AI's Turn-Taking Model for Seamless Calls | Retell AI](https://www.retellai.com/blog/how-retell-ais-turn-taking-model-ensures-seamless-calls) [[3] LLM WebSocket](https://docs.retellai.com/api-references/llm-websocket) [[4] Update Voice Agent](https://docs.retellai.com/api-references/update-agent) [[5] Create Agent Version](https://docs.retellai.com/api-references/create-agent-version) ​
m
@AI Evy Hey — single-word user replies like "No." (0.24s, 1 word) are NOT triggering response_required for our custom-LLM WebSocket agent, even though they show up in the final transcript. 2-word replies like "Okay. Yes." (0.56s) work fine. Agent ID: agent_1c71408607b44528d264346046 (web_call, en-US, custom LLM) Repro call: call_48c9529a6ca09ce353821003256 In that call, latency.llm.num = 3 but the user spoke 4 turns. Both "No." utterances were transcribed but never promoted to a turn. Call eventually ended via end_call tool after a 24s silence. Current config: - Response Eagerness: 0.95 - Dynamically adjust: OFF - Interruption Sensitivity: 0.92 - Enable Backchanneling: ON (frequency 0.8, default words) - Denoising Mode: Remove noise - Transcription Mode: (need to confirm) - Boosted Keywords: "Leena, Leena AI" - Reminder: 10s × 1 Questions: 1. Is there a minimum user-utterance duration (~300ms?) before Retell fires response_required? If yes, can it be lowered? 2. Your docs at /build/handle-background-noise say "No denoising" fixes missing short responses like "sure", "yes" — is that the right move here, even though we don't have background noise? 3. Does Enable Backchanneling = ON cause Retell to hold short user utterances longer before committing them as turns? 4. Any other knob we should look at for reliably promoting sub-500ms / 1-word user replies to response_required?
a
Thanks for the follow-up, @mannankhan. I'll get back to you soon.
### Answer Based on the available documentation, I can address your questions about short utterance handling: Question 2 - Denoising Mode: The documentation specifically states that "No denoising" mode should be chosen "if you experience issues with missing short responses (e.g. 'sure', 'yes') " and notes this is particularly relevant "when background noise is not significant." [(1) ]() This directly applies to your situation where single-word replies like "No." aren't triggering
response_required
. Even without background noise, switching to "No denoising" mode may help with short response detection. Custom LLM WebSocket Behavior: For Custom LLM agents, Retell "continuously assess[es] if it's a good time for agent to speak, and would ask for content for response / reminder when appropriate." [(2) ]() The system sends
response_required
events when determined suitable, though "not all responses Retell ask for would get spoken out (as user might continue to speak) ." Backchannel Configuration: Your agent has
enable_backchannel
set to true with
backchannel_frequency
at 0.8. [(3) ]() Backchannel is described as when the "agent interjects the speaker with phrases like 'yeah', 'uh-huh' to signify interest and engagement" and "tends to show up more in longer user utterances." The documentation doesn't explicitly state whether this affects turn-taking for short utterances. What's Not Documented: The sources don't specify: - A minimum utterance duration threshold for
response_required
events [(2) ]() - Whether this threshold can be adjusted - How backchannel settings specifically impact short utterance promotion **Recommendation:
** Try switching
denoising_mode
from "noise-cancellation" to "no-denoise" since the documentation explicitly mentions this helps with missing short responses like "yes" and "sure." [(1) ]()
​ To learn more, see the sources I considered: [[1] Handle background speech & noise](https://docs.retellai.com/build/handle-background-noise) [[2] LLM WebSocket](https://docs.retellai.com/api-references/llm-websocket) [[3] Update Voice Agent](https://docs.retellai.com/api-references/update-agent) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.