Outbound Call
An outbound call is a phone call that a Salesforce user starts toward a customer, rather than one that arrives from the customer.
Definition
An outbound call is a phone call that a Salesforce user starts toward a customer, rather than one that arrives from the customer. In Service Cloud and CTI integrations it is usually placed straight from a record using click-to-dial, so the agent never has to copy a number into a separate phone app.
Outbound calls cover proactive contact like case callbacks, follow-ups, renewals, and sales prospecting. The call center or telephony provider connects the line, while Salesforce supplies the record context and writes the activity back to the customer's timeline.
How outbound calling actually fires from a record
Click-to-dial is the front door for most outbound calls
Click-to-dial turns a formatted phone number into a clickable control. When an agent clicks the phone button next to a number, that number is dialed in the first open softphone line. In Salesforce Classic the documentation notes a few guardrails worth knowing. The phone button does not appear next to fax numbers, and a number that was just clicked cannot be clicked again for five seconds. That short cooldown stops a double-click from starting two calls. Numbers are dialable from the records agents work in every day, including contacts, leads, accounts, and activities. To use the feature an agent must belong to a call center and have an open softphone line available. Without call center membership the phone button stays inert. In Lightning Experience the same behavior is delivered by the lightning-click-to-dial component, which renders a number as click-to-dial enabled or disabled for Open CTI and Voice. The component needs a phone system enabled before anyone can dial, and it does not support iFrames, so it cannot live inside an iframe-hosted utility.
What Open CTI passes to the phone system
When an agent clicks a number in Lightning Experience, Open CTI hands the telephony adapter a payload so the call has context, not just digits. The onClickToDial() method for Lightning Experience registers a listener that fires on the click. It works with the lightning-click-to-dial component and the lightning:clickToDial Aura component, and it is available from API version 38.0 onward. It cannot be used with the older Visualforce support:clickToDial component. The listener receives an object with concrete fields. The number field carries the phone number that was clicked. recordId, recordName, and objectType describe the record the number came from, so the adapter knows whether the call relates to a Contact, a Lead, or a custom object. For person accounts there is a personAccount boolean plus an accountId or contactId. A params field holds a comma-separated list of extra parameters tied to the number. enableClickToDial() and disableClickToDial() turn the behavior on and off for the session. That payload is what lets the partner log the right activity and pop the right screen.
Outbound calling inside Service Cloud Voice
Service Cloud Voice brings the phone into the Salesforce console, so outbound calls share the same workspace as cases, chats, and other channels. With Voice an agent can place a call to a customer from a record and have the interaction tracked against that record without juggling a separate phone tool. Voice also supports click-to-dial for transfers, so a rep can call or transfer to a number that appears in the console. Voice comes in flavors, including Service Cloud Voice with Amazon Connect and Service Cloud Voice for Partner Telephony, where a telephony provider plugs in through a documented framework. For partner telephony the provider implements the methods that actually start the call, while Salesforce owns the record context and the call record. Because the channel lives in the console, supervisors get a single view of voice activity next to digital work. That unified picture is the main reason teams move click-to-dial onto Voice rather than running a bolt-on dialer beside Salesforce.
Dialing modes change how outbound scales
A single click-to-dial press is fine for one-off outreach. High-volume teams need automation, and that is where dialing modes come in. Service Cloud Voice for Partner Telephony supports a preview dialer and a progressive dialer for outbound campaigns. A preview dialer shows the agent the record before the call connects, so they can read context and decide when to dial. That suits complex accounts where a few seconds of prep improves the conversation. A progressive dialer leans on automation to manage the calling rate based on real-time agent availability and to connect agents to live, answered calls. The goal is to cut the dead time agents spend listening to ringing or voicemail. Salesforce also offers high-volume outbound calling and automated dialing campaigns built from customer profiles. Picking the right mode is a tradeoff. Preview protects call quality on high-value records. Progressive and predictive styles protect agent minutes when the list is large and the script is short. Most contact centers mix both depending on the campaign.
Logging, disposition, and the customer timeline
An outbound call only helps the next agent if it leaves a record. With click-to-dial the call ties back to the contact, lead, account, or activity it started from, so the interaction lands on that record's timeline. Many telephony adapters create a call log or task automatically using the record context Open CTI supplied, which spares agents from retyping who they called and why. Call disposition is the outcome an agent records after the call, such as connected, left voicemail, wrong number, or callback requested. Capturing disposition consistently is what makes outbound activity measurable. It feeds reports on connect rates, callback volume, and campaign effectiveness. Without it, an outbound call is just a number that was dialed. Mature centers also pair outbound and inbound metrics to see the full interaction load on each agent, since an agent who places many proactive calls may still be carrying a heavy queue. The discipline is less about the dial itself and more about the structured note that survives it.
Where outbound calling fits across Sales and Service
Outbound calling is not only a support motion. Sales reps with access to both Sales Engagement and Salesforce Voice can click-to-dial records that come from a cadence, their personal list, or a work queue, so they make outbound calls without leaving the flow they already work in. That keeps prospecting calls attached to the same activity history as emails and tasks. On the service side the same click-to-dial mechanics power case callbacks and proactive follow-ups, often triggered by an entitlement or a milestone that needs a human touch. The shared plumbing means an admin who learns click-to-dial and Open CTI once can support both teams. The difference is mostly the surrounding process. Sales wraps outbound calls in cadences and lists, while service wraps them in cases and SLAs. Because Voice and Open CTI sit underneath both, an outbound call from a sales cadence and a callback from a case use the same dial path and write to the same kind of activity record.
Set up click-to-dial for outbound calls
Outbound calling through click-to-dial depends on a working call center and an Open CTI or Voice adapter. The exact screens vary by telephony provider, but the order of operations is consistent. Here is the typical admin path to make numbers clickable for agents.
- Set up a call center
Install or define a call center definition for your telephony provider, then add the agents who place outbound calls as call center members. Click-to-dial does nothing for a user who is not a member.
- Enable the phone in the console
Give agents a softphone in the utility bar through Open CTI or Service Cloud Voice. The phone system must be enabled before any number renders as clickable in Lightning Experience.
- Confirm click-to-dial on records
Open a contact, lead, or account and verify the phone button shows next to phone fields. The lightning-click-to-dial component handles this for standard layouts, so check that your layouts surface the relevant phone fields.
- Wire logging and disposition
Make sure the adapter creates a call log or task from the Open CTI payload and that agents can set a call disposition. Without this, outbound activity will not show up in reports.
Each agent must be a member of the call center, or the click-to-dial phone button will not appear or work.
Choose Open CTI with a partner adapter for a bring-your-own-telephony model, or Service Cloud Voice to run the phone natively inside the console.
For campaigns, pick a preview dialer to give agents record context first, or a progressive dialer to maximize connected talk time on large lists.
- The phone button does not appear next to fax numbers, and a number cannot be re-clicked for five seconds after it was clicked.
- The lightning-click-to-dial component does not support iFrames, so it cannot run inside an iframe-hosted utility or Lightning Out app.
- onClickToDial() does not work with the legacy Visualforce support:clickToDial component, so plan Lightning and Classic click-to-dial separately.
- Click-to-dial needs an open softphone line; if every line is busy, the new outbound call cannot start.
Prefer this walkthrough as its own page? How to Outbound Call in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Outbound Call.
Hands-on resources to go deeper on Outbound 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. In a Service Cloud CTI setup, how does an agent typically place an Outbound Call from a contact or case record?
Q2. What distinguishes an Outbound Call from an Inbound Call inside the same CTI softphone?
Q3. After an agent finishes an Outbound Call placed through the softphone, what does the platform record automatically?
Discussion
Loading discussion…