This article outlines all of the error codes you may receive when 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.
Error 601: Campaign Attributes do not match website and/or sample message content. Action to Resolve: Please re-create the campaign, making sure to select the correct 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.
Error 602: Inaccurate Registration. Inconsistency between sample message and use-case. Action to Resolve: Ensure that the selected use case is consistent with the sample messages. Example: If they select charity as their use case but are sending appointment reminders, they would be rejected. They either need to update their sample messages or change their use case to better align with the content they are sending.
Error 603: Inaccurate Registration. Inconsistency between website, brand name, and/or sample messages or inconsistent sample messages. Action to Resolve: Ensure that the content on the website, sample messages, and brand are all consistent. Example: If the Brand name is ABC Physicians, they would be rejected if they 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 ABC Physicians, sending appointment reminders, and a link to their practice's webpage.
Error 701: Prohibited Content; Cannabis. Action to Resolve: Do NOT resubmit. Cannabis/hemp/CBD is not allowed over 10DLC, 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 chiropractor's office has CDB Oils on its website, this is prohibited, and the campaign will be denied, even if not directly related to CBD marketing.
Error 702: Prohibited Content; Guns/Ammo {Failure to age gate}. Action to Resolve: 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.
Error 703: Prohibited Content; Explicit sexual. Action to Resolve: Do NOT resubmit. Explicit sexual content is not allowed over 10DLC, and campaigns related to this content will be rejected.
Error 704: Prohibited Content; Gambling. Action to Resolve: Do NOT resubmit. Gambling content is not allowed over 10DLC, and campaigns related to this content will be rejected.
Error 705: Prohibited Content; Hate. Action to Resolve: Do NOT resubmit. Hate speech is not allowed over 10DLC, and campaigns related to this content will be rejected.
Error 706: Prohibited Content; Alcohol {Failure to age gate}. Action to Resolve: 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.
Error 707: Prohibited Content; Tobacco / Vape {Failure to age gate} Action to Resolve: 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.
Error 708: Lead Gen/Affiliate Marketing prohibited; other. Action to Resolve: Do NOT resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected.
Error 709: Lead Gen/Affiliate Marketing prohibited; high-risk financial services. Action to Resolve: Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected.
Error 710: Reseller / Non-compliant KYC. Register the brand info, not the agency or software provider behind the brand. Action to Resolve: Make sure that 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, they will be rejected. Instead of the software company (ABC Wireless Reseller), the brand should be the doctor's office sending appointment reminders.
Error 711: Repeated use of the same EIN for multiple different brands. Action to Resolve: 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.
Error 712: Misleading Registration. Based on the details submitted, Campaign appears to be a Direct Lending Arrangement but the appropriate Content Attribute was not selected. Action to Resolve: 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?").
Error 713: 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. Action to Resolve: 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. Example: A large bank (ABC BANK) would not be using an email address like jsmith@gmail.com, we would expect the email to match the business such as jsmith@abcbank.com
Error 714: Invalid Opt-In. Permission to text users via Court Order does not meet carrier code of conduct Action to Resolve: 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.
Error 801: Not Sole Proprietor. Does not meet small business Sole Prop (EIN) criteria set by TCR and mobile carriers. Action to Resolve: At this time new Sole Proprietor campaigns are not being accepted. Please find another use case for the campaign.
Error 802: Sole Proprietor. Not yet authorized. Action to Resolve: Bandwidth is not supporting Sole Proprietor use cases at this time, please reach out to your Bandwidth Support Team with any questions.
Error 803: Opt-in language is required on the website if used to collect mobile numbers. Action to Resolve: 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.
Error 804: Unable to verify, need a working website or complete CTA information if opt-in occurs outside of the website. Action to Resolve: 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.
Error 805: Compliant privacy policy is required on website. Action to Resolve: 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. Steps toward approval would be adding a compliant privacy policy or editing the non-compliant privacy policy.
Error 806: Unable to verify, needs compliant and accurate CTA information. Action to Resolve: Either the CTA is inaccurate and doesn't explain where the customers opt into the campaign (website, verbal, written, etc.), or the opt-in is on the website but there is no phone field to add the phone number.
Error 807: Unable to verify inauthentic website Action to Resolve: Please ensure any references to websites in your brand and campaign registration are working links and pertain to the specific business being registered.
Error 808: Campaign has been declined 5+ times Action to Resolve: The campaign has been declined 5+ times without sufficient updates. Each denial incurs a vetting fee. For questions, please reach out to your Direct Connect Aggregator (DCA).
Error 809: Compliant privacy policy is required to be attached to registration if not available on website Action to Resolve: Compliant privacy policy example is required to be attached to registration in TCR or emailed to your Direct Connect Aggregator (DCA) when opt-in is collected either in person or over the phone and not via a website.
Code 1100: Brand Inconsistencies: No website URL or attachment was found in the campaign submission.
Action to Resolve: The brand needs an online presence. Provide their online presence in the Brand Details.
Code 1101: Brand Inconsistencies: No website or domain was found with the website URL.
Action to Resolve: Confirm the brand website URL provided leads to the direct page.
Code 1103: Brand Inconsistencies: Received a 'certificate verify failed' error for the website URL.
Code 2100: Invalid Call to Action: No form of opt-in whatsoever was found in the description or message flow.
Action to Resolve: 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.
Code 2101: Invalid Call to Action: This was determined to be a promotional campaign, but there was no mention of a written opt-in.
Action to Resolve: Marketing/promotional content requires prior express written consent. Update the campaign with a valid opt-in collection method.
Code 2102: Invalid Call to Action: This was determined to be an informational campaign, but no explicit means of opt-in was given.
Action to Resolve: 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.
Code 2103: Invalid Call to Action: Got a "certificate verify failed" error for the opt-in URL.
Action to Resolve: Ensure the opt-in URL provided leads to the direct opt-in form.
Code 2104: Invalid Call to Action: No website or domain was found with the given opt-in URL.
Action to Resolve: Ensure the opt-in URL provided leads to the direct opt-in form.
Code 2105: Invalid Call to Action: This campaign has verbal opt-in, but does not contain an explicit script of what the company says.
Action to Resolve: 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.
Code 2106: Invalid Call to Action: The script for verbal opt-in must contain instructions on how to reach the privacy policy.
Action to Resolve: 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.
Code 2108: Invalid Call to Action: The verbal opt-in script does not contain the brand name.
Action to Resolve: 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.
Code 2109: 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.
Action to Resolve: 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.
Code 2110: Invalid Call to Action: The verbal opt-in script contains no disclosure about the frequency of message delivery.
Action to Resolve: 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.
Code 2111: Invalid Call to Action: The verbal opt-in script has no disclosure that message and data rates will apply to messages sent.
Action to Resolve: 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.
Code 2112: Invalid Call to Action: The verbal opt-in script has no information detailing how a customer can stop receiving messages.
Action to Resolve: 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.
Code 2113: Invalid Call to Action: The brand name could not be found in the opt-in form.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as the brand name.
Code 2114: Invalid Call to Action: The opt-in form should mention the types of messages a customer can expect to receive.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as the types of messages being sent.
Code 2115: Invalid Call to Action: The opt-in form must mention message frequency.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as message frequency disclosure.
Code 2116: Invalid Call to Action: The opt-in form has no disclosure that message and data rates will apply to messages sent.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as the "message and data rates may apply" disclosure.
Code 2117: Invalid Call to Action: The opt-in form must include information on how a customer can receive help.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as HELP information.
Code 2118: Invalid Call to Action: The opt-in form must include information on how a customer can opt out.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures, such as STOP information.
Code 2119: Invalid Call to Action: There is no HELP message available in the verbal opt-in script.
Action to Resolve: 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.
Code 2120: Invalid Call to Action: No opt-in URL was found in the campaign submission.
Action to Resolve: 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.
Code 2121: Invalid Call to Action: The opt-in form must provide instructions on how to find the privacy policy.
Action to Resolve: Ensure the opt-in form includes all of the necessary disclosures and links to the privacy policy and terms and conditions.
Code 2125: Invalid Call to Action: The webpage used for opt-in does not contain an opt-in form.
Code 2129: Invalid Call to Action: The attachment used for opt-in does not contain an opt-in form.
Code 2130: Invalid Call to Action: The attachment used for opt-in does not contain a script for verbal opt-in.
Code 3100: 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.
Action to Resolve: Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected.
Code 3101: 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.
Action to Resolve: 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.
Code 3102: Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow or description.
Action to Resolve: Do NOT resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected.
Code 3103: Invalid Campaign Description: The campaign has content related to direct lending in the description, message flow, or sample messages, but the direct lending field is set to False.
Code 3105: Invalid Campaign Description/Attributes: Not all required fields populated.
Action to Resolve: 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.
Code 3106: 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.
Action to Resolve: 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.
Code 3107: 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.
Code 3108: Invalid Campaign Description: The Embedded Phone Number was set to true, but no phone number found in the sample messages.
Code 3109: Invalid Campaign Description: The Embedded Link was set to true, but no link found in the sample messages.
Code 4100: Disallowed Content Detected: Sample message contents violate SHAFT-C requirements.
Action to Resolve: Do NOT resubmit. The use case is disallowed and will be rejected.
Code 5100: Missing Mandatory Message Terminology: The opt-out message must contain the brand name.
Action to Resolve: The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages.
Code 5101: Missing Mandatory Message Terminology: No valid opt-out keywords are listed. Valid opt-out keywords are: STOP, END, UNSUBSCRIBE, and CANCEL.
Action to Resolve: Please let all opt-out keywords be supported. At minimum, STOP must be supported.
Code 5102: Missing Mandatory Message Terminology: The opt-out message must contain a confirmation that no more messages will be sent.
Action to Resolve: The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages.
Code 5103: Missing Mandatory Message Terminology: HELP is not listed as a help keyword.
Action to Resolve: Please let all opt-out keywords be supported. At a minimum, HELP must be supported.
Code 5104: Missing Mandatory Message Terminology: The opt-in message must contain the brand's name.
Action to Resolve: The Opt-in confirmation message must include the brand name.
Code 5105: Missing Mandatory Message Terminology: The opt-in message must contain disclosures on message frequency.
Action to Resolve: The Opt-in confirmation message must include the message frequency disclosure.
Code 5106: Missing Mandatory Message Terminology: The opt-in message must contain disclosure mentioning data rates may apply.
Action to Resolve: The Opt-in confirmation message must include the "message and data rates may apply" disclosure.
Code 5107: Missing Mandatory Message Terminology: Opt-in message does not contain HELP keyword.
Action to Resolve: The Opt-in confirmation message must include HELP information.
Code 5108: The opt-in message must contain the provided opt-out keywords.
Action to Resolve: The Opt-in confirmation message must include a keyword to opt out.
Code 6100: Invalid Brand Info: Sole proprietors are not yet supported.
Action to Resolve: Bandwidth does not support Sole Proprietor use cases at this time. Please reach out to your Bandwidth Support Team with any questions.
Code 6101: 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}
Action to Resolve: 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.
Code 6102: Other Invalid Campaign Feature: The email and/or phone number must not contain any spaces.
Code 7100: Invalid Privacy Policy: No privacy policy URL was found in the campaign submission.
Action to Resolve: Please provide the link to the privacy policy in the Privacy Policy Link field.
Code 7101: Invalid Privacy Policy: No website or domain was found with the given privacy policy URL.
Action to Resolve: Please confirm the link to the Privacy Policy leads to the direct page.
Code 7102: Invalid Privacy Policy: The link or attachment used to analyze the privacy policy does not appear to show an actual privacy policy.
Action to Resolve: Please ensure the link provided directs to the brand's Privacy Policy.
Code 7103: 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.
Action to Resolve: Update the Privacy Policy to make it clear that text messaging opt-in is not shared with any third parties.
Code 7105: Invalid Privacy Policy: Received a 'certificate verify failed' error for the privacy policy URL.
Code 8100: Invalid Sample Messages: At least one sample message must contain opt-out language.
Action to Resolve: Update at least one of the sample messages to include opt-out language (Reply STOP to stop).
Code 8101: Invalid Sample Messages: All sample messages must contain the brand name.
Action to Resolve: Ensure each sample message includes the Brand name.
Code 8102: Invalid Sample Messages: A sample message must be provided for each use case and sub-use case.
Action to Resolve: 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).