Know why the customer expects your message.
Keep the source, wording, and date of the permission record appropriate to the message program. A phone number in a customer file is not, by itself, a complete description of permission.
Responsible U.S. business texting
Good messaging starts before the send.
Plan who you will message, why the message is expected, how people can opt out, and which registration your number and provider require.
This page is general information, not legal advice or a compliance certification.
Before your first message
- Define the message purpose and audience.
- Document how recipients agreed to receive messages.
- Explain who is sending and how to get help or stop.
- Confirm the number registration with your provider.
- Keep a process for opt-out and delivery issues.
A practical setup checklist
Build a responsible process around the customer.
No one checklist covers every business, message type, number, and jurisdiction. Confirm the current requirements with qualified counsel and the selected provider.
Make the sender and message purpose clear.
Describe the business, the kind of messages it sends, and how the customer can ask for help or stop messages. Make campaign forms and examples match actual behavior.
Process opt-out requests reliably.
Design a process to recognize and record opt-out requests, stop the relevant future messages, and keep the record available to authorized staff. The specific legal and carrier requirements depend on the program.
Ask whether your local number needs registration.
For app-to-person SMS/MMS to U.S. recipients over a U.S. 10-digit long code, Twilio’s documentation describes Brand and Campaign registration steps. Other providers may have different workflows, fees, eligibility rules, and review times.
Match registration to the actual use case.
Provider documentation can tie registration details and review to message purpose, sender identity, throughput, and daily volume. Do not publish a limit or delivery promise without account-specific evidence.
Keep an owner for the messaging process.
Decide who reviews the message content, registration details, customer complaints, STOP requests, failed deliveries, and changes to the program.
Primary references
Check current sources before launch.
Requirements and carrier processes change. These sources provide a starting point for review, not a substitute for advice tailored to your business.
A2P 10DLC overview
Twilio explains the U.S. 10DLC Brand and Campaign workflow for traffic sent through its service.
Read Twilio’s current guide ↗Registration details
Review what business and campaign information a provider may request and confirm which requirements apply to your account.
View information checklist ↗FCC rules and orders
Consult current FCC materials and qualified counsel on consent revocation, robotexts, and requirements that apply to your specific program.
Open FCC order ↗Loopline status: No provider, sender number, consent-record tool, opt-out feature, or registration workflow is connected to this local preview. Do not use this page as a claim that the product makes a campaign compliant.