Ask any sales rep what happens between calls. Copying a number. Flipping to a separate dialer. Typing notes from memory before the next call even starts. On a 10-person team running 50 calls a day, that dead time quietly eats over 30 hours of selling time every week.
Click-to-dial in Salesforce keeps calls and customer data in the same place, reps call straight from any record, outcomes log automatically, and notes stay attached to the right lead or contact without anyone stopping to file them.
This guide covers how click-to-dial actually works inside Salesforce, where it saves the most time for sales and support teams.
One click on a phone number inside Salesforce and the call goes out. That’s it. No copying the number, no switching to another app, no manual dialing. The call initiates directly from whatever record the rep is on; lead, contact, account, opportunity, case, or a custom object.
Under the hood, it runs on Salesforce Open CTI. That’s the JavaScript framework that lets telephony apps sit inside the Lightning interface and talk to CRM records in real time. When the rep clicks, the CTI softphone grabs the number, places the outbound call, and starts logging the activity against the record at the same time.
But here’s what separates a solid implementation from a basic one: it’s not the click. It’s everything that happens around it — the automatic logging, the disposition capture, the follow-up task creation. A CTI solution that handles only the dial and drops everything else is still leaving manual work on the table.
How Salesforce Click to Dial Connects Calling, Logging, and CRM Data
Salesforce Open CTI exposes a set of JavaScript methods that CTI adapters use to control the softphone. When a rep clicks a phone number, the CTI solution reads it and hands it to the telephony layer, which places the call.
When the call wraps up, the adapter calls Salesforce’s saveLog() method, part of the Open CTI API — and writes the call activity directly into Salesforce’s own activity objects. Not a sync from a third-party database. Not a webhook that fires later. It writes straight into the CRM.
That’s why the call log, duration, outcome, agent name, and timestamp all land on the record without anyone typing them. Notes and dispositions get captured during the call or right after, tied to the specific record automatically.
Sales reps don’t lose time on calls. They lose it in the spaces between them. Finding the next number. Updating a log. Remembering to set a callback. One-click calling in Salesforce compresses all of that into the same motion.
Reps can call from a lead page, a contact, an opportunity, or straight from a filtered list view. That last one matters more than people realize. Running a re-engagement push on 80 cold leads? Set up the list view, hit dial. No need to open each record one at a time.
360 CTI’s click-to-dial works across standard and custom Salesforce objects, so teams with non-standard CRM builds don’t have to jury-rig anything.
Manual logging breaks down fast. Reps rushing through calls pick dispositions at random, skip notes when they’re tired, and forget follow-up tasks entirely. Managers end up with activity data they can’t use for coaching.
Automatic logging changes the baseline. Every call attempt gets recorded with the right fields — timestamp, duration, agent. Dispositions get picked while the conversation is still fresh. And the activity hits the record immediately, not two hours later when someone finally gets around to updating it.
Click to dial is the base. For teams running outbound campaigns, a power dialer takes it further. Agents work through a call list automatically. 360 CTI’s Break, Skip, and Call controls let them stay in control mid-sequence — skip a record, take a break, restart from any point without losing where they left off. The next number queues up as soon as one call ends.
Screen pop. That’s the inbound version of click to dial. When a known customer calls in, the CTI system recognizes the number and pulls up the matching Salesforce record before the agent picks up. Case history, account details, previous call notes — it’s all loaded. The agent doesn’t ask the customer to repeat their account number or explain an issue they’ve already described twice.
Click to dial is outbound-first, but support teams tap the same underlying CTI infrastructure for callbacks. The rep clicks to call from the case or contact record. The call logs against the case. Notes and dispositions land in the right place.
Here’s a thing that gets overlooked in most click-to-dial writeups: what happens when nobody answers. With 360 CTI, missed calls show up directly in the softphone’s call log tab. Agents don’t have to dig through a separate page or check a notification elsewhere. The number is clickable. A callback task takes seconds to create.
It’s a small detail, but it’s the kind of thing that stops real opportunities from slipping through.
Manual dialing is a process tax. The cost doesn’t show up in one place — it bleeds out across hundreds of small moments. But run the math on a 10-person team doing 50 calls a day: if each rep burns 3 to 4 minutes per call on non-call admin (copying numbers, writing notes, creating follow-up tasks), that’s 25 to 33 hours of productivity gone every week. For the whole team. Every week.
And that’s before the data problem. Managers can’t coach from logs that don’t exist. Incomplete call records mean broken pipeline visibility. Patchy activity data makes forecasting unreliable and lets follow-ups fall off entirely.
| Workflow Step | Manual Dialing | Click-to-Dial (360 CTI) |
| Initiating a call | Copy number, open dialer, dial manually | One click from the Salesforce record |
| Call logging | Manual entry after the call, often incomplete | Auto-logged on call end with full fields |
| Notes and disposition | Typed from memory, frequently skipped | Captured during or right after call, on-record |
| Follow-up task creation | Manual step, often forgotten | Captured during or right after call, on-record |
| Missed call tracking | Check a separate system or email alert | Visible directly in the softphone call log tab |
| List-based outreach | Inconsistent depends on rep discipline | Consistent, auto-written from CTI to Salesforce |
No external APIs. No middleware. No separate integration to maintain. 360 CTI installs directly from the Salesforce AppExchange as a managed package and runs natively inside Lightning. The Salesforce softphone sits in the interface and stays there agents don’t toggle between systems.
Click to dial covers leads, contacts, accounts, opportunities, cases, and custom objects. Every call writes back to Salesforce via the saveLog() method duration, direction, disposition, recording link, agent name, follow-up task. Agents can see outgoing calls, incoming calls, missed calls, and pending calls from one softphone view without navigating anywhere.
Sales teams running bulk outreach get the power dialer on top of that. Filtered list views. Break, Skip, and Call controls agents configure themselves. No admin ticket required to set up a campaign list.
Support teams get screen pop for inbound calls, so context is loaded before the phone rings through. And for availability, 360 CTI’s Online/Away/Offline status controls mean inbound calls only route to agents who can actually take them not to someone who stepped away 20 minutes ago. Auto-forwarding covers up to nine mobile numbers when no desktop agents are available.
Which is the kind of feature that feels optional until you’re running high call volumes and calls start hitting dead air.
Salesforce holds every lead, contact, account, and interaction your team works from. So when you need to reach thousands of contacts with…
Ask any sales rep what happens between calls. Copying a number. Flipping to a separate dialer. Typing notes from memory before…
You have a list of 300 leads, a daily call target, and six working hours to get there. Half that…
Live Chat
