Standing up Mobile Studio across channels

Standing up Mobile Studio is a multi-step project across configuration, compliance, and operational training. The four-phase routine covers: provision the sending capability (phone numbers, push certificates, messaging app integrations), set up subscriber attributes and audiences, build and test message templates, and operationalize the launch with compliance monitoring. Mobile marketing has higher engagement than email but also higher regulatory risk; skipping the compliance step at launch is the most expensive mistake mobile programs make.

1. 1
   Provision the sending capability per channel

   For SMS and MMS, work with Salesforce or a partner carrier to provision the right phone number type (long code for low volume, short code for high volume, toll-free for two-way support). Submit the number for carrier approval (a few weeks for short codes). For Push, generate iOS Apple Push Notification certificates and Android FCM credentials, upload them to Marketing Cloud, and have the mobile dev team integrate the Marketing Cloud SDK in the app. For GroupConnect, provision WhatsApp Business numbers, Facebook Pages, and any other channel integrations through their respective platform admin consoles. Document each provisioned channel in the Mobile Studio runbook.

2. 2
   Set up subscriber attributes and audiences

   In Marketing Cloud, create Subscriber Attributes that capture the data needed for personalization and segmentation: First Name, City, opt-in date, opt-in source, communication preferences. Build Data Extensions that hold subscriber records with these attributes. Configure the source systems (Sales Cloud, the company website, the mobile app) to write subscriber data into the Data Extensions on a scheduled or real-time cadence. Test the data sync by adding a test subscriber and confirming the record appears in the Data Extension with the right attributes. Document the data flow in the runbook.

3. 3
   Build and test message templates

   For each channel, build the message templates marketers will use. SMS templates should be under 160 characters when possible (longer messages charge multiple SMS units) and include the brand name, the merge fields, and a clear call to action. Push notification templates include title, body, image, and deep link. GroupConnect templates follow each channel restrictions (WhatsApp 24-hour window, Message Template approval). Test each template through Marketing Cloud Test Send to a small group of internal users before launching to subscribers. Iterate on the wording and the merge field selection based on the test feedback.

4. 4
   Operationalize the launch with compliance monitoring

   Document the opt-in workflow for every subscriber acquisition channel: web form, app install, in-store signup. Capture the opt-in text the subscriber agreed to, the timestamp, and the source. Configure Mobile Studio to enforce per-country compliance rules: TCPA opt-in tracking for US SMS, GDPR consent records for EU subscribers, quiet hours for late-night sends. Build a compliance dashboard tracking opt-out rates, complaint rates, and any carrier-level warnings. Schedule a monthly compliance review with the marketing operations team. Train marketers on the rules; one bad send can trigger fines or carrier blocks that take months to resolve.