Sales Dialer Has Local Presence. Read the Fine Print Under It.
A prospect in Austin sees a 415 number and lets it ring out. The list was good, the rep was ready, and the caller ID lost the call anyway. Salesforce knows this, which is why Sales Dialer ships with Local Presence: an admin enables it from Setup, reps turn it on in personal settings, and outbound calls show numbers local to the prospect. Credit where due, the feature works. But Salesforce’s own documentation attaches three qualifiers that decide whether you can build an outbound calling motion on it. Local Presence is only available in the US and is not available in Canada. The product carrying it is scheduled for retirement, with no new features or enhancements being added. And when one of its numbers picks up a spam label, the documented path is manual.
US Only, Desktop Only, and Tied to a Retiring Product
The Dialer Limitations page spells out the boundaries. Sales Dialer can call the US and Canada, but its Local Presence feature works only in the US, so Canadian teams and Canadian contacts are outside it entirely. Dialer features run in Lightning Experience on desktop only. Numbers are subject to availability, and Salesforce notes that numbers from all area codes may not be available, which caps how local your local presence can actually get. Above all of it sits the retirement notice on the same page: Sales Dialer is retiring, and Salesforce points teams toward Salesforce Voice as the replacement. No formal end-of-life date has been published, so no one can tell you how long the runway is. What is certain is that any local presence setup you invest in today lives inside a product Salesforce says it is winding down.
The Documented Spam Fix: Ask the Receiver to Call Their Carrier
Salesforce help article 000392040 addresses what happens when Sales Dialer calls show as Potential Spam or Potential Fraud. It states that spam tagging is not within Salesforce’s scope of support because the receiver’s carrier controls it, suggests the receiver of the call contact their own carrier to adjust their line settings, and notes there is currently no way to prevent a number from showing as spam, so an admin can release the flagged number and assign a new one. The limitations page adds a throttle: admins can release and replace at most a single number per user each month. For a team dialing at volume, that is remediation by attrition, one number at a time, after the damage to answer rates already happened.
ConnectionBoost: Local Presence as a Managed Service
Kixie’s local presence dialing is part of ConnectionBoost, and the difference is who carries the number burden.
- Managed number pool: each call to a Salesforce Lead or Contact presents a caller ID matching the contact’s area code, drawn from a pool Kixie provisions and controls, with nothing for your admin to buy, assign, or release.
- Number Health Automation: your trailing 30 days of call activity are analyzed across North American area codes, and numbers are added, replaced, and retired automatically by reputation and performance, so a degrading caller ID rotates out before it drags a week of dialing down with it.
- Carrier trust built in: every current and future Kixie number is enrolled in First Orion business registration through a direct carrier partnership, and every call carries A-Level STIR/SHAKEN attestation, the highest level.
No vendor can honestly promise a number will never be flagged; carriers score calling behavior with proprietary algorithms that change. What a managed pool changes is what happens next: monitoring catches the flag, rotation retires the number, and remediation runs as a service instead of waiting on a one-per-month release quota.
Every Rotating Caller ID Still Lands on the Salesforce Record
The displayed number changes; the logging does not. Every Kixie call logs to the matching Lead or Contact as a typed Task with the disposition and recording attached, and the activity rolls up to the Account and Opportunity. Pair local presence with the Kixie PowerDialer for Salesforce and a Salesforce list view becomes a multi-line calling session where every parallel dial shows the contact a local number. Setup and the rest of the logging mechanics are covered in the full Salesforce integration overview.
Plan Local Presence Past the Retirement Notice
If your team is US-only, calls a few regions, and is comfortable riding Sales Dialer until Salesforce announces its end date, the native feature may hold for now. If you call into Canada, cover the map, or simply do not want spam-flag cleanup to be someone’s job, the managed model is the point of this page. Local presence should be a capability of your outbound calling stack, not a feature of a product on its way out.