Salesforce dialer: native options, setup, and when a standalone wins

If your reps live in Salesforce, the dialer question usually starts with "can't we just turn on the one Salesforce sells?" Often the answer is yes. Salesforce Dialer (it used to be called Lightning Dialer) handles click-to-call, logging and recording inside the record your rep already has open. Problems tend to appear later: when the team wants to dial through a list faster than one click per call, when the per-user add-on cost grows with headcount, or when someone asks why follow-up texts happen in a different tool that doesn't sync.

This post covers the three paths a Salesforce admin can take: the native dialer, a third-party dialer connected through Open CTI, and a standalone tool that runs next to Salesforce. It includes setup steps, limits, cost math and an honest answer on where Ready fits. For Salesforce teams, Ready is often a partial fit, and we explain why below.

The three ways to dial from (or near) Salesforce

Service Cloud Voice, built on Amazon Connect, is a fourth option, but it's a contact center product. If you're running an inbound support queue, evaluate it separately. For outbound sales it is usually more than you need.

Setting up Salesforce Dialer

The native setup is short when your edition and licenses are already in place. The steps in Lightning:

1. Confirm licensing. Dialer is sold as an add-on. Each rep needs the Dialer permission set license, and features such as local presence and voicemail drop have their own permission sets. Your account executive can tell you which ones your contract includes.
2. Enable it in Setup. Search "Dialer" in Quick Find, open Dialer Settings and turn the dialer on.
3. Assign permission sets to the users who will make calls.
4. Add the Dialer utility to the utility bar of the Lightning app your reps use, such as Sales Console. If you skip this step, reps won't see a phone.
5. Configure call recording. Decide whether recording is on by default, and set up the consent announcement. Some states require all-party consent, so take this step seriously.
6. Set up voicemail drop and local presence if you licensed them, then test each one from a real rep profile, not only an admin profile.
7. Check activity logging. Make sure calls create Task records with the fields your reports use, such as call result, duration and disposition picklist values.

Plan for an afternoon for the configuration itself and a week for reps to get used to the dispositions. Most of the ongoing work is in step 7. If the call result values don't match your pipeline reporting, the dialer data won't be useful.

What the native dialer does well

• Calls, notes and recordings attach to the Lead, Contact or Opportunity automatically.
• Reps don't switch tabs.
• Admin, security and data residency stay with one vendor you've already reviewed.

Where it runs out

• Dialing pace. It's built around click-to-call from a record or list view. Teams that want the next number dialed automatically, or several lines dialed at once, end up buying an Open CTI tool. If you aren't sure which pace you need, our breakdown of predictive vs auto dialers covers the differences and the compliance exposure of each.
• Cost per seat. It's a per-user license whether a rep makes 10 calls a day or 200. Part-time callers and seasonal staff cost the same as your heaviest dialer.
• Texting. Follow-up SMS usually needs another product, such as Digital Engagement or an AppExchange texting app, with its own 10DLC registration.

Open CTI dialers: more speed, more vendors

Most AppExchange dialers connect through Open CTI. The vendor's softphone sits inside Salesforce, and calls are logged back as Tasks. Setup usually means installing a managed package, assigning a call center in Setup, and mapping dispositions to Task fields.

Before you sign, ask these three questions:

• Does the logging write to standard Task fields, or to custom objects? Custom objects break existing reports.
• What happens when Salesforce is slow or down? Some tools queue the logs and retry. Others lose them.
• How is the pace mode governed? Power and predictive dialing to cell phones carry TCPA consent requirements. A vendor that says "we're compliant" hasn't removed your responsibility for the list.

Our guide to dialer CRM integrations compares how sync depth differs between Salesforce, HubSpot, Pipedrive and others. Sync depth matters more than the feature list.

Cost trade-offs: per seat vs per minute

Per-seat pricing suits a team where everyone dials all day. Per-minute pricing suits a team where calling volume is uneven. Before you compare tools, do this math with your own numbers.

Here is a worked example of usage-based dialing. The assumptions are illustrative, not benchmarks:

• 5 reps, each dialing 80 inbound leads a day (400 dials)
• An assumed 15% of dials answered, so 60 answered calls a day, including a few that reach voicemail
• An average of 3 billed minutes per answered call

On the Ready Dialer at $0.025/min, only answered time is billed. Each started minute counts as a full minute, and a ring-out or a busy line costs nothing. A call answered by voicemail counts as answered.

• 60 answered calls × 3 minutes = 180 minutes
• 180 × $0.025 = $4.50 a day, or about $237 over a 22-day month

Compare that with the per-user add-on price for the same 5 reps on whatever quote your Salesforce or Open CTI vendor gives you. When the reps call steadily all day, per seat can come out ahead. When half the team calls only on Mondays, usage pricing usually does. For a broader view of what dialers cost, see auto dialer pricing.

Where Ready fits, and where it doesn't

The Ready Dialer gives you click-to-call from a dial pad, consented call recording and transcripts, inbound calls that ring the open pad, and a Missed call card in the Inbox thread for each call you miss. It does not do queue or auto dialing, voicemail drop, transfers, or manager barge and whisper. If you're replacing Salesforce Dialer because you want faster list dialing, Ready isn't the tool for that. An Open CTI dialer with power or parallel dialing is.

Ready also has no Salesforce dialer and no two-way message sync with Salesforce, though a Ready automation can create Salesforce leads, opportunities and tasks through the app library. Our deepest integration is GoHighLevel, which offers two-way sync per sub-account, and the dial pad works in the Ready dashboard and inside GHL. A Salesforce-centric team that uses Ready would be calling outside the CRM, and logging each call or text to Salesforce would still be built against our messaging API.

Ready makes sense next to Salesforce in a few specific cases:

• The calling team doesn't work in Salesforce. An inside sales pod, a sister brand or an agency runs on GHL or the Ready app, while Salesforce stays the system of record for enterprise deals.
• You want text and call in one thread. The fastest first touch on a web lead is often a text sent within seconds, followed by a call. Our post on text-first or dial-first order explains how lead source changes which channel should go first. Ready puts SMS, replies and calls in one inbox.
• You're a platform building texting for your own customers. In that case the API, sub-accounts and registration handling matter more than any one CRM.

The SMS side, costed

The texting runs on registered 10DLC. Registration has no setup fee. The first charge is $25 when you submit, after which the monthly cost is $25/mo for registration and $2 per number. Most approvals take 2 to 7 days.

Here's a worked example. In the same day as the dialing example above, you text 100 consented leads who didn't answer, each with a 150-character message and no emoji. That's 1 segment per text:

• 100 × $0.0075 = $0.75 plus 100 carrier fees
• Replies you receive are billed the same way per segment
• TCPA/DNC scrubbing and landline validation are off by default. If you turn them on for the account, each adds $0.003 per segment.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

The per-segment price isn't the lowest available, because raw CPaaS providers charge less per segment. What you get for the price is registration handled in the app, automatic STOP handling, quiet-hours holds based on the recipient's area, and the inbox. The first 20 one-to-one texts are free, and to send any text you need a card and a number ($2 a month, the first month charged when you get it).

Compliance: same rules regardless of tool

Changing dialers doesn't change your obligations. Calls to cell phones made with an autodialer or prerecorded voice need prior express consent. Texts need consent as well. Do Not Call lists apply to both. A standalone scrub at $0.005 per contact checks numbers against TCPA-litigator and DNC-complainer lists before you send. It reduces risk against exposure of $500 to $1,500 per violation, but it doesn't make you immune to claims. Recording disclosure rules vary by state. Compliance is ultimately the sender's responsibility.

The practical takeaway

• Stay native with Salesforce Dialer if reps call from records at moderate volume and you value one vendor and clean reporting.
• Add an Open CTI dialer if the goal is faster list dialing and you want logs to stay in Salesforce.
• Run a standalone tool next to Salesforce when the calling team works elsewhere, when usage pricing beats seats, or when text and call need to share one thread.

If the third case describes your team, you can sign up, use the free one-to-one texts before you register, and test the dial pad on a few real leads before changing your process. Check the per-segment rate on our pricing page against your current bill first.