As 10DLC continues to evolve, the wireless carriers have identified a gap in the registration process – campaigns are not being registered appropriately and do not adhere to the carriers’ codes of conduct. As a result, every newly created 10DLC campaign must go through vetting. Bandwidth has implemented its own internal pre-screening of campaigns before they are sent to our vetting partner for further review.
This article outlines all of the error codes you may receive from the Bandwidth vetting. In some cases, the same campaign may receive several rejection codes, so you can get the most comprehensive feedback to bring your campaign into compliance.
Brand Inconsistencies
Rejection Description | Rejection Code | Action to Resolve |
Brand Inconsistencies: No website URL or attachment was found in the campaign submission. |
1100 | The brand needs an online presence. Provide their online presence in the Brand Details. |
Brand Inconsistencies: No website or domain was found with the website URL. |
1101 | Confirm the brand website URL provided leads to the direct page. |
Brand Inconsistencies: Received a 'certificate verify failed' error for the website URL. |
1103 |
Confirm the brand website URL provided leads to the direct page. |
Invalid Call to Action
Rejection Description | Rejection Code | Action to Resolve |
Invalid Call to Action: No form of opt-in whatsoever was found in the description or message flow. |
2100 | Either the CTA is inaccurate and doesn't explain where the customers opt in to the campaign (website, verbal, written, etc.), or the opt-in is on the website, but there is no phone number field to add the phone number. |
Invalid Call to Action: This was determined to be a promotional campaign, but there was no mention of a written opt-in. |
2101 | Marketing/promotional content requires prior express written consent. Update the campaign with a valid opt-in collection method. |
Invalid Call to Action: This was determined to be an informational campaign, but no explicit means of opt-in was given. |
2102 | Informational messaging requires express consent from the consumer. The consumer needs to agree to receive texts for a specific informational purpose. Update the campaign with a valid opt-in collection method. |
Invalid Call to Action: Received a "certificate verify failed" error for the opt-in URL. |
2103 | Ensure the opt-in URL provided leads to the direct opt-in form. |
Invalid Call to Action: No website or domain was found with the given opt-in URL. |
2104 | Ensure the opt-in URL provided leads to the direct opt-in form. |
Invalid Call to Action: This campaign has verbal opt-in, but does not contain an explicit script of what the company says. |
2105 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures: brand name, types of messages being sent, message frequency disclosure, "message and data rates may apply" disclosure, HELP information, STOP information, and a link to the privacy policy and terms and conditions. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The script for verbal opt-in must contain instructions on how to reach the privacy policy. |
2106 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include a link to the privacy policy and terms and conditions. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The verbal opt-in script does not contain the brand name. |
2108 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the brand name. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The verbal opt-in script has no information about the type of messages being sent. Examples include but are not limited to: Marketing, MFA, reminders, etc. |
2109 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the types of messages being sent. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The verbal opt-in script contains no disclosure about the frequency of message delivery. |
2110 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as message frequency disclosure. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The verbal opt-in script has no disclosure that message and data rates will apply to messages sent. |
2111 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the "message and data rates may apply" disclosure. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The verbal opt-in script has no information detailing how a customer can stop receiving messages. |
2112 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as STOP information. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: The brand name could not be found in the opt-in form. |
2113 | Ensure the opt-in form includes all of the necessary disclosures, such as the brand name. |
Invalid Call to Action: The opt-in form should mention the types of messages a customer can expect to receive. |
2114 | Ensure the opt-in form includes all of the necessary disclosures, such as the types of messages being sent. |
Invalid Call to Action: The opt-in form must mention message frequency. |
2115 | Ensure the opt-in form includes all of the necessary disclosures, such as message frequency disclosure. |
Invalid Call to Action: The opt-in form has no disclosure that message and data rates will apply to messages sent. |
2116 | Ensure the opt-in form includes all of the necessary disclosures, such as the "message and data rates may apply" disclosure. |
Invalid Call to Action: The opt-in form must include information on how a customer can receive help. |
2117 | Ensure the opt-in form includes all of the necessary disclosures, such as HELP information. |
Invalid Call to Action: The opt-in form must include information on how a customer can opt out. |
2118 | Ensure the opt-in form includes all of the necessary disclosures, such as STOP information. |
Invalid Call to Action: There is no HELP message available in the verbal opt-in script. |
2119 | If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such a HELP information. Please see 10DLC campaign vetting tips and tricks for an example. |
Invalid Call to Action: No opt-in URL was found in the campaign submission. |
2120 | If the opt-in is collected online, the direct URL to opt in must be provided. If the online opt-in is obscured behind a log-in or application, you can provide a screenshot and explain that the opt-in screenshot is attached. |
Invalid Call to Action: The opt-in form must provide instructions on how to find the privacy policy. |
2121 | Ensure the opt-in form includes all of the necessary disclosures and links to the privacy policy and terms and conditions. |
Invalid Call to Action: The webpage used for opt-in does not contain an opt-in form. |
2125 | Ensure the webpage listed in the message flow contains an opt-in form with all necessary opt-in disclosures. |
Invalid Call to Action: Opt-in information in the description or message flow implies that opt-in is acquired through a court order, which is disallowed. |
2126 | If you can obtain opt-in via another method, this can be resubmitted. If not, please do not resubmit as opt-in will never be compliant. |
Invalid Call to Action: The attachment used for opt-in does not contain an opt-in form. |
2129 | Ensure the attachment used for an opt-in form contains an opt-in form with all necessary opt-in disclosures. |
Invalid Call to Action: The attachment used for opt-in does not contain a script for verbal opt-in. |
2130 | Ensure the attachment used for a verbal opt-in scripts contains a verbal script with all necessary opt-in disclosures. |
Invalid Call to Action: SMS consent must be optional on a multi‑purpose form. |
2131 | The phone number or opt in checkbox must be optional. |
Invalid Call to Action: The instructions provided for a customer to give SMS opt-in are not sufficient. |
2132 | Add additional information to clearly describe the method of opt-in (verbal, web form, etc). Customer initiated opt-in methods must identify how customers are notified on how to opt in and feature all required disclosures. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain the brand name. |
2133 |
Add the brand name into the CTA/Message Flow field. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in should mention the types of messages a customer can expect to receive. |
2134 |
Add in the type of messages the end user can receive from this brand in the CTA/Message Flow field. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain a disclosure about the frequency of message delivery. |
2135 |
Add in the frequency of messages the end user can expect in the CTA/Message Flow field. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain a disclosure that message and data rates will apply to messages sent. |
2136 |
Add in the “message and data rates may apply” in the CTA/Message Flow field. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain information about how a customer can receive help. |
2137 |
Add in the “HELP” disclaimer in the CTA/Message Flow field. |
Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain information on how a customer can opt-out. |
2138 |
Add in the “STOP” disclaimer in the CTA/Message Flow field. |
Invalid Call To Action: The provided opt-in form does not contain any phone number input field. |
2139 |
Add in a phone number field to the current opt-in method. |
Invalid Call To Action: The verbal opt-in script must provide instructions on how to find privacy policy or provide necessary privacy disclosures. |
2140 | Add instructions to the call to action on how to find privacy policy or provide necessary privacy disclosures. |
Invalid Call To Action: The keyword opt-in instructions must provide instructions on how to find privacy policy, or provide necessary privacy disclosures. |
2141 | Add details to the keyword call to action disclosures that include instructions on how to find privacy policy or provide necessary privacy disclosures. |
Invalid Call To Action: The message flow or opt in mentions promotional or marketing messages, but the use cases do not include marketing. |
2200 | Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the message flow if it will not be used. |
Invalid Campaign Description/Attributes
Rejection Description | Rejection Code | Action to Resolve |
Invalid Campaign Description/Attributes: The campaign was detected as having relations to high-risk financial services in the description or message flow, which is prohibited. |
3100 |
Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow and description, and also featured high-risk financial loans on the website, which is prohibited. |
3101 |
Do NOT resubmit. Lead generation, affiliate marketing, and high-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow or description. |
3102 | Do NOT resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected. |
Invalid Campaign Description/Attributes: The campaign has content related to direct lending in the description, message flow, or website, but the directLending field is set to False. |
3103 | Please re-create the campaign making sure to select "direct lending or loan agreement" under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Please note that any campaign for a lender will need this attribute checked.
Example: If the campaign type is Marketing but the sample messages ask questions about qualifying someone for a loan and the campaign/content attributes do not indicate lending (i.e., sample message that asks "Can you please provide your first and last name, and either the year, make and model of your vehicle or the last 4 digits of your SSN?"). |
Invalid Campaign Description/Attributes: Not all required fields populated. |
3105 | Please re-create the campaign, making sure to select the correct campaign and content attributes under campaign and content attributes. Currently, these fields are not editable in existing campaigns.
Example: If a customer selects "no" for the embedded link, but the sample content provided clearly shows links. They will need to resubmit their campaign with "yes" selected for the embedded link. |
Invalid Campaign Description/Attributes: Either a phone number or link was found in the sample messages, but the associated embedding field was not set to true. |
3106 | Please re-create the campaign, making sure to select the correct campaign and content attributes under campaign and content attributes. Currently, these fields are not editable in existing campaigns.
Example: If a customer selects "no" for the embedded link, but the sample content provided clearly shows links. They will need to resubmit their campaign with "yes" selected for the embedded link. |
Invalid Campaign Description: The Direct Lending field for the campaign was set to true, but the campaign description, sample messages, or website did not have content about lending. |
3107 | Add a sample message that includes data related to lending that aligns with the brand and use case OR update the attribute to 'No' if you do not intend to send messages related to lending or financing. |
Invalid Campaign Description: The Embedded Phone Number was set to true, but no phone number found in the sample messages. |
3108 | Add a sample message that contains a phone number OR update the attribute to 'No' if you do not intend to send messages that include a phone number. |
Invalid Campaign Description: The Embedded Link was set to true, but no link found in the sample messages. |
3109 | Add a sample message that contains a link OR update the attribute to 'No' if you do not intend to send messages that include a link. |
Invalid Campaign Description: Campaigns may only use the charity use case if they solicit donations. |
3110 | Register a new campaign with a more relevant use case if donations will not be solicited OR add proper disclaimers to the description if donations will be solicited. |
Invalid Campaign Description: The description describes a promotional or marketing use case, but the use cases do not include marketing. |
3200 | Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the description if it will not be used. |
Disallowed Content Detected
Rejection Description | Rejection Code | Action to Resolve |
Disallowed Content Detected: Sample message contents violate SHAFT-C requirements. |
4100 | Do NOT resubmit. The use case is disallowed and will be rejected. |
Missing Mandatory Message Terminology
Rejection Description | Rejection Code | Action to Resolve |
Missing Mandatory Message Terminology: The opt-out message must contain the brand name. |
5100 | The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: No valid opt-out keywords are listed. Valid opt-out keywords are: STOP, END, UNSUBSCRIBE, and CANCEL. |
5101 |
Please let all opt-out keywords be supported. At minimum, STOP must be supported. |
Missing Mandatory Message Terminology: The opt-out message must contain a confirmation that no more messages will be sent. |
5102 | The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: HELP is not listed as a help keyword. |
5103 | Please let all opt-out keywords be supported. At a minimum, HELP must be supported. |
Missing Mandatory Message Terminology: The opt-in message must contain the brand's name. |
5104 | The Opt-in confirmation message must include the brand name. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: The opt-in message must contain disclosures on message frequency. |
5105 | The Opt-in confirmation message must include the message frequency disclosure. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: The opt-in message must contain disclosure mentioning data rates may apply. |
5106 | The Opt-in confirmation message must include the "message and data rates may apply" disclosure. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: Opt-in message does not contain HELP keyword. |
5107 | The Opt-in confirmation message must include HELP information. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: The opt-in message must contain the provided opt-out keywords. |
5108 | The Opt-in confirmation message must include a keyword to opt out. Please see 10DLC campaign vetting tips and tricks for an example. |
Missing Mandatory Message Terminology: The help message must contain the brand's name. |
5109 | The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. |
Missing Mandatory Message Terminology: The help message must contain a website, phone number, and/or email for customers to contact you. |
5110 | The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. Please see 10DLC campaign vetting tips and tricks for an example. |
Other Invalid Campaign Feature
Rejection Description | Rejection Code | Action to Resolve |
Invalid Brand Info: Sole proprietors are not yet supported. |
6100 | Bandwidth does not support Sole Proprietor use cases at this time. Please reach out to your Bandwidth Support Team with any questions. |
Other Invalid Campaign Feature: A campaign was previously processed with the same description, company name, website, message flow, and sample messages, but with a different campaign ID. Duplicate campaigns: {duplicate_campaigns} |
6101 | Identical campaigns without differentiation are disallowed and viewed as snowshoeing. If you need more than 49 numbers, please submit a Number Pool request. If your need differs, please open an appeal ticket with the use case for identical campaigns. |
Other Invalid Campaign Feature: The email and/or phone number must not contain any spaces. |
6102 | Check contact details for extra spaces before or after your inputs. |
Other Invalid Campaign Feature: No campaign field may contain emojis. |
6103 | Remove emojis from any fields where they are included. |
Other Invalid Campaign Feature: We could not complete your CNP migration as your Bandwidth account has not been configured to accept the migration. Please reach out to Bandwidth support to remediate before trying again. |
6104 |
Please reach out to Bandwidth support to configure your account for CNP migrations. |
Other Invalid Campaign Feature: This campaign has been submitted 4+ times with the same unresolved errors. To prevent further fees, it will be placed in a PENDING state the next time you submit it. Please initiate an Appeal Request for review, and our team will assist you. |
6105 |
Please open a ticket with our support team for campaign review and next steps. |
Invalid Privacy Policy
Rejection Description | Rejection Code | Action to Resolve |
Invalid Privacy Policy: No privacy policy URL was found in the campaign submission. |
7100 | Please provide the link to the privacy policy in the Privacy Policy Link field. |
Invalid Privacy Policy: No website or domain was found with the given privacy policy URL. |
7101 | Please confirm the link to the Privacy Policy leads to the direct page. |
Invalid Privacy Policy: The link or attachment used to analyze the privacy policy does not appear to show an actual privacy policy. |
7102 | Please ensure the link provided directs to the brand's Privacy Policy. |
Invalid Privacy Policy: The privacy policy does not mention that mobile opt-in will not be shared, and appears to allow for the sharing of data with other companies. |
7103 | Update the Privacy Policy to make it clear that text messaging opt-in is not shared with any third parties. Please see 10DLC campaign vetting tips and tricks for suggested verbiage. |
Invalid Privacy Policy: Received a 'certificate verify failed' error for the privacy policy URL. |
7105 | Please confirm the link to the Privacy Policy leads to the direct page. |
Invalid Privacy Policy: The verbal opt-in script does not contain a valid privacy policy disclaimer or link to a valid privacy policy webpage. |
7107 | Add a privacy policy disclaimer to the script or add mention of the link to locate the privacy policy to the script. |
Invalid Privacy Policy: The privacy policy must prohibit the sharing of SMS opt-in data with third parties for marketing purposes, even with consent. |
7108 | Messaging originator opt-in data may never be shared, sold, or rented even with consumer consent. Please review your client’s privacy policy to remove exception reasons for sharing, and add specific disclosures found here. Please open a support ticket for additional assistance. |
Invalid Privacy Policy: The privacy policy contains a disallowed exception for the sharing of SMS opt-in data. |
7109 | Messaging originator opt-in data may never be shared, sold, or rented. Please review your client’s privacy policy to remove exception reasons for sharing, and add specific disclosures found here. Please open a support ticket for additional assistance. |
Invalid Privacy Policy: The privacy policy mentions promotional or marketing messages, but the use cases do not include marketing. |
7200 | Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the privacy policy if it will not be used. |
Invalid Sample Messages
Rejection Description | Rejection Code | Action to Resolve |
Invalid Sample Messages: At least one sample message must contain opt-out language. |
8100 | Update at least one of the sample messages to include opt-out language (Reply STOP to stop). |
Invalid Sample Messages: All sample messages must contain the brand name. |
8101 | Ensure each sample message includes the Brand name. |
Invalid Sample Messages: A sample message must be provided for each use case and sub-use case. |
8102 | Ensure each use case selected in the Use Case Selection is represented in at least one of the sample messages (i.e., if you have a Mixed Use Case with Account Notifications, Customer Care, and Marketing, you will need a sample message for each of the three use cases). |
Invalid Sample Messages: One or more sample messages are for promotional or marketing purposes, but the use cases do not include marketing. |
8200 | Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the sample messages if it will not be used. |
