Contact Us

UK +44 (734) 008 7301

USA +1 (737) 395 8587

Contact Us

UK +44 (734) 008 7301

USA +1 (737) 395 8587

Salesforce SMS Marketing: How It Works in Marketing Cloud, and When to Send From the CRM

May 15, 2025

Get your 100 Free SMS Credits for your Salesforce Org

salesforce-sms-marketing

“Salesforce SMS marketing” means two different engines, and mixing them up is the most common reason projects stall.

One is Marketing Cloud. It’s built around campaigns, audiences and journeys. The other is the CRM side, where texts go out from Lead, Contact and Case records through Flow or an app. They use different data, different sending numbers and different billing. This guide covers how the Marketing Cloud route is built, what its options include, and when the CRM route is the simpler call.

Which Path Fits?

Compare by

Marketing Cloud Engagement (MobileConnect)

Marketing Cloud Growth (Agentforce) 

CRM-side (Flow or an app)

Built around

Campaigns, audiences, Journey Builder

Newer Agentforce Marketing platform

Records in Sales and Service Cloud

Best for

High-volume campaigns to defined audiences

RCS and the newer content tools

Follow-ups and one-to-one conversations tied to a record

Rich media

MMS in the US and Canada

MMS, plus RCS

Depends on the app

Salesforce’s own guide to sending SMS in the US lists short codes and 10DLC as the supported sender types. Provisioning takes about 10 to 12 weeks for a short code and 2 to 5 business days for 10DLC. We explain the difference in our SMS code types guide.

How A Marketing Cloud SMS Campaign Gets Built

  1. Get a sending number. You can’t buy a short code inside the Marketing Cloud interface. Salesforce provisions codes through approved partners. Allow the weeks mentioned above.
  2. Describe your program. Carriers review a Campaign Application Form (CAF). It covers your use case, where people opt in, your keywords, and links to your SMS terms and privacy policy.
  3. Set up your keywords. You need an opt-in keyword, plus working STOP and HELP replies. The same rule covers every message: say who you are, how often you’ll text, that rates may apply, and how to opt out. A sample: “Acme Alerts: Your order shipped. Msg & data rates may apply. Reply HELP for help, STOP to cancel.”
  4. Build your audience. Pick a data extension or list of subscribers who’ve opted in.
  5. Create the message. In MobileConnect, you choose the send method: schedule it, trigger it through the API, or run it from Automation Studio. SMS messages for journeys are created directly in Journey Builder. If you pick “timezone specified by contact,” Salesforce uses the contact’s MobileConnect demographics.
  6. Test, then send. Send to a few real phones on different carriers before the full audience.

Consent and opt-out rules sit behind every step. Our compliance guide covers them.

An SMS Drip Campaign That Doesn’t Annoy People

A drip is a short sequence where each text depends on what happened to the last one. Here’s a simple shape for a trial sign-up:

  1. Day 0: a welcome text confirming the opt-in and the frequency you promised.
  2. Day 2: one useful tip tied to what they signed up for.
  3. Day 5: a decision split. Did they click? If yes, send a next-step offer. If not, send a gentle reminder.
  4. Day 9: a final check-in, then stop.

Two rules keep it healthy. Never send more often than the frequency you promised at opt-in. And let any reply of STOP end the sequence immediately, not at the end of the day.

Track Results With Data Views

Marketing Cloud stores SMS activity in system tables called data views. Some log events: _SMSMessageTracking records messages and _SMSSubscriptionLog records opt-ins and opt-outs. Others show the current state of a number: _MobileAddress and _UndeliverableSMS.

One caution. Documentation from the Marketing Cloud community enforces a hard 6-month (180-day) rolling retention window on _SMSMessageTracking. To prevent your analytics from zeroing out after 180 days, you must automate a nightly query to move this data into a custom Data Extension for long-term storage. Billing matters here too. Marketing Cloud counts outbound texts whether they’re delivered or not, which is one more reason to watch undeliverable numbers. We cover cost in our Salesforce SMS pricing guide.

MMS and RCS

MMS lets you send images and other media. Salesforce’s FAQ says MMS is supported in the US and Canada. Enabling it on an existing code means resubmitting the CAF through your approved partner. One Salesforce help page says US only, so check the page for your product before you plan a Canadian send.

RCS is the richer, branded option, with cards, carousels and reply buttons. Salesforce introduced it in Marketing Cloud Growth and Advanced with the Summer ’26 release. Its practitioner guide lists the US, Mexico, Brazil, France, Germany, the UK and India as available, with more markets coming. It also describes a fallback: if a recipient’s device can’t receive RCS, an SMS goes out instead.

WhatsApp From Marketing Cloud

If you’re running journeys, you can add WhatsApp as a channel. In Journey Builder, a WhatsApp display name and phone number are called a channel. Salesforce’s docs say channels in Marketing Cloud Engagement and in Service Cloud need separate WhatsApp business accounts, so don’t plan on one number covering both. If you need a single channel for marketing and service, Salesforce’s unified WhatsApp channel is built for that, with its own edition requirements.

Meta’s per-message fees, templates and the 24-hour window apply here as they do everywhere. Our WhatsApp and Salesforce guide covers them.

When Sending From The CRM Is The Simpler Call

Marketing Cloud shines for audience-wide campaigns. It’s heavier for a rep who just needs to follow up with a lead, or a support team replying to a customer. If your audience already lives on Lead, Contact and Case records, and replies need to land with the person who owns the record, sending from the CRM can be simpler.

Whichever tool you use, ask four things:

  • Can it send from the number type you need, and who handles carrier approval?
  • Does every text, reply and delivery status attach to the right record?
  • Are STOP and HELP handled, with the opt-out stored on the record?
  • Can a Flow trigger the send and react to replies?

Where Message Blink Fits

Message Blink is engineered exclusively for the core CRM-side route inside Sales and Service Cloud, which makes it an ideal execution layer for Agentforce Sales and Service actions. It does not run natively inside Marketing Cloud Engagement journey data extensions. Instead, it uses Named Credentials to secure your tokens, sends CRM texts asynchronously to avoid database crashes, and automatically updates lead records the second a carrier STOP command arrives.

If you want to test it in a sandbox, you can:

Book a Free Demo | View Pricing | Install on AppExchange

Post Tags :

Share :

Table of Content

Frequently Asked Questions