---
title: Ring to All / Parallel Ringing
slug: contact-center/ring-to-all-parallel-ringing
docTags: 
createdAt: 2025-09-28T18:11:05.533Z
---

# Overview

Ring to All, or Parallel Ringing, is a call distribution strategy where an incoming call is simultaneously offered to all available agents in a specific queue. The first agent to accept the call is connected. This method is used to ensure calls are answered as quickly as possible.

# How It Works

This strategy is determined by the Resource Scheduler Type selected for a queue. When set to Parallel Ringing, the system does not follow a sequential order but instead pushes the call to every available agent in that queue at once.

## Prerequisites

- An Inbound Voice Campaign must exist.
- A queue must be created within the campaign.

## Configuration Steps

- **Feature Enablement:** This functionality is configured with the help of the Professional Services Team. Please contact your customer success manager to get it enabled or raise a support ticket (for existing customers).

# Use Cases

- **High-Priority Queues:** Used for VIP customer lines where minimizing wait time is critical.
- **Small Teams:** Effective for small support teams where it's efficient to alert everyone at once.

# Benefits

- **Maximized Call Answer Rates:** Significantly increases the probability of a call being answered promptly.
- **Minimized Customer Wait Times:** Drastically reduces the time a customer spends in the queue.
- **Improved Agent Utilization:** Ensures that idle agents are immediately engaged with incoming calls.

# Limitations

- **Not Scalable for Large Teams:** Ringing dozens of agents simultaneously creates unnecessary noise (ring fatigue) and disruption on the contact center floor. It is best suited for small groups (3-5 agents).
- **Uneven Workload Distribution:** This strategy inherently rewards the fastest agent to answer.This can skew performance metrics, leaving some agents overworked while others handle very few calls.
- **Resource Intensive:** Ringing multiple SIP endpoints or extensions at the exact same time consumes significantly more bandwidth and system resources.