US Short Code Campaign Compliance Overview

Before you launch your US short code campaign, Sinch and US Carriers must review your brand and campaign. We make sure your message program aligns with carrier and industry requirements. Principally we look for alignment with the CTIA Messaging Principles and Best Practices and CTIA Short Code Monitoring Program Handbook documents. 

For Sinch to approve your short code campaign, you will need to:

• Identify the campaign use case(s). It should not be a prohibited use case in North America. Read more about Sinch's Disallowed Content Policy.
• Describe in detail the campaign and the service it is providing to end users.
• Provide information about how the end user will opt-in to the campaign. Identify the opt-in method (website, text-to-join, paper form, etc).
• Provide several message types. This includes the confirmation message, opt-out message, help message, and sample messages.
• Identify special attributes associated with your campaign. For example, if your campaign will host any age restricted content.  In that case an age gate must be presented.  If it involves direct lending, those relationships must be documented.

US Short Code Campaign Requirements

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

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)
• Link to complete Terms and Conditions
• Privacy policy OR link to privacy policy
• Message frequency (#msgs/mo, msg frequency varies, recurring messages, etc. Not required for one-time transactional programs)
• Opt-out instructions (Reply STOP to stop)
• Help instructions (Reply HELP for help)

CTA is still required for one-time transactional programs, but message frequency and opt-out instructions are optional

For One-Time PIN programs, SMS-only verification methods are not sufficient. The call-to-action must offer an alternative user verification method - such as voice call, email, or authentication apps, etc. This requirement originates from the wireless carriers and is intended to ensure users are not obligated to receive SMS messages.

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
• Recommended but NOT required: Opt-out instructions. (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.

STOP MT (for One-Time-Pin programs):

• This is not a subscription program. You will not receive any further messages from <brand> unless you request another OTP.
   

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.

Visit the Sinch Short Code Product Page to learn more about Sinch Short Codes or if you need more help with 10DLC or have any questions, contact Sinch, who will be happy help!