the agent stopped talking
# support
c
id : c2315082-547a-401c-90ef-992d7accc8d1 the timestamp of when this occurred : 1:50 the response i expected to receive : Continue to talk the response i actually received : silence
v
Based on the information I found, your agent might have stopped talking due to a silence timeout issue. This commonly happens after tool calls or when the system doesn't detect user input for a certain period. Try this fix:
Copy code
// Check and adjust your silence timeout settings
// In your Vapi dashboard:
1. Navigate to your agent configuration
2. Look for "endpointing" or "silence timeout" settings
3. Increase the timeout value or disable it temporarily
If this doesn't resolve the issue, please contact Vapi support with your agent ID for further assistance. Source: - [Possible reasons why a Vapi agent stops talking during a conversation](https://discord.com/channels/1211482211119796234/1327662627882795059)
c
the problem occurred without him using a tool it was just answers on the prompt on vapi
s
@coco the user audio didn't came after 110 seconds from the start. https://storage.vapi.ai/c2315082-547a-401c-90ef-992d7accc8d1-1746402136030-65d59538-f9bd-4dc6-abff-d13d26c288ca-mono.wav cc: @Kings_bigđź’«
c
the issue wasn’t that the client didn’t respond — the agent didn’t finish the sentence. He was in the middle of saying he would calculate the price when it suddenly cut off. That’s the real problem.
Once again, in this call, ID :6493abee-5939-4d81-ae74-823c1239d027 time : 0:18
s
You need to change your start speaking plan.
updated-config
Copy code
"startSpeakingPlan": {
  "waitSeconds": 0.6,
  "transcriptionEndpointingPlan": {
    "onPunctuationSeconds": 0.1,
    "onNoPunctuationSeconds": 1.2,
    "onNumberSeconds": 0.5
  }
}
- changed
onNoPunctuationSeconds
is changed to 1.2, because  when set to 0.8 value it may be slightly aggressive for non-English language. This change gives your assistant more breathing room to correctly identify when a user has actually finished speaking versus just interrupting momentarily. If interruptions happen, increase onNoPunctuationSeconds by 0.2 until it feels natural. If responses seem too slow, decrease by 0.1. - I strongly recommend A/B testing different values with native speakers to find the optimal balance. The best settings often emerge through iterative testing. let me know how it goes for you.