Skip to content
Contact Us
  • There are no suggestions because the search field is empty.

The Need-To-Know For A2P Registration Requirements

Summary

This article is meant to serve as a streamlined version of our more comprehensive article: A2P Compliance Updates. For more detailed information on what's required for A2P registration, please review that article. 

If you are being sent this article, it is because the consent information we have on file for your organization is out of date or no longer compliant. Around mid-March 2026, the carriers (AT&T, Verizon, T-Mobile, etc.) became stricter about the requirements for collecting consent for texting. Because of this, to register a new shared inbox, we must supply them with documentation showing that your organization collects consent compliantly and that your organization has the proper disclosures.

Please Note:

As part of your service here with Mongoose, we stay on top of changing A2P requirements. This article may have been sent to you as part of our proactive outreach to ensure that you are not caught by surprise when it comes to these updated requirements.

We are recommending that you update your consent and A2P supports so that your organization is future-proofed.

This update in requirements does not change or affect any previously/currently registered inboxes or SMS numbers.

What We Need to Supply to Twilio for Review

The pieces that Twilio checks for A2P compliance are: a form, your organization's privacy policy, and your organization's SMS terms and conditions.

Which Form Should you use for Submission:

Any form that your organization uses to collect phone numbers for the purposes of texting.

  • The form can be (but is not limited to):

    • an intake form

    • a request more information form

    • an event sign up form

  • The best form to use to ensure a quick and successful registration review is one that matches all the following criteria:

    • Is a public-facing form, meaning no sign in is required to access the form

    • Is an evergreen form, meaning it will not expire or not be accessible after a certain date

    • Has a phone number field on it, meaning it captures phone numbers for the purpose of texting

For the Privacy Policy:
  • If your organization has a privacy policy that's linked in the footer of your website, this is the one that Twilio will be checking
  • If you do not have a privacy policy linked in the footer of your organization's website, please consider adding the privacy policy to it to ensure a quick and successful registration review

Twilio will not accept privacy policies that are PDFs, or ones that are not linked on your organization's website

For the SMS Terms and Conditions:
  • If your organization does not currently have SMS terms and conditions, the example below checks off all of the requirements that Twilio and the carriers are looking for

Next Step - The Updates

Now that you've gathered your form, privacy policy, and SMS terms and conditions, here's what will need to be updated.

Important Note:

Any deviation from the information below will result in a delayed review process. Twilio and the carriers do not allow for any abiguity when it comes to these requirements.

If there is something below that is not getting approved by your legal team, please let us know what it is and the alternative your legal team is suggesting. With that information we can reach out to Twilio's compliance team to see if any alternatives would pass registration.

On the Form:

Directly underneath the phone number field, there must be a single, unselected and non-required checkbox along with the consent statement. It should look like this on your form:

Phone Number:_______________________

[   ] I agree to receive text messages from [name of organization]. [Name of organization] utilizes text messaging to send out important notifications and updates about **. Message frequency may vary. Message and data rates may apply. You can text STOP to opt out at any time. Text HELP for assistance. For more information visit our privacy policy (hyperlinked to the organization's privacy policy) and SMS terms and conditions (hyperlinked to the organization's SMS terms and conditions).

**Please fill in what types of messages you wish to communicate via SMS. This can be broad or more specific. Ex: ...about application and enrollment deadlines, application updates, event notifications, and reminders.

In the Privacy Policy:

Carriers now require that you include specific SMS language in the privacy policy. There are two routes that you can take here:

  1. Separating the privacy policy and the SMS terms and conditions
  2. Adding the SMS terms and conditions within your privacy policy

1. For organizations that want to separate the privacy policy and the SMS terms and conditions, the following SMS sharing statement must be added to the privacy policy:

Mobile phone numbers and SMS opt-in consent are collected solely for the purpose of delivering the text messages described at the time of opt-in. SMS opt-in data and consent will not be sold, rented, shared, transferred, or disclosed to any third parties or affiliates for marketing or promotional purposes.

The clearer this information is defined in the policy, the better. This statement should ideally be added under a "data sharing" section in the privacy policy. If your policy does not have a "data sharing" section, please add it where it makes the most sense.

2. If your organization chooses to include all of the SMS disclosures into the privacy policy, add a section in the policy and label it: SMS Terms and Conditions.

The example below should be used verbatim (including how they're sectioned), except for the information that's in the [brackets]. Everything in brackets can be changed to fit your organization, or you can choose to leave it as is.

SMS Terms and Conditions

[Organization name] sends text messages using an SMS messaging service to communicate with students about [application and enrollment deadlines, application updates, event notifications, and reminders.]

Opt-In

[Prospective students] may opt in to receive SMS messages by completing an [information request form, creating an account, or updating communication preferences.] Consent to receive SMS messages is optional and not a condition of [applying, enrolling, or participating in the admissions process.] Message frequency may vary.

Opt-Out

Text STOP to stop receiving text messages. Text HELP for help.

SMS Privacy Disclosure

Mobile phone numbers and SMS opt-in consent are collected solely for the purpose of delivering the text messages described at the time of opt-in. SMS opt-in data and consent will not be sold, rented, shared, transferred, or disclosed to any third parties or affiliates for marketing or promotional purposes.

We do not share text messaging originator opt-in data or consent with any third parties, except with trusted service providers that assist us in delivering SMS communications (such as messaging platform providers), and only for the purpose of facilitating message delivery and related support services.

Final Step - Submission or Holding

With your supports ready, please fill out and submit this form: A2P Consent Info Form

Once your form, privacy policy, and SMS terms and conditions are all up to date and adhere to the above guidelines, we will take one of the following actions:

  • Provide this information to Twilio to register a new inbox
    • The current timeline for Twilio's review is 1 week. If there are any deviations from the above guidelines, the review process + opening a support case with Twilio can take 2+ weeks. 
  • Hold on to your information so that you are ready to go if you would like to add a new inbox to your account in the future
    • Please note that since there would not be a need to submit this information to Twilio right away, we cannot guarantee that your supports are 100% compliant until we submit things to Twilio.
Important Tip:

If your organization is not adding any new inboxes, it's still a good idea to work on getting all of this updated to future-proof the way you are collecting consent. Doing so will ensure that you're set up for the future if you choose to add a new inbox later on, or if at any moment you encounter high opt-outs that causes your number(s) to be flagged. In the event that this were to occur, we would need to provide Twilio with proof that you are collecting consent in a compliant way.

Having this ready to go ensures there are no delays if either of these scenarios plays out.

Questions?

Your support team here at Mongoose is ready to help and ensure your supports are compliant. Please do not hesitate to reach out with any questions: support@hellomongoose.com