---
schema_version: "1"
id: 6fee548920496462744933295d1b180eebe5fd304086af869ce1a3800fa64531
title: Understanding SMS Codes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_moc_sms_codes.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_moc_sms_codes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bc37e8d569b30c89f8ac9e14d7ea0919b38d37df56f1a1c435e76a644c2a5582
description: To optimize deliverability and cost, use the correct sender ID for your campaigns based on your country's regulations. For international SMS service, use an international long code in transactional alerts and provide a separate opt-out option through a web form or call center.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Understanding SMS Codes

To optimize deliverability and cost, use the correct sender ID for your campaigns based on your country's regulations. For international SMS service, use an international long code in transactional alerts and provide a separate opt-out option through a web form or call center.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:16.666666666666664%">
        <col style="width:16.666666666666664%">
        <col style="width:16.666666666666664%">
        <col style="width:16.666666666666664%">
        <col style="width:16.666666666666664%">
        <col style="width:16.666666666666664%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e45">Sender ID</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e48">Description</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e51">Use Cases</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e54">Considerations</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e57">Reply Support</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13782e61">Supported Regions</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Sender ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e45 ">Alphanumeric Code (Alpha Code or FromName)</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e48 ">The company or brand name used instead of a phone number.</td>

          <td data-label="Use Cases" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e51 ">One-way messaging and brand recognition.</td>

          <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e54 "><a name="mc_moc_sms_codes__ul_lg2_xsr_bgc"><!-- --></a>
            <ul id="mc_moc_sms_codes__ul_lg2_xsr_bgc">
              <li>Requires preregistration.</li>

              <li>Some countries restrict special characters or case-sensitive codes.</li>

            </ul>
          </td>

          <td data-label="Reply Support" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e57 ">No</td>

          <td data-label="Supported Regions" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e61 ">Europe and Asia</td>

        </tr>
        <tr class="">
          <td data-label="Sender ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e45 ">Long Code</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e48 ">A 10–14 digit phone number that’s used for SMS.</td>

          <td data-label="Use Cases" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e51 ">One-way and two-way messaging, such as transactional alerts and support.</td>

          <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e54 "><a name="mc_moc_sms_codes__ul_mzc_dtr_bgc"><!-- --></a>
            <ul id="mc_moc_sms_codes__ul_mzc_dtr_bgc">
              <li>Some countries limit long codes to transactional use.</li>

              <li>If used internationally, carriers often overwrite the sender ID.</li>

            </ul>
          </td>

          <td data-label="Reply Support" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e57 ">Yes</td>

          <td data-label="Supported Regions" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e61 ">Latin America and India</td>

        </tr>
        <tr class="">
          <td data-label="Sender ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e45 ">Short Code</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e48 ">A 5–6 digits number used for sending high-volume, interactive messages.</td>

          <td data-label="Use Cases" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e51 ">Two-way messaging, such as campaigns, opt-ins, and promotional alerts.</td>

          <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e54 "><a name="mc_moc_sms_codes__ul_dkf_ftr_bgc"><!-- --></a>
            <ul id="mc_moc_sms_codes__ul_dkf_ftr_bgc">
              <li>Requires carrier approval and provisioning. </li>

              <li>Mandatory in some countries, such as France.</li>

              <li>Setup varies from weeks to months.</li>

            </ul>
          </td>

          <td data-label="Reply Support" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e57 ">Yes</td>

          <td data-label="Supported Regions" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e61 ">United States and Canada</td>

        </tr>
        <tr class="">
          <td data-label="Sender ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e45 ">International Long Code</td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e48 ">A 10-digit phone number used for two-way communication outside your
            country.</td>

          <td data-label="Use Cases" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e51 ">Sending in regions where regulations are lenient.</td>

          <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e54 "><a name="mc_moc_sms_codes__ul_bx1_3tr_bgc"><!-- --></a>
            <ul id="mc_moc_sms_codes__ul_bx1_3tr_bgc">
              <li>Carriers often overwrite the sender ID, reducing brand visibility.</li>

              <li>Higher costs and inconsistent delivery.</li>

            </ul>
          </td>

          <td data-label="Reply Support" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e57 ">No</td>

          <td data-label="Supported Regions" class="slds-cell-wrap" style="vertical-align:top;" headers="d13782e61 ">Latin America and Africa</td>

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

## FromName Registration and Guidelines

Before you start sending messages, register your FromName. Your account executive can help you with the registration forms for most countries. In other countries, you can submit a signed letter from an authorized signatory and a copy of your local trading license. Skipping preregistration can cause your messages to be filtered or blocked, which harms SMS deliverability and brand recognition.

Follow these guidelines when using FromName:

- FromNames must be 3 to 11 characters long and can’t include special characters.
- Registered FromNames are case-sensitive, so use the exact registered format in MobileConnect Setup.
- Avoid using generic terms, such as Sales, Offer, or Promotion.
- If you’re using a brand name as your FromName, you must own the trademark and provide details to Salesforce and the carrier.
- Check your country's FromName [guidelines](https://help.salesforce.com/s/articleView?id=mktg.mc_moc_mobileconnect_enablement_guides.htm&type=5&language=en_US).

## Sending SMS with FromName

If your country supports an alphanumeric code, use a custom FromName instead of a numeric long code. Using an international long code can lead to message blocking. In MobileConnect, you have the option to set the FromName for your account. For more information, see [Set the MobileConnect Account-Level From Name](https://help.salesforce.com/s/articleView?id=mktg.mc_moc_set_account_level_from_name.htm&type=5&language=en_US).

## Sending SMS with International Long Code

If your country doesn’t support FromName or local two-way codes, we recommend using a numeric international long code. This long code is sometimes preserved in the delivered messages, or it can be overwritten with a generic alpha or local (short or long) code. To ensure compliance and successful delivery, use a sender ID that meets the regulations of the destination country. For more information, see [Request a Location-Specific Sending Code](https://help.salesforce.com/s/articleView?id=mktg.um_channel_sms_request_location_specific_code.htm&type=5&language=en_US).

## Manage Short Codes in the US and Canada

To get carrier approval in the US and Canada, work with Salesforce or an approved partner to complete the Campaign Approval Form (CAF), sign the contract, and complete all necessary business agreements.

If you have questions about partner options, costs, or implementation, contact your account executive. Salesforce offers a range of services related to SMS codes. These services include setting up new short codes, migrating codes to Marketing Cloud, and modifying your US short code campaigns. We can also help you integrate new program types and MMS functionality.

- **[Align Sender ID with SMS Campaigns](https://help.salesforce.com/s/articleView?id=mktg.mc_moc_align_sms_codes_with_campaigns.htm&release=264.0.0&type=5)**  
    To adhere to compliance guidelines, build customer trust, and improve deliverability, choose the right sender ID for your SMS campaigns based on message type.