A2P SMS Messaging Registration Guidelines

📘

We're here to help

The following A2P SMS messaging registration best practices apply to both 10DLC registration as well as Toll-Free registration. If you have questions about any of the registration practices, please contact FreeClimb Sales.

Business/Company Name

• This is the name of the business/company the messages are being sent on behalf of. If you are an ISV registering the use case, this should not be your company.
• Should match what is on the business website listed on the form.
• Should match the EIN registration exactly (this is particularly important for 10DLC registration).

Business/Company Address

• Should match any published addresses on the business website.
• Should match the address on the EIN registration (this is particularly important for 10DLC registration).

Business/Company Contact

• Should be the contact for the end user. If you are a vendor sending messages on behalf of a company, the contact listed here must be a contact at that company.
• The contact’s email domain should match the company website/domain.

Business/Company Website

• Should include a Terms & Conditions section which includes a reference to SMS messaging.
• Should include a Privacy Policy which includes a reference to SMS messaging.

Sample Messages

• Submit as many messages as needed to accurately show what you will be sending in production. You can use brackets to show data that may be variable (such as a one time passcode). If you feel the form does not provide enough sample messages for your use case, please contact FreeClimb Sales with additional details.
• Ensure that the sample messages do not have any prohibited content.

Opt-In

• Consumers must opt-in to receive messages from non-consumers. Non-consumers are required to track this opt-in and may be required to provide evidence of an opt-in.
• A good opt-in message should be clear, concise, and transparent, effectively communicating what the recipient is signing up for, the frequency of the messages, and how to opt-out.
• Any page that is asking for someone to type in their phone number to receive messages must include opt-in language that is easily visible for a customer to read after they have entered their phone number and before they click the submit/contact/save button.
  • If there is more than one page asking for a phone number on the website, each of the pages has to include the opt-in language.
• Opt-in language has to include something that says the customer is agreeing to being contacted by SMS messaging/texting/SMS.
• If the opt-in is completed on a form, please provide a sample of that form or a publicly available URL where it can be accessed.
• Sample Opt-In flows/language
  1. Within an IVR: “Press one to receive a text message with a link to directions to our store.”
  2. Customer Signup form: “By submitting this form, you agree to receive text messages from < company name > at the phone number used when signing up. Reply HELP for assistance and STOP to cancel. Msg and data rates may apply.”
  3. Text opt-in: “Get weekly updates on our latest products and special offers! Text YES to subscribe.”
• Double Opt-In: For marketing/promotional opt-in, it is recommended that you complete a double opt-in. For instance, the customer provides their phone number on a form on a business' website in exchange for a discount on their first purchase (first opt-in). The business sends them a text message acknowledging the first opt-in that includes the instruction, “Reply YES to receive promotional messages.” The customer replies, “YES” (second opt-in).