@anyhero I'm happy to clarify how the concurrency limit works and assist you with your queries: 1. The concurrency limit does not queue outbound phone calls by default. Instead, it restricts the number of simultaneous calls that can be made. If the limit is reached, additional call attempts are typically rejected or fail. To see what calls have been affected, you would need to check your call logs or use monitoring tools provided by VAPI, which can give you insights into call attempts and their statuses. 2. To get information about calls hitting the concurrency limit, you can use webhooks or API endpoints that provide call status events. While Server-Sent Events (SSE) are not directly supported for this purpose, webhooks can be configured to send real-time notifications to your server when certain call events occur, including when a call is rejected due to concurrency limits. 3. Removing the concurrency limit entirely may be possible with an on-premises deployment, as you would have more control over your infrastructure and could scale it according to your needs. However, this would depend on the specific capabilities and configurations of the on-premises solution provided by VAPI. You would need to discuss this with the VAPI enterprise team to understand the feasibility and any potential implications for your system. If you need further assistance or have more questions about these topics, please let me know!

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

Got it. Tagging @User for additional help.