Softphone Connector
A Softphone Connector is the vendor-built JavaScript layer that wires a third-party phone system into the softphone panel Salesforce renders inside the Service Console.
Definition
A Softphone Connector is the vendor-built JavaScript layer that wires a third-party phone system into the softphone panel Salesforce renders inside the Service Console. It listens for call events coming off the telephony platform: ringing, answered, held, transferred, ended. It pushes those into the Salesforce UI, then sends the agent's clicks back down to the phone system.
Connectors run on Open CTI, the browser-based API Salesforce publishes for exactly this purpose. Salesforce supplies the API and the Call Center configuration record. The telephony vendor writes and hosts the Connector itself, usually shipping it inside an AppExchange managed package. Capabilities differ sharply from one provider to the next as a result.
The Softphone Connector is the older way to put a phone in Salesforce. Salesforce deprecated Open CTI and moved it into maintenance mode, with retirement set for February 28, 2028. Newly created Agentforce Service orgs cannot use it at all. The newer option is Salesforce Voice, branded Service Cloud Voice until recently. Existing Connectors run until the retirement date, but nothing is being added to the API underneath them.
In plain English
“Your phone system and Salesforce are two separate programs that do not speak the same language. The Connector is the translator sitting between them. When a call comes in, it tells Salesforce to show you the caller's record. Click the hang-up button on screen and it tells the phone system to drop the line. Salesforce is retiring the plumbing this translator runs on, so most teams are moving to a newer setup.”
Worked example
A 400-agent insurance claims team keeps its existing phone platform and installs the vendor's Open CTI managed package. An admin imports a call center definition file in Setup, with reqAdapterUrl pointing at the vendor's HTTPS-hosted Connector. The agents then get assigned to that Call Center record. A policyholder dials in from +1-416-555-0142. The Connector catches the ringing event, calls sforce.opencti.searchAndScreenPop with that number, and Salesforce matches Contact.Phone on the record for Priya Raman. Her contact page opens in the console before the agent finishes saying hello. When the call ends four minutes later, the Connector writes a Task with Subject set to Inbound Call and CallDurationInSeconds set to 252.
Inside the Connector: the contract, the config file, and the 2028 clock
The five jobs a Connector actually performs
Strip away the branding and every Connector does the same five things. It registers the agent with the phone platform when they log into Salesforce. It keeps agent state in sync so a Ready flag in one system does not contradict the other. It translates telephony events into console updates, so a held call actually looks held on screen. It asks Salesforce to find and open the right record when a call lands. And when the line drops, it writes the activity record that makes the call auditable later. Vendors differentiate on how gracefully they handle the awkward cases. Warm transfers, extra conference legs, and agents who close the browser tab mid-call.
The Open CTI contract a Connector implements
Open CTI is a browser-based JavaScript API, which is the entire point of it: nothing gets installed on the agent's machine. The Connector is hosted either on a Visualforce page or on the vendor's own HTTPS domain, and Salesforce loads it into the softphone panel. From there it calls documented methods. sforce.opencti.searchAndScreenPop finds matching records and surfaces one. enableClickToDial turns phone fields in the console into dial links. setSoftphonePanelVisibility shows or hides the panel as call state changes. Salesforce publishes two separate method sets, one for Lightning Experience and one for Salesforce Classic, and they are not interchangeable. Code written against the Classic methods needs genuine porting work, not a config toggle.
The call center definition file is where deployments break
Salesforce learns a Connector exists through a Call Center record, created by importing an XML definition file in Setup. The element that matters most is reqAdapterUrl, which points at the URL hosting the Connector. Use HTTPS; the docs are explicit about it, and mixed content simply fails to load without a useful error. Once the record exists, you assign users to it from the User detail page or through your provisioning process. Orgs running two phone vendors create two Call Center records and split users between them. When a softphone panel renders blank, the cause is almost always this file. Usually a wrong URL, a typo in an element name, or an unassigned user.
Screen pop is the feature people buy, and the one that misfires
The default lookup takes the caller's number and searches phone fields on Contact, Account, and Lead. A single clean match opens that record. Nothing matching leaves the agent on a blank tab, which is annoying but honest. The messy case is multiple matches, and it turns up constantly. Think shared household landlines, a switchboard number stored on forty contacts, or a number the carrier recycled and reissued. The Connector decides what happens next, either showing a picker or applying vendor tiebreaker rules. Teams that need better accuracy stop matching on phone number entirely and pass an identifier collected in the IVR instead. Train agents on what a wrong pop looks like either way. A confidently wrong record produces worse notes than no record at all.
Salesforce moved it under Explore Legacy Service Features
Setup navigation is a decent proxy for product strategy, and this one is not subtle. Call center configuration now sits under Explore Legacy Service Features, then Open CTI, then Learn and Set Up Open CTI. If you last touched this a few years ago and go hunting for a top-level Call Centers node, that is why you cannot find it. The functionality is unchanged and the definition file format still works. The label is the message. Anyone maintaining runbooks or onboarding docs that reference the old path should update them now. A new admin will read the word Legacy and reasonably ask whether they should be building here at all. They should not, if they have a choice.
What replaces it, and how much runway you actually have
Salesforce Voice is the named successor, and the shape of the migration depends on which flavour you land on. Salesforce Help lists a managed offering, a partner telephony option, and an Amazon Connect option. Partner telephony matters most if you already hold a carrier contract. It lets you keep the provider and swap the integration layer underneath, which is a smaller project than replacing the phone system. Still a project, though. On runway: Salesforce commits to supporting each Open CTI version for at least three years from first release. Dropping a version comes with a year of notice. So a working Connector will not fall over next quarter. Budget the replacement anyway, because maintenance mode means every gap you find in the API from here stays a gap.
How organizations use Softphone Connector
Leans on the Connector's end-of-call write-back rather than its screen pop, because the regulator wants a Task with a duration against every customer conversation.
Runs two Call Center records: the support team on a cloud phone vendor, the sales team on an outbound dialer. Every user is assigned to exactly one.
Watches agent state drift when the Connector loses its session. People stay marked Ready in Salesforce while the phone platform has stopped routing to them.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Softphone Connector.
Hands-on resources to go deeper on Softphone Connector.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
+5 pts / dayQ1. When is Open CTI, the API that Softphone Connectors run on, scheduled for retirement?
Q2. A freshly imported Call Center loads a blank softphone panel for every assigned user. What should you check first?
Q3. Who writes and hosts the Softphone Connector itself?
Discussion
Loading discussion…