Sales Engagement Gives You the Cadence. The Phone Channel Needs an Engine.
Credit where it is due: Salesforce Sales Cadences are a real sequencing product. The Sales Engagement add-on, listed at 50 dollars per user per month billed annually, builds multi-step cadences with branching, scores the leads inside them, and surfaces the next touch in every rep’s Work Queue. Teams that buy it get genuine cadence logic, not task reminders dressed up as a sequence.
Then the cadence tries to execute. The call step depends on whatever dialer you attach, and the native option, Sales Dialer, carries a retirement notice on Salesforce’s own help pages: no new features or enhancements are being added. While it lasts, reps work those call steps one manual dial at a time. The text step exists, with conditions: Cadence Builder 2.0 supports SMS steps only after SMS Messaging for Sales is running on Digital Engagement and Omni-Channel, and Salesforce notes those steps don’t support track entry rules or exit criteria. So the add-on delivers a three-channel brain whose phone channel has no future-proof engine and whose text channel needs its own licensing project. Kixie is the engine for both.
How Kixie Executes the Touch Layer
Call Steps at Multi-Line Speed
The prospects your cadence queues for calls flow into a Kixie PowerList, and the Kixie PowerDialer for Salesforce works that list at up to 4 lines at once, connecting the rep only when a human answers. Sales Engagement still decides who is due and when; the Work Queue is fed, not replaced. What changes is the drain rate: a queue that took an afternoon of single-line dialing empties in an hour, and the call step stops depending on a product Salesforce has marked for retirement. The same auto-enrollment mechanic also powers the day-zero motion covered on the Salesforce speed to lead page, where a brand-new Lead gets dialed the minute it is created.
The Text Step Without the Messaging Stack
Kixie’s documented automation recipes give the cadence a text channel without Digital Engagement. A record-triggered Flow, keyed to a field, a stage, or a prior call outcome, sends an Outbound Message that Zapier hands to Kixie, which fires an automatic SMS from the rep’s own number, the same number that has been calling. The prospect experiences one persistent person, not a sequence of systems. Each message logs to the Lead or Contact as a completed SMS Task once your admin adds the SMS types to the Task Type picklist. The full texting channel, from two-way inbox to templates, lives on the Salesforce SMS automation page; here it matters as a scheduled cadence touch.
Dispositions Branch the Follow-Up
Every Kixie call outcome logs as a closed Task with the Disposition activity type, which turns a linear cadence into a branching one using automation your admin already knows. A Connected disposition can trigger a Flow that moves the Opportunity stage and sends the native Salesforce email template, so the conversation’s follow-up email fires without a rep writing it. A No Answer disposition leaves the retry queued and the sequence keeps running. And because every touch is a typed Task rolling up from Lead or Contact to Account to Opportunity, cadence performance reports with standard Salesforce dashboards instead of a bolt-on analytics tab.
The Honest Division of Labor
Kixie cadence touches are calls and SMS only. They never send email, and that is the design, not a gap: Salesforce already owns email through templates, deliverability settings, and the automations that send them, and it owns the fields, stages, and sequencing logic around every touch. The working sentence is always the same: Kixie handles the calls and texts, Salesforce sends the email and moves the fields and stages. Teams that own Sales Engagement keep their cadence logic where they built it. Teams without the add-on can run Kixie’s own timed call and text cadences and let Salesforce automations carry the email half.
Before You Build
Kixie’s native Salesforce integration requires Professional edition or higher with API access, and connects with one authorization from the Kixie dashboard, no middleware. Have your admin make the Task Type field visible through Field Accessibility and add the SMS types to the Task Type picklist; that one-time setup is what makes every touch land as filterable, reportable Salesforce data instead of typeless tasks. From there, your cadence decides the touches, Kixie performs them, and the Work Queue finally moves as fast as the logic behind it.