You can log calls manually with the Log a Call action or automatically via softphone and Salesforce Voice, and both work. For one-off notes, manual logging gets the job done in seconds. For teams handling real volume, automated logging through VoiceCall gives you durable records with duration, recordings and transcripts attached, which is what you need for reporting and AI-driven analysis.

42voice
42voice.com
Automate Your Salesforce Call Records
42Voice builds AI voice agents for bookings, enquiries, sales follow-up and support, with seamless human handoff when needed.

Book a demo

Table of Contents

How to log calls manually in Salesforce

Manual logging is built into Salesforce and sits on the Activities component on Lightning or the Activity History related list in Classic. If you don’t see the Log a Call action on a record, an admin needs to add it to the page layout first.

Here’s the basic flow for a rep logging a call after hanging up:

  1. Open the Contact, Lead, Opportunity or Case record.
  2. Click Log a Call in the Activity composer.
  3. Fill in the subject, comments, call duration and disposition.
  4. Save. The entry appears in Activity History, tied to that record.

Admins can tighten this up for consistency:

  • Encourage making disposition and subject fields mandatory to improve data completeness.
  • Standardise picklist values (such as “Connected”, “Voicemail”, “No Answer”) to keep reporting consistent and avoid free-text variants.
  • Add Log a Call to every relevant object your reps call from, not limited to Contacts.

The Salesforce Help documentation on the Log a Call button covers the setup steps for both Classic and Lightning in detail.

Pro Tip: Build a macro or quick text template for common call outcomes, like “left voicemail, will follow up Thursday,” so reps spend seconds logging instead of typing a paragraph each time.

Automatic call logging: softphones, CTI and what to expect

Automated logging removes the manual step entirely. A softphone or CTI integration can create the activity record the moment a call connects, or at wrap-up once the rep finishes, depending on how the connector is built; for tailored solutions in this area, custom AI-powered software development can provide the integration or bespoke connector help you need.

Behaviour varies a lot between integrations. Softphone documentation from Salesforce shows that calls made or received through a softphone generate call log entries in Activity History automatically, but the older Open CTI framework relied on a method called saveLog to pre-create Task records before the call even finished. That approach is deprecated, and Salesforce now points teams toward Salesforce Voice instead.

What this means in practice:

  • Expect timestamps, recording links and duration fields to populate automatically rather than relying on a rep’s memory.
  • Completeness improves because calls don’t get skipped when someone forgets to log them.
  • You trade a bit of setup complexity, integration, field mapping, consent workflows, for that completeness.
  • Not every connector behaves identically, so test before you roll out broadly.

A quick checklist before you flip automatic logging on for your team:

  • Do you have a CTI or softphone connector that’s actively supported, or still running on deprecated Open CTI?
  • Does your call volume justify the setup effort, or would manual logging cover a small team fine?
  • Have you mapped out who needs to see recordings and transcripts, and who shouldn’t?

Pro Tip: If your team is still on Open CTI, treat this as a planning trigger rather than a fire drill. Migration is straightforward when you test it properly, rushed when you don’t.

Salesforce Voice and the VoiceCall object: what it stores and migration guidance

Structured record replacing legacy call activities

VoiceCall is Salesforce’s native record for voice interactions, and it’s built to replace the patchwork of Task-based logging that Open CTI relied on. According to the VoiceCall field reference from Salesforce Developers, it captures fields like CallDurationInSeconds, call disposition, owner and recording links, which makes it the object your reports should point to going forward.

The practical advantage is reliability. Because the platform creates VoiceCall records directly rather than waiting on a connector to pre-create a Task, the record survives connector hiccups that would otherwise leave a call untracked.

If you’re moving off Open CTI, Salesforce’s migration guidance recommends:

  1. Test the migration in a sandbox first, never production.
  2. Map legacy Task fields to their VoiceCall equivalents, or to the AdditionalFields JSON where there’s no direct match.
  3. Update any Flows or automations that currently trigger off Task creation.
  4. Rebuild reports to query VoiceCall instead of Task.

Things worth testing specifically: Flow triggers that fire on the old Task object, report filters that assume Task fields, supervisor dashboards, and multi-leg calls, since VoiceCall models each leg separately and links them through parentVoiceCallId. Skip that last check and your call-duration reports can quietly double-count.

Logging that a call happened is different from capturing what was said. Metadata, like duration and disposition, is lower risk. Recordings and transcripts are personal information, and collecting them brings the Australian Privacy Principles into play, including obligations to collect fairly and notify people about what you’re capturing.

OAIC guidance makes clear that collection includes information you generate, not just information you receive directly, from OAIC’s APP guidelines. That means an automatically generated transcript counts as collection even though no one typed it.

Practical steps worth putting in place:

  • Update your collection notice to mention call recording and transcription where it applies.
  • Capture and log consent somewhere auditable, not just verbally on the call.
  • Limit who can access recordings and transcripts, and log who views them.
  • Set a retention period and actually enforce it rather than keeping everything indefinitely.

If you’re running outbound calling, also check your obligations under the Do Not Call Register and the Privacy Act, and get a compliance or legal review before automating outbound voice at scale. We’re not lawyers, so treat this as a starting point, not advice.

Reporting and practical setup: relating calls to contacts, leads, opportunities and cases

The value of logged calls depends entirely on what you relate them to. Link calls to Contacts or Leads for outreach tracking, Opportunities for pipeline visibility, and Cases when the call relates to a support issue.

Record-triggered Flows on VoiceCall are the recommended way to extend this automatically, creating a follow-up task when a call ends in voicemail, for instance, or updating an Opportunity stage when disposition shows “Connected, interested.”

Useful reporting patterns once your data is clean:

  • Calls per rep per week, to spot coaching opportunities.
  • Average call duration by disposition, to flag calls that are too short to be substantive.
  • Calls per Opportunity, to see how much touch it takes to close.
  • Transcripts pulled for coaching reviews on specific call types.

Pro Tip: None of this works if your disposition picklist has 40 inconsistent values. Standardise it to a short list and make it required before you build a single report.

How automated call logging supports AI-ready data: a 42Voice perspective

Structured VoiceCall records with transcripts attached let teams run conversation analytics and route calls based on what was actually said, not just that a call happened. That’s the foundation we build on when we deploy AI agents to catch missed calls and qualify leads automatically. Sensitive conversations still need explicit consent and a person on the line. Automation earns its place on repeatable, high-volume work, never on the calls that need judgement.

Quick rollout checklist for enabling automated logging

Before going live, we recommend running through this checklist:

  1. Test in sandbox and map every legacy field.
  2. Validate Flows, reports and supervisor views.
  3. Confirm consent capture and human handoff paths.
  4. Train reps on dispositions and keep a rollback plan ready.

— Alston

How 42Voice can help automate call handling and feed Salesforce with useful voice data

We offer AI voice agents designed to handle repetitive, high-volume calls, handing every call needing nuance or judgement to a person. Our AI Receptionist and AI Sales Development Rep agents connect directly to your calendar and CRM, logging the interaction automatically instead of leaving it to whoever remembers to click Log a Call.

42voice

What this looks like in practice:

  • Missed and after-hours calls get answered instead of going to voicemail.
  • Calls can be reviewed under human-in-the-loop quality control before patterns are trusted.
  • Complex or sensitive calls hand off smoothly to your team, not to a script.
  • Deployment can be quick and does not require long-term lock-in contracts.

If you want to see how this fits your setup, book a free 15-minute demo and we’ll walk through it live.

FAQ

Can Salesforce record phone calls?

Salesforce itself doesn’t record calls natively; recording depends on your telephony provider or CTI integration, with the resulting file linked to a VoiceCall or Task record. Whether you’re legally allowed to record depends on your obligations under the Australian Privacy Principles, so check notification and consent requirements before switching recording on.

Can you make phone calls through Salesforce?

Yes, through a softphone or CTI integration like Salesforce Voice, which lets reps dial and receive calls from within the Salesforce interface. The call activity then logs automatically rather than requiring a manual entry afterward.

How to log meetings in Salesforce?

Meetings log the same way calls do, through the Log a Call or Event action on the relevant record, with the subject and outcome entered manually or synced from a connected calendar. For meetings tied to a deal, relate the entry to the Opportunity so it shows up in pipeline reporting.

How to set up a call log?

For manual logging, add the Log a Call action to your page layouts and standardise the disposition picklist so entries are consistent. For automated logging, connect a softphone or Salesforce Voice integration, which creates VoiceCall records with duration and recording data filled in without manual entry.

Sources

Check Salesforce’s own developer docs and the OAIC for the details that affect your setup.

42voice
Discuss Your Call Data Needs
Email 42Voice to discuss automating repetitive calls and helping your team focus on complex work requiring empathy and judgment.

This article is general information about AI voice technology and isn’t legal or compliance advice. Requirements for call recording, AI disclosure and outbound calling vary by state and use case.