“10,000+ Appointments Booked Across AI-Powered Campaigns”-Get the System
Skip to content
MediaBloom
Blog
Insights 12 min readNov 18, 2026

Salesforce SMS Integration: Options, Setup and Rules

How to send SMS from Salesforce: native options, setup steps, U.S. sender and consent rules, and how to automate text follow-up so leads get answered fast.

JJ
John Jahshan
Founder and CEO, MediaBloom
Salesforce SMS Integration: Options, Setup and Rules

Watercolor frame for Salesforce SMS integration

Salesforce can send and receive text messages, but the texting only works as well as the follow-up process behind it. You pick a messaging channel, register a U.S. sender number, give users access, and then build the automation that decides who gets a text, when, and what happens when they reply. Most owners get the first three right and lose leads on the fourth. We build and run that follow-up for clients: AI agents that text, call and book appointments around the clock, connected to the CRM you already use.

This guide covers what Salesforce offers natively, the two ways to add SMS, setup, cost, U.S. consent rules, and where the process usually leaks.

Mediabloom
mediabloom.us
Turn Salesforce Texts Into Booked Appointments
MediaBloom connects AI texting and calling with CRM follow-up, helping businesses respond to leads and book appointments around the clock.
Book a free strategy call

TL;DR

  • Salesforce supports SMS natively through messaging channels, and a Send Text action is available in its mobile app for Leads, Contacts and Accounts.
  • In the U.S., messages go out from a short code or a 10-digit long code (10DLC), and your terms and opt-in flow must match carrier expectations.
  • Standard SMS channels were retired on February 14, 2026, so any setup should use Enhanced SMS channels.
  • Texting inside the CRM does not answer leads for you. Speed, qualification and booking need automation on top.
  • We deliver that layer done-for-you: the AI agents, the CRM workflows and the appointment setting, so no lead sits waiting.

Table of Contents

Does Salesforce have SMS built in?

Yes. Salesforce’s own documentation treats SMS as a messaging channel. Its SMS terminology page says a text can be started by a service representative, a campaign, a chatbot or an application, and that automated outbound messages can follow a change to a Salesforce record.

That page also separates two kinds of traffic you will see in every setup guide:

  • Person-to-person (P2P): a rep texts a customer one to one.
  • Application-to-person (A2P): software sends the message, as with campaigns, reminders and chatbots. It is typically higher volume and outbound.

The difference matters because carriers treat the two differently. A rep texting a few leads a day and a system texting every new web inquiry are not the same thing in registration terms.

Salesforce’s Digital Engagement guide lists the building blocks: SMS channels, flows for automatic notifications, automated responses, quick text replies, and links from messaging records to cases or contacts.

For marketing, Marketing Cloud Next supports SMS, MMS, RCS and WhatsApp. Salesforce notes that setup can involve account validation, sending-code requests or other registration steps.

What you can do with SMS inside Salesforce

The practical uses for a local service business or law firm are narrow and valuable:

  • Text a new lead within seconds of a form fill.
  • Send appointment confirmations and reminders.
  • Reply to inbound texts from a rep or an agent queue.
  • Run a reactivation campaign to older contacts.
  • Log the conversation against the lead, contact or case.

On mobile, Salesforce documents a Send Text action for Accounts, Contacts, Leads and Person Accounts. It needs a properly formatted phone number and an administrator to add the quick action. The same page warns that messages sent this way are not currently saved in the record’s activity history, and that the action does not work on iPad.

That detail is the one to plan around. If your reps text from a phone action and nothing lands on the lead record, your pipeline reports will miss real conversations. Use a channel-based setup for anything you need to track.

The two ways to add SMS to Salesforce

Option 1: Salesforce’s own messaging channels

This is the native route. Salesforce describes a guided messaging setup in Lightning Experience that automatically enables Omni-Channel and walks you through user access, per its Digital Engagement guide. Omni-Channel routes service conversations to the right person, while Flow handles marketing messages on SMS and RCS channels, according to Salesforce’s Unified Messaging documentation.

One phone number or RCS agent can carry both one-way marketing promotions and two-way support conversations. For a small team, that means a single number for reminders and replies.

A warning from that same documentation set: Standard SMS channels were retired on February 14, 2026, and organizations must use Enhanced SMS channels to avoid interruption. If someone set up texting years ago and it “just stopped,” check the channel type first.

Option 2: A connected messaging layer

The second route is to keep Salesforce as the system of record and connect an external messaging and automation layer through an app or API. The messages are sent and answered outside the CRM, and the conversation, outcome and appointment are written back to the lead.

This is the route that makes sense when texting is only one part of the job. If you also want voice calls, instant response, qualification questions, appointment booking and reactivation of old leads, a single SMS field in the CRM is not enough. You need an agent that does the work and a CRM that records it. Our platform connects to CRMs across 600+ platforms, and our guide to integrating AI agents with Salesforce CRM walks through that pattern.

How to set up SMS in Salesforce, step by step

Whether you go native or connected, the sequence is the same. Here is what each step takes and where it tends to go wrong.

1. Choose your sender type

In the U.S., Salesforce’s SMS guide says the supported carrier-approved sender types are short codes and 10-digit long codes (10DLCs).

  • Short code: a 4 to 8 digit number. Salesforce’s terminology page says U.S. short codes can support 10 to 500 messages per second, subject to carrier approval and country limits. Built for high volume.
  • 10DLC: an ordinary-looking local number registered with carriers. A common fit for local service businesses that want texts to look like they come from a real local line.

Where it goes wrong: choosing a short code for a team that sends a few hundred messages a month, then waiting on approvals it did not need.

2. Register and get approved

Carriers approve the sender and the use case. Salesforce’s Trailhead module says U.S. and Canadian private short codes require professional services, and that Salesforce covers the first year of the code lease and waives activation fees. It tells customers to confirm later fees with their account executive. See the Trailhead SMS code module.

Where it goes wrong: submitting a vague use case. Describe exactly what you send, to whom, and how they opted in.

3. Create the channel and assign users

An admin creates the messaging channel, connects the number, and assigns permissions so reps can see and reply to conversations. For mobile texting, the admin also adds the Send Text quick action to the page layouts.

Where it goes wrong: giving access to everyone and routing nothing. Decide who owns replies before launch, because an unanswered inbound text is a lost lead.

4. Clean the phone data

Salesforce’s mobile action requires a formatted phone number. Standardize numbers on import and on web forms so the text actually sends. Check that mobile numbers are flagged separately from landlines.

5. Build the automations

This is where speed is won. A Flow can fire when a lead is created, when a status changes or when an appointment is booked. If you want a worked example of the logic, this piece on automating CRM workflows with Flow shows how data changes can trigger notifications and campaign messages.

Typical triggers for our readers:

  • New web lead: text within a minute, ask one qualifying question.
  • No reply after the first text: second text, then a call attempt.
  • Quote or estimate sent: reminder two days later.
  • Appointment booked: confirmation now, reminder the day before and the morning of.
  • Dormant lead: a reactivation text sequence.

6. Test every path

Send to your own phone. Reply STOP. Reply HELP. Confirm that each reply is logged on the record and that the opt-out actually suppresses future sends.

Business owner testing a text message on her phone

Our team handles steps 3 to 6 for clients as part of CRM optimization: pipelines, automations and follow-up set up so each lead gets a defined next touch. Campaigns go live in days, and you are not left stitching the pieces together between vendors.

What it costs

Salesforce lists Marketing Cloud Next SMS at $2 per 1,000 sends for Growth and Advanced editions, in USD and billed annually. That is the messaging add-on only. It does not include your Salesforce licenses, number registration support, someone to build the flows, or anyone to reply.

Before you budget, add up four lines:

  1. Salesforce edition and user licenses.
  2. Messaging cost per send.
  3. Number or short code fees after any included first period.
  4. The hours to build, test and maintain automations and answer replies.

The fourth line is the one most owners leave out. Sending is cheap. Response is the expensive part.

Salesforce also recommends reviewing message length, segmentation, daily limits and industry-specific considerations before you turn messaging on, per its Digital Engagement guide. A long message splits into several segments, so keep texts short.

Texting leads in the U.S. is regulated, and your messaging setup should reflect that from day one. This section covers how Salesforce describes the requirements. It is not legal advice, and your attorney should confirm what applies to your business and your market.

From Salesforce’s U.S. SMS guide:

  • A campaign’s call to action should identify the program and message frequency, and link to terms, privacy and help information.
  • Terms and conditions should explain how opt-in works and include STOP and HELP instructions.
  • A web-form checkbox for text consent cannot be pre-checked.

On the legal side, one industry explainer says marketing texts require prior express written consent and that senders should keep a record of how, when and where consent was obtained. Treat it as a practical prompt: store the consent source and timestamp on the lead record in Salesforce, so you can find it in seconds.

Opt-out handling is a workflow, not a promise. When a lead replies STOP, the system must suppress every future text, across every campaign and every rep. Rules on consent revocation have been changing, so ask your counsel which standards apply to you now.

Where Salesforce SMS leaks leads

A working integration still loses revenue in five common ways:

  • Slow first touch. The text is queued behind a batch or waits for a rep to click.
  • One text and silence. No second attempt, no call, no change of channel.
  • Unowned replies. Inbound texts land in a queue nobody watches after hours.
  • No booking path. The lead answers, and the rep still has to trade six messages to find a time.
  • Unlogged conversations. Texts sent outside the record never show in reports, so you cannot see what works.

For a personal injury firm, an unanswered intake text at 9 p.m. can be a signed case that goes to the next firm. For a roofer or HVAC contractor, the first company to reach a homeowner often wins the estimate. That is why Speed to Lead AI is built around instant contact and appointment booking, not just message sending. Our AI appointment setter qualifies and books so your team shows up to calendar slots instead of chasing.

Older contacts are a second source. A text and voice sequence through Reactivation AI re-engages leads that already sit in your database, with replies and bookings written back to the CRM.

If you also run on GoHighLevel, the same logic applies. Our CRM automation and GoHighLevel setup covers pipelines, automations and follow-up so no lead slips through, and our guide to HubSpot SMS integration shows the same pattern on another CRM.

What to look for before you commit

Use these criteria for any SMS approach, native or connected:

Question Why it matters
Does every message log to the lead record? Reporting and handoffs depend on it.
Can it text and call in one sequence? Many leads answer a call faster than a text.
Does it book appointments directly? Fewer messages between inquiry and calendar slot.
Who builds and maintains the flows? Automations drift as your process changes.
How are opt-outs and consent stored? You need one suppression list across all senders.
Who answers after hours? Most inquiries do not arrive at 10 a.m. on a weekday.

Our perspective

We think most businesses ask the wrong question. They ask which app sends texts from Salesforce. The better question is who responds to the lead in the first minute, and what happens if the lead does not answer.

A text field in a CRM is a tool. It does not qualify anyone, book anything or follow up on day three. That is why we build it done-for-you: the AI agents, the CRM workflows and the people who book appointments, from one partner. Nothing falls between vendors, and no lead waits for someone to log in.

Our work with 300+ businesses since 2022 has been built on that idea. Speed, persistence and a clean handoff to your calendar beat a clever template every time.

MediaBloom

How we deliver it

We are a Tampa, Florida digital marketing and AI agency, and we run AI systems that call, text and book appointments 24/7, connected to your CRM. For Salesforce users, that means the lead is contacted, qualified and booked, and the record updates without your team lifting a finger. Our AI voice agents cover inbound and outbound calls, and Customer Service AI handles routine questions. Prices are quoted after a demo, since each build depends on your CRM and volume.

Mediabloom

If your leads are coming in but bookings are not, see how MediaBloom’s AI voice automation works and get a demo.

FAQ

Can you send SMS from Salesforce without an app?

Yes. Salesforce offers native messaging channels, and its mobile app has a Send Text action for Leads, Contacts and Accounts once an administrator adds it. The mobile action does not currently save messages to activity history, so use a channel-based setup if you need every conversation logged.

What is the difference between a short code and a 10DLC?

Both are carrier-approved U.S. sender types supported by Salesforce. A short code is a 4 to 8 digit number built for high-volume sending, while a 10DLC is a registered 10-digit local number. Smaller local businesses often fit the 10DLC better.

Is SMS being phased out in Salesforce?

No, but the channel type changed. Salesforce retired Standard SMS channels on February 14, 2026, and organizations need Enhanced SMS channels to keep texting without interruption. If texting stopped working, check which channel type you are using.

Can SMS follow-up be automated in Salesforce?

Yes. Salesforce says automated outbound messages can follow a record change, and Flow handles marketing messages on SMS channels. Triggers like new lead, status change and booked appointment are the usual starting points. We build and maintain these sequences for clients, along with the AI agents that reply and book.

Mediabloom
Discuss Your Salesforce Follow-Up
Tell us where leads stall in your texting or CRM workflow, and we can discuss how MediaBloom’s AI agents and follow-up systems may help.

Sources

About the writer
JJ

John Jahshan

Founder and CEO, MediaBloom
Fort Myers, Florida Writes on AI voice agents, Speed-to-lead automation

John Jahshan is the founder and CEO of MediaBloom. He works directly with agencies, operators, and enterprise teams to design and deploy AI revenue systems — voice agents, speed-to-lead automation, reactivation campaigns, and ads management — that turn attention into booked appointments and signed deals. He writes about the operator playbooks, engineering decisions, and partnership models behind the systems MediaBloom ships for clients.

AI voice agentsSpeed-to-lead automationRevenue operationsPartnership programs
Newsletter

Get the MediaBloom newsletter.

One email per week. Research, launches, and operator playbooks. Zero fluff.

Ready to see MediaBloom in action?

Talk to our team about deploying AI across your funnel.