Setting Up Call Queues: Members, Priority and Overflow
How to set up call queues in Call: who is offered calls by skill, how long phones ring, what happens on overflow, who goes first and which alerts to set.
A queue is the waiting room of your phone line. When a call arrives and nobody is free, the caller waits there, and the queue's rules decide who gets the call next. Get those rules right and callers are answered quickly by someone who can help. Get them wrong and calls pile up behind the wrong people while others sit idle.

This guide walks through the choices behind a queue: who belongs in it, how callers are ordered, what happens when it is busy, and how to know it is working. The last section shows where each setting lives in Call. If you want the wider picture first, read What Is ACD? Call Routing Methods Explained.
What a queue actually does
Think of a queue as three decisions made in a fixed order. First, which agents are eligible to take the call. Second, which waiting caller is next. Third, what happens when nobody can answer in a reasonable time. Everything else, such as music, announcements and alerts, supports those three decisions.
The three decisions every queue makes
- Who is eligibleOnly agents with the right skill, who are available, are offered the call.
- Who goes nextCallers are normally answered in arrival order, with exceptions you choose on purpose.
- What happens on overflowAfter a limit, the call moves to another queue, a message or a call-back instead of waiting forever.
Before you build anything, write down your call types in plain words: new orders, billing questions, technical help, appointment changes. Each type that needs different knowledge is a candidate for its own queue. A very small team may need only one. A queue per person is almost always a mistake, because it breaks the moment that person is out.
Choosing who is in the queue: skills, not names
The most reliable way to decide who receives a queue's calls is by skill. You give people skills such as support, billing or a language, and the queue requires one of them. Anyone with that skill who is available can be offered the call. When someone joins, leaves or goes on holiday, you change their skills and the queue follows.
Keep skills few and meaningful
It is tempting to create a skill for every product and nuance. Resist this. Each extra skill splits your agents into smaller groups, and small groups wait longer for each other's calls. A good rule is to add a skill only when a mistake by an untrained agent would really cost you, for example a billing question or a regulated topic.
- Start with two or three skills and look at the numbers for a few weeks before adding more.
- Make sure every skill is held by at least a few people, so a single absence does not empty the queue.
- Name skills after the work (billing) rather than the team (finance), because teams get reorganised.
Order and priority: who gets answered first
By default, callers are answered in the order they arrived. That is fair and easy to explain, and it is the right default for most queues. Priority rules change the order only for groups you have a clear reason to favour, for example callers marked as VIP, callers with a high-value open deal, or people returning a call from a campaign.
Keep priority rules few and write down why each exists. A boost that made sense a year ago may now push important calls behind less urgent ones. Boosts from several rules add up, so two modest rules can combine into a large jump. Review the list when you review your queues, and remove anything nobody can justify.
First come first served vs priority rules
| Arrival order | Priority rules | |
|---|---|---|
| Fairness | Everyone waits their turn | Some callers move ahead, so you must be able to explain why |
| Best for | Most general queues | Known groups with a real business reason |
| Risk | Urgent callers wait behind routine ones | Rules pile up and bury ordinary callers |
| Upkeep | None | Review the rules regularly |
Ringing time and overflow
Two settings decide how long a caller waits before the system tries something else: how long a phone rings for each agent, and where the call goes if the queue cannot answer.
How long to ring
If a phone rings too briefly, an agent who is reaching for the headset misses the call. If it rings too long, the caller sits through silence while the system waits for someone who is not there. A few seconds more than feels necessary is usually right for a desk team; shorter times suit teams who are always in their headsets. Automatic answering can be useful on a high-volume desk, but it needs a short warning beep so agents are not surprised by a live caller.
Where overflow goes
Overflow is your safety net. A good overflow target is another queue with people who can help, even if they are slower. A weaker one is a message and a call-back request. The worst is nothing at all. Decide in advance which waits are acceptable: a caller who has waited longer than your target is already unhappy, and the overflow route is your chance to keep them.
A sensible overflow path
- Primary queueSkilled agents are offered the call and the phone rings for a set time.
- WaitThe caller hears an honest message about the wait, and optionally a link to chat.
- Overflow queueAfter the limit, a wider group of agents is offered the call.
- Call-back or messageIf that also fails, the caller can leave a message or ask to be called back.
Overflow works best when it is tested. Place a few calls while the primary queue is full and confirm they land where you expect. See What Callers Should Hear While They Wait for the wording of the waiting message.
Targets and alerts: knowing when it is going wrong
A queue without a target is a queue nobody can judge. Choose a service-level target in the usual form: a share of calls answered within a number of seconds. Start from what your callers and your staffing can realistically support, and tighten it later. Service Level and the 80/20 Rule explains how to think about that choice.
Then set alert limits for the longest wait, the number of calls waiting and the share of callers who hang up while waiting. Alerts are for people, not for the routing: they tell a supervisor to act, for example by asking a colleague to help or opening another queue. They do not change how calls are routed.
| Alert | What it tells you | A typical response |
|---|---|---|
| Longest wait | One caller has been waiting too long | Free an agent or move the caller to overflow |
| Calls waiting | Demand is outrunning the team | Ask other skilled people to log in |
| Abandon rate | Callers are giving up | Check wait messages and offer a call-back |
Set each limit just above normal levels at first. Alerts that fire all day teach people to ignore them, while alerts that never fire hide real trouble.
Hours and closed behaviour
Every queue should know when it is open. Outside those hours the caller needs a clear alternative: a short message and the chance to leave a message, or a route to another queue that is open. A queue with no hours at all takes calls at any time, which is only right if someone really is there at any time. Details on setting hours, holidays and closures are in Business Hours, Holidays and Closures in Call.
Reviewing a queue after launch
A queue is never finished. Look at it weekly for the first month, then monthly. The questions are simple: did we meet the target, did callers abandon, did overflow fire, and did anyone get calls they could not handle?
Queue review checklist
- Service level against target, by time of day
- Longest waits and the hours they happened in
- Calls that overflowed, and where they ended up
- Calls transferred out because the agent lacked a skill
- Agents with a skill who were never offered calls
- Alerts that fired too often or never
Setting it up in Call
In Call, queues live under Calls, in Queues & SLA. The page shows calls waiting, the service level, calls handled and agents available, and compares every queue's target, answer speed, handle time, longest wait, offered calls and abandoned calls. Pick a time window at the top, then press Configure on a queue to open three tabs: Thresholds, Hours and Routing. Only owners, administrators and managers can configure queues.
- Thresholds: the queue name, the share of calls to answer within a number of seconds, and the alert limits for longest wait, waiting calls and abandon rate.
- Hours: the time zone, opening and closing times for each day, what happens when closed (take a message or send to the overflow queue), the closed greeting and the holiday calendar.
- Routing: a required skill, an overflow queue, how long a phone rings (5 to 120 seconds), optional automatic answering with a warning beep, a web chat address for long waits and a recording announcement.
Skills are set per person under Team & Roles. Priority rules are under Settings, Routing rules, on the Who goes first tab, and the Queue operations tab shows waiting callers in answer order with the reason for each position. Before you go live, use the routing simulator under Inbound ops: it walks a pretend call through hours, holidays, capacity and skills without dialling anyone. If a queue gets out of hand, Inbound ops can pause it or drain it, which moves everyone waiting to the call-back list. For the next step, see Per-Queue Voicemail in Call: Setup and Follow-Up.
Frequently asked questions
How many queues should a small team have?
Usually one or two. Add a queue only when a call type needs different knowledge or different hours. Every extra queue divides your agents into smaller groups, which can make waits longer.
Should I route to named people or to skills?
Skills are safer. Named routing fails when that person is away or busy, while a skill lets any qualified agent take the call. Use named routing only for rare cases, such as a personal account manager.
What is a good ring time?
It depends on how your agents work. Teams that wear headsets all day can use shorter ring times; teams who move around need a little longer. Test with real calls and adjust if calls are missed or callers hear too much silence.
What should happen when a queue is full?
Callers should move to an overflow queue, hear an honest wait message, or be offered a call-back. Leaving them in silence with no end in sight is the outcome most likely to cause hang-ups.
Do priority rules make the queue unfair?
They can. Use them only for groups with a clear business reason, write the reason down, and review them regularly, because boosts from several rules add together.
How do I know if my queue settings are working?
Compare the service level with your target, and look at abandoned calls, longest waits and overflow. If those stay healthy across busy and quiet periods, the settings are doing their job.