fascinating-indigo•2w ago
Query Tool Searches Then Stops Responding.
Whenever my agent uses a query tool it gets the right info, but instead of responding it stops talking until I say something, then it starts up again and gives the requested info.
I have had this problem for a few days and have read a few threads on it but I still have no idea how to solve it.
Any help is appreciated.
5 Replies
fascinating-indigoOP•2w ago
@Vapi Can anyone respond to this?
Hello,
Thanks for patiently waiting for us,
Can you give any screen recording, session ID and CallID that we can refer to about this error?
Thanks for patiently waiting for us,
Can you give any screen recording, session ID and CallID that we can refer to about this error?
fascinating-indigoOP•6d ago
Summary
On PHONE CALLS (also reproducible on web calls), when my assistant invokes a Query Tool, the tool completes successfully, but the assistant stays silent until the caller says something. In CHAT it works fine; the next assistant turn happens immediately.
Call IDs :
- 13e9a7e4-2499-4bd8-bce9-8dd409ed225e
- 770ec36d-273f-4c6f-8b68-bf14d4c221da
Expected
Query Tool completion should force the next assistant turn and speak the result immediately on calls.
Actual
Tool returns ✅ “Completed successfully”, then no speech until the caller says “Okay/I’m ready,” etc.
Repro (phone/web)
1) Caller: “fault code 17/13”
2) Assistant triggers Query Tool
3) Tool finishes with result card
4) Assistant remains silent until caller speaks
What I tried (no lasting fix)
- Tool Messages: Request Start = Default / None / Custom; Request Complete = None / Custom
- Toggled “Wait for message to be spoken before triggering tool call”
- Start Speaking Plan: Wait 0–0.5s; Smart End-Pointing with LiveKit and with Vapi
- Prompt explicitly says to speak immediately after tools
- Forced “speak on tool complete” → still didn’t fix for phone calls
Workaround (not a fix)
Changing Request Start from a prompt to a declarative line (removing “Let me know when you’re ready?”) helps, but I still need a platform-level resolution so phone calls behave like chat.
Request
Please confirm intended behavior (tool completion should force the next assistant turn on calls) and advise a fix or setting so the assistant speaks immediately after tool completion on PHONE calls. Happy to provide screen recordings if needed.
fascinating-indigoOP•6d ago
Summary (refer to images below)
On PHONE CALLS (also reproducible on web calls), when my assistant invokes a Query Tool, the tool completes successfully, but the assistant stays silent until the caller says something. In CHAT it works fine; the next assistant turn happens immediately.
Call IDs :
13e9a7e4-2499-4bd8-bce9-8dd409ed225e
770ec36d-273f-4c6f-8b68-bf14d4c221da
Expected
Query Tool completion should force the next assistant turn and speak the result immediately on calls.
Actual
Tool returns ✅ “Completed successfully”, then no speech until the caller says “Okay/I’m ready,” etc.
Repro (phone/web)
1) Caller: “fault code 17/13”
2) Assistant triggers Query Tool
3) Tool finishes with result card
4) Assistant remains silent until caller speaks
What I tried (no lasting fix)
Tool Messages: Request Start = Default / None / Custom; Request Complete = None / Custom
Toggled “Wait for message to be spoken before triggering tool call”
Start Speaking Plan: Wait 0–0.5s; Smart End-Pointing with LiveKit and with Vapi
Prompt explicitly says to speak immediately after tools
Forced “speak on tool complete” → still didn’t fix for phone calls
Workaround (not a fix)
Changing Request Start from a prompt to a declarative line (removing “Let me know when you’re ready?”) helps, but I still need a platform-level resolution so phone calls behave like chat.
Request
Please confirm intended behavior (tool completion should force the next assistant turn on calls) and advise a fix or setting so the assistant speaks immediately after tool completion on PHONE calls. Happy to provide screen recordings if needed.
Hello,
Thanks for patiently waiting and we are truly sorry for the delay.
We are still looking onto this and we will get back to you once we have answers.
We really appreciate your kind understanding.
Thanks for patiently waiting and we are truly sorry for the delay.
We are still looking onto this and we will get back to you once we have answers.
We really appreciate your kind understanding.