What is the most important tip for working with CTI System?

Quick fact: a CTI System is the whole telephony integration, the phone platform plus the adapter plus the Salesforce Call Center record. The classic Open CTI version of it retires in 2028.

ServiceIntermediate

CTI System

Q: When do organizations use CTI System?

A 300-seat insurance claims center: Runs its CTI System on a legacy Open CTI connector fed by an on-premises PBX. With the 2028 retirement now dated, it is piloting Salesforce Voice with 25 adjusters while everyone else stays on the old call center record.

Q: Open CTI is scheduled for retirement on which date?

Salesforce has set Open CTI retirement for February 28, 2028. New telephony work should target Salesforce Voice now, since a fresh Open CTI build would be obsolete before it pays for itself.

Q: An org built its softphone on Open CTI for Salesforce Classic and is moving to Lightning Experience. What has to be true of the adapter?

Salesforce ships two separate Open CTI APIs. They load from different script endpoints, take arguments differently, and a few methods differ in input and output, so the code cannot simply be swapped. The Lightning API also runs only in real Lightning apps, not Classic apps viewed inside Lightning Experience.

Q: How many call centers can one Salesforce user be assigned to at a time?

A user belongs to a single call center at any moment, which is what makes a phased migration workable. Moving an agent onto a new telephony vendor becomes a Setup assignment change instead of a code deployment or a package reinstall.

A CTI System is the set of moving parts that connects a company's phone platform to Salesforce.

Hear it

§ 01

Definition

A CTI System is the set of moving parts that connects a company's phone platform to Salesforce. Agents take calls and log them without leaving the CRM. It has three pieces: the telephony platform, the adapter that translates events between phone and browser, and the Call Center record that registers that adapter. People say CTI System when they mean the integration as a whole, not any single component.

The classic way to build one is Open CTI, a browser-based JavaScript API that wires a third-party phone system to a Salesforce Call Center. That framework still runs in production, but it is on the way out. Salesforce put it in maintenance mode and set retirement for February 28, 2028. New Agentforce Service orgs no longer get it at all.

The successor is Salesforce Voice, which Salesforce renamed from Service Cloud Voice. It ships telephony, adapter, configuration, and routing as one first-party product instead of asking you to assemble them yourself.

§ 02

In plain English

👋 Study buddy

“Your phone system and your customer database normally know nothing about each other. A CTI System is the wiring between them. When someone calls, the wiring tells the database who is on the line, so their details appear on screen before you say hello. When you hang up, it writes down that the call happened.”

§ 03

Worked example

scenario · real-world useCTI System

Northwind Appliance Repair runs a 60-agent support desk on a cloud phone platform. A customer dials the main line from +1-415-555-0142. The platform picks an available agent and hands the call to the CTI adapter loaded in her Lightning console. The adapter matches that number against Contact.Phone, finds Priya Raman, and screen pops her Contact record next to her one open Case, number 00114287. The softphone panel rings in the utility bar. The agent answers, resolves the fault, and clicks End Call. The adapter then writes a Task with Subject of Call and CallDurationInSeconds of 412, related to the Case. Nobody typed a phone number or searched for a record. That exchange is the CTI System doing its job.

§ 04

From dial tone to database record

The four layers you are actually integrating

A working CTI System stacks four layers. The phone platform carries the voice from an on-premises PBX or a cloud service like Amazon Connect. The integration layer is the CTI adapter, the JavaScript that runs inside the softphone, usually a packaged connector. The configuration layer is the Call Center record, the user assignments, the softphone layouts, and the console app that hosts the panel. The logic layer is the Flows, Apex, and Lightning components that decide what happens when a call arrives or ends. Each layer only talks to its neighbors. The phone platform never touches a record directly. It raises an event, the adapter catches it, and the layers above turn that event into something an agent sees.

Open CTI, the browser API most systems still run on

Open CTI is the Salesforce framework the classic build sits on. It is a JavaScript API for wiring third-party telephony to a Salesforce Call Center. Because it lives in the browser, there is no desktop client to install on every agent machine. One sharp gotcha lives here. Salesforce ships separate Open CTI APIs for Salesforce Classic and for Lightning Experience, and you cannot swap them in custom JavaScript. They load from different script endpoints and take arguments differently: Classic positionally, Lightning as one named object. A few methods also behave differently in input and output. The Lightning API runs only in Lightning apps, and a Classic app viewed inside Lightning Experience is still a Classic app underneath. Confirm your vendor ships a Lightning-ready adapter before you plan any interface move.

The Call Center record and who can use it

The Call Center is the Salesforce half of the integration. You create one two ways. Import a call center definition file, the XML the vendor supplies that names the fields and values for that softphone. Or clone a call center you already have. Importing, viewing, editing, and deleting all require the Manage Call Centers permission. From Setup, enter Call Centers in the Quick Find box, then select Call Centers. The record alone does nothing. An admin has to assign each user, and a user belongs to exactly one call center at a time. When a fresh install appears to do nothing, check the assignment and the softphone layout before anyone calls the phone vendor.

What leaving Open CTI actually costs

Open CTI has stopped evolving. Salesforce adds no new features or enhancements to it, so the question is no longer whether to move but when. Work out what actually breaks. The adapter's JavaScript is served by Salesforce from a versioned path inside your own org, and none of it sits on the agent's machine. When that path goes away the panel stops initializing, and every agent loses call control at once. The cutover bill is larger than an adapter swap suggests. You rebuild the call center records and the softphone layouts, then reassign every user. Whatever Flow or Apex logged calls against the old adapter's events gets rewritten. Then there is the telephony contract. A three-year renewal signed this year runs past the 2028 cutoff, so check the end date before you sign.

Salesforce Voice, the first-party replacement

Salesforce Voice is the modern answer, and the name is new. Salesforce renamed Service Cloud Voice to Salesforce Voice, so both names turn up across the docs. It comes in a few shapes. Salesforce Voice with Amazon Connect provisions and manages the telephony for you. Partner telephony options let you keep an existing carrier. There is also a path for an external contact center you already operate. The gain over the classic build is routing. Calls flow through Omni-Channel beside chat, email, and messaging in one agent workspace, not in a bolted-on frame. The cost is licensing plus the real work of leaving an incumbent phone vendor.

Running two systems through a cutover

Plenty of orgs operate two CTI Systems at once. Usually one vendor for the contact center and another for sales, or two overlapping during a migration. Salesforce allows multiple call centers in a single org, and each user sits in exactly one. So moving a person from the old setup to the new one is a Setup change, not a deployment. That makes a phased cutover practical. Move a pilot team, watch handle time and abandon rate for two weeks, then shift the rest. The hard part is organizational, not technical. You are maintaining two adapters, two dashboards, two training tracks, and two vendor escalation paths. Write down which call center maps to which vendor, because an undocumented dual-vendor org punishes whoever inherits it.

§ 05

How organizations use CTI System

A 300-seat insurance claims center

Runs its CTI System on a legacy Open CTI connector fed by an on-premises PBX. With the 2028 retirement now dated, it is piloting Salesforce Voice with 25 adjusters while everyone else stays on the old call center record.

A mid-market manufacturer

Keeps one cloud phone provider for a 40-person service desk. Its CTI System screen pops the Account and open Cases on caller ID. A technician sees warranty status before answering, instead of asking for a serial number.

A 200-seat nonprofit contact center

Uses Salesforce Voice with Amazon Connect so donor calls route through Omni-Channel next to email and chat. Supervisors watch every channel in one queue view rather than reconciling a separate telephony dashboard.

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on CTI System.

Keep learning

Hands-on resources to go deeper on CTI System.

Was this entry helpful?

Help us write better definitions. Quick reactions or detailed edit suggestions.

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.