Softphone CTI Adapter
A Softphone CTI Adapter in Salesforce was a browser plugin (a desktop-installed binary) that connected a user deskphone or softphone software to the Salesforce UI.
Definition
A Softphone CTI Adapter in Salesforce was a browser plugin (a desktop-installed binary) that connected a user deskphone or softphone software to the Salesforce UI. The Adapter delivered screen pops for incoming calls, click-to-dial outbound calling, and call logging directly into Salesforce records. It was the original mechanism for tying telephony into Salesforce, dating from the late 2000s.
The Adapter has been retired in favor of Open CTI, a JavaScript-based API that lets phone vendors integrate with Salesforce through a Lightning component or a Visualforce page rather than a desktop binary. Open CTI runs entirely in the browser, supports modern phone systems (cloud-based softphones, WebRTC), and does not require user-level installation. Existing Softphone CTI Adapter deployments still work on some browsers but no new investment goes into the technology; every new phone integration should use Open CTI instead.
Softphone CTI Adapter in 2026: legacy mechanics, retirement, and the migration to Open CTI
What the original Softphone CTI Adapter actually did
The Softphone CTI Adapter was a small piece of software the user installed on their Windows or Mac desktop. The Adapter listened on a local port, registered with the desktop phone system (Cisco, Avaya, Genesys, Mitel, depending on the vendor), and exposed an API that the Salesforce browser plugin could call. When the phone rang, the desktop Adapter detected the call, looked up the caller in Salesforce, and surfaced a screen pop on the user Lightning or Classic UI. When the user clicked a phone number on a record, the Adapter dialed it through the desk phone. Call activity (start time, end time, outcome) was logged back to Salesforce as a Task record. Without the Adapter installed, none of this worked.
Why the Adapter approach was retired
Salesforce retired the Softphone CTI Adapter for three reasons. First, browser plugins (NPAPI, then ActiveX) were deprecated by every modern browser due to security concerns. Without browser plugin support, the Adapter communication channel between desktop and browser broke. Second, the Adapter required user-level installation and ongoing maintenance, which made it expensive to support at scale. Third, modern telephony moved from desk phones to cloud-based softphones (Zoom Phone, Dialpad, RingCentral, Five9), and those systems already run as web applications that do not need a desktop adapter to integrate. Open CTI replaced the Adapter with a JavaScript API that runs in the browser, requires no plugin, and integrates with any modern web-based phone system.
Open CTI: the modern replacement
Open CTI is a JavaScript API that Salesforce ships with the platform. Phone system vendors build a Salesforce-side Lightning component (or Visualforce page in Classic) that hosts the vendor phone UI. The component calls Open CTI methods to query for caller records, display screen pops, control the agent softphone, and log call activity. The whole interaction runs in the browser; nothing is installed on the user desktop. Every major phone vendor that integrates with Salesforce ships an Open CTI implementation today. AppExchange listings for Cisco Webex Contact Center, Genesys Cloud, Five9, Aircall, Talkdesk, and most others are all Open CTI based. Migrating from a Softphone CTI Adapter deployment to an Open CTI deployment is a vendor-led project.
Migration: from Adapter to Open CTI
Migrating from a Softphone CTI Adapter to Open CTI is mostly a vendor-coordinated project. The phone vendor publishes (or has already published) an Open CTI implementation packaged as an AppExchange listing. The Salesforce admin installs the package, configures the Call Center record in Setup (which lets users see the softphone in Lightning or Classic), and assigns users to the Call Center. The vendor takes care of the JavaScript component and the connection back to their phone system. Custom Apex logic that depended on the Adapter (Task creation rules, screen pop customizations, custom telephony fields) may need rework to use the Open CTI hooks instead. Plan the migration as a quarter-long project per phone system; do not try to swap on a single weekend.
When Softphone CTI Adapter knowledge still matters
In 2026, Softphone CTI Adapter knowledge matters in three scenarios. First, certification exams. The System Architect and CTA exams still reference the Adapter for historical context, since understanding the platform evolution is part of the architecture role. Second, mature orgs running an older on-prem phone system (Cisco UCM, Avaya, Mitel) may still have Softphone CTI Adapter deployments in production; rotating those out is part of the platform modernization roadmap. Third, troubleshooting legacy integrations: when a Softphone CTI Adapter user reports screen pops not working, the root cause is usually browser plugin disablement or a Windows OS update breaking the local port the Adapter listens on. None of these are reasons to build new on the Adapter; all of them are migration drivers.
The broader contact center direction inside Salesforce
Beyond the Adapter to Open CTI shift, Salesforce has invested heavily in Service Cloud Voice, which is a built-in telephony product that includes a Salesforce-hosted softphone and (optionally) Amazon Connect under the hood for call routing. Service Cloud Voice is what Salesforce recommends for new contact center implementations; it eliminates the need for a separate telephony vendor and a separate CTI integration entirely. Open CTI remains the right answer when the customer already has a phone vendor relationship they want to keep; Service Cloud Voice is the right answer for greenfield contact centers. Softphone CTI Adapter is the right answer for nothing in 2026 except finishing existing migrations off it. Architects designing a new contact center should evaluate Service Cloud Voice first, Open CTI second, and the Adapter never.
Migrating from Softphone CTI Adapter to Open CTI
In 2026, the operational task around Softphone CTI Adapter is migration off it, not new deployment. Browser plugin support is gone, vendor maintenance is in maintenance-only mode, and the user experience degrades on every browser upgrade. The migration path goes to Open CTI in most cases, or to Service Cloud Voice for greenfield contact center work. This guide covers the Open CTI migration, which is the higher-effort and higher-impact path that most existing Salesforce orgs running the Adapter need to follow over the next 12 to 24 months.
- Inventory the existing Softphone CTI Adapter deployment
Document the current state: which phone vendor (Cisco, Avaya, Genesys, Mitel, other), how many users have the Adapter installed, which Salesforce Lightning or Classic UI is in use, which custom Apex or Visualforce code depends on the Adapter, and what custom screen-pop logic the team relies on. Capture the current call volume and the SLA the contact center operates under. The inventory is the source of truth for the migration scope; without it, you cannot estimate the rework effort or set a realistic timeline. Share the inventory with the phone vendor account team so they can scope their side of the project.
- Engage the phone vendor for the Open CTI package
Contact the phone vendor and confirm they have an Open CTI implementation available on AppExchange. For tier-one vendors (Cisco, Genesys, Avaya, Mitel, Five9, NICE), this is a yes. For smaller or specialized vendors, you may need to push them to publish, or migrate to a different vendor that already has Open CTI. Get the vendor to commit to a migration plan: their package version, the user provisioning steps on their side, the supported Salesforce editions, and the expected migration window. Document the plan with named owners on both sides; vendor migrations stall without explicit ownership.
- Install Open CTI in sandbox and migrate custom logic
In a sandbox refreshed from production, install the vendor Open CTI AppExchange package. Configure the Call Center record in Setup, including the SCV-XML configuration the vendor publishes. Assign a pilot user group to the new Call Center. Migrate any custom Apex logic that depended on the old Adapter to use Open CTI hooks instead: screen pop customizations move from the Adapter pop logic to the Lightning component lifecycle hooks; call logging customizations move to the Open CTI logging API; custom telephony fields stay in place if the field references the standard Call object. Test thoroughly with the pilot users for two weeks before promoting.
- Roll out, decommission, and document
Roll out Open CTI to production users in waves: pilot for two weeks, then 25 percent of users for one week, then 50 percent, then full population. After each wave, monitor call volume, screen pop success rate, and user-reported issues. Once the full population is on Open CTI, deactivate the old Softphone CTI Adapter Call Center, document the rollback path (in case of unexpected issues), and remove the Adapter desktop installer from the IT software catalog. Update the org telephony runbook and the user training materials. Set a date in three months to validate the migration is sticking; users sometimes regress to old behaviors when frustrated.
- Browser plugin support is gone. Modern browsers (Chrome, Edge, Firefox, Safari) all dropped NPAPI and ActiveX. Softphone CTI Adapters that depend on plugins do not work on current browsers; users may be running degraded older browsers.
- Open CTI is a vendor-coordinated migration. Without an Open CTI package from your phone vendor, you cannot migrate. Smaller vendors may not have shipped one; verify availability before committing to the timeline.
- Custom Apex and Lightning code that called Adapter-specific APIs has to be rewritten to use Open CTI hooks. Estimate this rework explicitly during the inventory step; surprise rework derails the project.
- User-side Adapter installation requires admin rights on the desktop. Removing the Adapter at decommission time also requires admin rights. Coordinate with IT to push the removal through the standard software management tools.
- Service Cloud Voice is the strategic Salesforce direction for new contact centers. Evaluate it as an alternative to Open CTI for greenfield projects; Open CTI is the right answer only when the customer wants to keep an existing phone vendor relationship.
Trust & references
Straight from the source - Salesforce's reference material on Softphone CTI Adapter.
- Open CTI Developer GuideSalesforce Developer Docs
- Call Centers OverviewSalesforce Help
- Service Cloud Voice OverviewSalesforce 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 was the Softphone CTI Adapter?
Q2. Why was it replaced?
Q3. What replaces it?
Discussion
Loading discussion…