Salesforce Dialer: SFDC Dialer and Sales Dialer Pricing

Does Salesforce have a dialer?

Yes, two of them, and the older one is being retired. Sales Dialer, which Salesforce previously sold as Lightning Dialer, is an add-on licence that puts click-to-dial on phone number fields in Lightning Experience and logs the call to the record. Salesforce Voice, sold through the Partner Contact Center packages, is the newer native telephony product and the one Salesforce now points customers toward.

What Sales Dialer is not is a sales dialer in the sense an outbound team means the phrase. The documentation describes a single click from phone number fields on contacts, leads and list views, plus call lists built from leads, accounts, person accounts and contacts. It does not document a power dialing mode, a parallel dialing mode or a predictive dialing mode. If your reps are working a list of 200 numbers a day, that distinction is the whole purchase, and it is why nearly every serious Salesforce outbound team ends up buying something third party. We put the three native CRM dialers side by side on our CRM dialer comparison, and the HubSpot equivalent, which has its own pooled-minute trap, on HubSpot calling and HubSpot dialer pricing.

Salesforce Voice is a different animal. It is contact-center shaped, priced per user on top of your CRM licence, and it either connects a telephony partner you already have or ships preintegrated with Amazon Connect. It is genuinely more capable than Sales Dialer. It is also several times the price once you add the platform licence underneath it.

Salesforce dialer pricing: what Sales Dialer and Salesforce Voice cost

Start with the honest answer on Sales Dialer: Salesforce does not publish a price for it. It is not on the Sales Cloud pricing page, it is not on the Service Cloud pricing page, and the help documentation says only that it is available for an additional cost as an add-on license. Any specific dollar figure you find for Sales Dialer on a comparison blog came from somewhere other than Salesforce, so treat it as a starting point for a conversation with a rep rather than a budget line.

Salesforce Voice is the opposite, and this is the most useful pricing table Salesforce publishes for telephony. Read on September 10, 2026, the Partner Contact Center page lists five packages in USD:

Contact Center at $125 per user a month, with native voice and unlimited platform voice minutes. Partner Contact Center at $50 per user a month, which connects telephony you already buy elsewhere and includes no minutes. Then three preintegrated Amazon Connect bundles: $75 for 750 minutes a month, $125 for 2,000 minutes, and $200 for 5,000 minutes. The page states plainly that this edition requires an annual contract.

Run the arithmetic on those three bundles, because the obvious reading is wrong. Divide each package by its minutes and you get $0.10 a minute at 750, $0.0625 at 2,000 and $0.04 at 5,000, which looks like a clean volume discount. Every one of those packages also contains the $50 Partner Contact Center platform fee, though, so you are not buying 750 minutes for $75. You are buying a $50 licence plus 750 minutes for $25. Take the $50 out and the middle tier inverts: $0.0333 per included minute at 750, $0.0375 at 2,000 and $0.0300 at 5,000. The 2,000-minute package is the most expensive of the three per minute of allowance. That is our arithmetic on Salesforce's published figures, dated September 10, 2026, not a quoted rate, and it means the middle option is the one to question before you sign.

None of that is the real number, though, because Voice sits on top of a CRM licence. Sales Cloud on September 10, 2026 lists Starter Suite at $25, Pro Suite at $100, Core at $195, Advanced at $395 and Max at $550 per user a month, with Core and above billed annually. A rep on Sales Cloud Core with the 2,000-minute Amazon Connect package is $195 plus $125, so $320 per user per month on an annual commitment. That is our arithmetic on Salesforce's published figures, not a quoted price, and it is the figure to carry into the comparison rather than the $125. We break the Voice ladder down on its own in Salesforce Voice pricing, and compare it against the standalone contact-center platforms on outbound call center software.

Salesforce dialer retirement: what Salesforce has actually said

The wording is worth quoting exactly, because it is milder than the rumours and more serious than it looks.

Every Sales Dialer page in Salesforce Help carries the same block: "Sales Dialer is scheduled for retirement. No new features or enhancements are being added to Sales Dialer. Information regarding formal end-of-life for features is posted on Salesforce Active Product & Feature Retirements. To use telephony features directly in Salesforce, we recommend that you modernize your experience by moving to Salesforce Voice."

So we went and read that list. On September 10, 2026 the Active Product & Feature Retirements page, itself carrying a publish date of August 17, 2026, lists around forty items, from Quip and Tableau Perpetual License to Salesforce for Outlook on December 1, 2027. Sales Dialer is not among them. The word Dialer does not appear on the page at all.

That is the actual state of play, and it is a genuinely awkward one for a buyer. The product is frozen: nothing new is coming, and Salesforce is steering you elsewhere in its own documentation. But there is no announced date, which means there is also no announced migration window, no end-of-renewal notice, and nothing to point at when you ask your account executive how long you have. The required-editions block on those same pages still names Essentials, Professional, Enterprise, Performance and Unlimited, edition names Salesforce retired from its own pricing page during the 2026 rename to Starter Suite, Pro Suite, Core, Advanced and Max. Documentation that has not been updated for its own company's product naming is a fair signal of how much attention the product is getting.

The practical reading: do not build a two-year outbound plan on Sales Dialer, do not assume you will get a long notice period, and if you are already on it, price the alternatives now while you are choosing rather than later while you are migrating.

What happens to third-party Salesforce dialers when Open CTI retires?

This is the part almost no dialer comparison mentions, and it affects far more teams than the Sales Dialer retirement does.

Open CTI is the Salesforce API that lets an outside phone system draw its softphone inside the Salesforce interface and do the things reps take for granted: screen pops on an inbound call, click-to-dial from a record, call controls in the utility bar. Salesforce's own description is exactly that: an API that allows partners and customers to build third-party CTI systems that integrate directly with the Salesforce user interface.

Knowledge article 005306437, published June 25, 2026, sets the terms. Open CTI is in maintenance mode with no new features being added. It is scheduled for retirement on February 28, 2028, and Salesforce states that after this date, Open CTI implementations will no longer function. There is an immediate restriction as well: no net new Agentforce Service orgs can implement or use Open CTI, though existing orgs can keep using it until the retirement date. The recommended path is Salesforce Voice, with partner telephony where you want to keep your carrier.

What that means when you are choosing a dialer in 2026 is simple enough. If the vendor's Salesforce integration is a CTI adapter, you are buying something with a known expiry on the integration layer, and the migration will not be on your schedule. It does not make those products unbuyable. Several vendors have already published their own migration plans. It does make one question mandatory in every demo: which Salesforce API does your integration use today, and what is your plan for February 2028? Get the answer in writing before you sign anything with a term that runs past 2027.

It is also worth knowing which integrations are not affected in the same way. A vendor that syncs through the Salesforce REST API, writing activities and call records to objects rather than painting a phone in the UI, is on a different track entirely. So is any approach where no human is holding a softphone in the first place, which is the shape our own product takes. Our dialer CRM integration guide covers what to check field by field, and AI cold calling with CRM sync covers the write-back side.

Salesforce dialer limitations

Salesforce publishes a dedicated limitations page for Sales Dialer, and it is more useful than most vendor documentation because it is specific. Read on September 10, 2026, the constraints that actually decide purchases are these.

Geography first. Outgoing calls are supported to the U.S. and Canada only, and Puerto Rico is not supported. Local Presence, the feature that shows a local area code to the person you are calling, is only available in the U.S. and is not available in Canada. If any part of your list is international, Sales Dialer is out before you get to price.

Then the environment. Dialer features are available in Lightning Experience on the desktop only, with no support in Experience Cloud sites. You cannot make or receive live calls in a sandbox at all, which makes proper pre-production testing of a calling workflow awkward. Voicemail is capped hard: users can store up to 20 voicemail messages, each limited to two minutes, and those messages are saved as files that count toward your file storage quota, so a busy inbound number quietly eats storage you are paying for elsewhere.

The licensing details are where teams get caught. Dialer users cannot have Salesforce Voice permission sets or be part of a Salesforce call center, so you cannot run Sales Dialer and Salesforce Voice alongside each other for the same user during a migration. Permission set groups are not supported for Dialer permissions, so those have to be assigned directly. A Dialer Inbound licence is required before a user can be assigned a number or reach personal Dialer settings. And the one that produces the most confused support tickets: users need the Edit Task permission to log calls, a permission that is not automatically included with some profiles, so reps with those profiles can make calls but the calls are not logged. A dialer that does not log is worse than no dialer, because the pipeline review silently reads as though nobody called.

Smaller things that still sting: Call Monitoring is not supported in Salesforce Essentials, the utility bar supports only one Phone item at a time, users cannot pop the call panel in or out during an active call, phone numbers on dashboards cannot be dialed directly, and when a rep calls a busy landline Dialer ends the call without a ring or a busy signal. For a team that dials all day, the last one alone is a meaningful volume of mystery-failed calls.

Salesforce power dialer, parallel dialer and predictive dialer

Search volume exists for all three phrases against Salesforce, and the honest answer is that none of them is a native Salesforce product. The Sales Dialer documentation describes click-to-dial and call lists. It does not document power dialing, parallel dialing or predictive pacing, and since no new features are being added, it is not going to.

So the question becomes which third-party shape fits, and the three are genuinely different purchases. A power dialer places one call per available rep and advances automatically down the list, which means it structurally cannot abandon a call, because there is always a rep waiting for the one call it placed. PhoneBurner is the clearest example of this shape with a native Salesforce integration on every tier, at $140 to $183 per user a month billed annually with unlimited calling. A parallel dialer places several calls at once per rep and drops the ones that do not connect, which lifts conversations per hour sharply and introduces exactly the abandonment exposure a power dialer avoids. Orum sits here, with a nine-seat minimum and no published price. A predictive dialer paces calls ahead of rep availability using a model of handle time and connect rate, which only works with enough agents to model: Genesys, for one, recommends at least 15 agents in a predictive campaign in its own documentation.

Watch the label rather than trusting it. Several vendors market multi-line parallel dialing under the phrase power dialer, and Kixie's own site says up to 10 numbers in parallel in one place and up to 4 lines in another. Ask how many simultaneous calls per rep, and ask what happens to the extra connects, and you will know which product you are actually being sold regardless of the name on the tier.

We go through the trade-offs properly on power dialer software, parallel dialer software and predictive dialer software, including the abandonment rules that apply to the last two. The short version for a Salesforce team: under ten dialing reps, power or parallel. Above fifteen, predictive becomes worth the compliance overhead. And if the constraint is that you do not have the reps and are not hiring them, none of the three is your answer.

Best dialer for Salesforce: what to check before you sign

Five questions separate the shortlist from the marketing, and none of them is about features.

First, which tier holds the Salesforce integration. This is the single most common budgeting mistake in the category. CloudTalk puts its Salesforce Ecosystem Integration on the 49 EUR Expert tier while advertising a 19 EUR entry seat. Aircall starts Salesforce CTI on Professional rather than Essentials, and sells Aircall for Salesforce Voice as a separate 30 EUR per licence product on top. JustCall omits Salesforce from its lowest plan. Ringover's 20 EUR TALK tier lists no integrations at all. Price the tier that actually has the connector, not the one on the billboard.

Second, integration is not write-back. Ask which objects and fields the vendor writes, and under which permission. PhoneBurner states that automatic write-back of notes, dispositions and recordings applies to its native integrations only. Salesforce itself documents that a rep without the Edit Task permission can make calls but the calls will not be logged. Both of those produce the same symptom months later: an activity history with holes in it.

Third, the API question from the section above. Which Salesforce API does the integration use, and what is the plan for the February 28, 2028 Open CTI retirement.

Fourth, the licence floor. Orum prints a nine-seat minimum above its plans. Five9's footnote sets a fifty-seat minimum on published pricing. Aircall's Power Dialer lives on a Custom tier with a twenty-five licence minimum. Apollo requires three seats on Organization and then charges $119 per team per month for the Advanced Dialer that actually dials. A vendor can be perfect for you and still be unbuyable at your headcount.

Fifth, what is an add-on. Kixie sells Do Not Call scrubbing as a compliance add-on. PhoneBurner sells numbers as an add-on. Orum sells webhooks and AI coaching as add-ons. The quote you get and the price page you read are frequently different documents.

Our full ranked shortlist for Salesforce teams, with the reasoning behind each pick, is in the best dialer for Salesforce breakdown, and the wider pricing comparison across sixteen dialers sits on best dialer for cold calling.

Salesforce dialer setup: what has to be enabled before a rep can dial

Worth knowing before you scope an implementation, because the admin work is not zero and some of it is easy to miss until a rep complains.

Sales Dialer is enabled from Setup, then added to the utility bar so the call panel is available, then granted through a permission set assigned directly to users. Permission set groups are explicitly not supported for Dialer permissions, so if your org manages access through groups, this is an exception you have to document or someone will undo it in six months. Call Monitoring has its own permission set and is not supported in Essentials.

Three further steps cause most of the tickets. Users need a Dialer Inbound licence before they can be assigned a number or open personal Dialer settings from the call panel. Users need the Edit Task permission before their calls will log. And Local Presence has to be enabled separately, is US only, and does nothing for Canadian numbers.

Sandbox is the other trap. You cannot make or receive live calls in a sandbox, so you can test the automation that fires after a call, such as the log-a-call task, but you cannot test the call itself. And if you spin a sandbox from an org that already has voice calls, the voice call records and recordings are not copied over, and Dialer has to be enabled again from Setup in the new environment.

All of which is manageable. It is just worth costing honestly alongside the licence, particularly if the plan is to do it once now and again when the retirement finally gets a date. If you would rather not stand up a telephony stack inside Salesforce at all, the alternative shape is to let an AI agent hold the conversation and write the outcome back through the API, which is what our AI dialer and AI cold calling software pages cover.