Docs/Compliance
A2POpt-inPublic guide

Prepare SMS consent and opt-in pages

SMS consent must be clear, optional, and separate from the ability to request service, buy, book, or complete a transaction.

A customer must be able to submit a request or complete the normal transaction without agreeing to receive SMS messages. If there is an SMS opt-in checkbox, it should be unchecked by default and clearly optional.

Important

Do not make SMS consent a required condition of service, purchase, appointment booking, information requests, or transaction completion.

Required disclosures

The opt-in page should plainly state:

  • Message frequency varies.
  • Message and data rates may apply.
  • Reply STOP to opt out.
  • Reply HELP for help or contact support.
  • SMS consent is not required as a condition of purchase, service, appointment booking, information request, or transaction completion.
  • Mobile information is not shared with third parties or affiliates for marketing or promotional purposes.
  • Terms and privacy policy links are available.

Sample flow

The safest flow is a normal request form plus a separate optional SMS opt-in choice. If the customer does not opt in, the confirmation should simply say the request was submitted. It does not need to explain SMS again.

Review checks

Before submitting A2P, check the public page in a browser:

  • The page loads on the business domain.
  • The form submits successfully.
  • SMS opt-in is optional.
  • The success message is short and clear.
  • Terms and privacy links work.
  • Business name and website match the submitted brand.
Next step

Run the launch checklist.

Check the public pages, forms, billing, phone setup, and Trust Center state before sending real traffic.

Open checklist