@O_XiNDa It's great to hear that you're using VAPI for your voice application needs. I understand that you're curious about how call queuing works in relation to the concurrency limits. VAPI does indeed have a call queue system in place to handle requests that exceed your concurrency limit. When you initiate more calls than your current limit allows, the excess calls should be queued by VAPI rather than rejected outright. This queue is managed internally to ensure that calls are processed as slots become available within your concurrency limit. If you're experiencing immediate rejections of calls beyond your concurrency limit, this is not the expected behavior. It's possible that there may be a configuration issue or another factor at play. I would recommend reviewing the API documentation and ensuring that your implementation aligns with the expected queuing behavior. If everything seems correct on your end, it might be beneficial to reach out to VAPI support for a more detailed investigation into your specific case. In the meantime, if you have any other questions or need further clarification, please feel free to ask.

You can continue this conversation by mentioning me in the message.