Could you please review Call ID 7eeea680-5195-4205-8aba-832f478a45af, most of my calls nowadays have not been recorded properly. The caller voice overlaps with the AI and transcript is also recorded this way and it doesnt make sense. The call itself is fine but the recording overlaps.

Hey Ivy could you please provide me another call ID where this happened? This specific example seems like they're talking over the assistant, especially because the overlaps line up with interruptions and the transcription is filled with interruptions. Mind just providing me one more call ID so I can compare?

I have a similar issue @User , I am wondering if it's related

Hello Stu could you please create a ticket and I can help you out there.

Another call ID: efea5eb8-bba3-42b5-880c-27480403c94e

Could you share a recording, I'm interested to see if it sounds like mine. I tried on a non client account with a duplicate transient assistant and it work with no issues...

There are all inbound calls and because of this, the AI is responding wrongly. This is the reason why mine is not performing well. You are right all my outbound transient call did not have this issue.

In my setup I've used make.com with a server url, the server url responds to an inbound call with and assistant request and sends the transient to the caller. 1 client account same server url, is unable to follow the call, repeating missing transcript data, mad audio. 1 other account, same server url, same transient, works perfectly. Api key is only difference, seperate vapi accounts. Inbound agents. Phone numbers have the same server url, all phone based (no web)

Thanks Stu, for me. My inbound call is not using make.com. I only use make.com for my transient outbound calls (this one works perfectly)

No worries , I wss only highlighting the fact that the environment is the same across accounts ( nothing to do with make). My personal belief is it is to do with endpointing changes to the vapi internal architecture ( this is theoretical). This is the interupt between the assistant and the caller we hear in the recording

Hey guys, this is a known issue now and the engineering team is working on it! Thank you for bringing this to our attention.

@Mason how do i know when this is resolved, i need to give my client some kind of eta.. I have to make changes

same here

@ivy @~Stu~ CoreAspect.Agency Hey guys, the issue was related to the Twilio drift. The Twilio system was having some issues, which eventually causing the model output and audio to be mixed up. You can verify the same over the Twilio status page. Hopefully, the issue has been resolved by the Twilio team now, so you can continue your calls without any issues. Let me know if you have more questions or need further assistance.

@Shubham Bajaj is there a way to get visibility on drift monitoring? I am going to have to explain this to my client and find a way to mitigate future issues. I understand it's not a vapi issue, I'd just like to give them confidence I'm trying to put in backup solutions 🙂

As of now, there is no way to monitor drift apart from checking Twilio's status page. In case you require, I can share Twilio call logs with you which you can share with your client to keep them as an proof that it was from Twilio's side where you haven't done anything wrong. And to add on it, you can also share the Twilio call status page where it was visible that there was an ongoing issue.

Appreciated, I think what I'll do is let them know I'm going to purchase backup numbers from a seperate service so I can mitigate this in the future. It's a minimal cost to me and proves my capacity to provide backup solutions.

Hi Shubham thank you for that. Yes I would like to also get a twilio call logs? can you also share the actual name of the issue in the status page? I cant seem to find anything that mention drift monitoring