{"id":17283,"date":"2026-08-28T17:36:37","date_gmt":"2026-08-28T17:36:37","guid":{"rendered":"https:\/\/www.onflo.com\/learningcenter\/?p=17283"},"modified":"2026-08-28T17:36:37","modified_gmt":"2026-08-28T17:36:37","slug":"twilio-registration","status":"publish","type":"post","link":"https:\/\/www.onflo.com\/learningcenter\/uncategorized\/twilio-registration\/","title":{"rendered":"Twilio Registration"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Setting Up Your District's Terms & Conditions Page for SMS Compliance<\/h2>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

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.<\/p>

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.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Why This Matters<\/h4>

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 \u2014 which adds delay to when your district can start sending text messages.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What Your Terms & Conditions Page Needs<\/h2>

Your district's T&C page should be publicly accessible (no login required) and include the following:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\n\n\n\n\t\n\t\n\t\n\t\n\t\n\t
A clear statement that your district sends SMS\/MMS messages<\/strong><\/td>Include a brief description of what those messages will contain (for example, attendance alerts, general announcements, or communications from your service desk).<\/td>\n<\/tr>\n
Expected message frequency<\/strong><\/td>Either a specific estimate (for example, \"up to 4 messages per month\") or a general statement such as \"message frequency varies.\"<\/td>\n<\/tr>\n
A message and data rates disclosure<\/strong><\/td>Lets recipients know their mobile carrier may charge standard rates for messages received.<\/td>\n<\/tr>\n
Opt-out instructions<\/strong><\/td>State that recipients can reply STOP to unsubscribe at any time.<\/td>\n<\/tr>\n
Help instructions<\/strong><\/td>State that recipients can reply HELP for assistance.<\/td>\n<\/tr>\n
A link to your Privacy Policy<\/strong><\/td>Should separately confirm that mobile opt-in information will never be shared or sold to third parties for marketing purposes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A simple compliant example might read:<\/p>

\"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.\"<\/em><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Common Pitfalls to Avoid<\/h2>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Consent can't be bundled<\/strong>\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Consent boxes must default to unchecked<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Your Privacy Policy needs to mention SMS specifically<\/strong>\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The T&C and Privacy Policy links need to be live before you submit<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

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.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Any opt-in checkbox or toggle needs to start off, not on.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A generic privacy policy that never references text messaging is a common cause of rejection \u2014 it needs a line confirming that phone numbers collected for texting won't be shared with third parties.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Reviewers will visit the pages you provide, so draft pages or placeholder URLs will hold up approval.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Getting Started<\/h2>

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)<\/a><\/strong><\/span>.<\/span><\/p>

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.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

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...<\/p>\n","protected":false},"author":44,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_kad_post_transparent":"default","_kad_post_title":"default","_kad_post_layout":"default","_kad_post_sidebar_id":"","_kad_post_content_style":"default","_kad_post_vertical_padding":"default","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[450,451,1],"class_list":["post-17283","post","type-post","status-publish","format-standard","hentry","category-best-practices","category-getting-started","category-uncategorized","tag-integrations","tag-call-center","tag-texting"],"_links":{"self":[{"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/posts\/17283","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/comments?post=17283"}],"version-history":[{"count":24,"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/posts\/17283\/revisions"}],"predecessor-version":[{"id":17323,"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/posts\/17283\/revisions\/17323"}],"wp:attachment":[{"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/media?parent=17283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.onflo.com\/learningcenter\/wp-json\/wp\/v2\/categories?post=17283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}