Hello, is anyone else experiencing 6 or
# general-english
j
Hello, is anyone else experiencing 6 or 7 second delays after each response, or the assistant stopping in the middle of talking and waiting 6 or 7 seconds to continue? I first starting noticing it this morning.
k
Lower the response delay, adjust the wait-function in Smart Endpointing for faster detection, optimize the stopSpeakingPlan settings, and consider switching transcribers or using Vapi’s webhook or SDK for better performance.
j
I have lowered the wait seconds to 0.2 seconds. Smart endpointing is set to Vapi. Stop speaking plan is set to number of words (0), voice seconds (0.2), and back off seconds (1). I do not see the response delay in my dashboard. Where would I find it? Also, the transcriber is set to Deepgram, model is nova 3 (default). What should I change this too? Right now I have timed 7 seconds between my response and when the assistant starts talking again. It is an awkward silence after each response.
This does not happen when I hit talk to assistant in top right corner. Only when I attempt an outbound call.
I am using web, and I am with Telnyx.
k
Go through this tutorial

https://youtu.be/qd3IWVFJXDk?si=MVraVVziMqZKJCWqâ–¾

j
My dashboard does not have the pipeline configuration. So response delay and llm request delay are not visible on my dashboard.
Latency is at 800ms. The assistant works as it should when I click talk to assistant. It is only when I try to call myself with an outbound call through the phone number tab or through a make.com scenario that it has extended pauses. Most of the time my changes do not stick. If I switch to another page (like phone numbers) and come back the changes are gone. For some reason after I click the publish button the pencil never goes away and the publish button is always lit up showing that there are always unsaved changes. https://cdn.discordapp.com/attachments/1366586321652420690/1366781410421248050/image.png?ex=681231e1&is=6810e061&hm=2da2cf6ffb099e8cb7e7df31af84284987f2b7d9df42b216b2e589edb6b05052&
This seems to be working better today. Not sure if anything changed.
2 Views