---
schema_version: "1"
id: efe013baf8bdfead8e13558cecaaca661c99188de99d302e5b4741c7de3bfa81
title: Recommendations for Message Sending
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mceplus_sending_recommendations.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mceplus_sending_recommendations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 959d4185241ba2427729152f81091e5a90b3732b37ca8ea0fd3928c3247e7327
description: With Marketing Cloud Engagement+, you can continue to send messages by using the Engagement apps you know and love, such as Email Studio, Mobile Studio, and Journey Builder. You can also augment and extend your existing marketing programs by using Salesforce Platform tools such as Flow Builder to send your messages. The right product to use depends on your objectives and use case.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Recommendations for Message Sending

With Marketing Cloud Engagement+, you can continue to send messages by using the Engagement apps you know and love, such as Email Studio, Mobile Studio, and Journey Builder. You can also augment and extend your existing marketing programs by using Salesforce Platform tools such as Flow Builder to send your messages. The right product to use depends on your objectives and use case.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Marketing Cloud Engagement <strong>Pro+</strong>, <strong>Corporate+</strong>, and <strong>Enterprise+</strong> Editions</td></tr></tbody></table>

This table includes our notes and recommendations for each messaging channel.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:33.33333333333333%">
        <col style="width:33.33333333333333%">
        <col style="width:33.33333333333333%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d32216e76"><strong>Channel</strong></th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d32216e80"><strong>Recommendation</strong></th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d32216e84"><strong>Notes</strong></th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Channel" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e76 "><strong>Email</strong></td>

          <td data-label="Recommendation" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e80 ">Continue to use <span>Marketing Cloud Engagement</span> for all use cases.</td>

          <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e84 ">
            <p style="margin-bottom:0;">IP addresses, or consent information between <span>Marketing Cloud Next</span> and <span>Engagement</span> isn’t supported. </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Channel" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e76 "><strong>SMS</strong></td>

          <td data-label="Recommendation" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e80 ">
            <p>For new use cases that use a new phone number or code, consider using a flow. See
              <a href="https://help.salesforce.com/s/articleView?id=mktg.mktg_admin_setup_sms.htm&amp;language=en_US" target="_blank"><u>Set Up SMS Messages in Marketing Cloud
                  Next</u></a>.
            </p>
            <p style="margin-bottom:0;">For existing use cases that require you to use an existing number or code, continue
              to use <span>Engagement</span>.</p>
          </td>

          <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e84 ">
            <p style="margin-bottom:0;">Sharing short codes, long codes, or SMS consent information between <span>Marketing Cloud Next</span> and <span>Engagement</span> isn’t supported. </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Channel" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e76 "><strong>WhatsApp</strong></td>

          <td data-label="Recommendation" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e80 ">Consider using a flow for new WhatsApp use cases. See <a href="https://help.salesforce.com/s/articleView?id=mktg.mktg_admin_setup_whatsapp.htm&amp;language=en_US" target="_blank"><u>Set Up WhatsApp in Marketing Cloud
                Next</u></a>.</td>

          <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e84 ">
            <p>You can use new or existing WhatsApp phone numbers in both <span>Marketing Cloud Next</span> and <span>Engagement</span>. </p>
            <p>Keyword-based opt-out information is shared between <span>Marketing Cloud Next</span>
              and <span>Engagement</span> isn’t supported.</p>
            <p style="margin-bottom:0;">Preference center opt-outs for specific subscriptions aren’t shared.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Channel" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e76 "><strong>Mobile App Messaging</strong></td>

          <td data-label="Recommendation" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e80 ">
            <p>Mobile App Messaging includes push notifications, in-app messages, and app inbox
              messages.</p>
            <p style="margin-bottom:0;">Continue to use <span>Engagement</span> for all use cases.</p>
          </td>

          <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d32216e84 ">—</td>

        </tr>
      </tbody>
    </table>