Salesforce has messaging built in for Service Cloud, Marketing Cloud which sends campaign texts, and AppExchange apps add texting to any record. So, which one you use depends on what you’re trying to do.
Are you sending one message to one person? The same message to a thousand? Something that fires when a record changes? Pick the situation, and the method follows.
Pick Your Situation
You want to… | Use | Detail |
Text one customer from their record | Messaging or an app | Method 1, below |
Send the same message to many people | A bulk send | Our bulk SMS guide |
Text automatically when something happens | Flow | Our automation guide |
Run a marketing campaign | Marketing Cloud | |
Build it yourself | Apex and a provider API | Method 5, below |
Before You Send Anything
Four things have to be true, whichever method you use.
- You have a sending number. In the US, that’s a registered 10-digit number or an approved short code. See our SMS code types guide for how to choose.
- The person has opted in. Record it on the Lead or Contact, not in someone’s memory.
- The phone number is clean. Use one format, such as +1 555 123 4567. A missing country code is a classic cause of “not delivered.”
- Someone owns the replies. A text that invites a reply and then lands on nobody’s desk is worse than not texting.
Method 1: Text One Person From Their Record
This is the everyday case: a rep opens a Lead, Contact or Case and sends a message.
With Salesforce’s own messaging. Salesforce’s SMS channel documentation says reps can answer text inquiries and start messaging sessions with customers who’ve opted in. Setup requires configuring Enhanced Messaging channels, as legacy “standard” SMS channels face full retirement on June 30, 2027. The outbound number must be mapped cleanly, and every operational user requires a valid Messaging User permission set license.
With an AppExchange app. Most apps add a message panel to the record page. The steps are usually the same: open the record, pick the channel, write or choose a template, send. Replies show up in the same thread and are logged on the record.
Do I Need A Third-Party App?
This is a common question. There are three honest answers.
- You don’t need an app. Salesforce’s own Messaging sends SMS, and you can link a number you already own or request one from Salesforce. It comes with its own licensing, covered in our pricing guide.
- You don’t need Marketing Cloud. It’s built for campaigns and journeys. For one-to-one and transactional texts, Service Cloud messaging or an app can do the job.
- You can’t avoid a carrier network. Someone, whether that’s Salesforce, an app vendor or a provider such as Twilio, has to deliver the text. The question is who you want to deal with.
Method 2, 3 and 4: Bulk, Automated and Marketing
These have their own guides. In short: bulk sends pick an audience from a list view, campaign or report. Automated sends use a Flow that fires on a record change. Marketing Cloud sends campaign messages through MobileConnect. If you’re not sure which you need, our SMS integration guide compares the routes.
Method 5: Build It Yourself
If you have a developer, you can call a provider’s API from Apex. It works, and it gives you control. But you’ll also build everything an app would have given you: logging each message to the right record, handling carrier webhooks safely using Platform Events to avoid apex concurrency crashes during high-volume reply surges, writing custom string matchers for mandatory STOP keywords, and maintaining complex transaction retry logs.
What About WhatsApp?
Sending a WhatsApp message from Salesforce follows the same pattern with two differences. Messages you start need pre-approved templates, and Meta charges per delivered message. Replies within the customer service window are simpler. Everything is in our WhatsApp and Salesforce guide.
What to Write
A good text answers three questions fast: who’s this, what do you want, and how do I opt out.
“Acme Dental: Hi Priya, your cleaning is Thursday at 2:30 PM. Reply C to confirm or R to reschedule. Reply STOP to opt out. Msg & data rates may apply.”
Identify yourself first, make one request, include an easy opt-out, and keep it short. Our compliance guide covers the rules in more detail.
When A Text Doesn’t Send
Check these in order:
- Number format. Missing country code, extra characters, or a landline.
- Sender status. An unregistered or inactive number gets blocked. Short codes can take weeks to provision.
- Consent record. Many setups won’t send to someone with no opt-in on file. Salesforce’s own flows only message customers with a messaging user record.
- Permissions. The user needs the Messaging User permission set license on Salesforce’s own messaging, or the app’s permission set on an app.
- Templates. For WhatsApp, an unapproved template won’t send.
Where Message Blink Fits
Message Blink functions as your native AppExchange execution console right inside Sales and Service Cloud records which was built to bypass complex custom apex webhook tracking, the app routes messages asynchronously to protect against database row-locking errors, isolates vendor authentication using encrypted Named Credentials, and automatically mirrors incoming carrier STOP commands to your standard opt-out checkboxes. You can know more if you:-
