Blog / IVR, Queues And Call Routing

Call Queue Setup: Routing Strategies and Settings by Team Size

A vendor-neutral guide to call queue setup: eight steps, how to choose between ring all and round robin by team size, and recommended ring time, max wait and overflow settings.

Call queue setup comes down to five decisions: which agents are in the queue, how calls ring them, how long each agent gets to answer, how long a caller waits, and where the call goes when nobody picks up. This guide walks through all five in eight vendor-neutral steps, then recommends settings by team size (1 to 3, 4 to 8, and 9 to 15 agents).

Key takeaways

  • A call queue holds callers in line and distributes them to agents by a routing strategy, while a ring group simply rings a set of phones with no hold line or wait handling.
  • Microsoft recommends round robin or longest idle routing, presence-based routing turned on, and an agent alert time of at least 20 seconds for Teams call queues.
  • SQM Group reports that the average caller abandons after 2 minutes 36 seconds, and it recommends keeping average waits under 2 minutes.
  • SQM Group treats call abandonment under 5% as good and 5% as the industry standard.
  • Callback offers fail silently when the queue timeout is shorter than the callback threshold plus the hold music length.

What is a call queue, and how is it different from a ring group?

A call queue is a phone system feature that holds incoming callers in line, plays a greeting and hold music, and connects each caller to the next available agent. A ring group only rings a set of phones. It has no line, no wait messages and no position handling.

Call queue vs ring group vs hunt group

A hunt group is an older term for ringing a list of numbers in sequence until someone answers. Vendors use these names loosely, so check what a feature actually does before assuming.

FeatureHolds callers in lineHold music and messagesWait limits and overflowTypical use
Ring groupNoNoBasic voicemail fallback2 to 3 people sharing one line
Hunt groupNoRarelyBasicSequential ringing of a number list
Call queueYesYesYes, with timeout and overflowSupport, sales, front-desk lines

When does a small team need a queue?

A small team needs a queue the moment two calls can arrive at once. Without a queue, the second caller hears ringing or lands in voicemail while agents are busy. If you handle more than a few calls per hour, or agents also work from mobile phones, a queue gives callers a predictable experience.

What should you have ready before call queue setup?

Before call queue setup, gather four things: a business number, a phone menu (also called an IVR or auto-attendant), an agent list with availability, and your business hours. Having these decided in advance turns the setup into a ten-minute configuration job.

Number, phone menu and business hours

  • A business number that will point at the queue, either a new number or a ported one.
  • A phone menu if you need more than one queue, such as "press 1 for sales, press 2 for support." Our IVR phone menu setup guide has scripts, and the IVR and call routing feature shows how menus connect to queues.
  • Written business hours, including lunch coverage and holidays.

Agent list and availability

List every person who should receive calls, which device they answer on (desk app, mobile, browser), and who covers when they are out. Note anyone who is part-time or shared across roles. Those people often cause the stale member lists covered later.

Fallback destinations

Decide in advance where unanswered calls go: voicemail, a backup group, a manager's mobile, or a callback. A queue with no fallback is the single most common cause of dropped calls.

How do you set up a call queue in 8 steps?

You set up a call queue by creating it, adding agents, choosing a routing strategy, recording messages, setting ring and wait times, defining overflow, adding after-hours routing, and pointing your number at it. These steps work in any cloud phone system, though menu names differ.

1. Create the queue and name it by purpose

Name the queue for the job, such as "Support Tier 1" or "Inbound Sales," not for a person. Clear names matter later when reports show five queues side by side.

2. Add agents

Add each agent once. Duplicate entries, including the same person added directly and through a group, can make that agent ring twice or skew call distribution. If your system offers presence-based routing, turn it on so agents who are in a meeting or on another call are skipped.

3. Choose a routing strategy

Pick ring all, round robin, longest idle, linear, or least calls. The next section defines each, and the section after that matches them to team size.

4. Record greeting and hold messages

Record a short greeting, a hold message and an optional position announcement. Details are in the greetings section below.

5. Set ring time per agent and max wait

Set how long each agent's phone rings (agent alert time) and how long a caller can wait overall. Recommended values appear in the cheat sheet below.

6. Set overflow and no-agent fallback

Define what happens when the maximum wait is hit and what happens when no agents are available at all. Those are two separate rules, and you need both.

7. Add after-hours routing

Attach business hours and send closed-hours calls to a greeting plus voicemail, or to an on-call number. Include a holiday schedule.

8. Point your number or menu option at the queue and test

Assign the number or phone menu option, then test with real calls: one answered, one unanswered until timeout, one after hours, and one while all agents are busy.

Which call routing strategies exist?

Call routing strategies decide which agent's phone rings for each caller. The five common ones are ring all, round robin, longest idle, linear (priority order) and least calls. Vendors name them differently, so confirm each definition in your admin panel before choosing.

Ring all (simultaneous)

Ring all rings every available agent at once, and the first to answer gets the call. It is fast, but it makes pickup collisions likely and favors whoever reacts quickest.

Round robin: in-order vs balanced-count

Round robin is where terminology breaks down. Microsoft defines round robin as giving each representative the same number of calls from the queue, which is a balanced-count model. Other vendors use round robin to mean rotating through agents in order, picking up after the last agent who rang ("with memory"). The two behave differently when agents miss calls or go offline, so read the vendor's definition.

Longest idle

Longest idle routes each call to the agent who has gone the longest without handling one. Microsoft notes that round robin and longest idle both treat only agents with "Available" presence as eligible, so presence accuracy matters.

Linear or priority order

Linear (also called serial, in-order or hunt) always rings agents in the same sequence, starting from the top. It suits tiered setups, such as a specialist first and a generalist second, but it overloads the first person on the list.

Least calls handled

Least calls routes to the agent with the fewest calls so far. It is similar to balanced-count round robin, but some systems measure by day and others by shift.

Round robin vs ring all: which fits your team size?

For round robin vs ring all, the Voicalyst Editorial Team recommends ring all for one to three agents and a balanced or in-order round robin for four to eight, with longest idle at nine to fifteen. These are our recommendations, not industry standards, and they reflect collisions, fairness and ring fatigue.

Solo to 3 agents

Use ring all. With so few people, waiting for sequential rings adds delay that callers notice, and fairness issues are small. Watch for two failure modes: everyone's mobile rings at once, and the same quick responder ends up with most of the calls.

4 to 8 agents

Switch to round robin (balanced-count if your system offers it) or longest idle. Ring all with six phones ringing creates "who's got it?" collisions, and ring fatigue sets in quickly. Rotation spreads the load and gives each agent a clear turn.

9 to 15 agents

Use longest idle, with presence-based routing on. At this size, call lengths vary widely, and a simple rotation can hand a call to someone who just finished a long one. Longest idle spreads the rest time more evenly. If you are growing past this range, see our guide to small call center phone systems for 5 to 50 agents.

Comparison table: strategy, pros, risks, best for

StrategyProsRisksBest for
Ring allFastest answer, simpleCollisions, same agents win, mobiles ring in parallel1 to 3 agents
Round robinFair rotationDefinitions vary by vendor, can ring absent agents if presence is off4 to 8 agents
Longest idleEvens out workload and restNeeds accurate presence9 to 15 agents
LinearPredictable, supports specialistsOverloads the first agentTiered coverage
Least callsBalances totalsTotals may reset oddly across shiftsMixed-load teams

What wait-time and overflow settings should you use?

Start with an agent ring time of 20 to 25 seconds, a maximum wait of 45 seconds to 2 minutes depending on team size, and an overflow path to a backup group, voicemail or callback. Only some of these numbers come from published sources, and the table below separates them from our defaults.

Agent ring time

Microsoft's recommended settings include an agent alert time of at least 20 seconds. That is a sourced minimum. Our default is 20 seconds for sequential strategies, because a shorter alert can expire before an agent reaches the phone.

Maximum wait before fallback

SQM Group's July 2023 research found that the average time to abandon is 2 minutes 36 seconds, and it recommends average waits under 2 minutes. Your fallback should trigger before callers give up. Our defaults cut that further for smaller teams, because a three-person team rarely has a reason to hold anyone for two minutes.

Max callers waiting

In Microsoft Teams, the maximum calls in queue defaults to 50 and ranges from 0 to 200. For small teams that is far too high. A queue that holds 50 callers will break every wait-time promise you make. Our defaults are much lower.

Overflow path: backup group, voicemail or callback

Overflow is where a call goes when the queue is full or the wait limit passes. A good pattern is: ring the primary queue, then a secondary group (a manager or another team), then voicemail or a callback offer. Do not send overflow back into the same queue.

Settings cheat sheet

Sourced values are marked. Everything else is a Voicalyst Editorial Team recommended starting point, not an industry standard.

Setting1 to 3 agents4 to 8 agents9 to 15 agents
StrategyRing allRound robinLongest idle
Agent ring time20 to 25 sec (20 sec minimum is Microsoft's)20 sec20 sec
Max wait45 to 60 secAbout 90 secAbout 2 min (SQM suggests averages under 2 min)
Max callers waiting3 to 58 to 1015 to 20
OverflowVoicemail or owner's mobileBackup group, then voicemailBackup group, callback, then voicemail
Callback offerAfter 30 to 45 secAfter 45 secAfter 45 to 60 sec

The callback and timeout trap

Callback only works if the queue timeout is longer than the callback eligibility wait plus the music length. Microsoft's example: a 60-second callback threshold with a 120-second timeout and the default 2-minute music means callback is never offered. Shorten the music loop or lengthen the timeout, then test with a real call.

What should greetings, hold music and position announcements say?

A good queue greeting identifies the business in the first 10 seconds, sets a wait expectation, and offers an exit (voicemail or callback). Keep hold messages short and avoid repeating "your call is important to us" more than once.

What to say in the first 10 seconds

Sample script: "Thanks for calling Northside Plumbing. You're in line for our support team, and an agent will be with you shortly. If you'd rather not wait, stay on the line to leave a voicemail or request a callback."

When to announce wait times

Announce position or estimated wait only if your system calculates it accurately. A wrong estimate is worse than none. For teams under eight agents, a plain "an agent will be with you shortly" is usually enough.

Music length vs timeout

Music length matters because the timeout clock and the music loop interact, especially with callbacks (see the trap above). Keep the loop short, about 30 to 60 seconds, and make sure the maximum wait is longer than the loop plus any callback threshold.

How should voicemail, callback and after-hours routing work?

When the queue times out or the office is closed, callers need a clear next step: leave a voicemail, request a callback, or reach an on-call number. Each path should end with someone knowing the caller needs help.

Voicemail with AI call summaries

Voicemail is only useful if someone reads it. Voicemail transcription turns messages into text so agents can triage quickly, and AI summaries shorten longer messages. Our AI call summary guide covers how teams use them for follow-up. For sales and support teams that use HubSpot, the HubSpot calling integration can log missed calls against the contact record.

Callback offers

Offer a callback after a set wait rather than at the start. It protects the caller's place without forcing them to hold, and it reduces abandonment. Confirm the number the caller is calling from, and have a clear owner for callback tasks.

Holiday and lunch coverage

Build lunch coverage into the schedule rather than relying on agents to log out. Staggered lunches keep at least one agent available, and a holiday schedule set months ahead prevents a Monday full of unanswered calls.

How do you measure and tune a call queue after launch?

Review abandonment rate, speed to answer and service level weekly for the first month, then adjust ring time, max wait or strategy based on what the numbers show. A 15-minute review is enough for small teams.

Metrics: abandonment, speed to answer, service level

  • Abandonment rate: calls where the caller hangs up before reaching an agent. SQM Group says under 5% is good, 5 to 10% is sometimes acceptable, and 5% is the industry standard.
  • Speed to answer: average seconds from queue entry to an agent picking up.
  • Service level (80/20): 80% of calls answered within 20 seconds. SQM reports only 16% of call centers consistently meet this, so treat it as a stretch goal for small teams, not a pass/fail test. Note that SQM is a call-center research firm, and its figures describe larger operations.

Weekly 15-minute review routine

  1. Check abandonment rate and the longest wait of the week.
  2. Look at calls that hit the timeout. Where did they go, and did anyone follow up?
  3. Check missed agent rings. A pattern points to a stale member list or a ring time that is too short.
  4. Change one setting, then review again next week.

When to switch strategy

Move from ring all to round robin when agents complain about collisions or uneven workloads, usually around four agents. Move from round robin to longest idle when call lengths vary and some agents are repeatedly handed calls right after long ones. If the numbers look fine, leave things alone.

What are the most common call queue mistakes?

The most common call queue mistakes are timeouts shorter than the music or callback threshold, no fallback, stale agent lists, and mobile agents inside a ring-all group. Each has a quick fix.

  • Timeout shorter than music or callback threshold. Callers never hear the callback offer. Fix: make the timeout longer than threshold plus music length.
  • No fallback when nobody is available. Calls ring out or disconnect. Fix: set a separate no-agent rule to voicemail or a backup group.
  • Stale agent list. Former employees still ring, and new hires are missing. Fix: review membership monthly and after every hire or departure.
  • Duplicate agents. One person added twice receives double rings or skews distribution. Fix: add each person once.
  • Mobile agents in a ring-all group. Personal phones ring in parallel and personal voicemail can answer the call. Fix: use an app-based softphone, or put mobile agents on a sequential strategy.

For a broader view of choosing a platform, see our guides to cloud phone systems for support teams and small business phone systems.

How do you set up a queue in Voicalyst?

In Voicalyst, you build a queue by adding agents, choosing a routing option, and attaching a number or phone menu option to it. Confirm the exact strategies and timeout fields available on your plan in the dashboard, since options can differ by plan.

Quick walkthrough

Create the queue, add agents once each, pick the routing strategy that matches your team size from the table above, record your greeting, and set the ring time and maximum wait. Then set the voicemail fallback and business hours, and connect your number through the virtual phone system or a phone menu. Test with real calls before sending traffic.

Use the cheat sheet row for your team size, run it for a week, and review abandonment and longest wait. If you want help mapping your team to a setup, you can book a Voicalyst demo and walk through your call flow.

Frequently Asked Questions

What is a call queue?

A call queue is a phone system feature that holds incoming callers in line and connects them to available agents based on a routing strategy. Callers hear a greeting and hold music while they wait. If nobody answers within your maximum wait time, the queue sends the call to voicemail, a backup group, or a callback.

Should a small team use ring all or round robin?

Teams of one to three agents can use ring all because it gets calls answered fast. From about four agents, switch to a balanced or in-order round robin or longest idle, because ring all causes pickup collisions and lets the same fast responders take most calls. Check how your vendor defines round robin first.

How long should callers wait in a queue?

SQM Group recommends keeping average waits under 2 minutes. As a starting point, Voicalyst suggests a maximum wait of 45 to 60 seconds for teams of one to three, about 90 seconds for four to eight, and about 2 minutes for nine to fifteen, then adjusting after reviewing your abandonment data.

What is a good abandonment rate?

SQM Group considers call abandonment under 5% good, treats 5 to 10% as sometimes acceptable, and calls 5% the industry standard. If your queue sits above 10%, shorten ring times, add agents to the queue at peak hours, or offer a callback before callers hang up.

Can I add callback?

Yes, if your phone system supports it. A callback lets callers keep their place without holding. Set the callback offer to trigger earlier than the queue timeout, and make sure the timeout is longer than the callback threshold plus your hold music length, or the offer will never play.

Put this into practice with Voicalyst

Voicalyst is the cloud phone system US sales and support teams set up in minutes: a business phone system with cloud telephony, AI call summaries and texting.

Start free trialBook a demo
VE

Voicalyst Editorial Team

Guides and research from the team building Voicalyst.