Phone injection with Assistant ID does not work
# support
n
When initialize a phone hook so that it does prompt injection at the start of the call, I have found out that if you setup the phone PATCH with the desired assistant ID, that server is not called and the variables are not injected. However, if I do NOT hook up an assistant ID through that PATCH request and instead just forward the desired assistant ID when that particular beginning of call injection is called, it works fine. What is the reason for this? Refer to
5ff66bc4-0a4d-451a-9301-7826fe2d8482
for an example of the ID being set, but not getting the prompts, and refer to
0840fce0-6bb8-4957-bdbb-a5ddfc5befc4
for an example of it being correctly injected (but no association between the phone id and the assistant id in the Vapi setup). I believe this may be a bug? Either way it is annoying to not have direct associations that we can set, and instead we have to manage those ourselves.
c
Hey Noah Vandal, Thank you for reaching out. Please note that our team does not operate over the weekend. We’ll be back in the office on Monday and will dive straight into your issue then to determine the best way forward.
n
Thank you~
!
c
Hi, could you please provide a call id where you experienced this issue? We would like to review the logs to identify the cause.
n
I provided two call ID's in the example description
Can you refer to those?
c
Hey Noah Vandal, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!
Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team