What is the most important tip for working with Inbound Call?

Add the Voice Call related list to your Contact and Case page layouts. Linking a call to a record helps nobody if the record page never shows the call.

ServiceAdvanced

Inbound Call

Q: When do organizations use Inbound Call?

A mid-market insurance carrier: Routes first-notice-of-loss calls to a Claims Intake queue and pops the caller's contact and open case, so reps skip the identity questions entirely.

Q: What does the CallType field on the Voice Call object record?

CallType is a restricted picklist on VoiceCall, and it is the field that separates the three call directions. Vendor detail, recording status, and routing history live in other fields and related records, so reporting on call direction always comes back to this one.

Q: What is the current status of Open CTI for inbound call integrations?

Open CTI is deprecated, closed to newly created Agentforce Service orgs, and set to retire in February 2028. Salesforce Voice is a separate product rather than a renamed Open CTI, which is why migrating means rebuilding rather than relabelling.

Q: An admin wants both Match Callers to End User Records and channel-object linking (Beta) switched on. What actually happens?

Salesforce documents these as mutually exclusive. Choose automatic End User matching when you want every caller identified, including abandoned calls. Channel-object linking suits reps who select the related record after accepting, but Salesforce Help still labels it Beta, so weigh that before it carries production traffic.

An inbound call is a customer-initiated voice call that reaches your contact center through Salesforce-connected telephony and lands in a rep's console.

Hear it

§ 01

Definition

An inbound call is a customer-initiated voice call that reaches your contact center through Salesforce-connected telephony and lands in a rep's console. The caller's record is usually open before the rep says hello. Salesforce writes the interaction to a Voice Call record, so the conversation has a permanent home on the customer timeline.

Direction is the distinguishing feature. An inbound call comes to you. An outbound call is one your rep dials, and an internal call runs between two colleagues. That distinction is stored on the Voice Call record itself, so you can report on it instead of inferring it from rep notes.

Salesforce handles inbound voice through Salesforce Voice, the product that carried the name Service Cloud Voice until the rebrand. Underneath it you choose Amazon Connect, a certified partner telephony provider, or an Amazon Connect instance your own team runs. Agentforce Voice can now answer the call first and pass it to a person only when the conversation needs one.

§ 02

In plain English

👋 Study buddy

“Someone calls your company's support number. Before the person answering says hello, their screen already shows who is calling and what they bought last month. Salesforce keeps a record of the call afterward, so nobody has to remember what was said or how long it took.”

§ 03

Worked example

scenario · real-world useInbound Call

A regional insurance carrier publishes one number for first notice of loss. Priya dials it at 9:12 a.m. An Agentforce Voice agent answers, confirms her policy number, and decides the claim needs a person. Omni-Channel matches the call to the Claims Intake queue and routes it to Marcus, who has capacity. Because Match Callers to End User Records is on, Salesforce matches 416-555-0142 to Priya's contact. An Omni-Channel flow screen-pops that contact plus her open case. Marcus opens with her name instead of asking for a policy number. The call runs six minutes and forty seconds, so CallDurationInSeconds saves as 400, CallType saves as Inbound, and Marcus sets the disposition to Claim Filed.

§ 04

How an inbound call gets from the ring to the record

The path a call takes before anyone says hello

A customer dials your published number and the telephony platform picks up. Before a rep is involved, the call meets an automated front door: a traditional IVR menu, or an Agentforce Voice agent holding an actual conversation. That layer collects intent and often verifies who is calling. Control then passes to Salesforce for routing. Omni-Channel treats the call as a work item, scores it against rep skills and remaining capacity, and pushes it to the Service Console. The rep accepts, the audio path connects, and the talking starts. Salesforce is building the Voice Call record the whole time. After the hangup comes wrap-up: a disposition, notes or an AI-written summary, and whatever follow-up automation you configured. Each of those stages is a separate place you can intervene, which is why inbound call design is almost never one setting.

Service Cloud Voice is now Salesforce Voice

The product carrying inbound voice changed names. Salesforce's developer guides now say plainly that Service Cloud Voice is Salesforce Voice. They warn that the old name still shows up in applications and in documentation, so expect to search both for a while yet. Trailhead has drifted too, with the long-running Service Cloud Voice module presented under a Partner Contact Center label. The deployment models survived the rebrand intact. Salesforce Voice with Amazon Connect is the Salesforce-managed telephony option. Salesforce Voice with Partner Telephony connects certified providers, and you can also point Voice at an Amazon Connect instance your own team owns. Whichever you pick, reps see the same console and the same data model. The choice is about who operates the telephony, not what an inbound call looks like on arrival.

Agentforce Voice answers the phone first

The bigger change for inbound calls is who picks up. Agentforce Voice replaces IVR menus with AI voice agents that hold a natural conversation at any hour. They act on your existing Salesforce data and processes, resolve some calls outright, and escalate to a human rep when the request needs one. Setting one up means creating a voice-enabled service agent, giving it a persona, and procuring a number. You then configure call routing and escalation over PSTN or SIP. The design consequence is easy to miss. Your reps stop receiving cold calls and start inheriting conversations already in progress. Transcript quality, escalation criteria, and whatever the agent already promised now decide whether the human half of the call goes well.

What the Voice Call record captures

Every call lands on the VoiceCall standard object, available since API version 40.0, representing a call in Salesforce Voice, Sales Dialer, or another supported connector. CallType is a restricted picklist marking the call internal, inbound, or outbound. CallDurationInSeconds is an integer you can filter, group, and sort on. CallDisposition holds the call status. When telephony creates the record through the Voice REST API, required parameters include callCenterApiName, vendorCallKey, to, from, initiationMethod, startTime, and participants. The initiationMethod value distinguishes an Inbound call from a Transfer, while callSubtype separates PSTN from WebRTC. Recording and transcript data hang off related records rather than the parent. Because all of it is standard Salesforce data, call volume and average handle time come out of ordinary reports.

Caller matching and the switch you only get to flip once

A screen pop is only as good as the match behind it. Match Callers to End User Records uses the inbound number to create or reuse an End User record. You then know who called even when the call was abandoned or missed. Once a rep ties that End User to a contact or account, later calls from the number associate automatically. You turn it on from Setup by entering Amazon Setup or Partner Telephony Setup in Quick Find. Channel-object linking is the alternative, and Salesforce Help still labels it Beta. After accepting, the rep picks from recommended records, searches, or creates one, following rules you define for found and not-found cases. Here is the catch worth knowing before you build. The two features do not work together, so you pick one, and the beta side comes with beta terms and no SLA. The pop itself comes from an Add Screen Pop action inside an Omni-Channel flow.

Open CTI is on a countdown

Open CTI is the browser JavaScript API that let telephony vendors embed a softphone in Salesforce without a desktop adapter. It carried call events and screen pops for years, in two incompatible flavors for Classic and Lightning Experience. It is now deprecated. Salesforce has closed it to newly created Agentforce Service orgs, stopped adding features, and set retirement for February 2028. The support policy tells developers to move their work to Salesforce Voice. That product is wired into Omni-Channel and supervisor tooling rather than bolted on through a vendor adapter. If your calls still arrive through an Open CTI softphone, the migration is present-tense work. Vendor packages need replacing, custom pop logic needs rebuilding as Omni-Channel flows, and reporting that reads vendor objects has to be repointed.

§ 05

How organizations use Inbound Call

A mid-market insurance carrier

Routes first-notice-of-loss calls to a Claims Intake queue and pops the caller's contact and open case, so reps skip the identity questions entirely.

A 400-seat retail support center

Lets an Agentforce Voice agent handle order-status calls end to end and escalates only refund disputes, which cuts queue volume without adding headcount.

A regional utility

Reports on Voice Call records where CallType is Inbound, grouped by disposition, to show which outage categories drive volume before storm season.

Trust & references

Sources

Cross-checked against the following references.

Open CTI Support Policy (opens in new tab)Salesforce
Salesforce Voice with Telephony Providers Implementation Guide (opens in new tab)Salesforce
Create a Voice Call Record (opens in new tab)Salesforce
Agentforce Voice Overview (opens in new tab)Salesforce
Record Linking in Salesforce Voice with Partner Telephony (opens in new tab)Salesforce
Route Calls with Omni-Channel Unified Routing (opens in new tab)Salesforce

Official documentation

Straight from the source - Salesforce's reference material on Inbound Call.

Keep learning

Hands-on resources to go deeper on Inbound Call.

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.