Salesforce CRM Call Center
Salesforce CRM Call Center is the framework in Salesforce that connects the platform to a third-party phone system, so agents can place and answer calls from a softphone that lives inside their Salesforce window.
Definition
Salesforce CRM Call Center is the framework in Salesforce that connects the platform to a third-party phone system, so agents can place and answer calls from a softphone that lives inside their Salesforce window. It ties each call to customer data, supports click-to-dial and screen pops, and can log call activity automatically against the right record.
A call center is set up by importing an XML call center definition file that tells Salesforce which telephony system to talk to and how. This is older technology. The browser plugin model behind it gave way to Open CTI, and Open CTI itself is now in maintenance mode with a retirement date of February 28, 2028. New work should target Salesforce Voice (Service Cloud Voice).
How Salesforce CRM Call Center wires phones into the agent workspace
What a call center record actually represents
A call center in Salesforce is a record that stores the configuration for one telephony system. You do not type that configuration by hand. Instead you import a call center definition file, an XML document that lists the fields and values a particular CTI system needs. Once imported, the field structure is fixed. You can change the saved values inside Salesforce later, but you cannot add or remove fields without importing a different file. Each CTI adapter or partner package ships with its own default definition file, named for the vendor, so the connection settings match what that phone system expects. After the call center exists, an admin assigns users to it. Only users attached to a call center see a softphone. This record-plus-users model is why two agents on different phone systems can both work inside the same Salesforce org. One belongs to call center A, another to call center B, and each gets the softphone wired to their own backend. The call center record also holds the dialing rules and the softphone layout reference that shape what agents see during a call.
The softphone and what agents do with it
The softphone is the call-control panel agents use. It is not a separate app. In Lightning Experience and the Salesforce console it sits in the footer (the utility bar), and in the older Salesforce Classic sidebar it appears on the left. From that panel an agent answers an inbound call, dials out, puts a caller on hold, transfers, starts a conference, and runs through call wrap-up before moving on. A built-in directory gives quick access to common numbers. The admin controls the layout, so the fields and buttons an agent sees can differ by profile. Two features make the softphone feel connected rather than bolted on. Click-to-dial lets an agent click a phone number on a contact, lead, or any record and have the system place the call, which removes mistyped numbers. Screen pop brings up the matching record (or a search of candidates) the moment a call arrives, so the agent is looking at the customer before saying hello. Call activity can be logged automatically as a task, capturing duration and notes against the record without manual data entry.
Call center definition files, field by field
The definition file is plain XML built from three nested elements. The root is callCenter. Inside it sit one or more section elements, and each section holds item elements that define the actual fields. A section groups related settings, for example general information about the call center or the dialing options. Each item has a name, a label, and a value. The required pieces include an internal name and a display label for the call center, plus the adapter URL or settings the CTI system needs to start the softphone. Salesforce reads this file on import and creates matching fields on the call center record. Because the structure locks after import, planning the file matters. If a vendor later needs a new field, you import an updated file rather than editing the record. Salesforce publishes a sample definition file you can copy and adapt, which is the usual starting point for a custom integration. In practice most teams never hand-edit XML at all. They install a managed package from AppExchange, and the package imports its own definition file and registers the call center for them.
Why this counts as legacy: the move to Open CTI
The original CRM Call Center relied on a desktop CTI adapter, software installed on every agent machine that bridged the phone system to the browser. That model was painful. It broke across browser versions, needed per-machine deployment, and tied agents to specific desktop setups. Salesforce replaced it with Open CTI, a browser-based JavaScript API. Open CTI builds the same kind of softphone inside Salesforce but needs no desktop adapter and no browser plugin. The integration runs as web code, so it works across browsers and operating systems and is far easier to roll out. Open CTI still uses the call center framework underneath. You still import a call center definition file, and agents still belong to a call center. What changed is how the softphone talks to the phone system: through JavaScript in the browser rather than a local adapter. Note that Open CTI has two separate APIs, one for Salesforce Classic and one for Lightning Experience, and they are not interchangeable in custom code. If you read older documentation referring to the CTI Toolkit, that is the retired desktop generation, and Open CTI is its successor.
What replaces it now: Service Cloud Voice
Open CTI modernized the plumbing, but it is itself winding down. Salesforce has placed Open CTI in maintenance mode, meaning no new features, and set a retirement date of February 28, 2028. It is already deprecated and unavailable for newly created Agentforce Service orgs. The recommended path forward is Salesforce Voice, also known as Service Cloud Voice. Voice brings telephony into Salesforce as a native channel rather than a third-party bridge. It integrates directly with Omni-Channel for routing and with the supervisor tools in the console, and it can layer in real-time transcription and AI assistance during calls. You can run Voice with Amazon Connect as the telephony backend, with your own contact center provider, or through a partner. For an organization still on the older CRM Call Center model, the practical message is to treat current setups as stable but frozen, and to scope new contact center projects on Voice. Spending heavily to customize a legacy call center is rarely worth it when the framework has a published end date and a clear successor.
A worked picture: one inbound call
Walk through a single support call to see the pieces working together. An admin has imported the definition file for the phone vendor, created the call center record, and assigned the agent to it. The agent opens the Service Console and signs in to the softphone in the footer. A customer dials the support line. The phone system passes the caller ID to Salesforce through Open CTI. Salesforce matches that number to a Contact and fires a screen pop, opening the contact record and any open cases in a console tab. The agent sees who is calling before answering, then takes the call from the softphone. During the conversation the agent updates the case, and when needed clicks a related contact number to click-to-dial a transfer. At wrap-up the softphone logs a call task with the duration against the case, so the interaction is recorded without retyping anything. Reporting later rolls those call tasks into metrics on volume and handle time. Every step here depends on the call center framework: the definition file made the connection, the assignment gave the agent a softphone, and Open CTI carried the call events into the page.
Set up a call center and assign agents
Setting up a call center means importing a definition file and assigning users so they get a softphone. Most teams install a partner package from AppExchange that does the import for them. Note that Open CTI is in maintenance mode with a retirement date of February 28, 2028, so weigh Service Cloud Voice for anything new.
- Get a call center definition file
Install the telephony vendor's managed package from AppExchange, which imports its own call center, or start from the Salesforce sample definition file and adapt the XML for a custom integration.
- Import the call center
In Setup, search for Call Centers, open the list, choose Import, and select the XML definition file. Salesforce creates the call center record with the fields defined in the file.
- Check and edit the saved values
Open the new call center record and confirm the internal name, display name, and the adapter or softphone settings. You can change values here, but not the set of fields, which is fixed at import.
- Assign users
On the call center record, manage its members and add the agents who should use this phone system. Only assigned users see a softphone, and a user belongs to one call center at a time.
- Shape the softphone layout
Create or edit a softphone layout to control which fields and call-related screen pop behavior agents see, then assign that layout to the relevant user profiles.
The XML file (callCenter, section, item elements) that defines the call center's fields. Required to create the call center; its structure locks after import.
The users assigned to the call center. Assignment is what gives an agent a softphone; unassigned users see nothing.
A profile-assignable layout that controls softphone fields and how screen pops behave for inbound, outbound, and internal calls.
Optional outbound dialing rules in the definition file or call center record that adjust how numbers are formatted when click-to-dial places a call.
- Open CTI is in maintenance mode and retires on February 28, 2028; it is already unavailable for newly created Agentforce Service orgs, so plan new contact centers on Service Cloud Voice.
- The fields defined by an imported definition file cannot be changed afterward; to alter the field set you must import a revised file.
- A user can belong to only one call center at a time, so agents who switch phone systems must be reassigned.
- The Open CTI APIs for Salesforce Classic and Lightning Experience differ and cannot be swapped in custom JavaScript.
Trust & references
Cross-checked against the following references.
- Salesforce Call CenterSalesforce
- Call Center Definition FilesSalesforce
Straight from the source - Salesforce's reference material on Salesforce CRM Call Center.
- What's a Softphone?Salesforce
- Open CTI Developer Guide: Introducing Open CTISalesforce
Hands-on resources to go deeper on Salesforce CRM Call Center.
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 Salesforce CRM Call Center?
Q2. What are modern alternatives?
Q3. What did CRM Call Center use for configuration?
Discussion
Loading discussion…