Yep, this is a pretty common gotcha with VAPI and ...
# general-english
j
Yep, this is a pretty common gotcha with VAPI and 5.1/5.1x you’re not imagining it. What usually happens is the model treats the tool call as the “final” action, so once the tool returns, VAPI thinks the conversation is done and drops the call. The pain point is that control never comes back to the assistant unless you explicitly send a follow-up assistant turn after the tool result. Are you currently returning an assistant response after the tool runs, or just letting the tool response be the last message? @Sean
2 Views