If a brand comes back as rejected or unverified it is because the Tax ID or Canadian Corporation Number does not match the registered business name. The registered business name must contain the same punctuation that is on the business registry. If these are not exact, it will be rejected by the third party the SMS (Short Message Service) ecosystem uses.
If a campaign is rejected, it will be given an error code and a reason. Please review the table below and make any necessary changes before resubmitting the campaign.
|
Error Description |
Error Code |
Action to Resolve |
|
Campaign Attributes do not match website and/or sample message content. |
601 |
Please update the campaign to make sure the attributes selected match the campaign description and characteristics. Example: If a customer selects "no" for the phone number, but the sample content provided clearly shows phone numbers. You will need to resubmit your campaign with "yes" selected for the embedded link. |
|
Inaccurate Registration. Inconsistency between sample message and use-case. |
602 |
Ensure that the selected use case is consistent with the sample messages. Example: If you select marketing as your use case, but are sending appointment reminders this would be rejected. Either the sample messages need to be updated or the use case needs to be updated to match the sample messages. |
|
Inaccurate Registration. Inconsistency between website, brand name, and/or sample messages or inconsistent sample messages. |
603 |
Ensure that the content on the website, sample messages, and brand are consistent throughout the sample messages, website and registered brand. Example: If the Brand name is Salesforce, the campaign would be rejected if it had sample content sent out regarding sales for a clothing shop, or had a website for a marketing firm. A good example would be the brand Salesforce, sending call reminders, and a link to Salesforce’s website.. |
|
Prohibited Content; Cannabis. |
701 |
Do NOT resubmit. Cannabis/hemp/CBD is not allowed over 10DLC (10 Digit Long Code, a standard US carrier registration system for business SMS messaging), and campaigns related to this content will be rejected. Please note: This content is not allowed to be on the customer's website at all. Example: If a doctors office has CBD Oils on its website, this is prohibited, and the campaign will be denied, even if not directly related to CBD. |
|
Prohibited Content; Guns/Ammo {Failure to age gate}. |
702 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
|
Prohibited Content; Explicit sexual. |
703 |
Do NOT resubmit. Explicit sexual content is not allowed over 10DLC, and campaigns related to this content will be rejected. |
|
Prohibited Content; Gambling. |
704 |
Do NOT resubmit. Gambling content is not allowed over 10DLC, and campaigns related to this content will be rejected. |
|
Prohibited Content; Hate. |
705 |
Do NOT resubmit. Hate speech is not allowed over 10DLC, and campaigns related to this content will be rejected. |
|
Prohibited Content; Alcohol |
706 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
|
{Failure to age gate}. |
706 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
|
Prohibited Content; Tobacco / Vape {Failure to age gate}. |
707 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
|
Lead Gen/Affiliate Marketing prohibited; other. |
708 |
Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected. Note: This rejection typically occurs if your privacy policy states information is purchased from or shared with third parties. If you would like to resubmit, you will need to update your privacy policy to state sms consent is not purchased from third parties. |
|
Lead Gen/Affiliate Marketing prohibited; high-risk financial services. |
709 |
Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
|
Reseller / Non-compliant KYC. Register the brand info, not the agency or software provider behind the brand. |
710 |
Make sure know your customer (KYC) is clearly laid out in the campaign. Remember the brand is the message sender – the EIN and company information should reflect the message sender, not necessarily you as the reseller. Example: If the band name is ABC Wireless Reseller, but their sample content is all appointment reminders for a doctor's office, this will be rejected. Instead of the software company (ABC Wireless Reseller), the brand should be the doctor's office sending appointment reminders. |
|
Repeated use of the same EIN for multiple different brands. |
711 |
Only register one brand per EIN. Do not resubmit unless the brand has been updated to reflect the actual sender (EIN, legal company name, etc) and the EIN and is not a duplicate of other brands. |
|
Misleading Registration. Based on the details submitted, Campaign appears to be a Direct Lending Arrangement but the appropriate Content Attribute was not selected. |
712 |
Please create a new campaign making sure to select "direct lending or loan agreement" under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Note: any campaign for a lender will need this attribute checked. Example: If the campaign type is Customer care but the sample messages ask questions about qualifying someone for a loan and the campaign/content attributes do not indicate lending. |
|
Appears to be a large company or company that would have an official email domain. Check for fraud, and use the official/working email domain. |
713 |
Please check to make sure that the correct email address was added. It is expected if the legal company name is well-known and recognized that it will have an official company email domain. |
|
Invalid Opt-In. Permission to text users via Court Order does not meet carrier code of conduct |
714 |
If you are able to obtain opt-in via another method, this can be resubmitted. If not, please do not resubmit as opt-in will never be compliant. |
|
Not Sole Proprietor. Does not meet small business Sole Prop (EIN) criteria set by TCR and mobile carriers. |
801 |
At this time new Sole Proprietor campaigns are not being accepted. Please find another use case for the campaign. |
|
Sole Proprietor. Not yet authorized. |
802 |
Salesforce is not supporting Sole Proprietor use cases at this time, please reach out to your Bandwidth Support Team with any questions. |
|
Opt-in language is required on the website if used to collect mobile numbers. |
803 |
The website provided did not include opt-in language where the customer provided a phone number. Please add this language to the website before resubmitting. |
|
Unable to verify, need a website / working website or complete CTA information if opt-in occurs outside of the website. |
804 |
We have often seen campaigns rejected for insufficient call-to-action sections. Please provide a working website link and a clear and concise description of how an end user signs up to receive messages. Opt-in must be 1 to 1, can't be shared with third parties, and can't be implied. |
|
Compliant privacy policy is required on website. |
805 |
Per 5.2.1 of the CTIA Guidelines, message senders are to maintain a privacy policy that is easily accessed by the consumer. It should be referenced in the call-to-action/opt-in. You may receive this denial if there is no privacy policy present OR if the privacy policy is non-compliant. The non-compliance generally would be around the sharing of consumer information with third-parties for marketing purposes. To resubmit, please add language to your privacy policy that states “SMS consent is not shared with or purchased from third parties.” This is an example and should not be used verbatim. Please consult your legal team to determine how to update your privacy policy. |
|
Unable to verify, needs compliant and accurate CTA information. |
806 |
CTA is inaccurate and does not explain where the customers opt into the campaign (website, verbal, written, etc.) Please update the opt in workflow with full details on how your end users provide SMS consent. |
|
Unable to verify inauthentic website |
807 |
Please ensure any references to websites in your brand and campaign registration are working links and pertain to the specific business being registered. |
|
Campaign has been declined 5+ times |
808 |
Campaign has been declined 5+ times, without sufficient updates. Each denial incurs in a vetting fee. For questions, please reach out your DCA. |
|
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. |
*NEW* 1103 |
Confirm the brand website URL provided leads to the direct page. |
|
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. |
*NEW* 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. |
*NEW* 2125 |
Ensure the webpage listed in the message flow contains an opt-in form with all necessary opt-in disclosures |
|
Invalid Call to Action: The attachment used for opt-in does not contain an opt-in form. |
*NEW* 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. |
*NEW* 2130 |
Ensure the attachment used for a verbal opt-in scripts contains a verbal script with all necessary opt-in disclosures. |
|
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. |
*NEW* 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. |
|
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: 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. |
|
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. |
|
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. |
|
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. |
|
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 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). |
002186625

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.