We created an assistant on Vapi, and normally it was working good, but from past couple of days, in some calls the assistant stops talking to the caller and the call ends via silence time out. Here're one of call details so that you guys can have a look at it - Call ID: 6a79e9bc-1a01-4b5a-918d-e9daf7d0c737 - It stopped talking from time stamp: 1:54 - The assistant stopped talking to the caller, and finally it silenced time out. - Basically the assistant should follow the script and talk to the user Please take a look at it, and let us know what could be done to avoid these type of calls

Hello Prince, could you please make another call? OpenAI made some changes that resulted in call failures. The issue was eventually fixed within an hour on the 15th, so please try making another call.

Hi Shubham, Yeah, recently we haven't faced that problem. But, today we encountered a new little issue, It's changing the voice to male to female all of a sudden. Is it a glitch? And also most importantly we're sometimes getting this reason for call ended "Twilio connection failed" Thank you

Hi @PrinceUstad / @Shubham Bajaj, any solutions on this? We've found we are experiencing this on a large amount of our calls too: d08f0c44-2eb1-4d08-b7e7-bcac72f89aee 901ba535-8247-4b00-afb2-e6ce3d17472e 1ad0b301-d5f9-45bb-8612-bf84b22ec95c

@princeustad To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

Hi @Shubham Bajaj, Here're the details you asked for Issue 1: The voice agent is changing the voice - Call ID: 4b91ad14-ca36-4034-9f73-679897a4ac96 - Until 2:48 it talks in the voice that we gave, then there's a little silence as it's running a tool, then around 3:00 it starts talking in a female voice - The issue is it shouldn't change its voice to a female voice. - We expect it to continue the whole conversation with the voice we gave to it. Issue 2: It's greeting the user 2 times(which is not in the script) - Call ID: 99cbdaa1-4f36-46d9-947f-c1b92e378e7f - around 0:04 it greets the user for the first time, and again at 0:11 it greets the user, it makes the agent too robotic, and the first impression of the caller is a little damaged - We expect the Voice agent to greet the user only once - This issue doesn't occur always, this happens once in 50 calls we make, but we expect this never to occur. Issue 3: Recently we've been getting 'Twilio Connection Failed' as the end-call reason - Call ID: d0ac96d9-2c62-44e3-bd40-b5cdb50c49f5 ed166cd0-b010-4acb-aca5-d7fe6a3a7724 202c8175-9e29-4a5e-bd49-4b5fd877487c - In the above calls we're getting this issue, those are only 3, we got this error all our calls done with a specific number - We use 5 different numbers, and one number is giving this issue, all the calls we're using that number for, are returning this ending reason - This is the Phone Number ID: a9a96f8d-b685-4e2e-b854-0a0303167c65 Please have a look into the 3 issues mentioned above. Thank you

Any update on this @Shubham Bajaj ?

Hi @Shubham Bajaj, Is there any update on this? Thank you.

Hi @Shubham Bajaj , could we please get an update on Assistant "pausing" or going "silent" during call. Call ID: d08f0c44-2eb1-4d08-b7e7-bcac72f89aee Timestamp: 00:07 What happened: Assistant went silent and did not answer customer for the rest of the call What we expect to happen: Assistant to answer customer. This has happened on a number of other calls: 901ba535-8247-4b00-afb2-e6ce3d17472e 1ad0b301-d5f9-45bb-8612-bf84b22ec95c

@PrinceUstad Looking into your calls.

Hi @Shubham Bajaj, Just wanted to ask if there's any update on the issue Thank you

Call ID: 4b91ad14-ca36-4034-9f73-679897a4ac96 🔵 18:30:46:385 [user CHECKPOINT] Voice fallback triggered 11labs flash model has few hiccups soit's best to use turbo model for now, and during the call it failed so voice fallbacked to cartesia. Call ID: 99cbdaa1-4f36-46d9-947f-c1b92e378e7f Although AI systems are not flawless, you can anticipate that they will function effectively for approximately 90% of the time without encountering any issues. Therefore, it is advisable to disregard this concern for the present. **Call ID: d0ac96d9-2c62-44e3-bd40-b5cdb50c49f5 ed166cd0-b010-4acb-aca5-d7fe6a3a7724 202c8175-9e29-4a5e-bd49-4b5fd877487c** 🔵 16:12:57:601 Call

ed166cd0-b010-4acb-aca5-d7fe6a3a7724

Waited 300s But Transport Never Connected. 🔵 16:13:02:291 Call

202c8175-9e29-4a5e-bd49-4b5fd877487c

Waited 300s But Transport Never Connected. All of these calls were never connected, as you have mentioned it is happening for a single number I suggest check with twilio team for this because they know what upgrade or anything else need to be done for your phone number.