raise the 5 second limit
# supporti
isaiahbuilds
01/04/2025, 6:12 PMon inbound calls, there is a 5 second limit for my server to return assistant details before VAPI gives up. Is there anyway to change this? we are trying to build on top of vapi, but there is alot that happens when an inbound call comes in 3-4 separate API calls to different parts of our CRM, and a step to assign a calendarID for our booking functionality. Personally it would be a lot better for us if a customer waits for one more ring (10 seconds) before the assistant picks up the phone than having to pick up the phone before the contact details are all set up.
Is there a way I can modify this myself? If not, any chance we can get that limit raised?
v
Vapi
01/04/2025, 6:14 PMmessage has been deleted
Vapi
01/04/2025, 6:14 PM@isaiahbuilds
I understand the importance of ensuring that all necessary steps are completed before the assistant picks up the phone. Currently, the 5-second limit for your server to return assistant details is a preset timeout within VAPI's system to ensure a timely response for inbound calls.
Unfortunately, as a support bot, I don't have the capability to change this timeout setting directly. However, I can suggest a couple of potential solutions:
1. **Optimization**: Review and optimize the API calls and processes that occur when an inbound call is received. This might involve caching frequently accessed data, streamlining the API call chain, or using more efficient queries to reduce the response time.
2. **Asynchronous Processing**: If possible, handle some of the processing asynchronously. For example, you could immediately return a default assistantId to VAPI and then continue with the CRM operations and calendarID assignment in the background.
3. **Contact Support**: If the above solutions are not feasible, you may need to contact VAPI's support team to discuss the possibility of increasing the timeout limit. They might be able to offer a custom solution based on your specific use case.
Would you like me to assist you with any of these suggestions, or is there anything else I can help you with?
Vapi
01/04/2025, 6:14 PMYou can continue this conversation by mentioning me in the message.
Vapi
01/04/2025, 6:15 PMGot it. Tagging @User for additional help.
i
isaiahbuilds
01/04/2025, 6:22 PMok, i will await a response from @User
v
Vapi
01/04/2025, 6:23 PM@isaiahbuilds
Please ask support for more info on this.
s
Shubham Bajaj
01/04/2025, 7:04 PM@isaiahbuilds We have a total of 15 seconds to answer a call: 7.5 seconds are required to set up the call infrastructure, and the remaining 7.5 seconds are allocated for selecting which assistant to use for the call.
c
Chowderr
01/04/2025, 7:05 PMWhy do 4 separate API calls happen if the information is in the CRM? They are not attached to the contact?
i
isaiahbuilds
01/04/2025, 7:05 PMthanks for the response. i asked the vapi bot in the dashboard and it said i have 5 seconds to respond. do i really have 7.5 seconds to respond?
s
Shubham Bajaj
01/04/2025, 7:08 PMYes you have 7.5 seconds
Shubham Bajaj
01/04/2025, 7:08 PMto answer server request.
i
isaiahbuilds
01/04/2025, 7:10 PMI know right? The api we are constricted to is not the most intelligent setup.
we have to search by phone number, this will return contactID, then we search by contactId but this only returns standard fields, then we have to get custom fields for the account at a different endpoint and match them up. and during that process we rely on an automation in the CRM to assign a calendar ID to the contact, so we may have to pull custom fields a second time, before we can have a viable prompt to send to vapi.
isaiahbuilds
01/04/2025, 7:10 PMThank you! 7.5 is doable. 5 is risky. Thank you for clarifying.
c
Chowderr
01/04/2025, 7:10 PMDam that sounds kind of terrible for a CRM. Yo ucan't search a contact by phone or email and all of that information appear?
i
isaiahbuilds
01/04/2025, 7:11 PMlol you would think. not very well organized.