Separate platform controls from your responsibilities.
Permission and purpose
Twilio's messaging policy requires consent before messaging and limits its scope to the sender and subject disclosed. Keep evidence of permission with your campaign records.
Sender and opt-out
Twilio requires messages to identify the sender and provide a straightforward opt-out process. Review the behavior of your actual sending configuration.
Review your use case
Provider policy and applicable law are separate considerations. Review your audience, location, message purpose, and records with the appropriate advisers before launch.
Source: Twilio Messaging Policy. This is general program-planning information, not legal advice or a guarantee that a campaign meets every applicable requirement.
Make messaging responsibilities part of campaign planning
Before launching an SMS program, identify who owns consent records, message review, and preference handling inside your organization. Those responsibilities should be clear to staff and any agency working on your behalf.
What to review before you start
Use this page as a starting point for reviewing the program with your advisers and messaging providers. Requirements depend on the activity and location; software features alone do not establish compliance. Keep the underlying permissions and review decisions with your campaign records.
- Assign ownership for consent records and campaign review.
- Check the applicable provider requirements for your use case.
- Review preference handling and document the path for questions.
Common questions
Does using a messaging platform make a campaign compliant?
No. Your organization still needs to review its audience, content, permissions, and applicable requirements with the appropriate advisers.
Where can a recipient find help about preferences?
The opt-out preferences page provides a starting point. For a specific message or account question, contact the responsible organization or Treply support as appropriate.