Manage DialNexa Call Concurrency

DialNexa call concurrency is the number of calls your workspace can run at the same time. Open Workspace Settings > Call capacity to review guaranteed capacity, reserve lines for inbound calls, limit total simultaneous calls, or purchase additional capacity.

​

When To Change Call Concurrency

Use concurrency settings when outbound activity must leave room for incoming calls, or when you need to control simultaneous call volume. A concurrency limit controls how many calls run together, not their duration or the total number of recipients in a batch.

​

Before You Begin

Confirm the active workspace and review its current settings. For a purchase, check the wallet balance, price, available quantity, and renewal terms displayed by the dashboard. Rates and available capacity can change; use the live preview before confirming payment.

​

Review Your DialNexa Call Concurrency

​

Read The Capacity Bar

The bar separates lines held for inbound callers, guaranteed capacity available for outbound calls, and hatched capacity that depends on spare platform capacity. Hatched capacity is not an additional guarantee. With an unlimited ceiling, the open end does not represent a fixed number of available calls. When you edit the settings, compare the preview with the saved configuration before clicking Save settings. Use Discard changes to restore the saved values. The preview does not apply a configuration change by itself.

​

Reserve Inbound Capacity And Set A Ceiling

1. Open the Your concurrency card.
2. Set Inbound reserve to the whole number of lines to hold for inbound callers at all times. This cannot exceed your guaranteed concurrency.
3. Optionally set Dynamic inbound reserve as a percentage of running outbound calls. Leave it blank to turn it off. The dashboard accepts whole numbers from 0 to 100 percent.
4. Set Concurrency ceiling to a positive whole number, or leave it blank for Unlimited.
5. Click Save settings and wait for the success message.

The fixed and dynamic reserves apply together, with the larger reserve taking effect. They are not added together. Outbound campaigns cannot use the reserved inbound capacity. Review any warning that a fixed reserve makes the dynamic setting ineffective at your chosen ceiling.

​

Purchase Or Release Extra Concurrency

In Add more concurrency, use the plus or minus buttons to choose your target purchased quantity. This is the total quantity you want to retain, not just the number of new slots. For an increase, the preview shows Charged today for the remaining days of the current month and the recurring monthly total. Review both before clicking Pay. The payment comes from the workspace wallet, and renewal is billed on the first of the month. Reducing the target quantity releases the difference immediately when you confirm Release concurrency. The dashboard states that the current month is not refunded; the reduced monthly amount applies from the next renewal. Review the impact on capacity before confirming a reduction.

​

Verify The Result

After saving settings or completing a purchase, check Your concurrency and the configuration fields again. Reload the page to confirm the saved values. For a purchase, also review the wallet transaction history before retrying an uncertain payment.

​

Outbound Call Start Rate And Concurrency

Calls per second (CPS) measures how quickly new calls start. It is separate from concurrency, which measures calls running at the same time. Extra concurrency does not remove a provider’s call-start rate limit. DialNexa paces outbound Plivo requests independently for its US and India provider accounts: 2 CPS for the US account and 3 CPS for the India account. US and UK number routes use the US account; other country routes use the India account. These are shared account limits, not a guaranteed rate per workspace or per number. A busy account can delay new calls while another account continues dialing. Single calls, retries, and batch calls share the relevant account allowance as well as workspace and platform capacity. If calls wait despite spare concurrency, review the selected route, batch status, calling hours, and retry schedule before increasing purchased capacity.

​

Troubleshooting Call Concurrency

​

Related Pages

• Workspaces
• Billing and wallet
• Batch call retries and statuses