Do you have documentation on managing the concurrency limit for inbound calls? Specifically, if our limit is 30 calls, what steps should we take when the 31st call comes in to ensure the client waits for a call to finish before being attended to by a VAPI assistant?

@Yoann C. Absolutely! To manage the concurrency limit for inbound calls, you would typically set up a call queue. When the 31st call comes in and your limit is 30, the call would be placed in the queue. Once one of the ongoing calls is completed, the next call in the queue will be automatically routed to a VAPI assistant. To ensure this process is smooth, you should configure your system to handle call queuing and specify the behavior for calls that exceed the concurrency limit. This might involve setting up hold music, announcements, or estimated wait times to keep the client informed while they wait. If you need to adjust your concurrency limit or implement specific features for call queuing, you may need to contact our support team to discuss your account's capabilities and any additional configurations that might be necessary. Would you like me to assist you with any specific configurations or get in touch with our support team for more detailed guidance?

@Vapi I would like more information about the configuration to handle call queueing. At the moment we used our Twilio phone numbers in vapi

@Yoann C. as of know we don't have the feature to ask for what to do if the limit is reached and hence calls are dropped. You have to manage limit progress at your end can use help telephony provider to route 31st call.

I would like more help from you. What would be the best way to manage these inbound calls ? The inbound calls should arrive directely to our Twilio Calls? And manage the POST API Call ?

@Yoann C. can you be clear here do you want to manage inbound calls concurrency limit or batch call scheduling?

Inbound calls concurrency. We will make available a phone numbers to our customers to contact our bots.

By default you can do 10 simultaneous calls, and currently there is no logic or api exposed from Vapi to get the live concurreny number. You have to track it on your own, you can use the status-update server event to identify if call has ended and update your numbers accordingly.

is there any way to increase this concurrency limit? Different subscription plan perhaps? We really like vapi and are exploring our options for building out voice agents as part of our AI saas software however we've noticed a lot of our competition has concurrency limits around 100 or none at all making 10 kind of low.

Yes @isaiahbuilds concurrency limit is applied accross the account.