SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Short Code Single vs. Recurring Message Programs

In the US carriers currently only recognize 2 different kinds of short code campaigns: Recurring and Single Message. Knowing which kind of program you are dealing with will determine how a given application is filed with the carriers, what requirements must be met for the Call to Action, and how keyword testing is setup.

Overview

The vast majority of US short code campaigns fall into the recurring program bucket. It is helpful to remember that single message programs must fit a very narrow set of requirements, and anything outside of those requirements will be put into the recurring bucket. The definitions depend on how users are being opted in, as well as the overall number of messages being sent.

Single Message Programs

Single-message programs, or “one-off” programs, deliver a one-time message in response to Consumers’ opt-in requests. Examples of single-message programs include, but are not limited to, the following:

  1. Informational alert
  2. Purchase receipt
  3. Delivery notification
  4. Two-factor authentication

At a minimum the opt-in should include:

  • Program description with a clear call to action for the end user to enter their phone number
  • Alternative communication channel (email or phone call)
  • User cannot be required to opt-in to receive SMS
  • “Message and data rates may apply”
  • “1msg/request”
  • Link to both SMS ToS and Privacy Policy

*Single message programs do not need to contain HELP or STOP language within the Call to Action. 

 

Recurring Message Programs

Because they reach out to Consumers on an ongoing basis, recurring-messages programs require additional disclosures. Examples of recurring-messages programs include but are not limited to the following:

  1. Content or informational alert subscriptions (e.g., horoscopes, news, weather)
  2. Flight status notifications (multiple messages)
  3. Marketing and loyalty promotions.

At a minimum the opt-in should include:

  • Program description with a clear call to action for the end user to enter their phone number
  • Opt-in must be optional
  • “Message and data rates may apply”
  • Message frequency
  • HELP and STOP language
  • Link to both SMS ToS and Privacy Policy

Further short code rules and regulations can be found in the CTIA Handbook

Have more questions? Submit a request
Powered by Zendesk