---
schema_version: "1"
id: e860ecbe42e697abbf9283f000c7e743a891bf171258705826e3823df65a4c28
title: Messaging
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_mce_parent_messaging.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_messaging.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0133e6008a9770e97c7feb1e8dbe77f2cacbf2c9e13eb9032f68eb0015c516fa
description: Keep up with customers who hide their phone numbers using Business-Scoped User IDs, connect multiple Marketing Cloud Engagement accounts to a single Data Cloud instance, and catch Direct Send template category mismatches before they trigger account restrictions.
products:
  - Cross Cloud
release: "264"
---
# Messaging

Keep up with customers who hide their phone numbers using Business-Scoped User IDs, connect multiple Marketing Cloud Engagement accounts to a single Data Cloud instance, and catch Direct Send template category mismatches before they trigger account restrictions.

- **[Connect Multiple Marketing Cloud Accounts to One Data Cloud Instance for WhatsApp](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_connect_multiple_marketing_cloud_accounts_to_one_data_cloud_instance_for_whatsapp.htm&release=264.0.0&type=5)**  
    When you set up WhatsApp in Unified Messaging, you can link a phone number to a business unit in any of the Marketing Cloud Engagement accounts connected to your Data Cloud instance. You can run different WhatsApp journeys from separate Marketing Cloud accounts while sharing one Data Cloud instance and a single WhatsApp Business Account (WABA). Previously, you couldn't assign a phone number to a business unit in a different account during WhatsApp setup.
- **[Reach WhatsApp Users with Usernames Using Business-Scoped User IDs](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_reach_whatsapp_usernames.htm&release=264.0.0&type=5)**  
    Maintain contact continuity with WhatsApp users when they hide their phone numbers with usernames. Import contacts with Business-scoped User IDs (BSUIDs), send outbound messages when phone numbers aren't available, and track message engagement across both identifiers. Marketing Cloud supports Meta's BSUID, which identifies users who enable username privacy.
- **[Skip Template Pre-Approval for WhatsApp Utility Messages with Direct Send](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_category_mismatches.htm&release=264.0.0&type=5)**  
    WhatsApp Direct Send eliminates the manual pre-approval step for utility messages, reducing operational bottlenecks in your messaging workflow. Unlike the traditional template lifecycle, Direct Send templates reach recipients without waiting for prior approval. Your teams deploy utility messages faster and at higher volumes.
- **[Prepare for WhatsApp Service and Utility Message Pricing Changes](https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_whatsapp_pricing_utility_services.htm&release=264.0.0&type=5)**  
    Meta is now charging on a per-message basis for WhatsApp service messages and utility messages sent within the Customer Service Window. These message types were previously free. As a result, on November 1, 2026, Salesforce is updating its pricing to reflect Meta’s new charges. If you exceed your entitlements, message delivery continues, however overage billing can apply.
- **[Prepare for the WhatsApp Account Model Update](https://help.salesforce.com/s/articleView?id=release-notes.rn_mktg_whatsapp_wame.htm&release=264.0.0&type=5)**  
    Meta is separating business phone numbers from provider-specific templates and billing through its WhatsApp Account Model Evolution update. You can now use a single WhatsApp phone number across Salesforce and another provider simultaneously without disrupting existing journeys, templates, or API integrations.