What's happening?
There will be updated requirements for several fields when submitting 10DLC campaigns. In order to ensure the most success for vetting, please make sure your campaigns follow these new requirements.
What do I need to do?
Ensure that your campaigns have the following new elements:
Campaign Description
Messaging frequency needs to be disclosed.
If donations are collected, it must be clearly stated.
If donations are a part of the campaign, the statement “Donations will be secured through ____ and Accreditation listing is _____” should be provided.
Message Flow/Call to Action (CTA) (Opt-In)
Provide the specific link, written form, or screenshot of the CRM used to collect opt-ins.
Use the “CTA (Call-to-Action), Privacy Policy and/or Terms and Conditions Multimedia Upload” field to attach the screenshot, if applicable.
If Verbal Opt-in is collected, please add the script that describes the opt-in flow.
The Call to Action may only apply to text messaging. If your customer also uses emails or voice calls, their opt-in should be collected separately.
Phone Numbers cannot be a required field on the website where opt-in is collected. This is considered a forced opt-in. Please ensure that this field is optional on the website.
Privacy Policy and Terms and Conditions
While not currently required, we highly recommend using the Privacy Policy and Terms and Conditions fields. Campaigns will not be rejected for these fields being empty now, but they will likely be required in the future.
While the fields are not required, you must link to the Terms and Conditions and the privacy policy within the CTA field if you do not include them in the designated fields.
Privacy Policy must include a disclaimer that no mobile opt-in will be shared with third parties for marketing purposes.
Terms of Service must have an SMS disclosure that includes the types of messages consumers can expect to receive, texting cadence, message and data rate notices, privacy policy links, and opt-out instructions.
Sample Messages
Sample Messages must correspond to the registered use case. If a campaign is registered under multiple use cases (mixed), a sample message for each use case should be provided, or the use cases should be addressed in the description field.
For example, if you register under the marketing use case, state in the description the use of texts for promotional purposes.