Salesforce CTI integration: connect your 3CX phone system to Salesforce

What Salesforce CTI integration actually means

CTI stands for computer telephony integration: the link between a phone system and the software your team works in. Salesforce CTI integration is the specific case where the CRM is Salesforce. When it is set up, an agent sees an incoming call surface inside Salesforce with the matched record already open, can click a number in a record to dial out, and finds the call logged as an activity with a recording link when the call ends. For a deeper grounding in the category itself, the parent topic is covered in our computer telephony integration guide.

The reason people search for salesforce telephony integration and cti integration with salesforce is that the manual alternative is expensive in lost time. A sales rep who logs every call by hand loses minutes per call and forgets some entirely, which means the pipeline data in Salesforce is wrong. The point of the integration is that the system of record stays accurate without anyone typing it in.

Salesforce supports this through Open CTI, a JavaScript API that runs in the browser. A telephony vendor builds a call-control panel that Salesforce loads inside a Lightning component, and Open CTI handles the screen pop, the click-to-dial, and the activity write-back. Open CTI is the same framework whether the phone system behind it is a cloud contact-centre product or an on-premise or self-hosted PBX such as 3CX. The framework does not care where the dial tone comes from. That is the detail most buyers miss, and it is the reason you can keep 3CX.

The three ways to build a Salesforce CTI integration

There are three architectures, and the right one depends on what phone system you have and how deep the integration needs to go. We cover the general version of this in our CRM telephony integration explainer; here is the Salesforce-specific shape.

Path one: replace your phone system with a bundled cloud telephony product

The vendors that show up first when you search for salesforce cti are usually cloud phone products that include a pre-built Salesforce connector. You move your numbers to them, pay a per-seat monthly fee for the phone service, and the Salesforce integration comes in the box. This is the simplest path to buy and the most expensive to own, because you are paying twice: once for the telephony you already had, and again for the bundle. If you are starting from no phone system at all, it can make sense. If you already run 3CX, you are throwing away a working investment to solve an integration problem.

Path two: native Open CTI build by your phone vendor

If your phone vendor publishes a Salesforce-managed package built on Open CTI, you install it from AppExchange, authenticate, and the softphone appears in Salesforce. This is the cleanest experience when the vendor maintains the package. The limitation is that you are tied to whatever events that vendor chose to expose and to their release cadence. For 3CX specifically, the native Open CTI route is documented in our companion guide on connecting 3CX and Salesforce via Open CTI.

Path three: an integration layer between 3CX and Salesforce

The third path keeps 3CX as your phone system and puts a dedicated integration layer between it and Salesforce. The layer listens to 3CX call events, matches the number to a Salesforce record, fires the screen pop through Open CTI, and writes the call activity and recording link back when the call completes. You keep the phone system, the extensions, the call routing, and the licences you already own. You add only the connection. This is the approach Connect Zero for 3CX is built around, and it is the one that suits an agency or managed service provider who has already standardised on 3CX and does not want a forced migration to get clean Salesforce data.

What a Salesforce CTI integration costs

Cost depends entirely on which path you pick, and the headline price is rarely the real one. For a full breakdown of the hidden line items, see our analysis of the real cost of CRM-bundled telephony. The short version:

The trap on the bundled path is the per-seat compounding. A 3CX licence is a one-off or annual cost that does not scale linearly with every new agent. A bundled cloud phone charges per seat per month forever, so the gap widens as the team grows. The cost question is not really about the integration; it is about whether you re-buy telephony to get it. The cost-focused deep dive lives in our piece on how Salesforce CTI integration works and what it costs.

How the keep-your-3CX approach works in practice

Here is what the integration-layer path does on a live inbound call. The call hits your 3CX system as it always has. 3CX raises a call event that the integration layer is listening for. The layer takes the caller number, queries Salesforce for a matching contact, lead, or account, and uses Open CTI to pop that record on the agent screen before they answer. The agent talks, hangs up, and the layer writes a completed-call activity against the matched record with the call duration, direction, and a link to the 3CX recording. On outbound, the agent clicks a number in Salesforce, Open CTI passes the dial request to the layer, and 3CX places the call from the agent extension.

Nothing in that flow changes your phone system. You do not move numbers, you do not retrain on a new softphone for calling itself, and you do not pay a second telephony bill. The integration is additive. For the broader picture of every way to wire 3CX into a CRM, including Salesforce, see how to integrate 3CX with your CRM.

What to check before you start

A Salesforce CTI integration on 3CX has a few prerequisites worth confirming up front. You need a 3CX edition and licence tier that exposes the call-control API, which is the same requirement as any 3CX CRM integration. You need Salesforce in Lightning Experience for the Open CTI softphone to load in the modern UI. You need a Salesforce user profile with the right call-centre permissions assigned. And you need agreement on number matching: Salesforce stores phone numbers in varied formats, so the integration has to normalise them to match reliably, which is the single most common cause of a screen pop that fails to find the record. We cover the 3CX side of the prerequisites in our note on 3CX licence requirements for CRM integration.

Open CTI versus voip Salesforce integration: the same thing under two names

People search both open cti salesforce and voip salesforce integration, and they usually mean the same outcome from two angles. Open CTI is the Salesforce-side framework that renders the softphone and handles the screen pop. VoIP Salesforce integration is the same connection described from the telephony side, where the calls run over IP rather than a traditional phone line. 3CX is a VoIP phone system, so connecting it to Salesforce is by definition a VoIP Salesforce integration, delivered through the Open CTI framework. There is no third product to buy; the two terms describe the two ends of one connection.

Why agencies on 3CX should not switch phone systems to get Salesforce CTI

The marketing around salesforce cti pushes buyers toward replacing their phone system because that is what the bundled vendors sell. For an agency or managed service provider that has already deployed 3CX, configured call queues, trained staff, and paid for licences, that is the wrong default. The integration problem is solvable without touching the phone system. Keeping 3CX and adding a connection layer gives you the same Salesforce experience, the screen pop, the click-to-dial, the logged activity and recording, at a fraction of the lifetime cost of re-buying telephony per seat. The decision is not phone system versus CRM data. With the right integration layer you keep both.

Frequently asked questions

About this article

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