Most businesses do not need a dedicated contact centre platform. They need a handful of well-configured queues on the phone system they already have, with reporting good enough to tell them whether customers are being served. A modern Cloud PBX includes full ACD (Automatic Call Distribution) capability as standard, and for teams up to a few dozen agents it does the job comfortably. What separates a queue setup that improves customer experience from one that damages it is configuration, not licensing tier.
Start With the Metric That Matters
Before configuring anything, decide what you are optimising for, because different goals produce different queue designs:
- Service level — the percentage of calls answered within a target time, conventionally expressed as 80/20 (80% answered within 20 seconds). This is the standard measure for customer-facing support.
- Abandonment rate — the percentage of callers who hang up before being answered. Above roughly 5–8% signals a real staffing or routing problem.
- First contact resolution — the proportion of issues resolved without a callback or transfer. Harder to measure, but the metric most correlated with customer satisfaction.
- Average handle time — useful for capacity planning, dangerous as a performance target, because agents optimise for it by rushing customers off the phone.
Pick one primary metric and at most two secondary ones. Teams that track a dozen equally-weighted metrics end up optimising none of them.
Choosing a Distribution Strategy
The strategy determines which agent gets the next call, and the right choice depends on how interchangeable your agents are:
- Ring all — every available agent's phone rings. Fast to answer, but disruptive at any scale and it produces a race that agents quickly learn to lose deliberately. Reasonable for two or three people, poor beyond that.
- Longest idle — the agent who has been available longest receives the call. The fairest general-purpose default, and the right starting point for most teams.
- Round robin — calls rotate through agents in order. Predictable and easy to explain, though it ignores how long each agent has actually been free.
- Tiered / skills-based — calls go to tier 1 first and only overflow to tier 2 after a defined wait. This is how you keep specialists available for the calls that need them while generalists absorb routine volume.
Tiered routing is where most teams see the largest improvement, because it stops your most experienced people being consumed by password resets.
The Queue Settings People Get Wrong
Four configuration details cause the majority of avoidable customer frustration:
Wrap-up time set to zero. If an agent is offered a new call the instant the previous one ends, they cannot complete notes, and quality collapses. Fifteen to thirty seconds of wrap-up is not idleness — it is what makes the next call competent.
No maximum wait time. A queue with no exit condition will hold a caller indefinitely while nobody is logged in. Every queue needs a maximum wait and a defined destination when it is exceeded — voicemail, an overflow queue, or a callback offer.
Position announcements without wait estimates. "You are number six in the queue" tells a caller nothing useful. An estimated wait time — even an approximate one — lets people decide whether to hold or call back, and measurably reduces abandonment.
Music on hold nobody has listened to. Play your hold audio through a phone, not a laptop. Heavily compressed music through a narrowband codec often sounds considerably worse than it does on the file you uploaded.
Offer a Callback Instead of a Longer Hold
Queue callback — where the caller keeps their position but hangs up and is called back when an agent is free — is the single highest-impact feature for customer satisfaction in busy queues. It converts a frustrating wait into a scheduled interaction, and it reduces the concurrent channel usage of your queue at peak. If your queues regularly exceed two minutes of wait, enable it.
Agent States Are Data, Not Surveillance
Agents need to go unavailable for legitimate reasons — breaks, training, after-call work, a supervisor conversation. Giving them clear pause reason codes produces two benefits: the queue stops routing calls to someone who cannot take them, and your reporting can distinguish "understaffed" from "staffed but everyone is in training". Teams that make pausing feel punitive get agents who leave the phone ringing instead, which is worse for everyone.
Reporting: The Handful of Reports Worth Running
The reports that consistently drive decisions are fewer than most dashboards suggest:
- Service level by half-hour interval — daily averages hide the 10:00–11:00 collapse that is actually the problem. Interval reporting is what tells you when to schedule people.
- Abandoned calls with wait time at abandonment — if most abandonments happen in the first fifteen seconds, callers are hanging up on your IVR, not on your wait.
- Calls offered versus calls answered per agent — reveals both genuine performance differences and misconfigured devices that are failing to ring.
- Repeat callers within 24 hours — a direct proxy for first contact resolution that most teams never look at.
A live wallboard showing calls waiting, longest wait and agents available is worth more than any historical report for day-to-day management, because it lets a supervisor act while the queue is still recoverable.
Record Calls, and Actually Listen to Them
Call recording is trivial to enable and almost universally underused. A supervisor who reviews three calls per agent per week — deliberately including good ones, not just complaints — will identify coaching opportunities no metric surfaces. Be clear about your legal position on consent: recording requirements vary by state, with several requiring all-party consent, so an announcement at the start of the call is the safe default.
When You Have Outgrown Cloud PBX Queues
Honest guidance: if you need omnichannel routing across email, chat and social alongside voice, workforce management with forecasting and shift optimisation, or speech analytics across every recorded call, you need a dedicated contact centre platform. Below that threshold — which covers the large majority of businesses running support, sales or dispatch teams — a well-configured Cloud PBX queue set does the job without the licence cost or the implementation project.
PBX SIP Trunking's Cloud PBX includes ACD queues with tiered agents, queue callback, live wallboard statistics, interval-based service level reporting and call recording on every plan, with no per-agent contact centre licence.