Call
A Call in Salesforce is a customer-facing telephone interaction that the CRM records as structured data.
Definition
A Call in Salesforce is a customer-facing telephone interaction that the CRM records as structured data. It shows up in one of two shapes. A logged Call is a Task record with TaskSubtype set to Call, created when a rep clicks Log a Call to document a conversation after the fact. A Voice Call is a standard VoiceCall object record, created automatically when a call runs through Salesforce Voice, Sales Dialer, or a partner telephony connector.
Both shapes capture the same idea, a conversation between a Salesforce user and a customer, but they differ in how the data arrives and how much context comes with it. Logged Calls are quick manual notes that carry a call type, a result, and a link to a Contact or Account. Voice Call records capture telephony detail automatically: the from and to phone numbers, start and end times, duration, a recording, a transcript, and the agent who handled it. Together they give a team one timeline of who talked to whom and what was said.
How Salesforce stores a phone call
Logged Calls live on the Task object
The most common Call in any org is a logged Task. When a rep finishes a phone conversation, they click the Log a Call quick action and fill in a short form. Salesforce creates a Task with TaskSubtype set to Call and Status set to a closed value, so it lands in the Past Activity section of the timeline rather than in open work. The CallType field records whether the call was Inbound or Outbound, and CallDisposition (shown as Call Result in the UI) captures the outcome the rep selected, such as Left Voicemail or Reached. The Task links to a person through WhoId (a Contact or Lead) and to a business object through WhatId (an Account, Opportunity, or Case). Because a logged Call is just a Task, it inherits everything Tasks already support: assignment to an owner, a subject line, a comment body, custom fields, validation rules, and flows. That reuse is why logged Calls are the backbone of activity reporting. Reps can create them in seconds, and managers can roll them up across the whole team without any special telephony setup.
Voice Call records and what they capture
A Voice Call is a different animal. It is a record of the standard VoiceCall object, available in API version 40.0 and later, and it represents a real call placed or received through Salesforce Voice, Sales Dialer, or a supported voice connector. The platform creates it automatically when the call connects, so an agent never has to remember to log anything. The record stores the from and to phone numbers, the start and end timestamps, the duration in seconds, the call type, a disposition, and a pointer to the recording location. It also links to the agent who handled the call and to the customer record the call was matched against. Related objects extend the picture: VoiceCallRecording holds the audio, and transcript records hold the spoken text when transcription is enabled. Because the data is captured by the telephony system rather than typed by a person, Voice Call records are far more complete and consistent than logged Calls. That reliability is what makes them the foundation for real-time agent assistance, supervisor monitoring, and AI analysis in Service Cloud Voice.
Attribution: linking a Call to the right record
A Call is only useful in reporting if it points at the correct parent. On a logged Task, attribution happens through the WhoId and WhatId fields. WhoId ties the call to a Contact or Lead, and WhatId ties it to an Account, Opportunity, or Case. On a Voice Call, the telephony layer matches the inbound or outbound phone number against existing records and links the call to the Contact and the related business object it finds. When that match fails or a rep forgets to set the parent, the Call becomes orphan activity. It still exists, but it does not appear when someone runs a report grouped by Account or Opportunity, so the numbers look lower than reality. Most production orgs close this gap with automation. A flow or Apex trigger can populate WhatId from the matched Contact, or screen-pop logic can pre-fill the parent before the agent ever touches the record. Getting attribution right is the single biggest factor in whether Call data can be trusted, because a missing link is invisible rather than obviously wrong.
Recordings, transcripts, and AI on the call
Voice Call records are where calls stop being timestamps and start being content. When recording is configured, the audio is stored and linked through the VoiceCallRecording object, and a recording location on the call points an agent to it. With transcription enabled, the spoken conversation is converted to text and surfaced inline in the Service Console, so a supervisor can read a call instead of listening to the whole thing. Einstein Conversation Insights then analyzes that transcript. It can detect sentiment, flag mentioned topics and competitor names, and pull out the moments that matter for coaching. Some of this runs live, giving an agent next-best-action guidance while the customer is still on the line, and some runs after the call to feed coaching dashboards and trend reports. None of this works without the transcript, which is the common failure point. If a team turns on Conversation Insights but never enables transcription on the Voice Call deployment, the AI has nothing to read and the panels come back empty. Plan the recording and transcript settings as part of the Voice rollout, not as an afterthought.
Reporting and the Activity Timeline
Calls feed two views that managers and reps rely on every day. The first is reporting. Standard report types cover Tasks, which you filter to TaskSubtype equals Call to isolate logged calls, and VoiceCall, which exposes the telephony-captured set. Typical reports include call volume by rep, outbound calls per day, average call duration, and average handle time for a service queue. The second view is the Activity Timeline on each record. Logged Calls appear under Past Activity with their subject and comments, while Voice Calls appear as their own activity type with the recording and transcript available inline. The combined timeline is what a rep sees before dialing a customer back and what a manager reviews when auditing an account. A subtle trap lives here. Logged Calls and Voice Calls are separate objects, so a dashboard built on only one of them tells half the story, and a dashboard that blends them carelessly can double-count a single conversation. Before trusting any Call metric, confirm exactly which object the report type sits on.
Open CTI, Salesforce Voice, and where the model is heading
For years, the way to bring a third-party phone system into Salesforce was Open CTI, a browser-based JavaScript API that let products like Five9, Genesys, and RingCentral embed a softphone in the console without a desktop adapter. Open CTI populated the same Call data model, so calls still landed as activity and, with the right connector, as Voice Call records. That framework is now in maintenance mode. Salesforce has set Open CTI to retire on February 28, 2028, it is no longer available for newly created Agentforce Service orgs, and the recommended successor is Salesforce Voice, also known as Service Cloud Voice. Voice brings telephony fully inside the platform instead of bolting it on, with native ties to Omni-Channel routing and real-time AI transcription. The important point for the Call concept itself is that it is not going anywhere. Logged Tasks and Voice Call records remain the standard way to store a phone interaction. What is changing is the integration plumbing underneath, so teams still running an Open CTI adapter should plan a move to Salesforce Voice well before the 2028 deadline.
How to set up Call logging in Salesforce
To capture Calls reliably, an admin sets up both the manual path (Log a Call) and, for contact centers, the automated path (Salesforce Voice). The steps below cover the common configuration that makes Call data show up in timelines and reports.
- Add Log a Call to page layouts
In Setup, edit the Activities section of the relevant Lead, Contact, Account, Opportunity, and Case page layouts (or the Lightning record page) so the Log a Call quick action is available. This is what lets reps create a Call as a closed Task in a couple of clicks.
- Customize the Call Result picklist
Edit the Task object's Call Result (CallDisposition) picklist to match how the team describes outcomes, for example Connected, Left Voicemail, No Answer, or Callback Requested. Consistent values here are what make later call-outcome reports meaningful.
- Decide on Voice and configure it
If the team runs a contact center, set up Salesforce Voice (Service Cloud Voice) so connected calls create VoiceCall records automatically. Choose recording and transcript settings during this step, since Einstein Conversation Insights depends on the transcript being enabled.
- Build the reports and dashboards
Create report types and dashboards on Tasks filtered to TaskSubtype equals Call and on VoiceCall, then combine them so leaders see both logged and telephony-captured activity in one place.
The action that creates a closed Task with TaskSubtype Call; the manual path every rep uses to document a conversation.
Picklists on the Task and VoiceCall that record direction (Inbound or Outbound) and outcome; the backbone of call-quality reporting.
Settings that capture the audio and convert speech to text; required before Conversation Insights can analyze a call.
A flow or trigger that fills WhoId and WhatId so calls roll up to the right Account or Opportunity instead of becoming orphan activity.
- A logged Call with no WhoId or WhatId is orphan activity. It exists but never appears in account-level reports, so totals read artificially low.
- Logged Calls and Voice Calls are separate objects. A dashboard built on only one undercounts, and a careless blend can double-count the same conversation.
- Conversation Insights returns nothing if transcription was never enabled on the Voice deployment. Turn on the transcript when you configure Voice, not later.
- Open CTI adapters retire on February 28, 2028. Teams on a partner CTI softphone should plan the move to Salesforce Voice before that date.
Prefer this walkthrough as its own page? How to Call in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Call.
Hands-on resources to go deeper on Call.
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. How is a manually logged Call represented in the Salesforce data model?
Q2. What additional context does a Voice Call record capture that a logged Call Task does not?
Q3. Why do logged Calls with a missing parent lookup cause reporting problems?
Discussion
Loading discussion…