How to Use Marketing Cloud MobileConnect: SMS Codes, Keywords, Journeys and Compliance
MobileConnect is the SMS tool inside Salesforce Marketing Cloud Engagement. This guide covers how it delivers messages, which sender codes to buy for each country, how keywords and opt-ins work, how to send from Journey Builder, Automation Studio and the API, and the 2025 US consent rules your program has to follow.
Key Takeaways
- Marketing Cloud MobileConnect is the SMS and MMS tool in Mobile Studio, part of Salesforce Marketing Cloud Engagement. It sends, receives and tracks text messages, manages keywords and handles opt-ins and opt-outs.
- Your sender code decides almost everything else: short codes are two-way and fast but take 10 to 12 weeks in the US, 10DLC long codes take 1 to 4 weeks, and sender names are one-way and blocked in the US and Canada.
- Salesforce does not support toll-free numbers for SMS to the United States, so plan on a short code or 10DLC there.
- Email consent is not SMS consent. Collect a separate opt-in, keep STOP and HELP working, and honour opt-outs fast: US rules in force since April 11, 2025 allow 10 business days at most.
- Every 160-character segment is billed, even when parts are joined. One US text uses 10 super messages from your Marketing Cloud allowance.
What is Marketing Cloud MobileConnect? MobileConnect is the SMS application in Salesforce Marketing Cloud Engagement. It sits in Mobile Studio next to MobilePush and GroupConnect. Marketers use it to send outbound text and MMS campaigns, reply automatically to incoming texts, run keyword opt-ins, surveys and data capture, and track delivery and clicks. Journey Builder, Automation Studio and the REST API can all trigger its messages.
We first published this guide in 2024. This version is rebuilt from Salesforce Help, Salesforce developer documentation and Trailhead, plus guidance from the FCC, CTIA, The Campaign Registry and the UK ICO, all checked in October 2026. It corrects figures the earlier version carried without a source, and adds country-by-country code timelines, the 2025 US consent rules, message-length billing and reporting. It is written for marketing operations teams and Marketing Cloud admins at growing and mid-market companies adding SMS to their Marketing Cloud programs.
What Is Marketing Cloud MobileConnect and How Does It Deliver an SMS?
MobileConnect builds and sends the message, but carriers deliver it. Marketing Cloud passes each SMS to an aggregator, a messaging company Salesforce has a relationship with in that market. The aggregator hands it to the recipient's mobile carrier, and the carrier delivers it to the phone. Replies travel back the same way, which is how keywords and two-way conversations reach MobileConnect.
1. Marketing Cloud
MobileConnect personalizes the message from your contact data, applies send windows and throttling, and releases it through the code you chose.
2. Aggregator
The messaging partner routes it to the right carrier. Salesforce counts a market as supported only where it has an established aggregator relationship.
3. Carrier
The mobile network delivers the text, applies its own filtering and registration rules, and returns a delivery receipt when it can.
4. Subscriber
The contact receives the message and can reply with a keyword, an answer or STOP, which flows back to MobileConnect.
This chain explains two things teams often learn late. First, a number or sender name has to be approved by carriers before you can send, so codes take weeks to provision. Second, delivery is reported by carriers, not by Marketing Cloud, so receipts can be slow or missing (Section 09). Salesforce describes MobileConnect in its MobileConnect documentation and defines supported markets in its supported markets article: at least 70% deliverability and reach of at least 10% of the country's population.
What Kinds of SMS Can You Send with MobileConnect?
MobileConnect offers ten message templates, from one-way outbound texts to automated replies, opt-in flows, surveys and data capture. You pick a template when you create a message, and it decides whether the message is pushed to a list or triggered by a keyword someone texts in. Journey Builder SMS messages are an exception: you now create them inside Journey Builder itself.
| Template | What it does | Typical use |
|---|---|---|
| Outbound Message | Sends an SMS to a list or data extension | Order and appointment updates, offers, service alerts |
| Outbound Media | Sends an MMS with an image or media file | Visual offers; check your code supports MMS (US, and Canada per Salesforce) |
| Mobile Opt-in | Invites people to subscribe to texts, with single, double or age-confirmed opt-in | Keyword sign-ups such as "Text JOIN to…" |
| Email Opt-in / Send Email | Collects an email address by text, or triggers an email | Growing the email list from SMS, sending a guide on request |
| Vote/Survey | Records answers texted in by subscribers | Post-purchase feedback, event polls |
| Text Response / Media Response | Replies automatically to an incoming keyword with SMS or MMS | Store hours, help menus, "reply 1 or 2" menus |
| Info Capture | Stores replies as attributes on the contact record | Progressive profiling: birthday, postcode, preferences |
| SMS Keyword Opt-out | Keyword-based opt-out for long codes | Australian contacts only |
The full list and settings are in Salesforce's article on creating messages in MobileConnect. Two details matter in practice: a new message takes several minutes to activate, and "Perform Test" switches the keyword on for 60 minutes so you can test it from a real phone.
Four use cases that work well
- Transactional updates. Order and registration confirmations, appointment reminders and delivery tracking. They need little personalization and customers expect them, so they are the easiest place to start.
- Security messages. One-time passcodes, login alerts and password-expiry reminders. Send these from a dedicated code: some countries do not allow one code to carry both transactional and marketing traffic.
- Marketing campaigns. Offers, re-engagement of dormant customers and links to landing pages. These need the strongest consent and the most care with frequency.
- Progressive profiling. Info Capture asks one question at a time and writes each answer to the contact record, skipping what you already know. Our guide to progressive profiling in Salesforce Marketing Cloud covers the design across channels.

Short Code, Long Code or Sender Name: Which Should You Use?
Use a short code for high-volume, two-way marketing where it is available, a local long code such as US 10DLC for conversational or lower-volume programs, and a sender name only for one-way alerts in countries that allow it. The choice is made per country, because carriers and regulators decide what each market accepts and how long approval takes.
| Sender type | What it is | Replies | Best for |
|---|---|---|---|
| Short code | 5 or 6 digits, approved and provisioned by carriers | Two-way | High-volume promotions and keyword campaigns; mandatory in some countries, such as France |
| Local long code (US/Canada 10DLC) | A standard 10 to 14 digit phone number | Two-way | Transactional alerts, support and conversations; some countries restrict long codes to transactional use |
| Alphanumeric sender name | Your brand name, 3 to 11 characters, preregistered | One-way | Alerts and promotions in Europe and Asia; you must give another way to opt out |
| International long code | A number from another country | No reply support | Avoid where possible: higher cost, inconsistent delivery, and carriers often overwrite the sender ID |
Source: Salesforce's guide to understanding SMS codes and its advice on aligning codes with campaigns. Earlier advice that long codes are one-way only, or that each code type has a fixed messages-per-second rate, does not appear in Salesforce's documentation, so plan throughput with your account team rather than a rule of thumb.
How long codes take in the main markets
Salesforce publishes a sending guide per country. These are its estimates for four common markets. Holidays and carrier network freezes add delay, so start the paperwork before you build anything.
| Country | Short code | Local long code | Sender name |
|---|---|---|---|
| United States | Supported · 10–12 weeks | 10DLC supported · 1–4 weeks | Not supported (blocked); toll-free not supported either |
| Canada | Supported · 10–12 weeks | 10DLC supported · 1–4 weeks | Not supported (blocked) |
| United Kingdom | Supported · 10 weeks | Supported · 1 week | Supported, one-way · 1 week |
| France | Supported · 12 weeks | Not supported | Supported, one-way · 1 week, on the protected sender list |
Sources: Salesforce's sending guides for the United States, Canada, the United Kingdom and France, plus the full list of country guides. In the US, Marketing Cloud Engagement customers register short codes through a Mobile Approved Partner; Marketing Cloud Next offers self-service registration. A 10DLC number needs a brand request, a campaign request and a code request, and the brand is vetted before a number is allocated.
How Do Keywords, Opt-Ins and Opt-Outs Work in MobileConnect?
A keyword is a word people text to your code to trigger an action, such as joining a list or getting a reply. Keywords are created per code. Every account needs a working HELP keyword, which an admin must create, and STOP, QUIT, CANCEL, END and UNSUBSCRIBE are recognized by default as requests to unsubscribe from everything. HELP and STOP cannot be edited and must stay active.
Good keywords. Short, memorable and tied to your brand or campaign, used once per campaign, and forgiving of typos. Trailhead notes keywords are not case sensitive, so JOIN, Join and join behave the same. Create common misspellings as extra keywords if people text them.
Opt-out traps. A sender name cannot receive replies, so STOP does not work from it: tell people how else to unsubscribe in the message. And under US rules, replies such as "revoke" and "opt out" also count as a stop request, so make sure they are handled, for example as custom STOP keywords.
Opt-in comes in three forms in the Mobile Opt-in template: single opt-in, double opt-in (the subscriber texts again to confirm) and double opt-in with age confirmation. When people subscribe on a web form or in an app rather than by texting, Salesforce's MobileConnect API guide points to CTIA and MMA practice of double opt-in, and its QueueMO call simulates the inbound text so the person receives one confirmation message. Until they reply, their status stays "In Progress" and they receive nothing.
Salesforce's getting started guide lists the default keywords. In the US, Marketing Cloud also opts out deactivated and ported numbers automatically each day, using carriers' deactivation files for short codes, as described in its automatic opt-outs article.
How Do You Set Up MobileConnect, Step by Step?
Start with markets and use cases, order the codes, prepare contact data and consent, configure keywords and templates, then test from real phones before you send at scale. The code lead time is the critical path, so the commercial and registration steps should run while the data and content work happens in parallel.
The contact fields are listed in the MobileConnect Demographics reference, and account settings in administering your MobileConnect account. For US and Canadian programs, Trailhead's unit on getting your SMS codes says a launch with a services partner typically takes 8 to 12 weeks, covering forms, provisioning, aggregator approval and carrier testing.
How Do You Send SMS from Journey Builder, Automation Studio or the API?
Use Journey Builder for SMS that is one step in a customer journey, Automation Studio for scheduled batch sends and data jobs, and the REST API for real-time messages triggered by another system, such as an order or login. All three send through the same MobileConnect account, codes and subscription rules.
| Method | How it works | Use it for |
|---|---|---|
| Journey Builder | The SMS activity appears once MobileConnect, Content Builder and Journey Builder are enabled; you create the message inside the journey | Welcome series, abandoned-cart reminders, mixed email and SMS journeys |
| Automation Studio | Activities to import mobile contacts, refresh filtered lists and send SMS to contacts | Recurring batch sends and nightly list updates |
| Schedule | Send now or at a future or recurring time from MobileConnect | One-off broadcasts and fixed reminders |
| REST API | messageContact sends to up to 250 numbers or subscribers per call; messageList sends to a MobileConnect list; QueueMO replicates an inbound text | Passcodes, order and shipping updates, web-form opt-ins |
Salesforce documents each path: MobileConnect with Journey Builder, MobileConnect with Automation Studio and the messageContact send reference. In Journey Builder, personalization first uses the journey's entry data and falls back to the MobileConnect contact record when a value is empty. Through the API, per-subscriber attributes become replacement strings in AMPscript, and a blackout window is honoured only when the contact's UTC offset is supplied. Our Journey Builder services page covers how we design multichannel journeys around these rules.
How Long Can an SMS Be, and How Do Links and Personalization Work?
A standard SMS holds 160 characters. One emoji or other non-GSM character drops the whole message to 70. Longer texts are split into parts, and each part is billed. Joined messages, which arrive as one text, carry 153 characters per part, or 67 for non-GSM text, and are still charged as separate sends.
| Character set | Single message | Per part when joined |
|---|---|---|
| GSM (standard Latin letters, digits, common symbols) | 160 characters | 153 characters |
| Unicode (emoji, accented or non-Latin scripts) | 70 characters | 67 characters |
Sources: Salesforce on character counts and message concatenation. Joining is available in the US but not in every market, and personalization can push a message over the limit, so test with the longest realistic values. Salesforce's best practice is to keep messages under 160 characters.
Links and click tracking
- Use the Marketing Cloud link shortener to track total and unique clicks. It is switched on automatically on Hyperforce, and each business unit can use one custom domain for short links. Bitly is the alternative, with total clicks only.
- Short links expire after 90 days, after which subscribers see a page-not-found error. Do not put shortened links in messages people will keep for months.
- Dynamic links need AMPscript care. Put AMPscript only in the query string, or wrap a fully dynamic URL in RedirectTo(). Some Android apps preview links automatically, which can inflate click counts.
Details are in Salesforce's link tracking article. For personalization logic beyond merge fields, our comparison of AMPscript and SSJS in Marketing Cloud explains which language to use where.
What SMS Compliance Rules Apply to MobileConnect Campaigns?
Get explicit consent for SMS before you send marketing texts, tell people what they are signing up for, make STOP and HELP work, honour opt-outs quickly, and keep records. MobileConnect gives you the tools, but compliance with each country's law is your responsibility. Salesforce's country guides are explicitly not legal advice, so involve your legal team.
Consent, revocation in 10 business days, registered senders
Since April 11, 2025, under the FCC's TCPA consent revocation rules, people can revoke consent in any reasonable way, and a reply of stop, quit, end, revoke, opt out, cancel or unsubscribe always counts. You must honour it within 10 business days and may send one confirmation text. The FCC's effective-date notice confirms the date. The CTIA Messaging Principles and Best Practices add carrier expectations: express written consent for marketing, one opt-in per campaign, no rented or shared lists, and a single final confirmation after STOP. 10DLC brands register through a Campaign Service Provider, not directly with The Campaign Registry.
Approved codes and audited programs
Canadian common short codes are administered by the Canadian Telecommunications Association through its txt.ca registry, and programs must follow its compliance policies. Salesforce's Canada sending guide adds that registration goes through a Mobile Approved Partner and that short codes are audited weekly.
Consent or soft opt-in, asked per channel
The ICO's PECR guidance treats marketing texts as electronic mail: you need consent or the soft opt-in, consent must be a clear affirmative action with no pre-ticked boxes, and you should ask for email and text consent separately.
Checklist for every SMS program
- 1
Separate SMS consent. Email consent is not SMS consent. Use unticked boxes and double opt-in for web and app sign-ups, and store when and how consent was given.
- 2
A clear call to action. Program name, message frequency, "message and data rates may apply", and links to terms and privacy policy, with "Text STOP to stop" and "Text HELP for help".
- 3
A confirmation message for recurring programs, naming the program, frequency, help contact and how to opt out.
- 4
Working opt-out on every code, handling for replies such as "revoke" and "opt out", and another route for one-way sender names.
- 5
Respectful timing and content. Use send blockouts, check country rules (France bans marketing texts on Sundays and public holidays), and avoid carrier-restricted content such as alcohol, firearms, tobacco, cannabis and high-risk financial offers in the US.
Salesforce's own compliance guidance for SMS campaigns also suggests renewing consent after long inactivity and registering the URLs you send with carriers, and the US guide explains that CTIA audits short code programs weekly for missing terms, broken STOP and HELP, and use-case drift.
How Do You Track SMS Delivery and Performance in MobileConnect?
Use the four standard MobileConnect reports for sends, delivery and clicks, and the SMS data views for message-level detail. Treat "delivered" carefully: MobileConnect counts a message as delivered until a carrier reports otherwise, and some carriers never send a receipt.
Standard reports
SMS Account Summary, SMS Message Detail, SMS Message Summary and SMS Link Clicks. Link Clicks needs the Marketing Cloud shortener with tracking on.
Delivery receipts
Usually back within an hour but can take up to 72. They are not read receipts, and low-quality routes can return fake receipts that show 100% delivery.
Data views
SMSMessageTracking holds message-level status, SMSSubscriptionLog the opt-in and opt-out history, and Undeliverable SMS the numbers that keep failing.
See Salesforce's articles on MobileConnect reports and delivery receipts. Track delivery, click and opt-out rates per code and per country, A/B test calls to action, and remove or reconfirm numbers that bounce repeatedly, as Salesforce's bounce management guidance advises. Budget matters too: Marketing Cloud measures usage in super messages, and one SMS within the US uses 10 of them, with multipliers from 10 to 95 depending on the country, according to Trailhead.
How Does MobileConnect Fit with the Rest of Marketing Cloud?
MobileConnect is one of three Mobile Studio tools in Marketing Cloud Engagement, and it relies on the platform's builders for data, content and journeys. In Marketing Cloud Next, the newer Data 360-based product, SMS is sent through Salesforce Flow instead, so check which product your licence covers before you plan the build.
| Tool | Role alongside MobileConnect |
|---|---|
| MobilePush | Push and in-app notifications for your own mobile app. See our guide to implementing MobilePush. |
| GroupConnect and WhatsApp | Messaging-app channels: LINE and Facebook Messenger through GroupConnect, and WhatsApp through Meta's business platform, sent from Journey Builder. See Marketing Cloud WhatsApp integration. |
| Journey Builder | Orchestrates SMS with email, push and waits in one customer journey |
| Automation Studio | Imports mobile contacts, refreshes filtered lists and runs scheduled SMS sends |
| Content Builder | Stores reusable content; SMS messages can also be built here |
| Marketing Cloud Next | Sends SMS and WhatsApp through Flow, uses self-service US short code registration, and can draft SMS copy with Agentforce |
The Mobile Studio components are listed in Salesforce's Mobile Studio overview, and the Marketing Cloud Next SMS features in Trailhead's Marketing Cloud Next unit. Social Studio, which earlier versions of this article listed beside MobileConnect, was retired on November 18, 2024. For a wider view of Mobile Studio, read our post on Salesforce Mobile Studio, and if you are weighing the newer product, our Marketing Cloud Next consulting page explains how we approach it.
What Are the Most Common MobileConnect Mistakes?
Most problems come from starting too late on codes, treating email subscribers as SMS subscribers, and ignoring message length and opt-out paths. Each is cheap to avoid at the design stage and expensive to fix after a carrier blocks the code or a complaint arrives.
The Bottom Line
Marketing Cloud MobileConnect turns SMS into a managed channel inside the same platform as your email and journeys, with keywords, opt-in flows, data capture and reporting built in. The work that decides success happens before the first send: the right code for each country, consent you can prove, and messages designed for 160 characters.
In a published Marketing Cloud case study, Twopir Consulting set up Mobile Studio for an e-commerce company that wanted to explore mobile journeys, alongside automations and multi-path journeys, and gave the client one environment to manage email, social, web and mobile communication. Our Marketing Cloud implementation services cover MobileConnect from code planning to journeys and reporting.
Plan Your SMS Program Before the Code Clock Starts
Tell us which countries you want to text and what you want to send. We will map the codes, consent flow, journeys and reporting your Marketing Cloud org needs.
Schedule a Discovery CallFrequently Asked Questions
MobileConnect is the SMS and MMS application in Mobile Studio, part of Salesforce Marketing Cloud Engagement. It creates, sends, receives and tracks text messages, manages keywords, and handles opt-ins and opt-outs. Messages can be sent on a schedule, from Journey Builder, from Automation Studio or through the REST API.
A short code is a 5 or 6 digit number approved by carriers for high-volume, two-way messaging, and it takes weeks to provision. A long code is a standard phone number, such as US 10DLC, that also supports two-way messaging, is faster to set up and suits conversational or lower-volume programs. Some countries restrict long codes to transactional use.
Salesforce estimates 10 to 12 weeks for a US or Canadian short code, about 10 weeks in the United Kingdom and 12 weeks in France. A US or Canadian 10DLC long code takes 1 to 4 weeks. Holidays and carrier network freezes add delay, so start registration before building campaigns.
No. Salesforce's US sending guide lists toll-free numbers as not supported, and messages sent with a sender name are blocked. For US recipients, use a carrier-approved short code or a registered 10DLC long code.
STOP, QUIT, CANCEL, END and UNSUBSCRIBE are recognized by default as requests to unsubscribe from all messages. Every account also needs a HELP keyword, which an admin creates. Admins can add custom STOP keywords, which helps cover US rules that also treat replies such as revoke and opt out as revoking consent.
A single SMS holds 160 GSM characters, or 70 if it contains any emoji or other non-GSM character. Longer messages are split into parts of 153 or 67 characters when joined, and every part is billed as a separate send. Salesforce recommends keeping messages under 160 characters.
Yes. When MobileConnect, Content Builder and Journey Builder are enabled, an SMS activity appears in Journey Builder and you create the message inside the journey. Personalization uses the journey's entry data first and falls back to the MobileConnect contact record when a value is empty.
No. Salesforce states that a subscriber who consents to email has not consented to mobile messages. Collect a separate SMS opt-in, preferably with double opt-in for web and app sign-ups, and keep a record of when and how each person agreed.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Salesforce Marketing Cloud journeys, SMS and mobile channels, for 500+ clients over 12+ years.