10DLC Campaign Checklist

Below is our checklist that guides you through each step of the campaign registration process to help you ensure that you don't miss any steps in campaign registration. Pitchprfct sees a high percentage of campaign acceptance when customers follow the checklist.

[ ] The Brand owner (or DBA) should be the business name that the end user receiving the SMS believes is sending them the message. (Check sample messages for match)

[ ] Confirm the contact email provided matches the Brand name and/or website URL.

[ ] Ensure that some form of online presence is provided - if no website is available, then a Facebook page, Google maps page, etc must be provided

[ ] Use Case Consistency - Ensure that the use case(s) selected match the sample messages and the reasons for sending messages that must be stated in the Campaign Description, Terms and Conditions, Campaign Attributes and SMS opt-in wording. Please note that the Use Case cannot be changed once the campaign has been created:

[ ] Ensure all pages, links and buttons on the site work properly (particularly contact form, privacy policy and terms links).

[ ] Make sure the content has no typos and accurately reflects the business and campaign.

[ ] Confirm there is no messaging that contains prohibited content, such as cash for homes, affiliate marketing or lead generation.

[ ] If the Brand’s Legal Name is different from the Brand’s website URL, ensure that the Legal Name is represented appropriately on the website (in the Terms and Conditions, Privacy Policy, or © by [Legal Name] in the website’s footer)

[ ] What the business does.

[ ] Who the business is sending messages to.

[ ] Why the business is sending the messages.

[ ] Message frequency (for now it is sufficient to write “message frequency may vary”)

[ ] Message Flow - Proof of SMS Opt-in

[ ] The explanation of how customers opt-in to receive SMS communications must be clear and complete.

[ ] You must provide demonstrable proof of the opt-in process for every declared method of opt-in

[ ] Wherever a Subscriber can opt-in (website, registration form, verbally, etc) the opt-in wording must have all of the required terms:

Example of compliant opt-in language: "By submitting this form, you consent to receive text messages from [Brand Name] for [Message Use Case(s) - reasons for sending SMS, for example “marketing and account notifications”]. Message frequency may vary. Msg and Data rates apply. Reply "STOP" to unsubscribe. Text HELP for support. Consent is not a condition of purchase. View Terms and Conditions (link) Privacy Policy (link)."

One of the following must be provided in the Message Flow description or provided as an attachment the campaign submission (if multiple opt-in methods are described, all of them must be demonstrated):

[ ] If opt-in is collected online: Provide a website URL containing the complaint opt-in wording and a check box that allows customers to select whether or not they want to opt in. The checkbox on the website cannot be pre-checked.

[ ] If opt-in is collected on a paper or digital form (registration form, service contract, etc): The form must contain the complaint opt-in wording and a check box that allows customers to select whether or not they want to opt in. The checkbox on the form cannot be pre-checked.

[ ] If opt-in is collected verbally: Include a the full script that captures the verbal consent (the script must contain all of the subscriber opt-in required terms, and it is communicated to those who are opting in), as well as screenshots or URLs of where the opt-in record is stored.

[ ] If opt-in is collected by texting START to opt-in (not valid for marketing use cases): Include the phone number customers text to opt-in and attach a screenshot or URL showing the opt-in process with compliant language, as it is presented to those who are opting in.

[ ] Contains the required disclaimer that mobile opt-in will not be shared with third parties

[ ] The privacy policy URL matches the website URL

[ ] If there is a company name and/or contact information in the privacy policy, it must match that of the brand

[ ] Contains a link to privacy policy

[ ] SMS disclosure that includes the types of messages consumers can expect to receive (use cases), message frequency, message and data rate notices, privacy policy links, HELP information, and opt-out instructions.

[ ] The Terms and Conditions URL matches the website URL

[ ] If there is a company name and/or contact information in the Terms and Conditions, it must match that of the brand

[ ] At least two messages must include opt-out instructions (e.g., “Text STOP to opt out”).

[ ] Ensure the sample messages match the use cases described in the Campaign Description, use case(s) and Campaign Attributes

[ ] If URLs or phone numbers are used in actual messages, include real examples of these in the sample messages.

[ ] Avoid using placeholders like {Name} or {Phone Number} in the sample messages.

[ ] Direct Lending: Yes (if applicable)

[ ] Number Pool - set to Yes ONLY if the campaign will be needing to use more than 49 phone numbers, and provided that their use case justifies the need for so many numbers (a separate request will need to be made to allow a number pool)

[ ] Embedded Links: YES (if applicable)

[ ] Phone Numbers: YES (if applicable)

[ ] Age Gated Content: YES (only if recipients must verify age before receiving messages).