Twilio's A2P 10DLC registration is to comply with carrier requirements

Carriers consider all SMS traffic from Twilio to be sent from an application, so anyone using a 10DLC number with Twilio to send SMS messages to the US will need to register. This includes individuals and hobbyists using Twilio.

Ten-digit long code numbers in the US were originally designed for person to person (P2P) communication. These routes were unregulated, and in recent years have started seeing abuse from spam applications and unsolicited messaging.

Due to the increase in spam messages, many consumers have lost trust in SMS as a form of communication. US A2P 10DLC is the standard that carriers have implemented in the US to regulate this communication pathway.

Registration tips

• Brand Type: Most small U.S. organizations qualify as “Low Volume Standard Brand”
• EIN required, less than 6,000 msg/day
• Skips expensive secondary vetting, much simpler!
  
• "Sole Proprietorship" registrations likely will fail if Twilio is given a company email address
• Campaign Use Case: Use the “Account Notification” campaign type for alarm/alerting. For municipal/government, “Emergency” may also be appropriate.
• Templates/Samples:
• Clearly label the customer/brand (“City Water Plant”) in sample messages
• Every sample must include opt-out language, even if it feels odd (“Alert: Water Pump #2 Alarm. Reply STOP to end alerts.”)
• Provide 2 specific sample messages (not just “test”, “notification”)
  

Resources

1. A2P 10DLC registration application quickstart | Twilio
   
2. Programmable Messaging and A2P 10DLC | Twilio

We know this can be a difficult process, please email support@exele.com with any questions, concerns, or feedback.