Contact Source URL

Carriers require that text message senders provide opt-in mechanisms for users, where a user can knowingly opt in to receiving text messages. For a use case to pass Manual Vetting, your website must include a valid Contact Source URL, where your opt-in form is located. You will be asked to provide this URL in the Use Case Registration form.

Contact Source Requirements

The Contact Source URL is a valid URL where your organization collects phone numbers from users. This URL should take the person verifying the application directly to the phone number collection page. To fulfill the requirements for the contact source URL, this page must contain the following:

• Phone Number Field: The form must include an optional phone number input field. The phone number field can't be required, as this is considered "forced" consent.
• Opt-in Language: a clear disclosure that informs the user that they are opting in to receiving text messages from your organization. More requirements detailed below.
• Clear Association with your Organization: It must be clear that this URL is directly associated with the organization provided in the Brand Registration. More details below.

Example

Here's an example of what a valid contact source form may look like:

Opt-in Language

The opt-in language should be easily discoverable and in close proximity to the phone number field. Opt-in language must contain the following:

• It should clearly state that by providing your phone number, you will receive text messages
• The type of messages being sent (account-related, informational, etc..)
  • If you are registering for the political or charity use case, please read the section below for an additional requirement.
• Organization name
• Message and data rate disclosure
• Message frequency
• Instructions on how to request help (Reply HELP for help)
• Instructions on how to opt-out (Reply STOP to unsubscribe)
• Links to the Privacy Policy and Terms & Conditions

For example: 

You can use our Opt-In Language Generator to help craft compliant opt-in language for your campaign.

Special Use Cases

If you are registering for the political or charity use case, the message type in the opt-in language must align with the use case. For these use cases, there should be only one type of message, and no additional types should be included. For Example:

• Political: "By providing your phone number, you agree to receive political call-to-action text messages..."
• Charity: "By providing your phone number, you agree to receive donation-related text messages..."

If you are registering for the Political use case but also intend to send texts related to donations, your opt-in language must reflect this. For example: "By providing your phone number, you agree to receive political call-to-action or donation-related text messages..."

Clear Association with your Organization

An acceptable contact source URL must be clearly associated with your organization in one of the following ways

• The URL matches your organization. For example, if the contact source URL is located at https://www.bartletforamerica.com/subscribe and the organization name is Bartlet for America
• The URL is linked from your main website. If the contact source is located on a third-party website, such as a donation page, the link to the form should be accessible from the organization's main website. For example, if your main website is https://www.bartletforamerica.com, and you have a donation form located at https://secure.actblue.com/donate/67899998212, then you must have a link to the donation page somewhere on the main website.

Before You Submit

Take this quiz to determine if your website fulfills all the necessary requirements for manual vetting.

Please write to support@getthru.io if you have questions or difficulty adding your website!