CTI Connector
A CTI Connector is the installable Salesforce package a telephony vendor ships to wire its phone platform into the Salesforce console.
Definition
A CTI Connector is the installable Salesforce package a telephony vendor ships to wire its phone platform into the Salesforce console. Install it and agents answer calls from a softphone inside Service Console. Inbound calls pop the matching record, and the call logs itself against that record, so nobody needs a second desktop application.
The word gets used loosely. Strictly, the Connector is the whole managed package and the CTI Adapter is the JavaScript inside it that talks to Salesforce through Open CTI. Vendors and admins swap the two freely, so listen for which layer someone actually means.
Every classic connector of this kind depends on Open CTI, which is now the older option. Salesforce put that framework in maintenance mode and set its retirement for February 28, 2028. It is already unavailable in newly created Agentforce Service orgs. The named replacement is Salesforce Voice.
In plain English
“Think of your phone system and Salesforce as two apps that cannot hear each other. A CTI Connector is the ready-made kit you install so they can. Once it is in, the phone controls sit right inside Salesforce and the caller's record opens by itself. Salesforce is now steering new setups toward a newer kit instead.”
Worked example
A 90-agent insurance claims team runs a third-party CTI connector installed from AppExchange. The admin deploys the managed package to a full sandbox first, then opens Setup, Call Centers and finds the record the package imported. Internal name stays as the vendor set it. Softphone Height goes to 550 and Softphone Width to 300, so the panel clears the utility bar. Queue mapping happens in the vendor's own settings object: the AutoFNOL telephony queue maps to the Auto Claims skill, PropertyFNOL to Property Claims. Twelve pilot users get the Call Center record assignment plus the vendor permission set, because neither one alone renders a softphone. The team then tests inbound, outbound, warm transfer, and conference on live numbers. Two checks close it out: the screen pop opens the matching Contact, and the call Task saves against it. Production install follows.
How a CTI Connector fits together, and where it stands now
What the vendor actually ships
Open a vendor package and the adapter is only one file among many. There is the JavaScript that loads inside the softphone iframe. There is an XML Call Center definition that registers the adapter URL and the softphone dimensions. Lightning Web Components come along too, for vendor screens like call history and queue monitors. Most packages add custom objects for concepts the Salesforce data model has no home for: agent skills, telephony queues, dispositions, recording preferences. Permission sets ship alongside, so you can grant component access without hand-building field-level security. Several vendors include a guided setup that collects tenant credentials and assigns users. Because it all arrives as one managed package, installing it is a single approval instead of a dozen manual steps. That packaging is the whole point. The adapter on its own would give you call control and nothing else. No history panel, no queue object, no configuration screen.
Connector, Adapter, or Call Center: which layer broke
From the agent seat every failure here looks identical: no softphone. The fixes are nowhere near each other, which is why the third layer matters. Alongside the package and its JavaScript sits the Call Center record. That record is the Salesforce-side registration naming which adapter URL to load and how big to draw the panel. Nothing renders until it exists and the user is on it. So triage by symptom instead of by guess. A blank space where the softphone should be usually means the Call Center record is wrong, or the user was never assigned to it. A softphone that draws itself and then sits dead usually means the code loaded but could not reach the telephony tenant. That one is the vendor's problem, not yours. A panel that works for one agent and not the next is almost never code at all. Rule out user assignment first. It causes most of these tickets and takes ten seconds to check.
Configuration lives in two places
Admins expect one settings screen and get two. Setup, then Call Centers, holds only what Open CTI cares about: internal name, adapter URL, standard keys version, softphone height and width. Everything platform-specific sits elsewhere, in the connector's own custom objects or in named credentials the vendor defined. Tenant IDs, API keys, queue-to-Salesforce mappings, skill assignments, and recording rules all live there, and Salesforce Setup has no idea they exist. The routing consequence is worth memorizing. A call reaching the wrong agent is almost always a vendor queue mapping problem. A softphone that loads at the wrong size, or refuses to load, is almost always the Call Center record. Write down which setting lives where before you hand the org to someone else, because nothing in the Salesforce UI will tell them.
Why this now sits under Legacy Service Features
Salesforce Help files Open CTI and Call Center under Legacy Service Features, and the developer guide explains the filing. The framework is in maintenance mode with retirement set for February 28, 2028. Nothing new is being built for it, so whatever method you were hoping for is not coming. Existing deployments are fine for now, and the Support Policy is more generous than the headline suggests. Salesforce commits to supporting each Open CTI version for a minimum of three years from the date of its first release. That protects an integration already written against a specific version. It does not push past the 2028 date, and it does not make any version worth building against today. Read it as a wind-down guarantee rather than a runway. If your contact center roadmap runs past 2028, a classic connector is the wrong floor to build on.
What Salesforce points you to instead
The recommended successor is Salesforce Voice, which the setup docs list as Salesforce Voice with Telephony Providers. If you learned this stack as Service Cloud Voice, current Help pages use the Salesforce Voice naming for the same family. It covers most of what Open CTI did, and it adds native Omni-Channel and Command Center integration. Transcription and AI call summaries run on platform data instead of inside a vendor iframe. Three deployment shapes exist: Salesforce-managed telephony, partner telephony delivered through a vendor package, and your own Amazon Connect instance. The partner option still involves installing a vendor package, so the word connector survives the transition even though the framework underneath changes. Migration is not a reinstall, though. Call history has to be moved. Agents have to be retrained on a different softphone. Any Apex or Flow logic keyed to the old adapter events has to be rebuilt, and that last one is usually what blows the estimate.
How organizations use CTI Connector
Keeps its on-premise phone platform and installs the vendor's connector, so call control lives inside Service Console instead of a second desktop application.
Runs a cloud telephony connector for screen pops on inbound calls, and has already put a Salesforce Voice migration into its next contract renewal.
Cannot install a classic connector there at all, so it starts on partner telephony under Salesforce Voice and skips the migration entirely.
Trust & references
Cross-checked against the following references.
- Other Voice Solutions | Open CTI Developer Guide (opens in new tab)Salesforce
- Open CTI Support Policy (opens in new tab)Salesforce
- Set Up a Call Center (opens in new tab)Salesforce
- Import a Call Center Definition File (opens in new tab)Salesforce
- Setup Prerequisites for Salesforce Voice with Telephony Providers (opens in new tab)Salesforce
Straight from the source - Salesforce's reference material on CTI Connector.
Hands-on resources to go deeper on CTI 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. What is the difference between a CTI Connector and a CTI Adapter?
Q2. An agent who already has the vendor permission set opens Service Console and sees no softphone at all. What should you check first?
Q3. Calls are reaching the wrong agent group, but the softphone loads correctly for everyone. Where does the problem almost certainly live?
Discussion
Loading discussion…