Salesforce SMS Automation: Text Leads From the Rep's Number

Yes. SMS Messaging for Sales, generally available since July 2025, lets reps start texts from the Activity Composer on Lead, Contact, and person account records, and Sales Engagement users can add SMS steps to cadences. It builds on Digital Engagement and Omni-Channel, which your admin sets up first, and Salesforce's considerations note that SMS messages don't support activity reporting. Marketing Cloud MobileConnect covers campaign broadcasts separately. Kixie adds rep texting without the Digital Engagement stack, logged as reportable Tasks.

Sales Cloud (now branded Agentforce Sales) gets rep texting through SMS Messaging for Sales, which borrows Service Cloud's Digital Engagement messaging and Omni-Channel routing, with an SMS channel per rep and conversations held in Messaging Sessions. Marketing Cloud MobileConnect sends campaign broadcasts under a separate license and is not a two-way sales conversation tool. Kixie texting runs on its own platform: reps text Leads and Contacts one-to-one from the number they call from, and every message logs as a Salesforce Task.

Not without a messaging product behind them, such as Digital Engagement, Marketing Cloud, or an AppExchange app. With Kixie, a record-triggered Flow becomes a texting trigger: it fires an Outbound Message to a webhook, and Kixie sends the text from the record owner's own Kixie number. No Digital Engagement license required.

It is a documented Kixie support recipe. A Salesforce automation sends an Outbound Message to a Zapier catch-hook webhook, the Zap looks up the record owner, and the Kixie send-SMS action finishes the job. Kixie's article was written for workflow rules, which Salesforce stopped supporting on December 31, 2025, so build new triggers as record-triggered Flows with the same Outbound Message action. The text goes out from the record owner's direct Kixie number with property tokens like first name filled in. It requires a Kixie Professional plan and a Zapier Starter plan or higher.

As completed SMS Tasks on the matching Lead or Contact. Kixie matches by phone number, logs the message as activity on the record, and syncs the same activity to the associated Account and the most recent Opportunity. The conversation sits on the record timeline next to calls and emails instead of on a rep's personal phone.

It is a ten-minute admin step that makes SMS a first-class activity type. Your Salesforce admin opens Setup, goes to the Task object's Type field, and adds the picklist values Incoming SMS and Outgoing SMS, or a single SMS value if you prefer one. With those values in place, every Kixie text logs as a properly typed Task, which means you can filter, report, and build Flows on texting activity specifically.

Yes. Because Kixie logs texts as standard completed Tasks with an SMS type, they flow into the same activity reports and dashboards you already run on calls and emails. That differs from SMS Messaging for Sales, whose messages Salesforce says don't support activity reporting. You can report texts per rep, per Lead source, or per Opportunity stage, and the roll-up to Account and Opportunity carries the texting history too.

Yes, and Kixie respects the difference. Texts log to whichever object matches the phone number. When both a Lead and a Contact share a number, Kixie syncs to the last-referenced record and prefers the Contact. And when a Lead converts, the texting history is preserved on the resulting Contact, so nothing about the early conversation is lost.

Yes. Reps can select records from a Lead or Contact list view and send a templated text with personalization tokens to each one, from the rep's own Kixie number, with every message logging back to its own record. It is built for targeted plays like following up a webinar list, not for broadcast marketing; carrier rules and deliverability both reward keeping list sends personal and relevant.

Kixie can create a Salesforce Lead automatically for any number that does not match an existing Lead or Contact, and all subsequent activity syncs to that Lead. The history is maintained when the Lead is later converted to a Contact. The behavior is a toggle under Manage, then Account, then Create Contacts in the Kixie dashboard, so you can turn it off if your org prefers manual record creation.

Texting US numbers from US numbers requires registering your business under the A2P 10DLC carrier standard, and Kixie supports registering the numbers your reps call and text from. Carrier rules require honoring opt-out keywords like STOP, and Kixie tracks opt-out status so reps and automations do not message people who have withdrawn consent. Your team remains responsible for collecting proper consent before the first message, so fold texting into the same consent capture you use for calls.

Kixie's native integration requires Salesforce Professional edition or higher with API access, and connecting is a one-time authorization with no middleware. Rep texting and SMS Task logging work from there once the Task Type values are added. The Zapier-brokered auto-SMS recipe specifically requires a Kixie Professional level account plus a Zapier Starter plan or higher.