The team never got back to me about inbound concurrency. If the limit is reached before we're able to reserve more lines, do calls start dropping or do calls over the concurrency limit become more expensive per minute? Scaling across multiple businesses right now that have their own end customers.

When your Vapi inbound concurrency limit is reached, additional calls are not processed immediately—they may be rejected or queued, depending on your setup. The per-minute cost does not increase for calls over the limit; pricing remains the same even after high usage. To avoid dropped calls, implement a call queue (e.g., with Twilio) to hold excess calls until capacity is available. Example:

js
// Place incoming calls in a Twilio queue when concurrency is maxed out
if (activeCalls >= MAX_CONCURRENCY) {
  // Add call to queue logic here
}

For more details, see the [Vapi call queue management guide](https://docs.vapi.ai/calls/call-queue-management). Sources: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management) - [Vapi Pricing](https://docs.vapi.ai/pricing) - [Vapi Billing: Estimating Costs](https://docs.vapi.ai/billing/estimating-costs)

Our team released a fix for the concurrency limit issue yesterday. Could you please give it another try and let us know if you still experience any issues? Thanks for your patience!