Integrations
Software PBX and your contact center
If your phone system runs on a software PBX such as 3CX or Elastix, keep it – you can still get a contact center. The office keeps calling through its own PBX, while CONTACT.WORK handles your sales and support lines: the next available agent takes the call, the conversation is recorded, and the call goes to your CRM. The platform can sit in front of the PBX and answer incoming calls from the carrier first, or sit behind it and receive only the calls for specific departments. We link the two systems with a SIP or IAX trunk and, if you choose, move departments to the platform one at a time.
Software PBXoffice, 120 usersconnectedTrunkSIP between systemsrunningInboundplatform IVR and queuesin progressInternal callson PBXsame as beforeCapabilities
What you get with Software PBX
Examples
Common setups
Three setups for companies running a software PBX.
The sales line gets queues and reports
The office has run on its own PBX for years, and nobody wants to change it. The sales team moves to the platform: calls are distributed, recorded, and sent to the CRM, and the sales manager sees reports for the line. If a customer needs accounting, the rep transfers them to an extension on the PBX.
- Office PBX unchanged
- Sales queues and reports
- Transfers to PBX departments
Officesoftware PBXno changesSales lineplatform queuesnewTransferto PBX extensionrunningReportsfor sales lineon platformThe platform takes calls first
Incoming calls from the carrier reach the platform first and go through its IVR. Sales and support answer from platform queues, while calls for other departments go over the trunk to the software PBX. Internal office calls work as before.
- One IVR for all inbound calls
- Sales and support on the platform
- Everything else on the office PBX
Carriercompany numberstrunkPlatformIVRchoose departmentSales, supportplatform queuesrecordingOther departmentsto software PBXvia trunkMoving departments over time
The company has decided to move all of its telephony to the platform eventually. The contact center goes live first, then the sales team, then the remaining departments. The software PBX keeps running as long as anyone is still on it and can serve as a backup at any time.
- Contact center goes first
- Departments in phases
- PBX as a backup
Stage 1contact centerdoneStage 2salesin progressStage 3remaining departmentsplannedPBXruns to the endfailoverIf your PBX caps the number of channels by license, as 3CX does, we check this in advance.
How it works
Trunk, call events, and data sync
Trunk
PBX and platform linked by a trunk
The software PBX and the platform are connected by a SIP trunk, or by IAX if your PBX supports it. We agree on the codec and keep extension ranges from overlapping. The trunk carries transfers between systems and calls to short extensions.
- SIP or IAX
- No overlapping ranges
- Channels per PBX license
ProtocolSIP or IAXper PBX capabilitiesCodecG.711matchedNumbersPBX rangesno overlapsChannelsper PBX licenseverifiedEvents
What the platform knows about PBX calls
If the PBX is built on Asterisk, as Elastix is, the platform receives its call events through AMI: who is calling whom, when the call was answered, and how long it lasted. With other PBXs, such as 3CX, data comes through their API, and what's available depends on the version.
- Asterisk-based PBX – via AMI
- Other PBXs – via their API
- A shared call log
Callext. 214 → customerwho called whomReplyafter 7 sanswer timeHangup2 min 40 sdurationLogPBX and platformsharedCRM
Call outcomes in the customer record
Every call on the line stays in the history with its audio and outcome, then syncs to your CRM – Bitrix24, Kommo (amoCRM), or any system that has an API. Sales and support see one history, even if some staff call through the PBX.
- Recording and outcome on the customer
- Sync to the CRM
- One history for every department
Bitrix24call with recordingsentKommo (amoCRM)call wrap-upsentOther CRMvia APIon requestHistoryone for all teamssharedSetup
How we connect your software PBX
- 01AssessmentWe review your PBX and its version, the number of users, license limits, and how your carriers are connected.
- 02DesignWe decide which system answers calls first – the platform or the PBX – and which lines move to the platform.
- 03TrunkWe link the PBX and the platform with a trunk so calls pass freely between them.
- 04EventsWe connect PBX call events: through AMI if the PBX runs on Asterisk, or through its API.
- 05CRMWe set up syncing of calls and outcomes to your CRM so managers see them in the customer record.
- 06TestingWe test transfers to and from the office, short extensions, and call recording on the line.
Requirements
What you'll need
- PBX
- 3CX, Elastix, or another software PBX with SIP
- Trunk
- Free channels on the PBX side
- Access
- A PBX administrator to configure the trunk
- Events
- AMI for Asterisk-based PBXs, API for others
- Platform
- Hosting option of your choice
- Billing
- Trunk and event setup – support hours
Preparation
What to have ready
Q&A
Frequently asked questions
Do we need to replace our PBX?
No. The two systems are linked by a trunk and work together.
Which software PBXs do you connect?
Any PBX that supports SIP trunks, such as 3CX and Elastix. FreeSWITCH and Kamailio have their own connection setups.
Can calls be transferred between the PBX and the contact center?
Both ways: an agent hands a customer off to the office, and an office employee sends a caller to the sales or support line.
Can the platform answer calls before the PBX?
It can. Incoming calls go through the platform's IVR first, and calls for departments on the PBX are passed over the trunk.
Will managers see calls that go through the PBX?
With an Asterisk-based PBX, its call events land in the platform's shared call log. With other PBXs, it depends on their API.
Does the PBX license limit the number of calls?
Some PBXs, such as 3CX, cap concurrent calls by license. We check this up front to make sure you have enough channels.
Will calls show up in the CRM?
Both the audio and the outcome of each call show up in the customer record and in your CRM.
Will calls be recorded?
The platform records calls that go through its queues. Calls inside the PBX are recorded by the PBX itself, if recording is turned on in its settings.
Can we move to the platform completely later on?
You can. Departments move one at a time, and the PBX keeps running until the last user has moved, serving as a backup.
How is the work priced?
You pay nothing for licenses. Work on the trunk, event sync, and the CRM comes out of your support plan hours, and we estimate it once we've looked at your PBX.
Glossary
Terms on this page
- IP PBX
- A company phone system that runs over the internet and your local network. Learn more →
- CRM – customer relationship management
- Where a company keeps its customers, deals, and full communication history. Learn more →
- API (application programming interface)
- The way programs exchange data with each other without a person in the loop. Learn more →
- SIP (Session Initiation Protocol)
- The protocol that sets up calls in IP telephony. Learn more →
- AMI – Asterisk Manager Interface
- The channel where Asterisk reports calls and takes commands. Learn more →
- Support tiers
- A support tier: tier 1 handles common issues, tier 2 handles complex ones. Learn more →
- IVR (interactive voice response)
- A phone menu: the caller hears a greeting and picks the right department. Learn more →
- Backup
- Data is regularly copied to a separate place so it can be restored if something goes wrong. Learn more →
- Customer record
- The screen of customer data an agent sees during a conversation. Learn more →
- SIP trunk
- A phone line from the carrier over the internet instead of a wire. Learn more →
- Call recording
- Calls are saved so they can be replayed and disputes settled. Learn more →
- Call queue – callers waiting to be answered
- Callers waiting for an available agent. Learn more →
- Hosting
- You rent a server from a provider instead of buying one. Learn more →
Updated: