Concurrency
Every workspace has two call limits that protect system stability and call quality. They matter most when you plan outbound volume or troubleshoot 429 responses.
Workspace limits
Legacy workspaces are on the earlier Pro, Growth, and Agency plans, which came with a fixed concurrency limit and a default CAPS limit. These plans are no longer sold, and existing workspaces keep their limits.
Subaccounts do not get their own limits. All subaccounts share the main account’s total.
Over-limit behavior
When you reach a limit, extra calls either return an HTTP 429 error or wait briefly in a queue, depending on your account setup.
For an Enterprise or account-managed deployment, agree on expected volume, queueing behavior, and limits with Synthflow before launch.
Custom limits
Enterprise and account-managed customers can request higher concurrency or CAPS limits. Contact our sales team with your expected volume.
FAQ
How do I avoid hitting the CAPS limit when calling a large list?
Use Campaigns. A campaign dials within your concurrency limit instead of sending requests to the API, so it is the safest way to work through a long list. Set reserved_concurrency to keep slots free for inbound calls and one-off calls.
If you start calls yourself from GoHighLevel, HubSpot, Zapier, or another automation tool, add a 1-second delay between calls. That keeps you within the default CAPS limit.
Can I monitor my current usage?
Yes. Your dashboard analytics show active call counts. If you call the API, track 429 responses, which mean you hit a limit.