How do I get a short code registered?

Below are some specific requirements you must apply to US short code campaigns you are bringing onboard.

Call to Action:

All US short code programs are required to have a call to action. This is how the program is advertised to end user and how consent is granted to receive messages. A call to action may be presented verbally (ie. Point of sale), via print ad (ie. “Text JOIN to XXXXX”) or via web (ie. Mobile number entry). Method of opt-in should be clear and concise. The call to action must include the following criteria for recurring programs:

• Clear Program description
• “Message and data rates may apply” disclosure (not required for FTEU)
• Full Terms OR link to complete Terms and Conditions**
• Privacy policy OR link to privacy policy
• Message frequency (#msgs/mo, msg frequency varies, recurring messages, etc)*
• Opt-out instructions (Reply STOP to stop)*
• Help instructions (Reply HELP for help)**

*Not required for one-time transactional campaigns
**Recommended. If full terms (including HELP instruction) is provided within the Call to Action, then Terms and Conditions for messaging is optional

Opt in: 

• Method of consumer’s affirmative opt-in “Web, Keyword or Verbal Opt in”

Opt in confirmation MT:              

• Program (brand) name
• Message frequency (#msgs/mo, msg frequency varies, recurring messages, etc)
• “Message and data rates may apply” disclosure (not required for FTEU)
• Customer care contact information (Reply HELP for help)
• Opt-out information (reply STOP to stop)

Example Content Messages:    

• Program (brand) name
• Opt-out information (reply STOP to stop)

If transactional notices are sent, examples need to be provided for each type Billing, Notifications etc.

HELP MT:            

• Program (brand) name 
• Additional customer care contact information (can be phone number, email address and/or URL that leads directly to a support contact page)

 Although single-message programs are not required to display HELP keyword, they should support HELP command.

STOP MT:           

• Program (brand) name 
• Confirmation that user has unsubscribed AND no further messages will be delivered

 Although single-message programs are not required to display STOP keyword, they should support STOP command.

Terms & Conditions: 

• Program (brand) name and description
• “Message and data rates may apply” disclosure (not required for FTEU)
• Customer care contact information (reply HELP for help) and another form of customer support (Phone number, support email or URL that leads directly to a support contact page)
• Link to Privacy Policy
• Message frequency*
• Opt-out instructions (reply STOP to stop)*

*Not required for one-time transactional programs

Terms & Conditions page must be live in production

Privacy Policy:

• Must be clear that end user’s personal information will not be shared or sold to third parties for the purpose of marketing
• Example statements: 
  • "No mobile information will be shared with or sold to third parties/affiliates for marketing/promotional purposes."*
  • “All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with or sold to any third parties."*

Privacy Policy page must be live in production

*No-sharing clause has to be present in Privacy Policy page or in within the Call To Action (as long as nothing contradicts it in Privacy Policy)

Additional documents needed:

• Call to Action screenshot (should be market ready)
• Sample MMS image (if applicable)
• Migration letter (if applicable)
• Website must be live Short code receipt
• Mock up of SMS Terms and Conditions, if that is not live in the website’s Terms and Conditions