Call Center Software: PBX Integration, Queues and How to Choose

Call center software is the layer that organizes agents' work around phone calls: who to call and from which list, what happened on each call, when to call back, how calls are queued, who may listen to recordings and how the team performs. The calls themselves are carried by a phone system (PBX). So the first real question is not "which software?" but "how will it work with the PBX we already have — or do we need one at all?"

The PBX and the call center software do different jobs

A PBX handles extensions, trunks (your lines to the operator), routing and audio. Call center software handles the business side:

• call lists and campaigns, with dialing modes;
• an agent screen with the customer record, call outcomes and callbacks;
• queues, agent statuses and breaks;
• recordings, permissions and audit trails;
• live supervision and reports.

Keeping them apart means you can modernize the agent experience without replacing a PBX that works.

Cloud PBX or on-premise PBX?

Aspect	Cloud PBX	On-premise PBX
Hardware	None on site	A server or appliance you run
Setup	Fast, provider-managed	Your team or an integrator
Maintenance	Provider updates it	You patch and back it up
Control	Provider's rules and limits	Full control over routing and data
Typical fit	Distributed or fast-growing teams	Existing telephony investment, strict data needs

If you already run Asterisk (FreePBX, Issabel), 3CX or a Twilio account, the software should connect to it rather than force a migration.

Connecting an existing PBX

The integration lets the software start calls (click-to-call), hang up, read call state and, where supported, pause agents in queues or let a supervisor listen in. Practical points:

• Asterisk, FreePBX, Issabel: the software talks to management interfaces such as ARI or AMI. Open them only to the call center server's IP address — never to the whole internet.
• 3CX: available API features differ between versions, so check which functions actually work with yours.
• Twilio: calls run through your Twilio account; there is no hardware to manage.
• Number format: the PBX's outbound route expects numbers in a certain format (national or international). A mismatch is the classic reason a call rings the agent but never reaches the customer.

Calling from the browser

With a WebRTC softphone, the agent talks through a headset in the browser — no desk phone and no separate softphone app. Two common pitfalls: the same extension registered on another device at the same time (calls land in the wrong place), and one-way audio, which usually means the PBX firewall blocks the media ports.

Queues, agent statuses and breaks

For inbound calls, a queue decides who answers. Key settings are the distribution strategy (longest idle, round robin, ring all, by skill), a service level target, a maximum wait, an overflow queue and after-hours routing.

Agent statuses — available, on a call, wrap-up, on break — should be recorded every time they change. Asking for a break reason code turns this history into something you can manage: break reports, adherence and occupancy.

Campaigns, dialing modes and callbacks

Outbound work starts with clean lists: CSV import with column mapping, one number format, no duplicates. Then pick a dialing mode:

• Manual: the agent starts every call.
• Preview: the agent sees the record first, then calls.
• Progressive: the next number is dialed when an agent becomes free.
• Predictive: the system dials ahead of agents; it needs an abandon-rate limit.

Outcome codes should drive the next step — schedule a callback, or put the number on the do-not-call list. Calling hours, do-not-call lists and consent rules vary by country, so they belong in campaign settings, not in agents' memory.

Call recordings and retention

Recordings help with quality and disputes, but they are personal data. Tell callers about recording, set a retention period, restrict who may listen and log every access. When the period ends, the audio file should be deleted while the call record stays for reporting.

Hiding customer numbers from agents

If agents can see and copy phone numbers, your customer list can leave with them. The cleaner approach is click-to-call from the record: the agent selects a record, and the server passes the number to the PBX. Note that this requires a PBX the software can start calls through.

Live dashboards and reports

Supervisors need a live board of open calls and agent statuses, with listen, whisper and barge-in where the PBX supports them. For review: queue, agent, campaign, break and hourly reports over any date range, plus quality evaluation forms.

How to choose: a short checklist

• Does it work with your PBX, or without one while you decide?
• Can agents call from the browser?
• Are dialing modes, calling windows and do-not-call checks built in?
• Can you hide customer numbers by role?
• Is recording access permission-based and logged, with automatic retention?

How VOLTR does it

VOLTR's Call Center module is outbound-first and not tied to a PBX brand. It has drivers for Asterisk (including FreePBX and Issabel), 3CX and Twilio, and a manual flow with no PBX at all, where calls are logged in the panel and placed from the agent's own phone. Only the central administrator connects the PBX; credentials are encrypted and never returned in responses, and buttons a driver doesn't support simply don't appear.

Agents call from the browser with the WebRTC softphone and move through the records assigned to them, with outcome codes, break codes, scheduled callbacks and a follow-up list on one screen. Campaigns import CSV lists and support manual, preview, progressive and predictive dialing, with the calling window and abandon-rate limit as campaign settings. Queues are defined with strategy, service level target, wait limit, overflow, after-hours and skill-based routing. Manual dialing can't bypass the do-not-call list, customer numbers can be hidden by role or person, and every recording access needs its own permission and is logged. A live board, weighted quality forms and reports complete the module; PBX options are also listed on the integrations page.

Frequently asked questions

Do we need to replace our PBX?

Usually not. If you run Asterisk (FreePBX, Issabel), 3CX or Twilio, call center software with a matching driver can sit on top of it.

Can we start without a PBX?

Yes, with a manual flow: calls are logged in the software and placed from the agent's own phone. You can connect a PBX later.

How long should recordings be kept?

As long as your purpose and local data protection rules justify — no longer. Set a retention period and let the system delete files automatically.

Ready to try it? Open a free account and request Call Center from the Subscription section in the app, or check current module prices on the pricing page.