This article covers the most common questions about SMS Short Codes and Long Codes in Marketing Cloud MobileConnect. Topics include provisioning new codes, migrating codes between vendors or accounts, managing Keywords, enabling MMS, adjusting the conversation window, and opening Support cases for code-related issues.
A) Reach out to your Account Representative to discuss your options and begin the necessary paperwork.Every country has a different provisioning process that your Account Representative will be able to provide details around.
A) The Approved Partner handling the SMS Code acquisition and provisioning should be reaching out to the Marketing Cloud Engagement Codes team and working through their separate portal. If the code is live and is having issues, please open a support case for further review.
A) Your Account Representative will be able to assist with the code migration.
A) Open a case with Marketing Cloud Engagement Support and the migration can be facilitated through Marketing Cloud Engagement Product. Please be aware that any Keywords in the original enterprise need to be deleted in order to be utilized in the new enterprise.
A) Open a support case with the code, Business Unit, and country you want to modify.
A) There can be some limitations on sharing across Stacks. Please open a support case if this is needing done. If it is possible, the code can be used across BUs concurrently, but keywords will not be shareable. Each unique keyword can only be used on a single BU.
A) Reach out to your Account Representative to add additional countries.
A) Your Account Representative can assist with the supported countries and cost.
A) Please contact your Account Representative to complete the necessary paperwork.
A) Your Account Representative will be able to provide updates on the timeline.
A) Conversation window is the amount of time a subscriber has to respond to a sms message before it is registered to the default keyword. The default window is 60 minutes.
For example: On a double opt-in, if a subscriber texts the Join keyword they have 60 minutes to text in Y for the double opt-in to process, otherwise they subscriber will need to start the opt-in process over. Most uses cases this should be no larger than 3-4 hours due to causing conflicts with other SMS engagement to the subscriber. If you would like to update the conversation window please review the following Configure the Conversation Window in MobileConnect.
A) Open a support case with the Code, Business Unit and the country that should be provisioned.
A) Open a support case with the code and requested number of keywords.
A) There is a guide on Super Message consumption here: https://salesforce.com/products/marketing-cloud/sfmc/sms-ratio-updates/ For more details, contact your Account Representative for more information on this topic
A) Please contact your Account Representative to discuss the option for each Country
A) To enable MMS capabilities on an existing code, you will need to resubmit the CAF (Campaign Application Form) for approval for MMS through an approved partner. (Please note: MMS is currently only supported in the United States and Canada)
To enable Media templates for an existing MMS code, please submit a Support case to have these activated for use.
A) Contact your Account Representative to assist with the code migration. A support case will be needed for a code migration to occur.
A) This occurs when the specified Long Code/ Short Code is not enabled for the target country (market). The system automatically searches for and uses any other existing, enabled Long Code in the account for that market to complete the send. This does not gurantee the sms delivery.
A) Sending entities must use a Long Code/short code that is explicitly configured and enabled for the specific market of the recipient.
000383747

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.