Skip to main content
Know how many calls you can handle simultaneously. Monitor utilization in real time, set up alerts for capacity limits, and scale before calls start queueing. What you’ll learn: Concurrency metrics, utilization thresholds, queue status, alerting setup, and scaling strategies.
Screenshots may differ from current UI version.

Understanding concurrency

Concurrency is the number of simultaneous active calls across your organization or agent. Each active call consumes one slot from your concurrency limit until it completes.

Key metrics

Definition: Percentage of concurrency capacity currently in use.Calculation method:
Performance thresholds:
Running at 100% utilization for extended periods degrades service quality. Calls queue longer, deadlines may expire, and inbound callers may abandon. Maintain at least 15-20% buffer capacity above typical peak usage.

View concurrency status

  1. Navigate to Dashboard home page
  2. View Active Calls section showing current utilization
  3. Color indicators:
    • 🟢 Green: Under 70% utilization
    • 🟡 Yellow: 70-90% utilization
    • 🔴 Red: Over 90% utilization
Monitor calls waiting in queue:

Concurrency metrics

Definition: Number of calls currently in Running status (actively connected and processing).Calculation method:
Typical range: 0 to concurrency limit. What high values indicate:
  • Peak usage periods
  • Bulk campaign in progress
  • Long average call durations
Definition: Number of calls waiting for an available slot to start processing.Calculation method:
Performance thresholds:
Definition: Time calls spend in queue before processing begins.Estimated calculation:
What long wait times indicate:
  • Insufficient concurrency for volume
  • Long call durations consuming slots
  • Bulk campaigns overwhelming capacity

Concurrency limits by plan

Limits vary by subscription plan:
Check your specific limits in Account SettingsBilling & Usage. Contact sales for Growth plan pricing.

What happens at capacity

When all concurrency slots are in use:
  1. New calls enter queue — Status changes to “Queued”
  2. Queue processed by priority — Higher priority calls processed first
  3. Calls start as slots free — First queued call gets next available slot
  4. Deadlines enforced — Calls exceeding deadline are auto-canceled

Impact on service quality

Priority during capacity constraints

Calls are processed by priority value (lower values processed first), then by deadline: Within the same priority level, calls closer to their deadline are processed first.

Monitor utilization

Track utilization for specific agents:
Analyze patterns over time:

Set up alerts

Export metrics for Prometheus monitoring:

Alert thresholds reference


Scaling strategies

Increase concurrency limits

Upgrade subscription tier:
  1. Navigate to Account SettingsBilling
  2. Click Upgrade Plan
  3. Select tier with higher concurrency
  4. New limits active immediately
Enterprise custom limits: Contact support for limits above standard tiers.
Distribute load across multiple agents:
Shorter calls free slots faster:
Avoid overwhelming capacity with large campaigns:

Best practices

Capacity planning

Load management

Alert configuration


Troubleshooting

Symptoms: Calls remain in Queued status for extended periods.Causes:
  • All concurrency slots in use
  • Agent disabled or outside business hours
  • Long-running calls consuming all slots
Solutions:
  1. Check current utilization — verify you’re at capacity
  2. Review active call durations — identify unusually long calls
  3. Verify agent is enabled and within schedule
  4. Increase concurrency limit or add agents
  5. Check for stuck calls in Running status that should have ended
Symptoms: Sudden increase in active calls not matching expected volume.Causes:
  • Bulk campaign started
  • Multiple systems scheduling simultaneously
  • Webhook retry storms
  • Inbound call surge
Solutions:
  1. Review recent call scheduling patterns
  2. Check if bulk campaigns started unintentionally
  3. Implement rate limiting in scheduling systems
  4. Stagger scheduled calls with delays
  5. Add capacity checks before scheduling
Symptoms: Regularly reaching 100% utilization.Causes:
  • Insufficient capacity for volume
  • Long average call durations
  • Poor load distribution
Solutions:
  1. Upgrade to higher tier for more concurrency
  2. Add agents for load distribution
  3. Optimize prompts for shorter conversations
  4. Set maximum call duration limits
  5. Implement application-level rate limiting
Symptoms: Some agents at capacity while others idle.Causes:
  • Fixed agent assignment
  • Uneven scheduling distribution
  • Different agent schedules
Solutions:
  1. Implement load balancing when scheduling
  2. Route calls to least-loaded agent
  3. Align agent schedules with expected volume
  4. Consider using agent pools for similar use cases

What’s next

Call History

Manage scheduled call queue

Outbound Calls

Schedule outbound campaigns