Private Branch Exchange (PBX)
A Private Branch Exchange (PBX) is a private telephone system that an organization runs to route calls between its own staff and the outside world.
Definition
A Private Branch Exchange (PBX) is a private telephone system that an organization runs to route calls between its own staff and the outside world. It owns the internal extensions, the call queues, and the lines that connect to the public phone network, so callers reach the right person without going through the carrier for every hop.
In a Salesforce context, the PBX is the phone system that sits behind a contact center. It is not a Salesforce feature itself. Salesforce connects to it through a computer telephony integration (CTI) layer, usually Open CTI or Salesforce Voice, so that calls handled by the PBX can trigger screen pops, click-to-dial, and call logging inside the agent's console.
How a PBX plugs into a Salesforce contact center
What a PBX actually does
A PBX is the switchboard for a business. Instead of buying a separate phone line from the carrier for every employee, the company runs one system that owns a pool of internal extensions and a smaller number of outside lines or trunks. When someone dials a four-digit extension, the PBX connects that call internally and never touches the public network. When a customer calls the main number, the PBX answers, applies its routing rules, and rings the right queue or person. Traditional PBX hardware lived in a wiring closet and used analog or digital phone lines. Most systems today are IP-based, which means calls travel as data over the network using Voice over IP (VoIP). That shift is what makes integration with software like Salesforce practical. An IP PBX can expose events and call data to other applications, so a CRM can react the moment a call arrives. The PBX still owns the dial tone, the hold music, and the call routing. Salesforce sits on top of that, reading what the PBX is doing and giving the agent a place to work the call. Understanding this split matters, because most telephony problems in a Salesforce project trace back to the PBX side, not the Salesforce side.
The role of CTI between phone and CRM
Computer telephony integration is the bridge that lets a phone system and a CRM talk to each other. The PBX knows there is a live call and who is calling. Salesforce knows everything about that caller as a customer record. CTI is what passes the phone number from one side to the other and lets the agent control the call from inside the application. On the Salesforce platform, the common bridge is Open CTI. It is a browser-based JavaScript API that lets partners and customers build telephony systems that integrate directly with Salesforce Call Center. The official guide is blunt about the benefit: agents can make calls from a softphone directly in Salesforce without installing CTI adapters on their machines. Everything runs in the browser, which removes a large desktop deployment headache. A vendor uses these APIs to wire their PBX or contact center platform into the Salesforce UI. The agent then sees one screen, not a phone app next to a browser tab. Without this layer, a PBX and Salesforce stay two separate tools, and agents copy phone numbers and notes by hand between them.
Call centers, softphones, and the call center definition
When you connect a PBX through Open CTI, the integration is registered in Salesforce as a Call Center. A Call Center is configured with a call center definition, which is an XML file that describes how the telephony system connects and which settings the softphone should use. An admin imports that file, then assigns users to the call center so they get the phone tools. The visible result for an agent is a softphone. This is a call-control panel that lives in the utility bar in Lightning Experience, or the sidebar in the older Classic interface. From the softphone the agent answers, holds, transfers, and ends calls, all without leaving the record they are reading. The softphone layout controls what Salesforce searches for and displays when a call comes in. Open CTI methods such as getSoftphoneLayout, setSoftphoneHeight, and enableClickToDial let the vendor's code shape that panel and turn phone numbers on the page into clickable dial links. The PBX drives the actual audio, while Salesforce supplies the window the agent works in.
Screen pops and click-to-dial, where the value shows up
The features that make integration worth the effort are screen pops and click-to-dial. A screen pop fires when a call arrives. The PBX hands the caller's number to Salesforce, Salesforce searches for a matching contact, account, or case, and the relevant record opens on the agent's screen before they say hello. That saves the agent from asking for an account number and digging through search. If the number matches nothing, the integration can open a new record so the agent starts from a clean slate. Click-to-dial works the other direction. Any phone number rendered on a Salesforce page can become a clickable link. When the agent clicks it, Open CTI tells the PBX to place the call, so nobody misdials a number typed by hand. Salesforce can also log the call automatically, writing a task or activity tied to the record with the call's time, duration, and the agent's notes. These three behaviors, screen pop, click-to-dial, and automatic logging, are the day-to-day payoff of connecting a PBX to the CRM. They cut handle time and keep the activity history accurate without extra clicks.
Open CTI is retiring, and what replaces it
There is a clock on the classic integration path. Salesforce has announced that Open CTI is in maintenance mode and is scheduled for retirement on February 28, 2028. Maintenance mode means it still works and still gets security fixes, but it receives no new features. Any contact center built on Open CTI today should have a migration plan, because the platform is steering customers toward Salesforce Voice for long-term support. Salesforce Voice (also known as Service Cloud Voice) is the modern, native phone channel. It brings the call into the Service Console alongside chat, email, and other channels, and adds real-time transcription and AI features that Open CTI cannot offer. Salesforce Voice supports more than one telephony model. You can use Amazon Connect as the underlying phone system, you can keep your existing provider through Partner Telephony (often called bring your own telephony), or you can connect a contact center platform through Bring Your Own Channel for CCaaS. Partner Telephony is the path that lets an organization keep its current PBX or provider while still getting the native console experience.
Planning a PBX integration that holds up
A phone integration touches more teams than a typical Salesforce change. The telephony vendor owns the PBX and the managed package, the network team owns the connectivity, and the Salesforce admin owns the call center setup and the agent experience. Misalignment between them is the usual reason a rollout slips. Get all three in the room before you commit to dates. Test the call flow end to end with real scenarios, not just a single happy-path call. Try an inbound call that matches an existing contact, one that matches nothing, a transfer between agents, and a call where the customer hangs up early. Each of those exercises a different part of the screen pop and logging logic. Pilot with a small group of agents before a full launch, because the softphone is the tool they live in all day and small annoyances compound fast. Finally, weigh the Open CTI retirement date against your timeline. If you are standing up a new contact center now, building on Salesforce Voice with Partner Telephony usually beats investing in an Open CTI integration you will have to replace before 2028.
Connect a PBX to Salesforce with a Call Center
To connect an existing PBX or telephony provider to Salesforce, an admin sets up a Call Center that points at the integration. The exact files come from your telephony vendor. These steps describe the Open CTI path; for a new build, prefer Salesforce Voice with Partner Telephony instead.
- Get the call center package from your vendor
Most telephony providers ship a managed package or a call center definition XML file. Install the package from AppExchange or obtain the definition file from the provider. This is what tells Salesforce how to reach the PBX.
- Import or create the Call Center
In Setup, search for Call Centers, then import the vendor's call center definition file. If the vendor uses a managed package, the call center record may already be created for you during install.
- Assign agents to the call center
Open the call center record and add the users who should get the softphone. Only assigned users see the phone tools, so this step controls who can take calls.
- Add the softphone and a softphone layout
Make sure the softphone appears in the utility bar of the agent's Lightning app, then configure a softphone layout to control what Salesforce searches for and displays on an incoming call.
- Test screen pop, click-to-dial, and logging
Place test calls in both directions. Confirm a matching record pops, a clicked number dials, and the call writes an activity to the record. Fix mismatches in the softphone layout or vendor mapping before launch.
The configuration file that describes how the telephony system connects to Salesforce and which softphone settings apply.
Controls which objects Salesforce searches and which fields it shows when a call arrives, driving the screen pop behavior.
Determines which agents are members of the call center and therefore see and use the softphone.
Where the softphone lives in Lightning Experience so agents can control calls without leaving the record.
- Open CTI is in maintenance mode and retires on February 28, 2028, so a fresh integration built on it has a limited shelf life.
- The PBX, not Salesforce, owns call routing and audio quality. Most "Salesforce phone" problems are actually network or PBX configuration issues.
- Screen pops only work if the caller's number matches a record. Plan for the no-match case so agents are not left on a blank screen.
- Softphone behavior differs between Lightning Experience and Salesforce Classic because they use different Open CTI APIs.
Prefer this walkthrough as its own page? How to Private Branch Exchange (PBX) in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Private Branch Exchange (PBX).
Hands-on resources to go deeper on Private Branch Exchange (PBX).
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Private Branch Exchange (PBX) in a Salesforce telephony context?
Q2. How does a PBX typically integrate with Salesforce to enable screen pops?
Q3. What is a common modern cloud alternative to an on-prem PBX in Salesforce contact centers?
Discussion
Loading discussion…