Queue, Salesforce CRM Call Center
A Salesforce CRM Call Center queue is the holding area within Salesforce CRM Call Center (the Classic CTI telephony product) where inbound calls wait until an available agent can take them.
Definition
A Salesforce CRM Call Center queue is the holding area within Salesforce CRM Call Center (the Classic CTI telephony product) where inbound calls wait until an available agent can take them. The underlying telephony platform places callers in line, applies the routing rules configured for that call center, and connects each caller to an agent through the softphone embedded in Salesforce.
This is a legacy concept. Salesforce CRM Call Center is built on Open CTI, which is now in maintenance mode and scheduled for retirement on February 28, 2028. Newer implementations use Service Cloud Voice, where call queuing and distribution run through Amazon Connect (or a bring-your-own partner) and feed directly into Omni-Channel for unified routing.
How call queuing worked in Salesforce CRM Call Center
What "queue" means in a Call Center context
The word queue is overloaded in Salesforce, so it helps to be precise. A standard Salesforce Queue is a record-ownership construct. It holds Cases, Leads, or custom records until a user claims them. A Call Center queue is different. It is a live, telephony-side waiting line for phone calls, and it lives in the connected phone system rather than in Salesforce data. When a customer dials in and every agent is busy, the call sits in this line. The caller usually hears hold music or an announcement while the system waits for an agent to free up. The Call Center queue is therefore a runtime concept tied to call distribution, not a row you query with SOQL. Salesforce CRM Call Center surfaces the result of that queuing inside the softphone, so the agent sees the call arrive, but the queue logic itself is owned by the telephony vendor. Understanding this split matters during legacy migrations, because the Salesforce-side configuration (the call center definition and softphone layout) is separate from the queue and routing rules that live in the phone platform.
Salesforce CRM Call Center and Open CTI
Salesforce CRM Call Center is the product that connects a third-party phone system to Salesforce so agents can handle calls without leaving the console. It relies on Open CTI, a browser-based JavaScript API. Open CTI lets a partner build a softphone that runs inside Salesforce, with no desktop CTI adapter installed on each agent machine. The phone vendor handles the actual call queuing, ringing, and routing. Salesforce handles screen pops, call logging, and the agent interface. The link between the two is the call center definition file, an XML document that registers the softphone and its settings in your org. Earlier versions of CRM Call Center used the CTI Toolkit and a desktop adapter, which is why so much of this stack is now considered dated. Open CTI replaced that adapter model, then itself moved into maintenance mode. No new features are being added, and it is unavailable for newly created Agentforce Service orgs. For anyone still running it, the practical takeaway is that the queue behavior depends almost entirely on the connected phone system, with Salesforce acting as the front end.
The call center definition file
Every Salesforce CRM Call Center starts from a call center definition file. This is an XML file that specifies the fields and values used to define a call center for a particular softphone. Salesforce uses these files so a single org can integrate with several CTI vendors at once. The structure uses three elements: callCenter, section, and item. Sections group related settings, and items carry the individual values. The reqInternalName item is the one value that must always be set, since it uniquely identifies the call center. A field named reqSalesforceCompatibilityMode declares whether the softphone targets Salesforce Classic, Lightning Experience, or both, which in turn decides which Open CTI API the implementation uses. An admin imports the vendor definition file once to create the first call center, then clones it to spin up additional call centers for the same softphone. The file can also carry vendor-specific items, such as a backup server address for platforms that support failover. None of this file controls the queue directly. It tells Salesforce how to display and talk to the phone system, while the queue and routing rules are configured on the vendor side.
How agents receive a queued call
From the agent point of view, the queue is mostly invisible until a call lands. The agent works inside the Service Console with the softphone docked in the utility bar or footer. When the phone system pulls a waiting call off the queue and assigns it, the softphone rings and a screen pop can surface the matching Contact, Account, or Case. The agent answers, talks, and uses softphone controls to hold, transfer, or start a conference. After the call, wrap-up time lets them finish notes and log the interaction. Call logs can be created automatically so the activity is tied to the right record. What the agent does not control is the order of the queue or the rules that decided which call to send. Those routing decisions, including priority, skills, and overflow, are set in the connected telephony platform. This is the central limitation of the legacy model. Salesforce shows the call and captures the data, but it does not own the distribution logic, so reporting on queue wait times and abandonment usually has to come from the phone vendor rather than from Salesforce itself.
Why it is considered legacy now
Open CTI, and therefore Salesforce CRM Call Center, is in maintenance mode with a retirement date of February 28, 2028. Salesforce is not building new features for it and has made it unavailable for newly created Agentforce Service orgs. The reason is architectural. In the Call Center model, queuing and routing sit outside Salesforce, so phone work cannot share a single distribution engine with cases, chats, and messaging. Agents can end up juggling separate availability states for calls and for everything else. The modern direction unifies that. Salesforce now recommends Salesforce Voice, which brings telephony into the platform with native integration to Omni-Channel and the Command Center for Service. That means voice, chat, and case routing can run through one presence model and one set of rules. For a team still on CRM Call Center, the queue keeps working until retirement, but it is a known endpoint. Treating the migration as planned work, rather than an emergency in early 2028, is the sensible path.
The modern replacement: Service Cloud Voice and Omni-Channel
Service Cloud Voice is the current answer for Salesforce-native telephony. It commonly runs on Amazon Connect as the contact center backbone, with options to bring your own telephony partner or your own Amazon Connect instance. In this model the call queue still physically lives in the telephony platform, but the integration is far deeper. Calls, transcripts, and presence flow into Salesforce in real time, and call routing is handled through Omni-Channel rather than a separate vendor console. That gives one queue model across channels. A single agent presence status can govern whether they receive a phone call, a chat, or a case. Supervisors get the Omni Supervisor view and Command Center for live monitoring. For teams that must keep an existing phone system, Open CTI still exists until its retirement, and a partner softphone can bridge it to Salesforce. The strategic difference is unification. The legacy Call Center queue is one isolated line for voice. The modern stack folds voice into the same work distribution that handles every other service channel, which is why most new builds skip CRM Call Center entirely.
Set up Salesforce CRM Call Center (legacy)
Setting up Salesforce CRM Call Center connects a third-party phone system to Salesforce through Open CTI. The actual call queue is configured in the phone vendor's platform; these steps register that system in Salesforce so agents get a softphone. For new projects, evaluate Service Cloud Voice first, since Open CTI retires on February 28, 2028.
- Get the call center definition file
Obtain the XML call center definition file from your CTI partner or AppExchange package. It specifies the fields and values that define the call center for that softphone, including the compatibility mode for Classic or Lightning Experience.
- Import or clone the call center
In Setup, open Call Centers and import the definition file to create the first call center. To run more call centers on the same softphone, clone the existing one rather than importing the file again.
- Assign users to the call center
A user must be associated with a call center to see the softphone. Add the relevant agents to the call center so the phone interface appears in their console.
- Customize the softphone layout
Configure the softphone layout to control which related records and fields appear during inbound and outbound calls, then add the softphone utility to the Service Console app.
The XML file that registers the softphone in Salesforce. reqInternalName is mandatory and reqSalesforceCompatibilityMode sets Classic, Lightning, or both.
Controls the screen pop and the record fields shown to the agent for inbound, outbound, and internal calls.
Determines which users see the softphone; without assignment the agent cannot take queued calls.
- The queue, routing rules, hold music, and overflow logic live in the telephony vendor's platform, not in Salesforce. Setting up the call center alone does not configure queuing.
- Open CTI is in maintenance mode and retires on February 28, 2028, and is unavailable for newly created Agentforce Service orgs. Plan migrations rather than building net-new on it.
- A Call Center queue is not a standard Salesforce Queue. You cannot query call wait times with SOQL; reporting usually comes from the phone vendor.
Prefer this walkthrough as its own page? How to Queue, Salesforce CRM Call Center in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Set Up a Call CenterSalesforce
- Get Started with Open CTI (Open CTI Developer Guide)Salesforce
Straight from the source - Salesforce's reference material on Queue, Salesforce CRM Call Center.
Hands-on resources to go deeper on Queue, 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 does a Queue do in the legacy Salesforce CRM Call Center (Classic CTI)?
Q2. What is the modern Service Cloud Voice equivalent of the Classic CRM Call Center Queue?
Q3. Why is a call-holding Queue important to a contact center's call-routing operation?
Discussion
Loading discussion…