Marketing Cloud SMS and MobilePush
MobileConnect SMS and MobilePush set up and run inside Marketing Cloud, with consent capture planned for the rules in each country you message.
SMS and push notifications reach people faster than email, and they annoy people faster too. In Marketing Cloud Engagement, MobileConnect handles SMS and MobilePush handles app notifications. Our Marketing Cloud SMS and MobilePush service sets up both channels, connects them to your journeys and builds consent capture you can stand behind.
If you mainly need journey design, see Journey Builder consulting. For Marketing Cloud Next consent, see consent and preferences in Marketing Cloud Next.
What's included
| Area | What we do |
|---|---|
| MobileConnect setup | SMS codes, sending, campaigns and reporting, following Salesforce's MobileConnect model |
| Journeys and automations | SMS and push in Journey Builder, plus Send SMS and Send Push activities in Automation Studio |
| App SDK | Integrate the MobilePush SDK, or the Unified Mobile Engagement SDK, with your iOS and Android apps |
| Personalisation | AMPscript in SMS and push content, with fallbacks for missing data |
| Send timing | Einstein Send Time Optimization for push, plus send windows and frequency rules |
| Consent | Opt-in capture, opt-out handling and consent records across forms, CloudPages and apps |
| Reporting | Delivery and engagement reporting for both channels |
How we work
- 01
Discovery
List use cases, countries, sending volumes and current consent sources, and confirm your licences.
- 02
Design
Design opt-in wording and flows, message types, frequency limits and journey placement.
- 03
Build
Configure MobileConnect and MobilePush, integrate the app SDK, and build messages and journeys.
- 04
Test
Test on real devices and carriers, and check opt-in, opt-out and quiet-hour behaviour.
- 05
Launch
Start with a small audience, watch delivery and opt-outs, then widen.
- 06
Support
Keep SDK versions current and review frequency and consent rules as you add countries.
Consent: what to plan for
Messaging rules differ by country and change over time. In the United States, plan for the Telephone Consumer Protection Act (TCPA) when sending marketing texts, and check state rules with your legal adviser. Elsewhere, plan for each country's own messaging and privacy laws. In practice, that means:
- Record when, where and with what wording each person opted in.
- Honour opt-outs promptly and across every system that can send.
- Respect send windows, which you can manage with throttling and send windows.
- Keep transactional and marketing messages clearly separated.
Our consent requirements worksheet helps you gather this before the build. We plan for these rules, but we don't give legal advice or guarantee compliance.
Prerequisites and licences
- MobileConnect and MobilePush are licensed Marketing Cloud Engagement channels. Salesforce's current Trailhead module covers MobileConnect, and we found no retirement notice for it.
- The MobilePush SDK is active. Recent releases are Android 11.0.1 (June 2026) and iOS 11.0.2 (July 2026), and the minimums are Android API 26 and iOS 12. Version 10.0.0 introduced a unified SDK architecture.
- Marketing Cloud Advanced Edition customers use the Mobile App Messaging module of the Unified Mobile Engagement SDK instead of MobilePush. Salesforce gives no status for that SDK.
- Send Time Optimization covers email and MobilePush. Trailhead doesn't mention SMS.
Common mistakes
- Using one opt-in for every channel and purpose.
- Letting the app SDK fall versions behind until an OS update breaks it.
- Sending SMS on email schedules, without local time windows.
- Writing push copy without a fallback when personalisation data is missing.
Related services
CloudPages development
Opt-in forms and preference centres
→Consent synchronisation
Keeping consent consistent across CRM and marketing
→Marketing Cloud managed services
Ongoing support once channels are live
→Lifecycle marketing automation for B2C
Welcome, replenishment and win-back journeys
→Questions we hear
Is MobileConnect still supported?
Can we add WhatsApp as well?
Can AI write our SMS and push copy?
Do you handle TCPA compliance?
Sources
Plan your SMS and push channels
Tell us which countries you message and what you want to send. We'll map the setup and consent questions to answer first.
