Call
A Call in Salesforce is a customer-facing telephone interaction, recorded in CRM either as a logged Task (TaskSubtype = Call) for manually documented calls, or as a Voice Call standard object record for calls placed through Service Cloud Voice or a CTI-integrated telephony platform.
Definition
A Call in Salesforce is a customer-facing telephone interaction, recorded in CRM either as a logged Task (TaskSubtype = Call) for manually documented calls, or as a Voice Call standard object record for calls placed through Service Cloud Voice or a CTI-integrated telephony platform. Both representations capture the same conceptual event (a conversation between a Salesforce user and a customer) but differ in how the data is created and what additional context is attached. Logged Calls are quick post-fact notes by an agent or rep. Voice Call records capture full telephony metadata: ANI, DNIS, call duration, recording URL, transcript, and a link to the connected Agent.
Calls are foundational to Salesforce activity reporting. Reps log them to track outreach. Service agents handle them through Voice Call records in the Service Console. Forecasting and account-based selling lean on call volume metrics as leading indicators. Service Cloud Voice extended the model with real-time transcripts and Einstein Conversation Insights, turning the Call record into a rich source of signal beyond timestamps and duration. The combination of logged Calls (the bulk of activity data) and Voice Calls (the high-quality, telephony-captured subset) gives Salesforce a complete view of how often the team is on the phone and what gets said.
How Calls flow through Salesforce
Logged Calls as Task records
The Log a Call quick action creates a Task record with TaskSubtype = Call, Status set to a closed value, and CallType (Outbound, Inbound) populated. The Task links to a parent (Account, Contact, Opportunity, Lead) and appears in the parent's Activity timeline. Logged Calls are the standard way reps document phone interactions outside Service Cloud Voice.
Voice Call records
Service Cloud Voice and partner CTI integrations create Voice Call records (standard object VoiceCall) on call connect. The record stores ANI, DNIS, start and end timestamps, duration, recording URL, transcript, and links to the connected Agent and customer record. Voice Call records persist beyond logged Tasks, giving service organisations richer call analytics.
Call attribution and parent lookups
Calls reference a parent through the WhatId or WhoId field on Task, or through the related Account/Contact lookups on Voice Call. Misattributed calls produce wrong reports (call volume by account is off when the call linked to the wrong parent). Most production orgs build automation to attribute calls correctly when an Agent does not capture the parent explicitly.
Call recording and transcript
Voice Call records store audio recordings and AI-generated transcripts when configured. Transcripts surface inline in the Service Console; recordings link out to storage. Einstein Conversation Insights analyses the transcript for sentiment, topics, and competitor mentions, feeding both real-time agent guidance and post-call coaching dashboards.
Reporting on Calls
Standard report types include Tasks (filtered to TaskSubtype = Call) and VoiceCall. Common reports include Call Volume by Rep, Call Duration by Account, Outbound Call Rate per Day, and Average Handle Time. Most sales operations dashboards combine both report types to cover logged and telephony-captured calls.
Calls and Activity Timeline
Both logged Calls and Voice Calls appear on the parent record's Activity Timeline. Logged Calls show in the Past Activity tab. Voice Calls show as their own type with the recording and transcript inline. The combined view is what reps and managers see when reviewing a customer's interaction history.
Calls and Open CTI
The Open CTI framework lets non-Salesforce telephony products (Five9, Genesys, RingCentral) integrate with the Service Console. The same Voice Call object model applies; the data source is the partner telephony platform rather than Amazon Connect.
Common pitfalls
Three patterns recur. Logged Calls with missing parent lookups produce orphan activity that does not show in account-level reports. Voice Call retention can fill storage quickly; plan archival explicitly. And confusing logged Calls with Voice Calls in reporting produces double-counted call activity. Always confirm which report type the dashboard sits on.
How to track Calls effectively
Configuring Call tracking is mostly about choosing the right surface (logged Task versus Voice Call), training users to attribute calls to the right parent, and building reports on both.
- Enable Log a Call
Ensure Log a Call quick action is on the relevant page layouts. Most standard page layouts already include it; custom layouts may need explicit configuration.
- Configure Service Cloud Voice or partner CTI
For telephony-captured calls, configure Service Cloud Voice with Amazon Connect or a partner CTI through Open CTI.
- Train users to attribute calls
Every Call should link to the right Account, Contact, Opportunity, or Lead. Without attribution, calls become orphan activity invisible in account-level reports.
- Build call reporting
Create reports filtered to TaskSubtype = Call and separate reports on VoiceCall. Combine in a unified dashboard for full coverage.
- Plan recording retention
Voice Call recordings consume storage. Configure retention policy in AWS S3 (or partner storage) plus Salesforce-side retention so storage costs stay predictable.
- Logged Calls with missing parent lookups become orphan activity invisible in account reports.
- Voice Call recordings consume storage fast. Plan retention before launch; storage bills surprise teams that skip the planning.
- Reports that mix Task (TaskSubtype = Call) and VoiceCall without filters can double-count call activity.
- Einstein Conversation Insights requires the transcript to be enabled; without it the AI analysis returns empty results.
Trust & references
Cross-checked against the following references.
- Log a CallSalesforce Help
- Voice Call ObjectSalesforce Help
Straight from the source - Salesforce's reference material on Call.
- Open CTI ToolkitSalesforce Developer Docs
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 Call represented in Salesforce?
Q2. Where do logged Calls appear on a record?
Q3. How can CTI integration help with Call logging?
Discussion
Loading discussion…