TL;DR

Salesforce CTI links your phone system to Salesforce so calls log themselves, the right record opens on every ring, and reps dial from the browser. You can buy bundled calling from a vendor, or keep the phone system you already run and connect it through Salesforce Open CTI. For teams already on 3CX, the second path is usually cheaper and avoids a phone-system migration. This guide covers how Salesforce CTI works, native versus third-party adapters, what each option really costs, and how to wire 3CX into Salesforce.

What Salesforce CTI actually is

CTI stands for computer telephony integration. In Salesforce, it means the link between your telephone system and the Salesforce interface, so a call event in the phone system becomes an action in the CRM. When a call comes in, Salesforce matches the caller number to a contact or lead and opens that record. When a rep finishes a call, the call is logged against the record with duration, direction, and notes. When a rep wants to dial out, they click a number in Salesforce and the phone system places the call.

Salesforce ships a framework called Open CTI. It is a JavaScript API that lets a telephony provider build a softphone panel that sits inside the Salesforce console. The softphone is the small call-control widget reps see in the corner of the screen. Open CTI replaced the older desktop CTI Toolkit, which required software installed on every machine. Open CTI runs in the browser, so there is nothing to install on the workstation and it works in Lightning Experience, Salesforce Classic, and the mobile app.

The practical result for a sales or support team is simple. Reps stop copying phone numbers between two windows. Calls stop going unlogged because logging is automatic. Managers get call data inside the same reports they already use for pipeline and cases, rather than in a separate phone-system dashboard nobody opens.

Native calling versus third-party CTI adapters

There are three broad ways to get calling into Salesforce, and the difference matters for both cost and control.

Salesforce-native calling

Salesforce sells its own calling product. It bundles the phone numbers, the minutes, and the softphone into a per-user subscription. It is the least work to turn on because Salesforce builds and maintains the integration. The trade-off is that you are buying a new phone system priced per seat, on top of any phone system you already pay for. For a team that has no phone system yet, this can make sense. For a team that already runs 3CX or another PBX, it means paying twice and migrating users off a working setup.

Third-party CTI adapter on top of your existing phone system

This is the path most established teams take. Your phone system stays where it is. A third-party adapter, built on Salesforce Open CTI, presents the softphone inside Salesforce and feeds call events back and forth. The adapter listens to the phone system for ring, answer, and hang-up events, then drives the Salesforce screen pop and call log. Because the phone system does not change, there is no migration, no porting of numbers, and no retraining on a new dialler. You add the CRM layer over the calls you already make.

Build it yourself with the APIs

Salesforce Open CTI and most phone systems both expose APIs, so a developer can wire the two together directly. This gives total control and no per-seat licence on the integration, but you own the build, the maintenance, and every breakage when either platform ships an update. For most MSPs and agencies the engineering time costs more than a packaged adapter, and the maintenance burden never ends.

The real cost of bundled telephony versus keeping your phone system

The headline price of native calling looks clean: one per-user fee. The full cost is rarely that tidy. When you replace a working phone system with a bundled one, you pay for the new per-seat subscription, plus the project to migrate, plus the time porting numbers, plus retraining, plus the call quality and feature gaps you discover after go-live. A 3CX deployment, by contrast, is already paid for, already configured, and already trusted by your team. Connecting it to Salesforce adds a thin integration layer rather than a whole platform.

A worked comparison helps. Take a 15-seat sales team. Bundled per-seat calling at a typical rate of around 30 US dollars per user per month is roughly 5,400 US dollars a year, and that is before usage overages, before the migration project, and before the productivity dip while reps learn a new dialler. Keeping 3CX and adding an integration layer removes the per-seat phone cost entirely, because the calls still run on the system you already own. The integration is the only new line item, and it scales with calls rather than seats. Over three years the gap widens, because the bundle keeps charging per seat every month while the kept-PBX path does not re-charge for the phone system you already bought.

This is the structural point that matters for buyers in 2026. Telephony has become a feature inside larger CRM and platform bundles, which is convenient but ties your call costs to your seat count forever. A phone system you own, connected to your CRM, breaks that link.

Screen pop and click-to-dial inside Salesforce

Two features deliver most of the day-to-day value of Salesforce CTI.

Screen pop. When a call arrives, the integration matches the caller ID against your Salesforce data and opens the matching record automatically. The rep answers already looking at the contact, their open cases, recent activity, and account. If no match is found, a well-built adapter offers to create a new lead from the number. Screen pop removes the five-to-ten second scramble at the start of every call and means the conversation starts with context.

Click-to-dial. Every phone number in Salesforce becomes a clickable link. The rep clicks, the phone system dials, the call connects, and the activity is logged against the record without anyone typing a number. For an outbound team working a list, this removes misdials and saves a few seconds on every call, which compounds across hundreds of calls a day.

Alongside those two, a complete integration also logs call duration and direction, attaches voicemail and recordings to the record where your phone system supports it, and can trigger CRM workflows on call events, for example creating a follow-up task when an outbound call goes unanswered.

Wiring 3CX into Salesforce via Open CTI

If you already run 3CX, the connection to Salesforce uses the Open CTI framework rather than a phone-system swap. At a high level the integration registers a softphone inside the Salesforce console, listens to 3CX call events through the 3CX call control interface, and maps caller numbers to Salesforce records for screen pop. Outbound clicks in Salesforce are passed to 3CX to place the call. Call results are written back to the Salesforce activity timeline.

The setup keeps 3CX as the source of truth for the call itself, which means call quality, routing, queues, and recording all stay inside the phone system your team already knows. Salesforce becomes the place the call is seen and recorded against the customer, not the place the call runs. For a step-by-step of the 3CX-to-Salesforce connection, see our guide to 3CX Salesforce integration. For the broader category background, the computer telephony integration guide covers the three CTI architectures and where Open CTI sits among them.

Frequently asked questions

Is Salesforce Open CTI free?
\n

The Open CTI framework itself is part of Salesforce and carries no separate licence. What costs money is the telephony and the adapter that uses the framework. If you keep your existing phone system and add a third-party adapter built on Open CTI, you avoid Salesforce per-seat calling fees and pay only for the integration layer over the calls you already make.

\n
Do I need to replace my phone system to use Salesforce CTI?
\n

No. The point of Open CTI is to connect the phone system you already run, such as 3CX, to Salesforce without a migration. Replacing the phone system with bundled native calling is one option, but it is not required and it is usually the most expensive route for a team that already has a working PBX.

\n
What is the difference between Open CTI and the CTI Toolkit?
\n

The CTI Toolkit was the older approach that required software installed on each desktop. Open CTI is the modern, browser-based replacement that needs nothing installed on the workstation and works across Lightning, Classic, and mobile. New integrations use Open CTI.

\n
Will screen pop work for unknown callers?
\n

Yes, with a well-built adapter. If the caller number matches a Salesforce contact or lead, that record opens. If there is no match, the adapter can prompt the rep to create a new lead from the number so the call is still captured rather than lost.

\n
Can call data flow into Salesforce reports and dashboards?
\n

Yes. Because calls are logged as Salesforce activities, call volume, duration, and direction sit alongside pipeline and case data, so you can build the same dashboards your managers already use rather than checking a separate phone-system report.

\n

About this article

Written by the Connect Zero team, an Australian-built Insights sold by Auswide IT, an Australian MSP integration vendor based in Adelaide. Last updated 29 May 2026.