User voice not getting picked up by transcriber bu...
# support
c
We've been having problems recently with the user's input/response not getting picked up by the STT and therefore triggering an idle-message "are you still there?". However, the user's input/voice is clear in the recordings. This is a dev test call, but there are two moments in this call where the idle-message is triggered - 18da30fc-4cb6-4168-a56e-c45ee82ce943 It's been occuring almost once on each call in our production. Is there something in our assistant configuration that could solve this issue?
v
You can continue this conversation by mentioning me in the message.
@Chris I'm sorry to hear that you're experiencing issues with the speech-to-text (STT) recognition. To address this, we can look into adjusting the
number
parameter, which determines the number of words the assistant waits for before interrupting. If this threshold is too low, it might not give users enough time to speak, especially if they pause mid-sentence. Additionally, we can check the
assistantOverrides.maxDurationSeconds
to ensure the assistant is allowing enough time for the user to respond. Could you please provide the current settings for the
number
parameter and the
assistantOverrides.maxDurationSeconds
? With this information, we can suggest an appropriate adjustment to improve the STT recognition during calls.
c
currently, we are setting: "maxDurationSeconds": 600, "responseDelaySeconds": 0.3, "backchannelingEnabled": false, "silenceTimeoutSeconds": 15, "endCallFunctionEnabled": true, "llmRequestDelaySeconds": 0.1, "dialKeypadFunctionEnabled": false, "numWordsToInterruptAssistant": 2
v
Got it. Tagging @User for additional help.
s
@Chris try this and lmk how it goes. "startSpeakingPlan": { "waitSeconds": 0.3, "smartEndpointingEnabled": true }, "stopSpeakingPlan": { "numWords": 0, "voiceSeconds": 0.2, "backoffSeconds": 2 }
c
Hi thanks for getting back to me
Yes I'm testing this atm and it seems to be working much better
So you would put smart endootingpointing on?
s
yeah it's specifically for phonecalls built by us.
c
Oh ok great! Thanks for letting me know. Appreciate you looking into this for me
3 Views