Hi Team, I have a question regarding concurrency limits. Is the concurrency limit applied per account (total active calls) or per campaign? For example: We have 20 concurrency limit on our account. If we start a campaign with 24 calls, how will VAPI handle this? Will 20 calls start immediately and the remaining 4 wait in queue? Or is the limit calculated per campaign? Please clarify how concurrency is enforced. Thank you!

Vapi enforces concurrency limits per account, not per campaign. If your account has a 20-call concurrency limit and you launch a campaign with 24 calls, only 20 calls will start immediately; the remaining 4 will wait until a slot is free. Example API response snippet:

json
"subscriptionLimits": {
  "concurrencyBlocked": false,
  "concurrencyLimit": 20,
  "remainingConcurrentCalls": 0
}

You can monitor and manage concurrency using these fields in your call responses. For more details, see the [Vapi concurrency documentation](https://docs.vapi.ai/calls/call-concurrency). Source: - [Understanding Call Concurrency](https://docs.vapi.ai/calls/call-concurrency)

If your account has a 20-call concurrency limit and you launch a campaign with 24 calls, only 20 calls will start immediately; the remaining 4 will wait until a slot is free. You can check the details in the [VAPI concurrency documentation](https://docs.vapi.ai/calls/call-concurrency).

Concurrency limits are enforced per account, not per campaign. This means the limit applies to the total number of active calls across all campaigns. If your account limit is 20 and you try to start 24 calls, only 20 calls will start. The remaining calls will wait until a slot frees up (or may fail, depending on your setup). There’s no separate concurrency allocation per campaign. Hope that clarifies how it’s enforced.