SureTel
VoIP & Cloud PBX Guide
Call Queues Explained
Route busy business calls fairly without leaving customers guessing.
- • Cloud PBX and VoIP specialists
- • Queue setup and call-flow planning
- • Support for SMEs, branches and call teams
- • South African business telecoms partner
Educational resource · Not a quote · Licensed SA ISP · ICASA licence 0009/CECS/AUG/09
Answer first
Call queues, in one paragraph
A call queue holds callers when your team is busy, then routes each call to an available person or group according to queue rules. Businesses use queues for sales, support, reception overflow, service desks and call teams. SureTel helps plan, configure, test and adjust call queues for Cloud PBX, business VoIP, Yeastar and 3CX environments where applicable. Request a quote.
- Useful for busy sales, support, reception and service teams.
- Can include announcements, callbacks, overflow and abandonment alerts.
- Queue behaviour depends on platform, licensing and configuration.
- Works with IVR menus, ring groups and business call flows.
- SureTel can assist with setup, testing, handover and later changes.
Problems call queues help solve
When calls arrive faster than staff can answer them
Call queues are useful when calls arrive faster than staff can answer them. They help create a more controlled caller experience instead of sending every busy-period call straight to voicemail or an overloaded receptionist. Queues do not replace staffing — they manage what happens while callers wait.
Missed calls during peaks
When multiple customers call at once, a queue can hold callers and route them as staff become available.
Reception overload
Queues can separate reception, sales, support, accounts or service calls so one person is not expected to handle everything.
No abandoned-call visibility
Abandonment emails and reporting can help teams follow up missed opportunities where supported.
Uneven call distribution
Queue strategies can route calls more fairly across available agents or prioritise specific staff.
Poor caller feedback
Announcements, music, position messaging or estimated wait messaging can keep callers informed where supported.
No overflow plan
Timeout, queue-full, no-agent and after-hours rules can route calls to another team, voicemail or fallback destination.
When call queues fit
Where a queue earns its place
A call queue fits when calls need to wait for a team, not just ring one person or follow a simple menu. The right queue design depends on team size, staffing hours, call volume and customer expectations — not every business needs one.
| Scenario | Queue fit | Why it matters |
|---|---|---|
| Sales team | Strong fit | Helps distribute inbound enquiries and reduce missed opportunities |
| Support desk | Strong fit | Gives callers a managed waiting experience and allows overflow rules |
| Accounts department | Moderate fit | Useful where finance teams receive repeated supplier/customer calls |
| Reception overflow | Strong fit | Helps when reception is busy or away from the desk |
| Automotive service desk | Strong fit | Useful during booking, collections and service-update peaks |
| Pharmacy or medical practice | Strong fit | Helps manage repeat inbound customer or patient calls — kept cautious and non-clinical |
| Multi-branch business | Strong fit | Routes callers to the right branch or team from a central call flow |
| Very small office with low call volume | Possible but not always needed | A ring group or simple voicemail route may be enough |
Sales team
Queue fit: Strong fit
Why: Helps distribute inbound enquiries and reduce missed opportunities
Support desk
Queue fit: Strong fit
Why: Gives callers a managed waiting experience and allows overflow rules
Accounts department
Queue fit: Moderate fit
Why: Useful where finance teams receive repeated supplier/customer calls
Reception overflow
Queue fit: Strong fit
Why: Helps when reception is busy or away from the desk
Automotive service desk
Queue fit: Strong fit
Why: Useful during booking, collections and service-update peaks
Pharmacy or medical practice
Queue fit: Strong fit
Why: Helps manage repeat inbound customer or patient calls — kept cautious and non-clinical
Multi-branch business
Queue fit: Strong fit
Why: Routes callers to the right branch or team from a central call flow
Very small office with low call volume
Queue fit: Possible but not always needed
Why: A ring group or simple voicemail route may be enough
Key call queue features
Fourteen queue features, grouped by what they do
Queue features vary by platform and configuration. The list below groups the fourteen features that scoping conversations usually cover, with plain-English explanations — never a promise that every feature is available on every PBX system.
Caller experience
What callers actually hear and how the queue behaves while they wait.
Queue announcements
Play a greeting, service message, waiting prompt or agent announcement before the call is answered.
Music on hold
Keep callers connected while they wait.
Callbacks
Allow callers to request a return call instead of staying on hold, where the phone system, licence and configuration support it.
Timeout behaviour
Send a caller elsewhere — voicemail, another team, a ring group or a fallback destination — if they wait too long. A timeout is the maximum time a caller stays in the queue before that rule fires.
Queue-full behaviour
Route or message callers differently when the queue is at capacity, so callers are not left listening indefinitely.
Agent routing
How the queue decides who receives the next call and what happens if nobody can.
Agent weights and priorities
Route calls to agents based on weighting or priority rules where the phone system supports it — for example, senior staff or escalation teams receiving more inbound calls.
No available agents
Define what happens when no agents are logged in — for example, route to voicemail, an approved fallback destination or after-hours behaviour.
No free agents
Define what happens when agents exist but are all busy — for example, keep the caller waiting with announcements, offer a callback or overflow to another queue where supported.
Wrap-up time
Wrap-up time is a short period after a call during which the agent is not offered another call, so staff can complete notes or admin before receiving the next one.
Reporting and visibility
What supervisors and teams can see about queue activity.
Abandoned-call emails
An abandoned call is one where the caller hangs up before being answered. Where the platform supports it, the queue can send an email so the team can follow up.
Queue SLA targets
Track queue service-level performance — for example, the share of calls answered within a chosen time threshold. A queue SLA target is a reporting and measurement goal only; it is not a contractual SLA or a guarantee that every call will be answered.
Wallboards
Show real-time queue activity for supervisors or teams where the platform supports wallboard displays.
Queue reporting
Review answered calls, abandoned calls, wait times, agent activity and queue trends where the platform supports it.
QueueMetrics integration
QueueMetrics is a call-queue reporting and wallboard platform sometimes used with Asterisk-based environments. It is scoped where deployed and supported — never bundled, included or endorsed by default.
Feature availability depends on the platform, licence and configuration. Queue SLA targets are reporting and measurement goals only — never contractual SLAs or guarantees of answer rate. QueueMetrics is cited only where deployed and supported; it is not bundled or included by default.
Queue strategies and routing
How the queue decides who receives the next call
A queue strategy controls how the system decides which agent should receive the next call. Exact strategy names differ by platform, but the business logic is usually easy to understand.
| Strategy | Plain-English meaning | Typical use |
|---|---|---|
| Ring all | Ring all available agents at once | Small teams, fast pickup expectations |
| Round-robin / rotating | Rotate calls through agents in order | Balanced distribution across a team |
| Least recent | Send the call to the agent who least recently answered | Fairer distribution over time |
| Fewest calls | Send the call to the agent with the lowest answered-call count | Useful where call volume should be spread |
| Priority / weighted | Prioritise certain agents or teams | Senior staff, escalation teams or weighted workloads |
| Skills-based or scoped routing | Route based on team, branch, language or role where supported | More advanced environments |
Ring all
Meaning: Ring all available agents at once
Typical use: Small teams, fast pickup expectations
Round-robin / rotating
Meaning: Rotate calls through agents in order
Typical use: Balanced distribution across a team
Least recent
Meaning: Send the call to the agent who least recently answered
Typical use: Fairer distribution over time
Fewest calls
Meaning: Send the call to the agent with the lowest answered-call count
Typical use: Useful where call volume should be spread
Priority / weighted
Meaning: Prioritise certain agents or teams
Typical use: Senior staff, escalation teams or weighted workloads
Skills-based or scoped routing
Meaning: Route based on team, branch, language or role where supported
Typical use: More advanced environments
Not every routing mode is available on every PBX. Exact options depend on SureTel Cloud PBX and, where applicable, Yeastar, 3CX or the customer’s scoped platform, licence and configuration.
Call queue vs auto-attendant vs ring group
Three roles that often work together
Many business systems use all three features together — the IVR chooses the destination, the ring group handles simple team calls, and the queue manages busier teams that need controlled waiting. The comparison below shows each feature’s role, not a winner.
| Feature | Main job | Best for |
|---|---|---|
| Auto-attendant / IVR | Helps callers choose where to go | “Press 1 for sales, 2 for support” style routing |
| Ring group | Rings a small group of people | Simple department routing when no queue logic is needed |
| Call queue | Holds callers and routes them by queue rules | Busy teams, support desks, service departments and call teams |
For the deeper walk-through of IVR menus, keypress options, business-hours rules and multi-branch routing, see auto-attendants and IVR menus. This article keeps the IVR treatment intentionally short so the two guides stay distinct.
Use cases by business type
Where queues fit in real South African businesses
Use these examples to make the topic tangible, but each queue should be scoped around the business’s departments, call volumes, hours and support process. More advanced dialler or contact-centre needs belong on the call-centre communications solution, backed by Hosted VICIdial where appropriate.
Sales teams
Queue inbound enquiries and route them to available sales staff, with abandoned-call follow-up where supported.
Support desks
Hold callers while support agents are busy, then route calls by availability or priority.
Reception overflow
Send calls to a queue when reception is already on a call or away from the desk.
Service departments
Useful for automotive workshops, appliance repair teams, field-service desks and maintenance teams.
Small inbound call teams
Basic queueing can support smaller inbound call teams. More advanced dialler or contact-centre needs are handled by a dedicated call-centre solution, not a general phone queue.
Pharmacies and medical practices
Manage repeat customer or patient calls. Wording stays cautious and non-clinical — a queue is not a triage or emergency-response system.
Automotive service desks
Queue bookings, service updates, collections and workshop calls during busy hours.
Multi-branch teams
Route callers from one main number to branch-specific queues or teams where the call flow supports it.
Advanced queue behaviour to scope
Fourteen questions to answer before go-live
Advanced queue behaviour needs careful scoping because features vary by PBX, licence, platform and reporting tools. Work through the checklist below during scoping — SureTel can help decide which items apply and how each should behave.
- Do callers need callbacks?
- Should abandoned calls trigger email alerts?
- What should happen on timeout?
- What should happen when the queue is full?
- What should happen when no agents are logged in?
- What should happen when agents are logged in but busy?
- Do agents need wrap-up time?
- Should agents hear an announcement before the caller is connected?
- Are queue weights or priorities needed?
- Is QueueMetrics integration required (scoped, not default)?
- Are wallboards needed for supervisors?
- What queue SLA reporting target should be measured?
- Should the queue overflow to voicemail, another queue, a ring group or an external number?
- Should after-hours and holiday rules be different?
Advanced feature availability depends on the phone system, licence and configuration. Queue SLA targets are reporting goals, not contractual guarantees. QueueMetrics is scoped where deployed and supported, never included by default.
What is a call queue
The mechanics behind the wait
Underneath the wording, a call queue is a PBX feature that manages inbound calls when staff are busy. It holds callers rather than sending an immediate busy tone or voicemail, then hands each call to an agent according to the queue rules. Queues are often placed after an auto-attendant menu, but they can also receive calls directly from a main number.
- Callers wait in line rather than getting an immediate busy tone or voicemail.
- Queue rules decide which agent or team receives the next call.
- Agents may log in and out of the queue depending on the setup.
- Queue behaviour can change after hours or during holidays where supported.
- Reporting and wallboards may be available depending on the platform.
A typical call-queue flow
Incoming call
Caller dials the published business number.
Auto-attendant / IVR
An IVR menu greets the caller and routes them to the relevant queue.
Call queue
The queue holds the caller and applies routing rules — sales, support, accounts or a shared team.
Available agent
The next available agent receives the call according to the queue strategy.
If busy: wait, callback, overflow or voicemail
Timeout, queue-full, no-agent and after-hours rules can send the caller to a callback, overflow destination, voicemail or an approved fallback route.
The diagram is a planning model. Actual behaviour depends on the phone system, its queue capabilities and how the queue is scoped for the business.
Why set up call queues with SureTel
The practical implementation partner, not just a number
SureTel plans, configures and tests call queues rather than leaving businesses to figure out PBX admin alone. Queues do not replace staffing and they will not guarantee that every call is answered — but a scoped queue design, sensible overflow rules and real testing consistently reduce noise on the main number.
Call-flow planning
SureTel helps map how calls should move through IVR menus, queues, overflow rules and fallback destinations.
Step 1 of 5
Call-flow planning
Cloud PBX and VoIP experience
SureTel can configure queues on SureTel Cloud PBX and, where applicable, Yeastar and 3CX environments.
Step 2 of 5
Cloud PBX and VoIP experience
Practical queue setup
SureTel can assist with queue logic, agents, prompts, announcements, callbacks and abandoned-call emails where supported.
Step 3 of 5
Practical queue setup
Reporting and visibility
SureTel can help scope wallboards, QueueMetrics integration and queue reporting where the customer's platform supports it.
Step 4 of 5
Reporting and visibility
Support after go-live
SureTel can help adjust queues after teams see real call behaviour, staffing patterns and peak-period pain points.
Step 5 of 5
Support after go-live
Licensed South African ISP · ICASA licence 0009/CECS/AUG/09 · Standard support Monday–Friday, 08:00–17:00. These facts do not guarantee call outcomes, caller satisfaction or specific answer rates.
Setup process
How SureTel scopes and configures call queues
The steps below describe the scoping and implementation path at a business level. They are not PBX admin instructions — the platform configuration is handled by SureTel where the environment is supported.
Understand call flow
Confirm departments, teams, working hours, fallback destinations and caller expectations.
Design queue logic
Plan queue strategy, announcements, timeouts, overflow, no-agent behaviour and after-hours rules.
Configure agents and destinations
Set up queue members, extension behaviour, ring strategy, weights and permissions where supported.
Add prompts and notifications
Configure greetings, announcements, abandonment emails, callbacks and agent announcements where required.
Test the queue
Test normal calls, busy-period scenarios, timeout, queue-full, no-agent and after-hours behaviour.
Handover and refine
Train users, explain reporting and adjust the setup after real usage.
Related resources
Keep planning the phone system
Practical next reads for teams scoping IVRs, queues, connectivity and phone-system decisions.
- Auto-Attendants (IVR) Explained
How IVR menus route calls before they reach a queue, with practical menu examples and after-hours rules.
- VoIP equipment and hardware guide
Desk phones, softphones and headsets that agents and reception teams actually use with a queue.
- VoIP bandwidth and internet requirements
What the connection needs to look like before piling queues and busy-period calls on top of it.
- Call recording for business
How recording, retention and permissions fit alongside queue activity and reporting.
- What is Cloud PBX?
How the hosted phone system that runs the queue fits together — extensions, routing and admin.
- Multi-branch phone systems
Routing branch calls through central queues and branch-specific teams from one main number.
For pricing context see Cloud PBX pricing. For hands-on scoping, use request a quote.
Call queue FAQs
Frequently asked questions about business call queues
What is a call queue?
A call queue is a business phone-system feature that holds callers when staff are busy, then routes each call to an available person or team according to queue rules. It can also play announcements, apply timeout rules and provide reporting where supported.
What is the difference between a call queue and a ring group?
A ring group usually rings a small group of people according to a simple rule. A call queue is more advanced because it can hold callers, manage agent availability, use queue strategies, play announcements, handle overflow and report on queue activity where supported.
What is the difference between an auto-attendant and a call queue?
An auto-attendant helps callers choose where to go, such as sales, support or accounts. A call queue manages what happens after the caller reaches a busy team. Many businesses use both: the IVR routes the call, then the queue manages waiting and agent distribution.
Can SureTel configure call queues for my business?
Yes. SureTel can assist with call-flow planning, queue design, agent setup, prompts or announcements, callback options, abandoned-call notifications, queue reporting, testing and user handover where supported by the customer's phone system.
Can call queues send emails for abandoned calls?
Yes, where the platform supports it. Abandoned-call emails can alert the right team when a caller hangs up before being answered, helping the business follow up missed calls or recurring peak-period issues.
Can a call queue call customers back?
Callback options may be available depending on the platform and configuration. This needs to be scoped because callback behaviour, caller prompts, queue position and reporting can differ between systems.
Do call queues guarantee that every call will be answered?
No. Queues help manage busy periods, but they do not guarantee that callers will wait, that every call will be answered, or that staffing problems disappear. Queue design works best when it is paired with realistic staffing, clear overflow rules and good reporting.
Can call queues be used for multi-branch businesses?
Yes. Multi-branch businesses can use call queues to route calls to branch-specific teams, central support desks or overflow groups. The final design depends on the phone system, branch structure, working hours and how calls should be escalated.
What is QueueMetrics?
QueueMetrics is a call-queue reporting and wallboard platform often used with Asterisk-based environments. Where deployed and supported, it can help supervisors view queue activity, agent performance, wait times, abandoned calls and service-level reporting. It is scoped where required, not included by default.
What happens if no agents are available?
The queue can be configured to follow a rule such as routing to voicemail, sending the call to another team, playing a message, triggering a callback option or using an overflow destination. The correct behaviour should be planned before go-live.
Next step
Need better call handling for busy teams?
SureTel can help plan and configure call queues, IVR menus, routing rules, callbacks, abandoned-call alerts and reporting where supported by your phone system. For the underlying phone system see Cloud PBX for South African businesses. For the calling service context see business VoIP services.
Your details are used to respond to this enquiry and are handled according to SureTel’s Privacy Policy.