CTI Connector
A CTI Connector in Salesforce is the broader installable package that bundles a CTI Adapter, the Call Center definition file, supporting Lightning components, and any vendor-specific configuration UI that connects a telephony provider to Salesforce.
Definition
A CTI Connector in Salesforce is the broader installable package that bundles a CTI Adapter, the Call Center definition file, supporting Lightning components, and any vendor-specific configuration UI that connects a telephony provider to Salesforce. The terms Adapter and Connector are often used interchangeably in vendor marketing, but in practice a Connector is the AppExchange-installable bundle, while the Adapter is the JavaScript code inside it that runs in the Salesforce console softphone.
Most major telephony vendors (Five9, Talkdesk, Genesys, RingCentral, NICE inContact, Dialpad, Amazon Connect partners) ship their integration as a Connector through the AppExchange. The Connector installs as a managed package, brings along the adapter and configuration, and surfaces in Setup as a Call Center plus any custom objects the vendor needs. Service Cloud Voice ships its own Connector as part of the SCV package.
What is in a CTI Connector and how it differs from a bare Adapter
What the Connector package includes
A typical CTI Connector is a managed AppExchange package that includes: the JavaScript Adapter that runs in the softphone iframe, the Call Center definition file that registers the adapter, Lightning Web Components or Aura components for any vendor-specific UI (call history panels, queue monitors), custom objects for vendor configuration (skills, queues, agent settings), permission sets that grant access to the components, and a setup wizard that walks the admin through initial configuration.
Connector vs Adapter: terminology overlap
In strict usage, the Adapter is the JavaScript code. The Connector is the package that includes the Adapter plus everything else. In casual usage, many vendors and admins use the terms interchangeably. Documentation from Salesforce and vendors often switches between them within the same article. The practical answer: when someone says CTI Connector, they usually mean the full installable package.
Installing a Connector through AppExchange
The standard path is to find the vendor Connector listing on the AppExchange, click Get It Now, sign in to Salesforce, pick the org to install into, and approve the install. Installation creates everything in the package: custom objects, permission sets, Call Center, and the Lightning components. Post-install, the admin runs the wizard to configure tenant credentials and assign users.
Connector-specific configuration
Beyond the Call Center file, Connectors usually have their own configuration screens. The vendor tenant ID, API credentials, queue mappings, agent skill assignments, and call recording preferences all live in the Connector custom objects or in named credentials. The Salesforce Setup UI does not know about these; the Connector ships its own UI.
Service Cloud Voice as the first-party Connector
Service Cloud Voice (SCV) is technically a Connector, but it is Salesforce-built and Salesforce-managed. It ships as part of the SCV product license, not as a separate AppExchange install. The Connector includes the adapter, the Voice Call object, transcription services, and Amazon Connect integration. SCV is the most tightly integrated Connector by design.
Connector upgrade and version management
Vendor Connectors upgrade through standard Salesforce managed package upgrades. The vendor publishes a new version on AppExchange, admins click Upgrade in the Installed Packages list, and Salesforce applies the changes. Major upgrades sometimes change the Call Center file or add new permission sets that need re-assignment. Always test upgrades in sandbox first.
Picking between Connectors
Choice of Connector depends on three things: which telephony platform the company already uses, the depth of features the Connector exposes (AI agent assist, call analytics, real-time monitoring), and the price point. Most enterprises pick the Connector that matches their existing phone vendor. Greenfield deployments often pick Service Cloud Voice or Amazon Connect for the first-party integration.
How to evaluate and install a CTI Connector
Picking a Connector is mostly about phone vendor relationships and feature depth. Installation is a standard AppExchange package install plus tenant configuration.
- Identify your telephony platform and supported Connectors
List the phone vendors that have Salesforce Connectors. Most major ones do. If your phone vendor is not on the list, evaluate switching or building a custom Connector.
- Pilot in sandbox
Install the vendor Connector in a sandbox. Walk through the included setup wizard. Test core flows: inbound call screen pop, outbound click-to-dial, call log to Voice Call or Task.
- Verify feature coverage
Compare the Connector features to your business requirements: skills-based routing, call recording, real-time agent monitoring, conversation analytics. Some Connectors are surface-level; others go deep.
- Compare to Service Cloud Voice
For any new deployment, do a parallel evaluation of SCV. The first-party integration depth is significantly higher; the trade-off is licensing cost and the requirement to move telephony to Amazon Connect.
- Plan tenant credential storage
Connectors store telephony vendor API keys in Salesforce. Use Named Credentials or the Connector recommended pattern; do not hardcode credentials in custom fields.
- Install in production after sandbox sign-off
Repeat the install in production. Train agents and supervisors on the Connector-specific UI before go-live.
- Connector and Adapter are often used interchangeably. Read the vendor documentation for what is in the package, not just the marketing material.
- Vendor Connectors require a vendor license for the underlying telephony service in addition to the Salesforce installation. The Salesforce side is free; the phone side is not.
- Some Connectors have hard dependencies on Service Cloud Voice; check before installing on a Sales Cloud-only org.
- Connector packages can grow large enough to bump against Salesforce managed-package field count and tab count limits. Audit before installing on a mature org.
- Connector upgrades may add new permission sets that require manual assignment; users without the new perms hit unexpected errors.
Trust & references
Straight from the source - Salesforce's reference material on CTI Connector.
- Service Cloud Voice OverviewSalesforce Help
- Set Up a Call CenterSalesforce Help
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 CTI Connector?
Q2. Which of these is a typical CTI Connector feature?
Q3. Where are CTI Connectors typically distributed?
Discussion
Loading discussion…