Current Location ：
Ring Groups and Hunt Group Design for Smooth Call Distribution
A ring group is one of the simplest features on a phone system and one of the most visible when it is wrong. Callers hear a phone ringing in an empty office, or hear nothing at all while the right person sits at a desk. The difference between a good and a poor queue is almost always a design decision made in configuration: who is eligible, in what order, for how long, and what happens when nobody answers.
The Four Decisions That Define a Ring Group
| Decision | Options | Effect when chosen well |
|---|---|---|
| Membership | Static list, or dynamic by presence or schedule | Only reachable staff ring, so callers reach someone who can actually help |
| Ring order | All ring together, or in priority order | Priority order serves specialists first without excluding the rest |
| Ring timeout | Per-member ring time | Long enough to reach a desk, short enough to escalate |
| Overflow destination | Next ring group, voicemail, or an announcement | No abandoned calls and no confusing loops |
Ring Order Strategies
Ring order is the decision most worth getting right. Ring-all-together maximises the chance of answering and is right for general enquiries. Priority order serves a specific role first, which suits a main line with a receptionist or a triage function. Cascading order, where each tier rings for a fixed time before expanding, is the right pattern when a call needs a specific skill before a general one.
A common and effective cascade
- Tier 1: the specialist or duty role for this enquiry type, for 20 seconds
- Tier 2: the wider team, for 20 seconds
- Tier 3: the broader department or a shared queue
- Overflow: a monitored overflow destination with a clear message, or voicemail with routing
Avoiding the Failure Modes
Members who cannot actually answer
The most common defect is membership that does not reflect reality. Staff on leave, part-time staff in a full-time queue, and staff whose primary role is not taking calls all degrade a queue. Dynamic membership based on presence or schedule resolves this and should be the default rather than an enhancement.
Overflow loops
If a ring group's overflow points at a ring group that eventually overflows back to the first, callers hear ringing that never connects and staff cannot diagnose it. Overflow targets must form a strictly descending hierarchy with no cycles.
Timeouts that are too generous
A long ring time per member feels better for the individual but is worse for the caller, who is left listening to ringing. Where a call is likely to be answered in person, shorter per-member timeouts with faster escalation usually produce a better caller experience.
Alignment With Working Patterns
Ring group behaviour should follow the site's actual operating hours. A queue that rings all members outside business hours reaches someone who cannot properly handle the call. Schedules and out-of-hours destinations should be configured per ring group, not globally, because a retail site, a hospital, and an office have completely different patterns.
Measuring Whether the Design Works
- Call answer rate by ring group, and the abandoned call rate alongside it
- Median time to answer, not average, because a few very long waits distort the average
- Overflow destination usage, which shows where the design does not match demand
- Calls ringing to a member who was not present, which indicates a membership problem
- Peak hour staffing against peak call volume, which shows whether the design is even feasible
Redstone Approach
Redstone IP-PBX platforms support ring groups with configurable membership by presence and schedule, priority and cascade ring order, per-member timeouts, and overflow routing, with call detail reporting that shows answer rates and overflow usage per group. Redstone can review an existing design and identify the rings that are not being answered and why.
Redstone provides ring group design review for existing estates, including membership accuracy, timeout tuning, overflow routing, and reporting to verify the design is performing.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
