Setting Up Your District's Terms & Conditions Page for SMS Compliance
Onflo uses Twilio to power SMS messaging, which means any district sending text notifications through Onflo must complete Twilio's A2P 10DLC (Application-to-Person, 10-Digit Long Code) registration. This is a carrier-level requirement, not an Onflo-specific one. It applies to any organization using SMS through Twilio's infrastructure, and it exists so mobile carriers can verify that messages are coming from a legitimate sender and that recipients have knowingly agreed to receive them.
One of the most common reasons a campaign gets rejected or delayed is a missing or incomplete Terms & Conditions page. This article walks through what carriers are looking for and what your district needs to publish before registering.
Why This Matters
Every A2P 10DLC campaign is reviewed by The Campaign Registry (TCR) before it's approved. Reviewers check that your Terms & Conditions and Privacy Policy pages are publicly accessible, clearly written, and contain specific SMS-related language. If that language is missing, the campaign is typically rejected and has to be resubmitted — which adds delay to when your district can start sending text messages.
What Your Terms & Conditions Page Needs
Your district's T&C page should be publicly accessible (no login required) and include the following:
| A clear statement that your district sends SMS/MMS messages | Include a brief description of what those messages will contain (for example, attendance alerts, general announcements, or communications from your service desk). |
| Expected message frequency | Either a specific estimate (for example, "up to 4 messages per month") or a general statement such as "message frequency varies." |
| A message and data rates disclosure | Lets recipients know their mobile carrier may charge standard rates for messages received. |
| Opt-out instructions | State that recipients can reply STOP to unsubscribe at any time. |
| Help instructions | State that recipients can reply HELP for assistance. |
| A link to your Privacy Policy | Should separately confirm that mobile opt-in information will never be shared or sold to third parties for marketing purposes. |
A simple compliant example might read:
"By providing your mobile number, you agree to receive text messages from [District Name] regarding [purpose, e.g., attendance and general announcements]. Message frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help."
Common Pitfalls to Avoid
Consent can't be bundled
Consent boxes must default to unchecked
Your Privacy Policy needs to mention SMS specifically
The T&C and Privacy Policy links need to be live before you submit
Opt-in for text messages needs to be its own, separate agreement. It can't be buried inside a general terms of service or required as a condition of registering for another service.
Any opt-in checkbox or toggle needs to start off, not on.
A generic privacy policy that never references text messaging is a common cause of rejection — it needs a line confirming that phone numbers collected for texting won't be shared with third parties.
Reviewers will visit the pages you provide, so draft pages or placeholder URLs will hold up approval.
Getting Started
Twilio's own onboarding guide is the most current source for exactly what's required during registration, including message examples and use-case guidance: A2P 10DLC Campaign Onboarding Guide (Twilio Help Center).
If your district needs help drafting or reviewing your Terms & Conditions or Privacy Policy language before submitting for A2P 10DLC registration, reach out to your Implementation Manager. We're glad to help review your draft before you submit it.