Ring groups, queues and hunt groups: which one your office needs

Three tools that look alike from the outside

All three do the same job at a distance: a call comes in, and instead of ringing one person, it is offered to several. The differences are in how it is offered, what the caller experiences while waiting, and what the team can see about what is happening. Those differences decide whether a caller hangs up at forty seconds or stays on the line for four minutes.

Providers use the terms loosely, and some systems fold hunt groups into ring groups as a setting. The behaviours are worth keeping separate in your head regardless, because each answers a different question about your office. This article is about picking the right one for a normal business, not for a Contact Centre; if you are staffing dozens of agents with skills routing and wallboards, the queue has already chosen you.

Ring group: everyone at once

A ring group rings every member’s phone simultaneously. The first to pick up gets the call. If nobody answers within a set time — typically twenty to thirty seconds — the call goes to a fallback: voicemail, another group, or a person. The caller hears ringing the whole time, which is honest and simple.

It suits a team where anyone can handle any call and where the number of simultaneous callers rarely exceeds the number of people. A four-person office with a shared main line is the textbook case. Its weakness appears when two calls arrive at once: the second caller hears ringing while everyone is already on the first, and then lands in voicemail with no idea why.

The practical rule: if a second simultaneous call is unusual, a ring group is enough. If it happens daily, look further down this page.

Hunt group: one after another

A hunt group rings members in sequence. The call tries the first phone for a set number of seconds, then the second, then the third, and finally the fallback. Variants exist — start with whoever has been idle longest, or start at a random member to share the load — but the shape is the same: one phone at a time.

It suits situations where there is a preferred order. A dental office where the front desk should answer first and the treatment coordinator second; a small firm where the partner’s assistant takes the call before it reaches the partner; a shop where the counter phone should ring before the office. It is also kinder to teams that dislike every phone ringing at once for every call.

Its cost is time. A three-member hunt group with fifteen seconds per member makes the caller wait forty-five seconds before the fallback, and the caller does not know why. Keep the per-step timer short and the group small, or the caller gives up before the third phone rings.

Call queue: hold in order, deliver when ready

A queue accepts the call immediately, plays an announcement, and holds the caller in line until a member is free. Callers hear music or messages rather than ringing, are usually told their position or estimated wait, and can often request a callback that keeps their place. Members are typically logged in or out, so the queue knows who is actually available.

The team gets something too: a view of how many are waiting, how long, and who is on a call. A supervisor can see that Thursday afternoons need one more person, or that one member is taking most of the calls. That visibility is the real reason to move to a queue, and it is why queues are the foundation of every Contact Centre.

A queue is the right choice when callers regularly outnumber available people, when wait time matters and should be managed rather than hidden, or when you need to know what is happening to calls rather than guessing from voicemail counts.

• Ring group: simultaneous, simple, no visibility — for small teams with occasional overlap
• Hunt group: sequential, ordered, short timers — when someone should answer first
• Queue: held in order, announcements, callback, reporting — when callers outnumber people

Sizing it for three common offices

A five-person professional office with one main line and a receptionist most of the day: a hunt group that starts at reception, moves to two colleagues, then goes to voicemail with an email transcript. During lunch the schedule swaps the first step out. No queue needed, and adding one would only add hold music to a problem that does not exist.

A clinic front desk with two people answering and a steady stream of appointment calls from eight to ten each morning: a queue with a short announcement, position updates and a callback option, staffed by both desk staff and a third person who logs in only for that window. The queue’s reporting will show whether the window needs a fourth person by autumn.

A support team of six taking calls all day with occasional spikes: a queue, members logging in and out, an overflow rule that sends waits over a set length to a secondary group or offers a callback, and a wallboard on the wall so everyone can see the line. This is where a Contact Centre begins, and the sizing question becomes a staffing question.

Mixing them, and knowing when to change

Most companies use more than one. The main line goes to a queue during the morning rush and to a ring group after two o’clock; the accounts line is a two-person hunt group; the after-hours emergency number is a hunt group that ends on an on-call cell phone. Each entry point gets the tool that matches its callers.

The signal that a ring group has been outgrown is voicemail. If the shared voicemail box fills with messages left during business hours from people who wanted to talk to someone, callers are arriving faster than the group can answer, and a queue with a callback would have kept them. The signal that a queue is overkill is an empty wallboard: if nobody ever waits, the announcements are just delaying the first hello.