Inbound Call
An Inbound Call in Salesforce refers to a customer-initiated voice call that arrives at a contact center routed through Salesforce-aware telephony, primarily Service Cloud Voice.
Definition
An Inbound Call in Salesforce refers to a customer-initiated voice call that arrives at a contact center routed through Salesforce-aware telephony, primarily Service Cloud Voice. The call is delivered to an agent inside the Salesforce console, with the platform automatically opening the matching customer record, attaching call metadata, and triggering downstream automation when the call connects, when it transfers, and when it ends. Inbound Call differs from an Outbound Call (agent-initiated) and from an Internal Call (agent-to-agent or agent-to-supervisor within the contact center).
Salesforce supports inbound voice through several products. Service Cloud Voice is the native option, where calls flow through Amazon Connect (the default partner), Service Cloud Voice for Partner Telephony (Cisco, Genesys, NICE CXone, others), or Bring Your Own Telephony with a custom integration. The Open CTI framework underpins all of them; it exposes JavaScript APIs that any telephony vendor can implement to render their softphone inside the Salesforce console and respond to inbound call events.
The full lifecycle of an inbound call through Service Cloud Voice
The Open CTI framework
Open CTI is the JavaScript API that lets any telephony vendor integrate a softphone into the Salesforce console. The framework defines events (call arriving, call answered, call ended) and methods (search for record, open record, save metadata). Vendors implement the API on their side; Salesforce renders the softphone in the utility bar. Every modern inbound-call integration runs on this foundation.
Service Cloud Voice as the native option
Service Cloud Voice is Salesforce''s own voice product, launched in 2020. It uses Amazon Connect under the covers for the telephony itself, but presents a unified experience inside Salesforce: real-time transcription, sentiment analysis, automatic call-summarization with Einstein, and seamless logging to the Voice Call record. Customers buy Voice licenses per agent, with Amazon Connect minutes billed separately.
Voice Call standard object
Inbound calls create a Voice Call record with fields for CallDuration, CallType (Inbound, Outbound, Internal), CallDisposition (Resolved, Escalated, Voicemail), AccountId, ContactId, CaseId, and a transcript stored on a related VoiceTranscript child object. Reports built on Voice Call surface call volume, handle time, transfer rate, and per-agent productivity.
Screen pop and ANI matching
When an inbound call arrives, Salesforce uses ANI (the caller''s phone number) to find the matching Contact or Lead. The screen pop opens the matched record automatically, saving the agent the lookup step. When multiple matches exist, Salesforce shows a picker. The matching logic is configurable; orgs typically extend it to match on additional identifiers (account number, customer ID).
Omni-Channel routing
Salesforce Omni-Channel routes inbound calls (alongside chats, emails, cases) to the right agent based on skills, availability, and SLA. Voice integrates with Omni-Channel so a call arriving at the contact center can be routed by Omni-Channel logic, with the agent receiving a unified work item in the Service Console. Older Open CTI integrations may use vendor-side routing instead.
Einstein Conversation Insights
Service Cloud Voice integrates with Einstein Conversation Insights, which analyzes call transcripts for sentiment, talk-time ratios, topic distribution, and coaching opportunities. The analysis runs in near-real-time during the call (showing the agent sentiment cues) and post-call (producing supervisor dashboards). Calls captured without Voice (legacy Open CTI integrations) need their own transcription pipeline to feed Insights.
Disposition codes and wrap-up
When the call ends, the agent enters a disposition code (Sale Closed, Information Provided, Refund Issued) on the Voice Call record. Some orgs require a wrap-up note, others auto-generate one from the transcript. Disposition codes drive reporting on call outcomes and are the primary signal of contact-center effectiveness.
Set up inbound call handling with Service Cloud Voice
Service Cloud Voice setup involves the Voice product, an Amazon Connect instance, and the agent-facing console configuration. Plan two to four weeks for a basic deployment.
- Provision Service Cloud Voice
Coordinate with the Salesforce account team to enable Voice licensing. Confirm Amazon Connect or partner telephony selection.
- Provision Amazon Connect (or partner)
Set up the Amazon Connect instance in AWS, configure the contact flow, and link it to the Salesforce Voice configuration.
- Configure Voice in Salesforce Setup
Setup, Voice, complete the wizard linking the AWS instance to Salesforce. Map Amazon Connect agent IDs to Salesforce users.
- Set up Omni-Channel routing
Configure routing channels, skills, and presence statuses. Route Voice work items the same way you route Cases and Chats.
- Configure screen pop and ANI matching
Define which fields Salesforce searches for ANI matches (Contact.Phone, Account.Phone, custom identifier fields). Test with a known number.
- Train agents on the Voice softphone
Walk agents through receiving a call, viewing the screen pop, taking notes during the call, dispositioning after the call. Practice in a sandbox before production cutover.
- Amazon Connect minutes are billed separately from Salesforce Voice licenses. Plan for both line items in the budget.
- Open CTI vendors vary in feature completeness. The full Voice experience (real-time transcription, Einstein Conversation Insights) requires Service Cloud Voice; legacy Open CTI integrations are more limited.
- ANI matching against Person Accounts requires additional configuration. Orgs using Person Accounts often need a custom matching path.
- Voice Call records consume storage like any other record. High-volume contact centers should plan storage growth and archival.
Trust & references
Cross-checked against the following references.
- Service Cloud VoiceSalesforce Help
- Open CTI Developer GuideSalesforce Developers
Straight from the source - Salesforce's reference material on Inbound Call.
- VoiceCall ObjectSalesforce Developers
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 an Inbound Call in CTI contexts?
Q2. What feature pops the right record on an inbound call?
Q3. What's the modern Salesforce inbound call solution?
Discussion
Loading discussion…