Hello, The phone number (id 5ebae207-3a18-4e4b-ade1-27287da15d7b) sometimes just gets detached from the assistant (id fb43cf9f-8ce1-434f-9d6c-d861944f8cee) OrgID: 4dd2575c-dec3-4d2f-bc73-63e885ad533c Please let me know if you can see it in the logs and the possible reason.

hey harter, not sure if I understood your question correctly. Do you mean that you assistant is getting detached even though you are not doing anything?

that is correct

Hey @Harter I don't see anything related to this. Do you mind sharing a Loom video displaying the detachment of the assistant?

Hey @Shubham Bajaj, not sure how to record this. It happens like this: The phone is attached to the assistant, and I’m able to call the assistant. After some time, when myself or my clients try to call to the assistant again, it can’t be reached. I check the phone ID using the API call, and I see that no assistant is attached to it. I attach it again — this keeps happening from time to time with the assistants (not just one of them)

In order to proceed with escalation, we require a loom recording to investigate this issue that you are describing. Is this happening on dashboard or API specifically?

I attach an assistant to the phone number via an API call. I can't see the number in the dashboard. Seems like only 100 numbers are shown and there is no pagination. I'd be happy to record a loom for you, I'm just not sure how to capture the issue. Like I said, the assistant gets detached in a random moment. Are you able to review the logs for a particular phone number, or an assistant to investigate the issue?

Yes, so if you record your screen, make a change to an assistant, then make a call with the change we can review the logs to see if anything changed between you making the call and us reviewing the logs as we have video recording proof.

Hi, today I experienced the same issue, with with same phone number and assistant. On may 25 I recorded this for you: https://www.awesomescreenshot.com/video/40179029?key=7e3ebe3f7cd9dcd118de12693682991d Today the assistant wasn't attached to the number. We got it attached again with an API call. Please view the logs for the phone number to see in which way the assistant got detached again. Reminder: The phone number id: 5ebae207-3a18-4e4b-ade1-27287da15d7b The assistant id: fb43cf9f-8ce1-434f-9d6c-d861944f8cee OrgID: 4dd2575c-dec3-4d2f-bc73-63e885ad533c I hope to hear from you soon.

I looked into the shared video, but I don't see you are able to describe the behavior of automatic de-attachment of the assistant from the phone number. You showed me a few GET requests. For now, I have attached the assistant_id to the shared phone number_id. In case it gets automatically de-attached or if you are able to reproduce this, please share a Loom video for it.

Thank you Shubham, Well, if you had to attach the assistant to the phone number, it probably already got detached. I'll keep an eye on it anyway. Just to clarify: 1. This is not the only our assistant that gets detached from the phone number. 2. I'm not a tech person, so I may not know how to describe the issue more clearly. I can't record a loom of an assistant getting detached from a phone number because I can tell it got detached only when I call the assistant and it doesn't work. If there a way to record how the issue is happening, please share.

Can you please check the API logs which can be found under the observe section to see all the logs related to it?

I could't find any records related to this phone number. What information should we provide you with to get this issue resolved or investigated?

logs

🔵 19:45:12:675 \[Postgres\] Querying

phone_number

(connection# 950)... Query: UPDATE phone_number SET "assistant_id"=$1, updated_at = date_trunc('milliseconds', NOW()) WHERE org_id = $2 AND id = $3 RETURNING \* Parameters: \[ null, "4xxxxc", "5ebaxxxx5d7b" \] Param Types: 0,0,0 2025-05-19T19:45:12.675Z Hey Harter! As you can check in the above call logs, you are making an update request to set the phone number assistant to null. Which technically removes or deattaches the assistant from the phone number. So it is coming from your side, not from our side. So I suggest you kindly take a look where you are looping your phone number and who has access to the API keys to resolve your issues. Let me know if you require further help or have more questions

Thanks you!

Hello Harter, Please share your organization ID so I can investigate your claim. Also, record a Loom video showing that only half of the phone numbers in the dashboard are associated with the Assistant, and the other half are not which are only accessible through the API. This information will help me reproduce the issue or find the bug. Thanks for your observations. I'm eager to resolve this and prevent similar issues in the future, If this Exisits !!

Thanks for your reply! The organization id is 4dd2575c-dec3-4d2f-bc73-63e885ad533c the video: https://www.awesomescreenshot.com/video/40621383?key=909d68132ba20c5b3e2847a2a953022b Please let me know if you need more info @Shubham Bajaj

Hello Harder, I have received your Loom video and your organization ID. I have not yet begun working on your claim and will review it once I have started. I will notify you when it is resolved and provide my next comments. Until then, this ticket is open with me under the investigating status.

Done. Assigned assistant id "2b529a45-695c-4ca6-b079-4b2a7825db60" with the phone number "id": "84e8d435-1ee1-45a4-89fa-aaea364807b8", "number": "+1 (813) 859 6023", which is not visible inside the dashboard. Please take a look and let me know what you see. Thanks!

Hey looks like the above assistant_id is incorrect. This is the correct assistant_id 4d1025ed-14de-42cd-b3a2-d67c9a5f4466 used for this phone number ID 84e8d435-1ee1-45a4-89fa-aaea364807b8. https://cdn.discordapp.com/attachments/1374072784300412938/1382089852052574358/image.png?ex=6849e2fa&is=6848917a&hm=338f55e127c856ee63ee470d1206671c7fc174253dc904a31f9f69c236b217f3&

You're right, the correct assistant id is 4d1025ed-14de-42cd-b3a2-d67c9a5f4466. I watch the assistant to see when it gets detached.

Let me know if you found anything.

The assistant id: fb43cf9f-8ce1-434f-9d6c-d861944f8cee got detached from The phone number id: 5ebae207-3a18-4e4b-ade1-27287da15d7b I re-attached it less than a week ago. Please look into this case. Thanks!

Hey Harter, thanks. Looks like it's a deep issue. I have to find out the source - which is wrongly updating these phone numbers. For sure, it isn't coming from our side (looking at the call logs and everything). There are people who are using more than 100+ phone numbers, and I'm hearing about this from you only. I'll see what's getting wrong here and then get back to you.

Can you share the api call logs for that particular case we're investigating? The assistant id: fb43cf9f-8ce1-434f-9d6c-d861944f8cee got detached from The phone number id: 5ebae207-3a18-4e4b-ade1-27287da15d7b Or show me how I can look at the api calls for this particular phone number from the dashboard? It seems like the current vapi's filtering system doesn't allow me to do that @Shubham Bajaj @User

DM'ing you logs.

@Harter If you don't mind reproducing this issue, can I join your organization? - I'll create a phone number and then assign it the assistant_id. - If this changes, it means the issue is on our side. Let me know what you think!

sure, what email should we add to the organization?

check your DM.

Invite sent

Thank you for the invite. We will proceed with the testing and will let you know next steps

Not sure what changed, but that stopped happening. Thank you for your help! We can close the ticket.

Marking this ticket as Solved ✅