- Print
- DarkLight
- PDF
Campaign registration Requirements & Recommendations
Campaign Registration Requirements
10DLC campaign registrations go through a manual vetting process and include a $15.00 campaign verification fee during external vetting. If a campaign is denied, additional charges may apply for resubmission.
To help ensure your campaigns are approved, please follow these requirements and best practices listed below.
Registration Requirements (Must-Have Summary)
Compliance requirements are constantly changing. Here are the latest key updates:
Privacy Policy and Terms and Conditions:
Having online Privacy Policy and Terms and Conditions documents will be mandatory for campaign registration. Additionally, the organization's Privacy Policy must include a statement specifically addressing mobile data, clarifying that personal mobile information will not be sold or shared for promotional or marketing purposes. The wording can vary, but it should clearly convey something like: "No mobile information will be sold or shared with third parties for promotional or marketing purposes."
Website Opt-In Forms (if opt-ins are collected via website)
- Phone number field in Website Opt-In Forms: It is recommended to leave the 'phone number' field on opt-in forms as an optional field, as mandatory fields are now considered forced opt-ins. If the phone number field on the opt-in form is currently a required field, it needs to have a check box added next to the opt-in language for the user to check the box to agree to receive text messages.
- Opt-In language: Consent language must now include: message rates frequency information (e.g., "Message frequency varies. Message and data rates may apply"); HELP instructions; STOP instructions; donations solicitations disclosure (see below for more details); and a link to the message program privacy policy, or language referring to the privacy policy. Additionally, the opt-in language must be specific for texting and should not include email or phone call permissions, which need to be collected separately.
- Donations Disclaimer
For Charity and Political use cases a donation solicitations disclaimer must be included in the consent language (opt-in form), and at the CTA/Message Flow (campaign registration form). This disclaimer must explicitly indicate if donations [will] or [will not] be solicited via text messages under this 10DLC campaign. Sample language: "Donations will be solicited." or "Donations will not be solicited."
Campaign Registration Requirements
Message Flow/Call-to-Action (CTA) Description
This field should provide a detailed description of the path a person needs to follow to opt-in to the campaign, therefore giving consent to the sender to receive their messages. The call-to-action must inform the user of the nature of the program. It should clearly specify the exact location (include links if its a website) where it happens. Finally it must include a donation solicitation disclaimer (Donations will [or will not] be solicited).
Here are common ways consent could be obtained for text messaging programs.
Type | Description & Requirements | Message Flow/CTA Example |
---|---|---|
Website Opt-In | Users can opt in by completing a Contact or Sign-up form in the organization's website. The web from should include language that clearly explains that the person is consenting to receive text messages and understands the nature of the program. Consent language example: “By submitting this form and signing up for texts, you consent to receive text messages from [Organization name] at the number provided. Msg & data rates may apply. Msg frequency varies. Unsubscribe at any time by replying STOP. Privacy Policy [link] & Terms [link]. Donations disclaimer must be included for Charity or Political use cases:("Donations will be solicited." or "Donations will not be solicited.").” Additionally, the organization's website must be compliant with TCR guidelines, see this article for more details about a TCR Compliant Website | "Voters opt-in by visiting https://www.organizationWebsite and sign up for texts by filling out the [Form title] form located at the bottom of the main page under the Contact Us section. They then check a box agreeing to receive text messages from [OrganizationName]. Donations may be solicited. |
Printed Form | The customer provides consent by filling out a printed form. A mock up of the form that includes consent language must be sent to support@echo19.com to be included to the campaign registration form for TCR verification | "The user fills out a form at a campaign in-person event, this form includes opt-in language for the user to agree to receiving text messages from this organization" |
Inbound Text | The CTA must clearly indicate that the customer is opting into text communication by initiating the conversation. The first message should always come from the customer. The process must clearly explain how the customer initiates contact, establishing implied consent. For example, "The user sends a text to start communication with the organization" or "The user opts in by texting a specific keyword to a designated phone number." The process should include both the keyword and the phone number | User opts in by sending 'VOTE' to phone number 1234567890 |
Note: If multiple opt-in methods are be used to collect opt-ins, you must list them all.
Links to Privacy Policy and Terms of Use
For TCR compliance, all campaigns must include the URLs for both the Terms and Conditions and the Privacy Policy. Even if these are available on the website, they must still be included within the campaign registration. The registration form includes fields to add these links, but should also be placed in the CTA itself.
Sample message(s)
The sample messages should align with the registered use case. They don't need to be the exact, approved messages that will be sent out; however, they should reflect the type of communication that will be delivered.
Privacy Policy requirements
Message Senders are responsible for protecting the privacy of Consumers’ information and must comply with applicable privacy laws. Message Senders should maintain a privacy policy for all programs and make it accessible from the initial CTA.
- The organization's Privacy Policy must include a statement specifically addressing mobile data, clarifying that personal mobile information will not be sold or shared for promotional or marketing purposes. The wording can vary, but it should clearly convey something like: "No mobile information will be sold or shared with third parties for promotional or marketing purposes."
- Any mentioning of 3rd Party Data Sharing, Renting, or Selling is disallowed unless the below disclosure is included: “All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.”
- If privacy policy already provides for data sharing or selling to nonaffiliated third parties, it needs to clarify that such data sharing or selling will not include a customer’s SMS opt-in data or consent status (because explicit, one-to-one consent is required for SMS).
- If privacy policy does not currently mention data sharing, you need to insert a similar clarification that you will not share SMS opt-in or consent status for non-service-related purposes.
Example: "We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. We may share your Personal Data, including your SMS opt-in or consent status, with third parties that help us provide our messaging services, including but not limited to platform providers, phone companies, and any other vendors who assist us in the delivery of text messages."
Donation Solicitations Disclaimer
For Charity and Political use cases, a donation solicitations disclaimer must be included in the consent language (opt-in form), and at the CTA/Message Flow (campaign registration form). This disclaimer must explicitly indicate if donations [will] or [will not] be solicited via text messages under this 10DLC campaign. Sample language: "Donations will be solicited." or "Donations will not be solicited."
Required Disclaimers and Examples
Consent Language / Opt-in Form Example:
"I would like to sign up for text updates and consent to receive text messages from [candidate or organization name] at the number provided. Msg & data rates may apply. Msg frequency varies. Text HELP for more information. Unsubscribe at any time by replying STOP. "Donations will be solicited."CTA/Message Flow Example:
"Customers opt in by visiting [link to Opt-in Form] and entering their phone number. They then check a box agreeing to receive text messages from [candidate or organization name]. The text messages will include political donation solicitations."
Campaign Registration Recommendations
Recommendation | Example |
---|---|
Consistency in brand name, website, and sample messages | The brand and website need to be the same that the ones you include in your sample messages. For example: If your brand name is ActionVote, but your sample messages say “Hi, this is Mike from OrganizationA...”, your campaign will be rejected |
Consistency in email domain and company name | If you register a brand as 'ABC Strategies', but you provide an email address with a personal &free email domain (like google, yahoo, hotmail, etc.), your campaign will be rejected. Note that this check only applies to large, well-known corporations that should have dedicated email domains |
Make sure you submit real, working websites | If you indicate that your customers opt-in to your messages via the website, but the website address you provide does not work, your campaign will be rejected |
Send messages according to the brand that you registered | For consultants, if you register a brand with your own organization’s information (e.g. Communications Strategy), but end up sending messages for your customers (e.g., Candidate A for mayoral campaign in Seatle), your campaign will be rejected |
Make sure opt-in is collected appropriately | Ensure you send messages only to the people who really want to receive them. Please refer to the CTIA guidelines to see detailed instructions and best practices on handling consumer consent |
The opt-in language needs to be available on your website if you indicated in the “message flow” field that a user opts into your campaign on your company website | If you collect the opt ins in your website, there should be an opt-in form on the website to collect the phone number. This section should include the following language, or similar, and a checkbox next to the disclaimer that any individual needs to check to be opted-in: [ ] "By providing your cell phone number, you are consenting to receive recurring automated text messages & automated calls from OrganizationName. Message frequency will vary. Message and data rates may apply. Text HELP for more information. Text STOP to stop receiving messages. Privacy policy and SMS terms available at: Privacy Policy" (provide link). Note: The privacy policy should state that you do not sell/share their mobile information fro marketing purposes. |
Express Opt In | Every place which requires a phone number on your website must have opt in language as well as a checkbox. This applies to contact pages, donation pages, etc. Opt in language must include consent and opt out instructions and links to Privacy Policy and Terms and Conditions |
Include the opt-out language in at least one of your sample messages | You need to include the opt out option in your sample messages, something like “Please reply STOP to opt out” |
Privacy Policy | The privacy policy CANNOT allow for the sharing/selling of end user's mobile information to third parties |
Do not include forbidden use cases | Make sure your campaign does not involve prohibited content such as sex, hate speech, firearms, or tobacco (CBD, cannabis included), etc. |
Please contact us at support@echo19.com if you have any questions.