I have a platform im working on, and it gets context about the person whos calling from a database , by looking up the phone number attached to that person whos calling . Currently i have it set up so outbound calls, have a proper assistant override and can process contextual contact lookup. Inbound, i can figure out with a tool call. But i'm trying to remove the tool call from being required to decrease the knowledge barrier to initiate this for regular clients. Is there a way to webhook the information whether its during the call, or before the call reaches vapi by intercepting the twilio webhook, then forwarding the call to vapi after overriding some context / passing context? tl;dr - i need to add phone number lookup context for inbound calls, and would like to know if you have any ideas

mine just aburptly ends in the middle of conversation is this a limit that's part of setting am missing? https://cdn.discordapp.com/attachments/1395468718859092088/1395539543515467948/image.png?ex=687ad0fb&is=68797f7b&hm=86c0900301e64a65576c95e6b3e2c406572e19245b524506527f55696fdaa525&

wrong place to post this

To set up inbound calls without requiring a tool call and instead use webhooks, you can configure your inbound call setup to leverage server-side processing instead of a predefined tool within the assistant. Here's a basic approach: 1. **Webhook Setup**: Configure a webhook in your server to handle incoming calls. 2. **Respond to Assistant Request**: When an inbound call occurs, your server can directly query your database using the caller’s phone number to fetch context or contact information. 3. **Return Context**: Use this context to form a JSON response back to the assistant, allowing it to use this information in its interaction with the caller. You can adapt this setup from the "Inbound Call Configuration" outlined in the [Configuring Inbound and Outbound Calls for Squads](https://docs.vapi.ai/squads-example) document. This provides flexibility in handling dynamic information without an upfront tool call. This setup would reduce the initial complexity for your regular clients, as most of the heavy lifting would occur on the server-side via webhooks.

Respond to Assistant Request: When an inbound call occurs, your server can directly query your database using the caller’s phone number to fetch context or contact information. - can you please explain how? i've tried this before but it didnt pass the information to the assistant after the inbound call was in place . Webhooks for calls are active and properly pointing to my server , just not entirely sure the route to take to allow for context to be passed in real time Return Context: Use this context to form a JSON response back to the assistant, allowing it to use this information in its interaction with the caller. - this can be sorted - i just dont know the exact way to allow the assistant to retreive the informations instantly

Hey Jr, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!

thx

how about outbound calls. How come it won't let me launch? What's causing https://cdn.discordapp.com/attachments/1395468718859092088/1397535349009551411/image.png?ex=688213b8&is=6880c238&hm=40caa09219d411ee282f91748f077890d2320f2c98df4471d07b7d06078aa3e9&

@Shubham Bajaj @Kings_big💫

On inbound calls, respond to Vapi’s assistant-request webhook within ~7 seconds by querying your database using the caller’s number and returning a squad JSON with a personalized firstMessage, enabling the assistant to start the call with full context, no tool call needed..

can you point me to docs page of this if possible

i'm not understanding how to use this. Where does the squads come into play?

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

this was resolved outside VAPI but through MAKE\

Glad it fixed