The 10DLC hub manual vetting team reviews registrations for alignment of the brand and the campaign attributes before campaigns are fully processed at the Campaign Registry. For example, the company’s legal or DBA name identified in the Brand registration must match the brand identity in the message content of the Campaign registration. The call-to-action language, opt-in and opt-out process, and Privacy Policy are also checked for compliance requirements. Prior to submitting a brand and campaign registration, use the below guidelines to reduce the likelihood of rejection and remediation iterations, delays and fees.
Brand Registration
- Brand’s company name is found in Google search.
- Brand is legitimate without fraudulent or inauthentic representation.
- Brand name is consistent across all materials, including campaign details, website and message content.
- Email address is consistent across all materials, including campaign details, website and message content.
- Email address is brand specific rather than a personal use domain (e.g. @aol.com, @gmail.com, @hotmail.com, @msn.com, @yahoo.com).
- If the brand is a Publicly Traded Company, the business contact email 2FA verification is completed.
- Phone number is consistent across all materials, including campaign details, website and message content
- Website is legitimate and clear in purpose or relationship to the brand.
- Website is a dedicated domain rather than a social networking page (e.g. Craigslist, Facebook, LinkedIn).
- Website does not mention sharing information with third parties or affiliates.
Campaign Registration
- Use case is not prohibited (e.g. insurance reseller, cannabis/CBD, sole proprietor, sexual content).
- For internal testing programs, the campaign is registered as a Low Volume use case.
- Direct Lending or Loan Arrangement attribute is checked for loan use case.
- Sample messages are accurate representation of the brand or use case.
- Sample messages are adequately descriptive of the use case.
- Sample messages are specific to the associated brand.
- Opt-in message contains brand name, a message frequency disclosure, data rates disclosure, help instructions, and opt-out language.
- HELP message contains brand name and customer care contact information (email, phone number, support website).
- Opt-out message contains brand name, confirms opt-out, and states no further messages will be sent.
- Privacy Policy and Terms & Conditions URLs provided.
- CTA/Message Flow field includes detailed description of the opt-in process.
- Full CTA verbiage is included in the CTA/Message Flow field (see Call-to-Action Attributes below)
- Website is provided on campaign form.
- Website is live and accessible for vetting.
- Website appears legitimate and clear in purpose or relationship to the use case.
- CTA/Message Flow field indicates whether website is used to obtain consent.
- If a website is used to obtain consent, the website’s URL is provided in CTA/Message Flow field.
Call-to-Action Attributes
- Method of obtaining consent is adequate for intended use case (implied, expressed, expressed written).
- CTA verbiage includes adequate description of use case, the brand name, message frequency, data rates disclosure, help instructions, opt-out instructions, and a link to the privacy policy.
- If webforms are used for opt-in, the phone number field must be optional. If the phone field is required, an optional opt-in checkbox that is not pre-checked must be used.
Rejection Codes and Remediations
To assist in identifying rejection reasons and next steps, here are the most common rejection reasons, their rejection codes and the remediation steps required to resolve them.
| Rejection Reason | Rejection Code | Remediation Required |
|---|---|---|
| "Campaign Attributes do not match website and/or sample message content" | 501 | Ensure the selected campaign attributes align with the website, campaign description, and message samples. Note: Attributes such as “Embedded URL” must be selected if URLs will be used. |
| "Inaccurate Registration. Inconsistency between sample message and use-case." | 502 | Ensure sample messages demonstrate the use case described in the campaign description. |
| "Inaccurate Registration. Inconsistency between website, sample messages or incomplete sample messages." | 503 | Ensure website details align with the sample messages, and that sample messages are complete and demonstrate the use case described in the campaign description. |
| "Unable to translate, for proper review, campaign must be in English" | 506 | Ensure all campaign components, such as the description, CTA, message samples, etc. are either in English or may be translated into English for manual review. |
| "Repeated use of same EIN for multiple different brands" | 511 | Ensure that the EIN provided is aligned with the end-brand for the campaign and is not the EIN of a reseller or service provider. |
| “Campaign Attributes do not match website and/or sample message content.” | 601 | Ensure the selected campaign attributes align with the website, campaign description, and message samples. Note: Attributes such as “Embedded URL” must be selected if URLs will be used. |
| “Inaccurate Registration. Inconsistency between sample message, description, attributes and/or call to action with selected use-case.” | 602 | Ensure the campaign call-to-action, description, and sample messages all align, and sample messages demonstrate the selected use case for the campaign (e.g., If the use case selected is OTP/2FA, the sample messages should demonstrate password retrieval of a one-time code, not a different use case such as customer care or marketing.) |
| "Inaccurate Registration. Inconsistency between brand, description, website and/or sample messages." | 603 | Ensure the identified brand aligns on the website, campaign description, the sample messages and any other materials, and that sample messages are complete and demonstrate the use case described in the campaign description. |
| “Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, msg frequency and associated fees disclosures. Opt-out message must contain brand name and indicate that no further messages will be sent. HELP message must contain brand name and contain support contact (email, phone number, or support website)” | 611 | Ensure all appropriate components are included in the opt-in, opt-out, and help messages. |
| “Prohibited Content; Cannabis” | 701 | The use case is prohibited for cannabis-related content. No remediation is available. |
| “Prohibited Content; Guns/Ammo-Failure to age gate” | 702 | The use case is prohibited for content related to firearms, ammunition, fireworks or other explosives. Implement an age gate to ensure minors cannot subscribe to receive this content. |
| “Prohibited Content; Explicit sexual” | 703 | The use case is prohibited for sexually explicit content. No remediation is available. |
| “Prohibited Content; Gambling” | 704 | The use case is prohibited for content related to gambling. No remediation is available. |
| “Prohibited Content” | 705 | The use case included prohibited content. No remediation is available. |
| “Prohibited Content; Alcohol-Failure to age gate” | 706 | The use case is prohibited for alcohol-related content without adequate age gating. Implement an age gate to ensure minors cannot subscribe to receive this content. |
| “Prohibited Content; Tobacco / Vape-Failure to age gate” | 707 | This use case is prohibited for tobacco-and/or-vape-related content without adequate age gating. Implement an age gate to ensure minors cannot subscribe to receive this content. |
| “Lead Gen/Affiliate Marketing prohibited; other” | 708 | This use case is prohibited for lead gen/affiliate marketing content. No remediation is available. If you believe this is a misunderstanding of the use case, ensure no third-party/affiliate information sharing is mentioned on the website. |
| “Lead Gen/Affiliate Marketing prohibited; high risk financial services.” | 709 | The use case is prohibited for lead gen/affiliate marketing or high risk financial services. No remediation is available. If you believe this is a misunderstanding of the use case, ensure no third-party/affiliate information sharing or high-risk financial services are mentioned on the website. |
| “Reseller / Non-compliant KYC. Register the brand info, not the agency behind the brand” | 710 | The “brand” registered for 10DLC must be the campaign’s content provider and cannot be the agency or software provider behind the brand. |
| “Repeated use of same EIN for multiple different brands” | 711 | Ensure that the EIN provided is aligned with the end-brand for the campaign and is not the EIN of a reseller or service provider. |
| “Misleading Registration. Based on details submitted, Campaign appears to be Direct Lending Arrangement but appropriate Content Attribute was not selected.” | 712 | Ensure all appropriate campaign content attributes are selected. |
| “Appears to be large company or company that would have an official email domain. Check for fraud, use official / working email domain.” | 713 | Ensure the email addresses submitted with the campaign are official company email addresses with company domains and not personal accounts. |
| "Not Sole Proprietor. Does not meet small business Sole Prop (EIN) criteria set by TCR and mobile carriers." | 801 | Sole Proprietors are not supported. No remediation is available. |
| “Sole Proprietor. Not yet authorized.” | 802 | Sole Proprietors are not supported. No remediation is available. |
| “Call to Action forces an Opt-In consent because it is missing the "Check Box". Check box either not present or mandatory causing a forced opt in.” | 803 | The CTA requires a checkbox demonstrating end users may voluntarily provide consent to opt-in to text messaging. |
| “Unable to verify, need working website or online presence provided for brand validation.” | 804 | Website must be functional. If a website is used to obtain consent, include the specific URL for the web consent page within the CTA field in the campaign form. |
| “Compliant privacy policy is required, add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties)” | 805 | Ensure a link to the Privacy Policy or appropriate SMS opt-in non-sharing disclosure is provided. If the privacy policy URL is provided, the policy must include a statement specifying SMS opt-in consent is not shared. |
| “Add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties). Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, msg frequency and associated fees disclosures. Opt-out message must contain brand name and indicate that no further messages will be sent. HELP message must contain brand name and contain support contact (email, phone number, or support website)” | 851 | Ensure a link to the Privacy Policy or appropriate SMS opt-in non-sharing disclosure is provided. If the privacy policy URL is provided, the policy must include a statement specifying SMS opt-in consent is not shared. Ensure all appropriate components are included in the opt-in, opt-out, and help messages. |
| “Unable to verify, needs compliant and accurate CTA information. Update with specific path for mobile opt-in, HELP instructions, STOP instructions, message frequency disclosure, “message and data rates may apply” disclosure and link to the message program privacy policy, or language referring to the privacy policy.” | 806 | Provided CTA details must be complete and compliant, ensuring end-users are fully aware they are opting in to receive messages and are not required to do so in order to participate. Furthermore, all aspects of the CTA must be fully represented in both the campaign form and the live CTA. |
| “Needs compliant and accurate CTA information, Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, msg. frequency and associated fees disclosures. Opt-out message must contain brand name and indicate that no further messages will be sent. HELP message must contain brand name and contain support contact (email, phone number, or support website)” | 861 | Provided CTA details must be complete and compliant, ensuring end-users are fully aware they are opting in to receive messages and are not required to do so in order to participate. Furthermore, all aspects of the CTA must be fully represented in both the campaign form and the live CTA. Ensure all appropriate components are included in the opt-in, opt-out, and help messages. |
| “Unable to verify, inauthentic website” | 807 | Website cannot be verified, or appears generic/incomplete. |
| "Campaign has been declined 5+ times, without sufficient updates. Each denial incurs in a vetting fee. For questions, please reach out your DCA." | 808 | Review previous rejections and perform appropriate remediation accordingly. |
| "Campaign has requested a Number Pool but does not meet the requirements to be a Number Pool eligible campaign." | 810 | Number Pool campaigns require T-Mobile special business review. |
| “Campaign contains adult content but age gate attribute is not selected.” | 1001 | Age-Gated Content attribute must be selected if the campaign includes age-gated content. |
| “Campaign is for direct lending or loan arrangement and is missing the content attribute indicating direct lending.”” | 1002 | Direct Lending or Loan Arrangement attribute must be selected if the campaign includes direct lending or loan arrangements. |
| “Brand website is inaccessible/does not exist/error status.” | 1003 | Ensure the brand’s website is live and accessible for vetting. |
| “The brand website is lacking sufficient information about the company and its products.” | 1004 | Ensure the brand’s website is accessible for vetting and includes sufficient information about the brand. |
| “Campaign registration is not unique or duplicate campaign.” | 2001 | Ensure each campaign is unique for the brand. |
| “Unclear campaign description.” | 2002 | Ensure campaign description provides adequate details on the purpose/use case. |
| “Campaign description does not match declared use case(s).” | 2003 | Ensure the campaign description aligns with the campaign use case. |
| “Campaign description does not match sample messages.” | 2004 | Ensure sample messages demonstrate the selected use case for the campaign. (e.g., If the use case selected is OTP/2FA, the sample messages should demonstrate password retrieval of a one-time code, not a different use case such as customer care or marketing.) |
| “Undeclared use case.” | 2005 | Ensure all intended use cases are selected and that sample messages align. |
| “Brand referenced in campaign description does not match registered/DBA brand.” | 2006 | Ensure brand name is consistent across all materials. |
| “Website provided for CTA is inaccessible/does not exist/error status.” | 3000 | If a website is used to obtain consent, include the specific URL for the web consent page within the CTA field in the campaign form. Ensure the website is functional and accessible for vetting. |
| “Call-to-action does not obtain sufficient consent.” | 3001A | Method of obtaining consent must be adequate for intended use case (implied, expressed, expressed written). |
| “Call-to-action does not contain registered/DBA brand name.” | 3002A | Ensure brand name is included in the CTA and consistent with all other campaign materials. |
| “Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions. HELP for HELP or customer care contact information must be provided in either the CTA or the Terms & Conditions.” | 3003A | Ensure appropriate help instructions are included in the CTA. |
| “Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel) or STOP instructions in the Terms & Conditions.” | 3004A | Ensure appropriate opt-out instructions are included in the CTA. |
| “Call-to-action does not contain message frequency disclosure for recurring message program.” | 3005A | Campaigns sending recurring messages must indicate the frequency in the CTA (ie. “recurring” or “message frequency varies”). |
| “Call-to-action does not contain “message and data rates may apply” disclosure.” | 3006A | Ensure appropriate data rates disclosure is included in the CTA. |
| “Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions.” | 3007A | Ensure a link to the Terms and Conditions is provided and/or the messaging terms are included in the CTA. |
| “Call-to-action does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties.” | 3008A | Ensure a link to the Privacy Policy is provided. The privacy policy must include a statement specifying SMS opt-in consent is not shared with third parties. |
| “Call-to-action does not contain a robust age gate for age-restricted message program (alcohol/firearms/tobacco).” | 3010A | Campaign includes alcohol, firearm, or tobacco-related content without adequate age gating. Implement an age gate to ensure minors cannot subscribe to receive this content. |
| “Call-to-action is missing/inaccessible.” | 3011A | Thorough and complete materials demonstrating the CTA must be provided, such as screenshots, mockups, paper forms, IVR scripts. If a website is used to obtain consent, include the specific URL for the web consent page within the CTA field in the campaign form. If consent is not obtained through a website, include the statement, “website is not used to obtain opt-in.” |
| “Call to action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear.” | 3012A | All methods of obtaining consent must be adequate for the intended use case (implied, expressed, expressed written). Ensure end-users are fully aware they are opting in to receive messages and are not required to do so in order to participate. |
| "Call-to-action have an implied consent mechanism but use case or message flow are not conversational." | 3013A | Campaign CTA, use-case, and message samples must align with conversational messaging expected of implied consent. |
| "Campaign submitted as marketing, but marketing disclosure is missing from the Call to Action." | 3014A | Marketing campaigns must indicate in the CTA that messages will be promotional. |
| "Campaign submitted appears to be soliciting donations but donation solicitation disclaimer is missing from the Call to Action or is not appropriately advertised." | 3015A | Charitable organizations soliciting donations must indicate messages will solicit donations. |
| “Call-to-action (on website, or provide via screenshot/media file) does not obtain sufficient consent.” | 3001B | Method of obtaining consent must be adequate for intended use case (implied, expressed, expressed written). |
| “Call-to-action does not contain registered/DBA brand name.” | 3002B | Ensure brand name is included in the CTA and consistent with all other campaign materials. |
| “Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions.” | 3003B | Ensure appropriate help instructions are included in the CTA. |
| “Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel) or STOP instructions in the Terms & Conditions.” | 3004B | Ensure appropriate opt-out instructions are included in the CTA. |
| “Call-to-action does not contain message frequency disclosure for recurring message program.” | 3005B | Campaigns sending recurring messages must indicate the frequency in the CTA (ie. “recurring” or “message frequency varies”). |
| “Call-to-action does not contain “message and data rates may apply” disclosure.” | 3006B | Ensure appropriate data rates disclosure is included in the CTA. |
| “Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions.” | 3007B | Ensure a link to the Terms and Conditions is provided and/or the messaging terms are included in the CTA. |
| “Call-to-action does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties.” | 3008B | Ensure a link to the Privacy Policy is provided. The privacy policy must include a statement specifying SMS opt-in consent is not shared with third parties. |
| “Call-to-action does not contain robust age gate for age-restricted message program (alcohol/firearms/tobacco).” | 3010B | Campaign includes alcohol, firearm, or tobacco-related content without adequate age gating. Implement an age gate to ensure minors cannot subscribe to receive this content. |
| “Call-to-action is missing/inaccessible.” | 3011B | Thorough and complete materials demonstrating the CTA must be provided, such as screenshots, mockups, paper forms, IVR scripts. If a website is used to obtain consent, include the specific URL for the web consent page within the CTA field in the campaign form. If consent is not obtained through a website, include the statement, “website is not used to obtain opt-in.” |
| “Call to action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear.” | 3012B | All methods of obtaining consent must be adequate for the intended use case (implied, expressed, expressed written). Ensure end-users are fully aware they are opting in to receive messages and are not required to do so in order to participate. |
| "Campaign submitted as marketing, but marketing disclosure is missing from the Call to Action." | 3014B | Marketing campaigns must indicate in the CTA that messages will be promotional. |
| "Campaign submitted appears to be soliciting donations but donation solicitation disclaimer is missing from the Call to Action or is not appropriately advertised." | 3015B | Charitable organizations soliciting donations must indicate messages will solicit donations. |
| “Opt-in message/Confirmation MT does not contain registered/DBA brand name.” | 6001 | Include the brand/DBA name in opt-in/confirmation MT message. |
| “Opt-in message/Confirmation MT does not contain HELP instructions (for example, Reply HELP for help).” | 6002 | Include HELP or customer care instructions in opt-in/confirmation MT message. |
| “Opt-in message/Confirmation MT does not contain opt-out instructions (for example, Reply STOP to stop).” | 6003 | Include opt-out instructions in opt-in/confirmation MT message. |
| “Opt-in message/Confirmation MT does not contain message frequency disclosure (#msgs/mo, msg frequency varies, recurring messages, and so on.)” | 6004 | Include message frequency in opt-in/confirmation MT message. |
| “Opt-in message/Confirmation MT does not contain clear and conspicuous language about any associated fees or charges and how those charges will be billed. (for example, “message and data rates may apply” disclosure).” | 6005 | Include data rates disclosure in opt-in/confirmation MT message. |
| “Opt-in message/confirmation MT not provided.” | 6006 | Ensure opt-in/confirmation message is included and contains all appropriate components. |
| “HELP message does not contain registered/DBA brand name.” | 6007 | Include the brand/DBA name in HELP message. |
| “HELP message does not contain support contact (email, phone number, or support website).” | 6008 | Ensure adequate support information is provided in the HELP message. |
| “HELP message support contact email address does not match the registered brand support email address.” | 6009 | Ensure the support email address aligns with the registered brand name. |
| “Opt-out message does not contain registered/DBA brand name.” | 6010 | Include the brand/DBA name in opt-out message. |
| “Opt-out message does not indicate that no further messages will be sent.” | 6011 | Ensure opt-out message states “no further messages will be sent.” |
| “Sample message(s) do not contain registered/DBA brand name.” | 6012 | Include the brand/DBA name in sample message(s). |
| “Sample message(s) contain public URL shortener.” | 6013 | Ensure the URL shortener is aligned with the brand, or there is no indication of a public URL shortener in the sample messages. |
| “Sample message(s) use case does not match declared use case(s).” | 6014 | Ensure sample messages are complete and demonstrate the use case described in the campaign description. |
| “This brand or program references third-party job boards.” | 7001 | The use case is prohibited for content related to third party job boards. No remediation is available. If you believe this is a misunderstanding of the use case, ensure there is no mention of third-parties on the website. |
| “This brand or program includes lead generation or affiliate marketing.” | 7002 | This use case is prohibited for lead gen/affiliate marketing content. No remediation is available. If you believe this is a misunderstanding of the use case, ensure no mention of third-party or affiliate information sharing is mentioned on the website. |
| “This brand or program includes gambling.” | 7003 | The use case is prohibited for content related to gambling. No remediation is available. |
| “This brand or program includes high risk financial services.” | 7004 | The use case is prohibited for high risk financial services. No remediation is available. |
| “This brand or program includes illegal substances.” | 7005 | The use case is prohibited for content related to federally illegal drugs. No remediation is available. |
| “This brand or program includes disallowed sexual content.” | 7006 | The use case is prohibited for sex-related content. No remediation is available. |
| “This brand or program includes direct promotion of SHAFT.” | 7007 | The use case is prohibited for alcohol-related content without adequate age gating, or content related to firearms, ammunition, fireworks or other explosives. No remediation is available. If the use case is for alcohol, implement an age gate to ensure minors cannot subscribe to receive this content. |
| “This brand or program includes competitive marketing.” | 7008 | The use case is prohibited for content related to competitive marketing. No remediation is available. |
| “This brand or program includes weapons that are not legal in all 50 states.” | 7009 | The use case is prohibited for content related to illegal weapons. No remediation is available. |
| “This brand or program includes 3rd party debt collection” | 7010 | This use case is prohibited for content related to debt forgiveness, debt consolidation, debt reduction, or credit repair. No remediation is available. If you believe this is a misunderstanding of the use case, ensure third-party debt or credit services are not mentioned on the website. |
| “This brand or program includes marketing of CBD related products.” | 7011 | The use case is prohibited for content related to marketing of cannabis/CBD products. No remediation is available. |
| “This brand or program includes HATE speech.” | 7012 | The use case is prohibited for hateful content. No remediation is available. |
| “Brand website or campaign references charitable donations and the declared use case is not charity.” | 8001 | If the brand’s use case involves soliciting charitable donations, then the campaign use case must be Charity. Create a new campaign with the appropriate use case. |
| “Brand website or campaign references political content and declared use case is not political.” | 8002 | If the brand’s use case involves political content, then the campaign use case must be Political. Create a new campaign with the appropriate use case. |
| “Brand website or campaign references cart reminders but declared use case is not marketing.” | 8003 | If the brand’s use case involves cart reminders, then the campaign use case must be Marketing. Create a new campaign with the appropriate use case. |
| “Brand website or campaign references multiple use cases but only one declared use case is selected.” | 8004 | If multiple use cases are involved for the brand, then all must be selected, and all materials must align with these use cases. |
| “Campaign submitted is POLITICAL but does not contain the required information for this use case.” | 9001 | Ensure the Politician/Organization Name, FEC Committee ID, and Politician/Organization website are included in the campaign description and materials. |
| “Campaign submitted is CHARITY but does not contain the required information for this use case.” | 9002 | Ensure the brand’s information for proof of qualified as tax-exempt under Section 501(c)(3) is included in the campaign materials. |
Comments
0 comments
Article is closed for comments.