Agent Died at end of call
# supportk
kitten
05/30/2025, 2:42 PMI have an agent that does interviews and it was doing an interview and died at the end of the call and stopped responding.
ID: 5371b919-9aaf-48fa-8c9f-6c99447292cd
k
Kings_bigđź’«
05/30/2025, 4:47 PMLooking into it
s
Shubham Bajaj
05/31/2025, 11:52 AMHey kitten, can you help me understand what you mean by the agent dying at the end of the call and what you expect it to work like?
k
kitten
06/04/2025, 1:48 AMIt literally should keep asking questions but stopped replying
kitten
06/04/2025, 1:48 AMHave another ticket for more IDs of this
kitten
06/04/2025, 10:36 AM#1379591022501302386
v
Vapi
06/05/2025, 6:28 AMcould you please provide a couple more call ids?
k
kitten
06/05/2025, 9:56 AMI already did here
There are some calls that the AI stops replying. It’s heppened a few times today:
Call IDs
6a3c2f90-4322-4ac5-a789-9ea9e5cd0696
0f3dd207-d835-4717-b3c6-2f35b90a1078
Look at the end of each call and see where it just stops replying
v
Vapi
06/07/2025, 4:30 AMJust letting you know that we are still looking into this issue
Vapi
06/17/2025, 11:19 PMLooking at this call transcript, the issue appears to be that the assistant failed to follow the conversation script and went silent when it should have continued asking questions. To prevent this, you could:
1. Add explicit instructions about handling silence/reconnection attempts
2. Use more robust conversation state management to ensure script adherence
3. Add fallback responses when the AI goes silent unexpectedly
4. Consider using conversation checkpoints to ensure critical script sections are completed