---
schema_version: "1"
id: fb4742575ddcc148886683ac4cf446f2a011163c0f54ae7ef7a503de4a9b6514
title: Unify SMS Messaging and Consent for Marketing Cloud Next
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_mce_parent_sms.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_sms.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5f3125c2cff690bb2d203c8430b42938000439ea9c5166ebbd089be37f5b61bc
description: The United States and Canada SMS short and long codes that you use in Marketing Cloud Engagement are now supported for next-gen messaging. Marketers can also map consent across apps to sync the subscriber’s status and help maintain compliance.
products:
  - Cross Cloud
release: "262"
---
# Unify SMS Messaging and Consent for Marketing Cloud Next

The United States and Canada SMS short and long codes that you use in Marketing Cloud Engagement are now supported for next-gen messaging. Marketers can also map consent across apps to sync the subscriber’s status and help maintain compliance.

**Where:** This change applies to Lightning Experience in Salesforce Enterprise and Unlimited editions with any Marketing Cloud Engagement + edition.

- **[Share Engagement SMS Codes with Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_sms_codes.htm&release=262.0.0&type=5)**  
    You can now use your existing United States and Canada SMS short codes and long codes in Marketing Cloud Next. Reprocuring them is no longer necessary, so you can unify your messaging strategy and manage outbound and inbound traffic for both Journey Builder and Flow Builder from a single code.
- **[Manage Consent with More Flexibility](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_consent.htm&release=262.0.0&type=5)**  
    Marketers can now map consent from Marketing Cloud Engagement lists and publication lists to communication subscriptions in Marketing Cloud Next. After you map the lists, a subscriber’s status syncs each time that they update their consent. This change enables you to maintain compliance when you send messages from either app.
- **[Publish Preference Pages for Different Audiences](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_consent_pref_pages.htm&release=262.0.0&type=5)**  
    Create and publish independent preference pages that are tailored to specific target audiences. Marketers can select the preference page URL as a merge field to make sure that recipients see only relevant subscriptions. This update preserves distinct brand identities for separate business units or customer segments.