Dear VAPI Support,
I am currently testing a new voice agent (Agent ID: 10bcb465-89d9-4e90-8468-4f7d7a4724cf) and have encountered a recurring issue. More often than not, calls show a 201 status in the HTTP request, indicating that the call has started, yet no actual call is placed to the designated phone number.
Despite this, the backlog suggests that a call did occur, although in reality, it did not. Additionally, I am being charged for these non-existent calls—often 10 times the normal rate—due to apparent conversational data that does not exist, as shown in the transcript and analysis.
To summarize:
Calls are not reaching the intended phone number.
Your system indicates they did, leading to incorrect billing.
I am being charged for interactions that never happened.
Here are five examples of affected calls:
Bd475de2-ff72-4a98-afa8-1a10292700e9
E775ec72-40ae-4939-8abe-38c5ca3ad1b3
6c352ea7-957c-4387-9808-b31a25a2aa6f
Bc7f390d-3df3-4d98-8e77-32e8fde93e3b
83e5837b-e96f-4062-94cb-2f808e902ac2
Analysis from one of the non-existent call (e775ec72-40ae-4939-8abe-38c5ca3ad1b3):
The call appears to be a confusing and largely incoherent conversation between an AI assistant named Aneta and a user speaking in broken Czech and nonsensical words. The AI repeatedly tries to understand and offer help, but the user's responses are mostly unintelligible, making it difficult for the AI to provide meaningful assistance.
Please advise if I am misconfiguring something or how this issue can be resolved.
Best regards