Understanding Call Concurrency
Overview
Call concurrency represents how many Vapi calls can be active at the same time. Each call occupies one slot, similar to using a finite set of phone lines.
In this guide, you’ll learn to:
- Understand the default concurrency allocation and when it is usually sufficient
- Keep outbound and inbound workloads within your subscription’s concurrency limit
- Increase capacity with concurrent call line add-ons
- Inspect concurrency data through API responses and analytics queries
What is concurrency?
Usage only or your Success Package determines how many concurrent call slots your subscription includes. When all slots are busy, you cannot start an outbound call or accept an inbound call until a slot becomes available. See Pricing and Success Packages for the included limits.
These limits help keep calls reliable for every customer. You can increase concurrency by adding concurrent call lines to your subscription.
Managing concurrency
Outbound campaigns
Batch long lead lists into smaller chunks (for example, 50–100 numbers) and run those batches sequentially. This keeps your peak concurrent calls near the default limit while still working through large sets quickly.
High-volume operations
If you regularly need more simultaneous calls, compare the concurrency included with each Success Package or purchase concurrent call line add-ons.
Use billing reports to pair minute usage with concurrency spikes so you can upgrade before calls are blocked.
Increase your concurrency limit
Usage only and your optional Success Package determine the concurrency included with your subscription. You can purchase concurrent call line add-ons for more capacity. See Buy capacity add-ons. The Dashboard shows when the additional capacity takes effect before you confirm the purchase.
View concurrency in call responses
When you create a call with POST /call, the response includes a subscriptionLimits object that shows the current state of your account.
Example request
Example response snippet
Field reference
concurrencyBlocked—trueif the call could not start because all slots were full.concurrencyLimit— Total concurrent call slots currently available to your org.remainingConcurrentCalls— How many slots were open at the time you created the call.
Build monitoring around these values to alert when you approach the cap.
Track concurrency with the Analytics API
Use the /analytics endpoint to review historical concurrency usage and spot patterns that justify more capacity.
Example request
Example response
Adjust the timeRange.step to inspect usage by hour, day, or week. Peaks that align with campaign launches, seasonality, or support events highlight when you should reserve additional call lines.