Concurrency
How many calls can run at once, how fast campaigns start new calls, and calling windows.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
Concurrency is the number of live voice sessions your account can run at the same moment. It is counted across every agent, campaign and API triggered call in your organisation.
Account wide concurrency
On Xebit VoiceCloud, the concurrent call limit is set by your plan and shared by all agents, campaigns and API sessions in the organisation.
| Plan | Concurrent calls |
|---|---|
| Trial | Not allowed |
| Base | 1 |
| Professional | 4 |
| Enterprise | Custom |
Trial accounts cannot place calls. Move to a paid plan to start voice sessions.
On Xebit VoiceKit, Xebit does not impose these figures. Limits are set by your own deployment: the infrastructure you run it on and your licence band. Your platform team sets them as part of the deployment.
Campaign pacing
For high volume outbound campaigns, Xebit paces how quickly new calls start so your carrier trunk stays stable.
- Maximum start rate: 10 new calls a minute.
- Maximum start rate: configured in your deployment; size it to what your SIP trunk and carrier accept.
- Queuing: once you reach your concurrency limit, further calls wait in a
pendingstate and start one by one as live calls finish.
Regional compliance
Outbound working hours
Outbound campaigns run only inside the calling windows you set: the days and hours calls may go out, in the contact's local time. Set them to match the rules that apply to you and your customers, such as TRAI rules in India and your own compliance policy. Calls scheduled outside a window are held and released when the next one opens.
On Xebit VoiceKit, defaults for calling windows can also be set for the whole deployment.
Do Not Disturb and consent
Xebit calls the numbers you send it. Checking numbers against Do Not Disturb preferences, recording consent, and registering your calling numbers and call types with your carrier are your responsibility and your carrier's, so scrub lists before you send them. A call that Xebit blocks for an account reason, such as insufficient balance, produces a call.disallowed event instead of a call. See Outbound Webhooks and TRAI calling rules for AI voice agents.