Running a call centre on Salesforce requires integrating telephony with CRM data – so that when a customer calls, their Salesforce record opens automatically, the call is logged without manual entry, and agents have full case, purchase, and contact history available during the conversation. Salesforce supports call centre operations through two approaches: Salesforce Service Cloud Voice (the native telephony platform, powered by Amazon Connect) and Open CTI (the standard API that connects third-party telephony systems – Genesys, NICE CXone, Avaya, RingCentral, Aircall – to Salesforce). This guide covers the core call centre features, telephony integration options, call routing and IVR, screen pop configuration, and key call centre metrics in Salesforce.
The best guide is the one that makes the service workflow feel smoother.
A useful explanation should help the reader understand how the CRM fits into the call flow.
That means the guide should focus on everyday call handling rather than only high-level platform claims.
For many organisations, the value is in reducing repetition and improving visibility during live support work.
It should also show how call-centre teams can keep conversations connected to customer records.
A good guide should explain how the platform supports service and integration needs in a busy environment.
That makes the call-center use case highly operational.
Salesforce for call centers is useful because teams handling high volumes of support or service calls need a CRM that can keep cases, customer context, and workflows organised in real time. It helps agents respond faster when the right information is available in one place.
Telephony Integration Options
Salesforce Service Cloud Voice
Service Cloud Voice is Salesforce’s native telephony offering, built on Amazon Connect’s cloud telephony infrastructure. Service Cloud Voice advantages:
- Native integration – calls are logged in Salesforce without a third-party connector, and call data is unified with CRM data in real time
- Einstein Conversation Intelligence included – AI transcription and sentiment analysis of calls runs natively
- Omni-Channel integration – voice calls route through the same Omni-Channel system as Cases and Chats, enabling blended agent capacity management across channels
- Supervisor tools native – monitoring, coaching, and barging built into the Service Console
Service Cloud Voice requires Amazon Connect configuration alongside Salesforce setup. Amazon Connect handles the telephony infrastructure (phone numbers, IVR, call routing) while Salesforce handles the agent interface, CRM integration, and reporting. The two connect via a Salesforce-managed integration package.
Pricing: Service Cloud Voice runs on a per-minute usage model (Amazon Connect charges) plus the Salesforce licence add-on. Total cost depends heavily on call volume – high-volume contact centres should model cost carefully against legacy on-premise telephony alternatives.
Open CTI (Third-Party Telephony)
Open CTI is Salesforce’s API standard for integrating any telephony system with the Salesforce interface – without requiring a native Salesforce telephony deployment. CTI adapter developers build a softphone panel (a JavaScript-based phone interface) that runs inside the Salesforce Service Console, providing call controls (answer, hold, transfer, mute) within the Salesforce UI while the telephony provider handles the actual call infrastructure.
Popular Open CTI integrations available on AppExchange:
- Aircall for Salesforce: VoIP telephony with native Salesforce integration, click-to-dial, call logging, and recording. Popular with SMB and mid-market organisations for its ease of setup.
- Genesys Cloud CX for Salesforce: enterprise-grade contact centre platform with full ACD (Automatic Call Distribution), IVR, and Salesforce data integration. Used by large contact centres.
- NICE CXone for Salesforce: another enterprise contact centre platform with Salesforce integration, strong WFM (workforce management) and analytics capabilities.
- RingCentral for Salesforce: UCaaS (Unified Communications as a Service) with call centre capabilities – suitable for organisations using RingCentral as their primary phone system.
- Avaya OneCloud CCaaS: traditional enterprise telephony vendor’s cloud contact centre, with Salesforce integration.
For organisations with an existing telephony investment (existing Genesys or NICE deployment), Open CTI integration preserves that investment while connecting it to Salesforce’s CRM data – avoiding a full telephony platform replacement.
Setting Up a Salesforce Call Center Definition
A Call Center in Salesforce (Setup ? Call Centers) is the configuration object that links a CTI adapter to Salesforce and defines which users are in the call center. Setup steps:
- Import the Call Center definition XML provided by your CTI adapter vendor (e.g., Aircall, Genesys) – this creates the Call Center record in Salesforce with the adapter’s configuration parameters
- Assign users to the Call Center: Call Centers ? Manage Call Center Users ? Add users who will use this CTI integration
- Install the CTI adapter package from AppExchange (if not already installed)
- Configure the adapter settings (authentication to the telephony provider, inbound number configuration, call recording preferences)
- Test by placing a test call – the softphone should appear in the Service Console footer and the screen pop should activate on answer
Screen Pop: Automatic Record Opening on Incoming Calls
Screen pop is the core call centre productivity feature – when an inbound call arrives, Salesforce automatically opens the caller’s Contact, Account, or Case record based on the calling number, without the agent manually searching. Screen pop configuration:
- When a call arrives, the CTI adapter passes the caller’s phone number to Salesforce via the Open CTI API
- Salesforce searches Contact and Lead records for a matching phone number (primary phone, mobile, fax – field matching is configurable)
- If a match is found: the Contact (or Account) record opens automatically in the Service Console when the agent accepts the call
- If no match is found: a new Lead or Contact creation form opens, pre-populated with the phone number – prompting the agent to create a new record during or after the call
- If multiple matches (the same phone number exists on multiple records): a disambiguation screen shows all matches for the agent to select the correct one
Screen pop eliminates 15-30 seconds of searching per call – in a 200-calls-per-day contact centre, that recovers 50-100 minutes daily per agent.
Click-to-Dial
Click-to-dial lets agents initiate outbound calls by clicking on a phone number field in Salesforce – no manual dialing required. With Open CTI or Service Cloud Voice configured, phone number fields throughout Salesforce (Contact’s Phone, Lead’s MobilePhone, Account’s Phone) render as clickable links that trigger the CTI adapter to place an outbound call.
Benefits:
- Eliminates manual dialing errors
- Automatically creates a call activity log on the related record when the call is initiated
- Enables click-to-dial from list views – an agent works through a call list by clicking each number sequentially without opening individual records
Automatic Call Logging
Call activities (inbound and outbound calls) are automatically logged as Activity records in Salesforce when call logging is configured in the CTI integration:
- Call direction: Inbound or Outbound
- Duration: call length in seconds
- Call outcome: configurable by the agent during or after the call (Reached, Voicemail, No Answer, Callback Requested)
- Call recording URL: a link to the recording stored in the telephony provider’s system (or in Salesforce Content if recordings are stored in Salesforce)
- Related record: the Contact, Lead, Account, or Case the call is logged against
Automatic logging replaces the manual activity creation that most call centre agents skip when busy – ensuring complete contact and account activity history without depending on agent discipline.
IVR and Call Routing
Inbound call routing is typically handled by the telephony platform’s IVR (Interactive Voice Response) before the call reaches Salesforce-connected agents:
- The IVR presents callers with menu options (“Press 1 for Billing, Press 2 for Technical Support”)
- Based on the selection, the call is routed to the appropriate Salesforce Queue (Billing Support Queue, Technical Support Queue)
- Omni-Channel then routes from the Queue to an available agent with the right skills, capacity, and presence status
For Service Cloud Voice (Amazon Connect), the IVR is built in Amazon Connect’s Contact Flow designer – a visual flow builder that defines the call routing logic, queue assignment, wait music, and callback options.
For third-party CTI (Genesys, NICE), the IVR is built within the telephony platform’s administration interface, then routes calls to Salesforce-mapped queues via the CTI integration.
Einstein Conversation Intelligence
Einstein Conversation Intelligence (included with Service Cloud Voice, available separately for other call recordings) applies AI to call recordings and transcripts:
- Automatic transcription: converts call audio to text in real time or post-call – the full call transcript is stored on the Salesforce Activity record
- Sentiment analysis: tracks customer sentiment (positive/negative/neutral) moment-by-moment during the call – a sentiment chart on the call record shows when the conversation shifted in tone
- Call summary: AI generates a brief call summary (key topics discussed, action items, customer concerns) that agents can review instead of listening to full recordings
- Keyword and topic detection: tags calls by detected topics (pricing, cancellation, bug report) – enabling filtering of all calls where customers mentioned cancellation, for proactive churn intervention
- Coaching insights: supervisors can filter calls by keyword, sentiment low point, or agent monologue length – identifying calls for coaching review without listening to all recordings
Salesforce has embedded deeper AI capability into call centre operations through Conversation Intelligence – real-time transcription, sentiment analysis, and keyword detection that runs during live calls and is stored against call records for post-call analysis. For organisations on Service Cloud Voice, Conversation Intelligence is included. For third-party telephony users, it is available as an add-on requiring call recording and transcript data to be fed into Salesforce.
The most operationally useful Conversation Intelligence features are: Real-Time Coaching – supervisors see transcripts and sentiment scores for all active calls on the Supervisor Dashboard and can send on-screen coaching prompts to the agent without the customer hearing (the agent sees the prompt as an overlay on their screen); Call Summaries – Einstein automatically generates a structured summary of each call (issue, resolution, next steps) and populates it into the Case or Contact record, removing post-call note-taking; and Keyword Alerts – configurable triggers that notify supervisors when specific phrases are detected (competitor names, cancellation intent, escalation language) enabling real-time intervention on at-risk calls.
For Agentforce integration, Salesforce has introduced AI agents that handle initial call triage via an AI-powered IVR before routing to human agents. The AI agent collects customer information, performs authentication, identifies the issue category, and – for routine requests such as account balance enquiries, address updates, or appointment scheduling – completes the interaction without a human. Complex or escalated calls are transferred to human agents with a full transcript and resolution summary, so the agent has complete context without repeating the authentication or issue identification process.
Key Call Centre Metrics in Salesforce
Build a Call Centre Operations Dashboard with:
- Average Handle Time (AHT): average call duration + after-call work time per agent – the primary efficiency metric
- First Call Resolution (FCR): percentage of calls where the customer’s issue was resolved without a callback or follow-up case – the primary quality metric
- Calls per Hour: volume metric per agent – used for capacity planning
- Call Outcome Distribution: breakdown of call outcomes (Resolved, Escalated, Callback, Voicemail) – shows case escalation rate and voicemail rate by agent
- Abandon Rate: percentage of callers who hung up while waiting in the queue – sourced from the telephony platform, not Salesforce natively
- CSAT from Call: post-call customer satisfaction survey scores by agent, queue, and call type
What is the difference between Service Cloud Voice and Open CTI?
Service Cloud Voice is Salesforce’s native cloud telephony platform, built on Amazon Connect. It handles both the telephony infrastructure (phone numbers, IVR routing, call handling) and the Salesforce integration natively, with Einstein Conversation Intelligence included. Open CTI is an API framework that allows third-party telephony platforms (Genesys, Avaya, NICE CXone, RingCentral, Aircall, and others) to embed their softphone interface inside the Salesforce Service Console and exchange data with Salesforce records. Open CTI does not handle telephony – the telephony provider does; Open CTI provides the integration bridge. Choose Service Cloud Voice if you want a single-vendor solution with native AI features and do not have an existing telephony investment. Choose Open CTI if you have an existing enterprise telephony platform you want to keep and need to connect it to Salesforce without replacing it.
How do you configure IVR menus in Salesforce?
For Service Cloud Voice (Amazon Connect), IVR menus are configured in the Amazon Connect console, not in Salesforce directly. You create Contact Flows in Amazon Connect that define the IVR experience – the prompts played to callers, the menu options, the data collection steps, and the routing decisions. Contact Flows can query Salesforce data in real time via Lambda functions (for example, pulling a customer’s account status to route premium customers to a priority queue). For Open CTI integrations, IVR is configured entirely within the third-party telephony platform – Salesforce is not involved in IVR logic, only in receiving the routed call and popping the relevant record. Document your IVR logic separately from your Salesforce configuration, as IVR changes in Amazon Connect or your telephony platform do not automatically surface in Salesforce admin tools.
Can Salesforce call centre features work for outbound calls as well as inbound?
Yes. Both Service Cloud Voice and Open CTI support outbound calling. In the Service Console, agents can click a phone number on any Contact, Account, or Case record to initiate an outbound call directly from the Salesforce interface – the call is routed through the softphone, connected to the customer, and logged as an Activity automatically. For high-volume outbound calling (sales follow-up, collections, appointment reminders), Salesforce supports predictive dialler integration via Open CTI – the dialler system manages call lists and agent connection, while Salesforce handles record display and call logging. Service Cloud Voice does not include a native predictive dialler; organisations requiring dialling automation typically integrate a specialist outbound dialler via Open CTI alongside Service Cloud Voice for inbound handling.
How do you measure call centre performance in Salesforce?
Salesforce provides call centre reporting via the Service Cloud reporting framework. Standard reports include: average handle time (total talk time plus after-call work time per agent), first-call resolution rate (percentage of Cases closed on the first call, measured by Case status), abandon rate (percentage of callers who hang up before connecting to an agent, requiring telephony data from Amazon Connect or your CTI provider), and call volume by hour, day, and queue. For Service Cloud Voice, Amazon Connect provides additional telephony metrics (queue wait times, IVR abandon points, agent adherence) accessible in the Amazon Connect reporting console and exportable to S3 for integration with Salesforce reporting via MuleSoft or a custom connector. Build a unified Service Dashboard in Salesforce combining both CRM metrics (Cases closed, CSAT scores, handle time) and telephony metrics to give service managers a complete view of call centre performance.
The best call-center setup is the one that keeps agents informed in the moment. If the context is missing, the conversation slows down.
Common Problems and Fixes
Problem: Screen Pop Not Triggering When Calls Connect
Screen pop – the automatic opening of the customer’s Salesforce record when an inbound call connects – is one of the highest-value call centre features, and one of the most commonly misconfigured. The diagnostic process: first, confirm your Open CTI softphone configuration has screen pop enabled (Setup ? Call Centre ? Softphone Layouts – verify that the Screen Pop Settings section has the correct object and matching field configured, typically matching on phone number to the Contact Phone field). Second, verify that the phone number format in Salesforce matches the format being passed by the telephony system – a contact stored as 07700 900000 will not match an incoming call formatted as +447700900000 without a normalisation step. Third, check the Softphone Layout assignment: the agent’s profile must have the correct Softphone Layout assigned (Setup ? Call Centre ? Softphone Layouts ? Layout Assignments). If screen pop is triggering but opening the wrong record, check whether multiple contacts share the same phone number – Salesforce will show a disambiguation page rather than popping automatically, which requires data cleaning or phone number deduplication.
Problem: Call Logs Not Automatically Creating in Salesforce
Agents report that after calls end, the call is not logged as an Activity in Salesforce – requiring manual log creation that wastes time and reduces logging compliance. For Service Cloud Voice, this is typically caused by the call not being properly associated with a Case or Contact record during the call. Ensure the agent has accepted the call through the Omni-Channel widget (not just the physical phone) and that the screen pop has fired – an associated record is required for automatic call log creation. For Open CTI integrations, the call logging depends on the CTI adapter’s configuration; check the adapter’s documentation for the saveLog() API call, which must be invoked at call end. If calls are logging but with missing fields (no duration, no recording link), check the field permissions on the Task object for the Call Duration, Call Recording URL, and Call Result fields – these must be readable and editable by agent profiles.
Problem: Call Audio Quality Issues with Service Cloud Voice
Agents or customers reporting echo, choppy audio, or dropped calls on Service Cloud Voice (Amazon Connect) points to a network quality problem rather than a Salesforce configuration issue. Resolution steps: first, run Amazon Connect’s built-in network quality test from the agent’s browser (accessible via the CCP – Contact Control Panel – by navigating to the diagnostics section) to identify packet loss, jitter, and latency metrics. Amazon Connect requires less than 150ms round-trip latency, less than 2% packet loss, and less than 30ms jitter for acceptable call quality. If the network test fails, escalate to the network team to prioritise VoIP traffic (UDP) on the corporate network and ensure firewall rules permit Amazon Connect’s required IP ranges and ports (documented in the Amazon Connect network requirements guide). For remote agents, ensure they are using a wired connection rather than Wi-Fi and that their ISP provides sufficient upload bandwidth (1 Mbps minimum per concurrent call).