Text Messaging: A2P 10DLC Campaign Rejection Errors

When you submit an A2P 10DLC Campaign in TE Recruit, we pass that information to Bandwidth, the provider of texting services for TE Recruit, and from there, each campaign goes through at least two levels of review (or "vetting"), all by 3rd party providers.

Top Echelon does not have any control over a campaign's review, approval, or rejection. The error messages that we receive from those 3rd party vetting providers can be obscure and confusing, so this guide will provide additional guidance on what to do when your Campaign has been rejected.

Campaign Vetting Stages

Each submitted Campaign will go through at least two stages of vetting after you submit it.

First, Bandwidth's AI "Prevetting" tool will review your submission and website for basic errors or omissions, and will quickly return a rejection if it finds any issues. If the Prevetting tool does not find any problems, the Campaign will proceed to manual vetting by actual human reviewers.

The mobile carriers (Verizon, AT&T, etc.) use providers called Direct Connect Aggregators (DCAs) to complete these manual reviews. Each mobile carrier will use one of two types of DCA: Proxy DCAs and/or Secondary DCAs. When you receive a rejection error from these DCAs, you will see them as "Proxy Connector" or "DCA2" errors, respectively. Campaigns will usually be reviewed by multiple DCAs, so you may receive multiple error types.

Bandwidth Prevetting, Proxy DCAs, and Secondary DCAs each return unique error codes, which we've listed below, with some additional guidance to help you correct each error before you resubmit your Campaign.

Bandwidth Prevetting Errors

Brand Inconsistencies

These errors will require you to update the Brand portion of the A2P registration form, and/or make sure your website is online and secure (https).

Error Description	Code	Action to Resolve
Brand Inconsistencies: No website URL or attachment was found in the campaign submission.	1100	In the Brand section of the A2P Registration form, add a Web Address for a working, secure (https) website that represents your organization.
Brand Inconsistencies: No website or domain was found with the website URL.	1101	In the Brand section of the A2P Registration form, ensure that the Web Address you provided leads to a working, secure (https) website that represents your organization.

Message Flow/CTA Errors

These errors will require updates to the Campaign's Message Flow field, and/or updates to your website to make it compliant with consent-collection requirements.

Error Description	Code	Action to Resolve
Invalid Call to Action: No form of opt-in whatsoever was found in the description or message flow.	2100	Message Flow must describe how recipients opt-in to receiving texts (website, verbal, written, etc.). If your Message Flow describes website opt-in, the website's opt-in form must have an optional phone number field.
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, usually via an "I consent..." checkbox or Y/N opt-in question. Update the website and/or Message Flow with a valid consent 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, usually via an "I consent..." checkbox or Y/N opt-in question. The recipient needs to agree to receive texts for a specific informational purpose. Update website and/or Message Flow with a valid opt-in collection method.
Invalid Call to Action: Got a 'certificate verify failed' error for the opt-in URL.	2103	Ensure that the Sample Consent Call-to-Action (CTA) URL you provided leads directly to the opt-in form on an active, secure (https) website.
Invalid Call to Action: No website or domain was found with the given opt-in URL.	2104	Ensure that the Sample Consent Call-to-Action (CTA) URL you provided leads directly to the opt-in form on an active, secure (https) website.
Invalid Call to Action: This campaign has verbal opt-in, but does not contain an explicit script of what the company says.	2105	If your Message Flow describes a verbal opt-in method, the verbal "script" read to consumers at the time of opt-in collection must also be provided. It must include all of the following: Brand name, types/contents of messages being sent, message frequency disclosure ("Message frequency varies."), "Message and data rates may apply" disclosure, HELP information, STOP information, and a link to the Privacy Policy and Messaging Terms & Conditions.
Invalid Call to Action: The script for verbal opt-in must contain instructions on how to reach the privacy policy.	2106	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must include a link to the Privacy Policy and Messaging Terms & Conditions.
Invalid Call to Action: The verbal opt-in script does not contain the brand name.	2108	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must include the Brand name and all other required disclosures. Example: "...messages from ABC Recruiters..."
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 your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must describe the types/contents of messages being sent, and include all other required disclosures. Example: "...messages regarding employment opportunities and/or recruiting services..."
Invalid Call to Action: The verbal opt-in script contains no disclosure about the frequency of message delivery.	2110	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must describe message frequency and include all other required disclosures. For conversational messaging, use "Message frequency varies." For automated/recurring texts, describe how frequently you send them: "...weekly text messages..." etc.
Invalid Call to Action: The verbal opt-in script has no disclosure that message and data rates will apply to messages sent.	2111	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must include the "message and data rates may apply" disclosure, and all other required disclosures. You may shorten this to "Msg & data rates may apply", or similar but it must have the same meaning and be easy to understand.
Invalid Call to Action: The verbal opt-in script has no information detailing how a customer can stop receiving messages.	2112	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must include STOP information ("Text STOP to opt-out"), and all other required disclosures.
Invalid Call to Action: The brand name could not be found in the opt-in form.	2113	On your website, update the opt-in form/CTA to include the Brand name, and all other required disclosures. Example: "...messages from ABC Recruiters..."
Invalid Call to Action: The opt-in form should mention the types of messages a customer can expect to receive.	2114	On your website, update the opt-in form/CTA to include the types of messages being sent, and all other required disclosures. Example: "...text messages regarding employment opportunities and/or recruiting services..."
Invalid Call to Action: The opt-in form must mention message frequency.	2115	On your website, update the the opt-in form/CTA to describe message frequency, and include all other required disclosures. For conversational messaging, use "Message frequency varies." For automated/recurring texts, describe how frequently you send them: "...weekly text messages..." etc.
Invalid Call to Action: The opt-in form has no disclosure that message and data rates will apply to messages sent.	2116	On your website, update the opt-in form/CTA to include "message and data rates may apply", and all other required disclosures. You may shorten this to "Msg & data rates may apply", or similar but it must be easy to read and have the same meaning.
Invalid Call to Action: The opt-in form must include information on how a customer can receive help.	2117	On your website, update the opt-in form/CTA to include HELP information ("Text HELP for assistance."), and all other required disclosures.
Invalid Call to Action: The opt-in form must include information on how a customer can opt out.	2118	On your website, update the opt-in form/CTA to include STOP information ("Text STOP to opt out."), and all other required disclosures.
Invalid Call to Action: There is no HELP message available in the verbal opt-in script.	2119	If your Message Flow describes a verbal opt-in method, the verbal script read to consumers at the time of opt-in collection must also be provided. It must include HELP information ("Text HELP for assistance."), and all other required disclosures.
Invalid Call to Action: No opt-in URL was found in the campaign submission.	2120	Ensure that the Sample Consent Call-to-Action (CTA) URL you provided leads directly to the opt-in form on an active, secure (https) website. If the online opt-in is not publicly-accessible (obscured behind a log-in or similar), please email a2p@topechelon.com for assistance.
Invalid Call to Action: The opt-in form must provide instructions on how to find the privacy policy.	2121	On your website, update the opt-in form/CTA to include link(s) to the Privacy Policy and Terms & Conditions, and all other required disclosures.

Campaign Description, Attributes, or Disallowed Content:

These errors relate to use-cases that are not allowed under 10DLC requirements

Error Description	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	Not eligible to resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. You may contact a2p@topechelon.com to initiate an appeal.
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	Not eligible to resubmit. Lead generation, affiliate marketing, and high-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. You may contact a2p@topechelon.com to initiate an appeal.
Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow or description.	3102	Not eligible to resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected. You may contact a2p@topechelon.com to initiate an appeal.
Invalid Campaign Description/Attributes: Not all required fields populated.	3105	Requires assistance from Top Echelon's A2P Team. Please contact us at a2p@topechelon.com.
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	Requires assistance from Top Echelon's A2P Team. Please contact us at a2p@topechelon.com.
Disallowed Content Detected: Sample message contents violate SHAFT-C requirements.	4100	Not eligible to resubmit. The use case is disallowed and will be rejected. Learn more about SHAFT-C at 10dlc.org. You may contact a2p@topechelon.com to initiate an appeal.

Mandatory Message Terminology:

If you receive any of these errors, there is most likely a technical issue between Bandwidth and TE Recruit.

To resolve any of the following, please email us at a2p@topechelon.com.

Error Description	Code
Missing Mandatory Message Terminology: The opt-out message must contain the brand name.	5100
Missing Mandatory Message Terminology: No valid opt-out keywords are listed. Valid opt-out keywords are: STOP, END, UNSUBSCRIBE, and CANCEL.	5101
Missing Mandatory Message Terminology: The opt-out message must contain a confirmation that no more messages will be sent.	5102
Missing Mandatory Message Terminology: HELP is not listed as a help keyword.	5103
Missing Mandatory Message Terminology: The opt-in message must contain the brand's name.	5104
Missing Mandatory Message Terminology: The opt-in message must contain disclosures on message frequency.	5105
Missing Mandatory Message Terminology: The opt-in message must contain disclosure mentioning data rates may apply.	5106
Missing Mandatory Message Terminology: Opt-in message does not contain 'HELP' keyword.	5107
The opt-in message must contain the provided opt-out keywords.	5108
Invalid Brand Info: Sole proprietors are not yet supported.	6100

Privacy Policy:

These errors relate to problems with your company's Privacy Policy. You will either need to update the Privacy Policy URL on the A2P Registration form, and/or the Privacy Policy published on your website, as described below.

For more information about Privacy Policy compliance, click here.

Error Description	Code	Action to Resolve
Invalid Privacy Policy: No privacy policy URL was found in the campaign submission.	7100	The link in the Privacy Policy URL field must lead to your company's published Privacy Policy,
Invalid Privacy Policy: No website or domain was found with the given privacy policy URL.	7101	Please confirm that the Privacy Policy URL leads to a valid, secure webpage containing the company's Privacy Policy.
Invalid Privacy Policy: The link or attachment used to analyze the privacy policy does not appear to show an actual privacy policy.	7102	Please confirm that the Privacy Policy URL leads to a valid, secure webpage containing the company'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, and that recipients may text STOP to opt-out of receiving texts.

Sample Messages:

These errors indicate problems with your Example Messages.

Error Description	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 all Example Messages include the Brand name. ("This is Jane from Acme Agency.")
Invalid Sample Messages: A sample message must be provided for each use case and sub-use case.	8102	If your Campaign Description or Message Flow describes different use-cases (texting clients & candidates about different topics), your Example Messages must include one message of each type.

Proxy Connector Vetting Errors

Use-Case or Description Issues

To resolve these errors, you will need to update Campaign fields or contents as described in the "Action to resolve" column.

Rejection reason	Code	Action to resolve
Campaign appears to be for an age-gated content type but age gate attribute is not selected.	1001	TE Recruit is unable to process age-gated campaign use-cases at this time. Please contact us at a2p@topechelon.com.
Campaign is for direct lending or loan arrangement and is missing the content attribute indicating direct lending.	1002	TE Recruit is unable to process direct-lending or loan arrangement campaign use-cases at this time. Please contact us at a2p@topechelon.com.
Campaign registration is not unique or duplicate campaign	2001	Duplicate campaigns are disallowed. Campaigns should be uniquely registered.
Unclear campaign description	2002	It must be clear from your campaign description what the purpose of your message program is. Add more details to the Campaign Description and Message Flow fields and resubmit.
Campaign description does not match declared use case(s)	2003	All campaigns in TE Recruit are a "Customer Care" use-case by default, so update your Campaign Description to describe how you use texting to assist candidates and/or clients. If this use-case does not accurately describe how you use texting, please contact us at a2p@topechelon.com.
Campaign description does not match sample messages	2004	All campaigns in TE Recruit are a "Customer Care" use-case by default, so update your Example Messages and/or Campaign Description to show how you use texting to assist candidates and/or clients. If this use-case does not accurately describe how you use texting, please contact us at a2p@topechelon.com.
Undeclared use case	2005	All campaigns in TE Recruit are a "Customer Care" use-case by default, so update your Campaign Description to describe how you use texting to assist candidates and/or clients. If this use-case does not accurately describe how you use texting, please contact us at a2p@topechelon.com.
Brand referenced in campaign description does not match registered/DBA brand	2006	The Brand name included in the Campaign must be consistent with the Brand you registered. If your Campaign describes a different Brand, you will either need to update the Campaign to match your Brand and resubmit, or create a new Brand. To create a new Brand, contact us at a2p@topechelon.com.

Call-to-Action (Opt-in experience as described in Campaign)

These errors relate to your Campaign's description of how you collect consent-to-text. Most of these will require you to update your Campaign's Message Flow field as described in the "Action to resolve" column, before you resubmit.

Rejection reason	Code	Action to resolve
Call-to-action does not obtain sufficient consent	3001A	Your Message Flow field must describe how recipients provide consent-to-text. In most cases, this will describe a visitor to your website answering an opt-in question, or checking a checkbox on a web form. Please check out our Help Article on compliant consent collection, and make sure your website is compliant before updating your Massage Flow field and resubmitting.
A Call-to-action does not contain registered/DBA brand name	3002A	The company/brand name must be included in the Message Flow field and must match the registered Brand or be easily recognizable as the same entity. Update the Message Flow field and resubmit.
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	TE Recruit adds this information to your Campaign from the Terms & Conditions field. If your Terms & conditions field does not include HELP instructions & contact information, please update those fields before resubmitting.
Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel)	3004A	TE Recruit adds this information to your Campaign from the Terms & Conditions field. If your Terms & Conditions field does not include STOP instructions, please add them before resubmitting.
Call-to-action does not contain message frequency disclosure for recurring message program	3005A	TE Recruit adds this information to your Campaign from the Terms & Conditions field. If your Terms & Conditions field does not describe messaging frequency ("Message frequency varies."), please add that description before resubmitting.
Call-to-action does not contain "message and data rates may apply" disclosure	3006A	TE Recruit adds this information to your Campaign from the Terms & Conditions field. If your Terms & Conditions field does not include the rates/fees disclosure ("Message and data rates may apply"), please add it before resubmitting.
Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions	3007A	TE Recruit adds this information to your Campaign from the Terms & Conditions field. Make sure your Terms & Conditions field includes all required instructions and disclosures before resubmitting.
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	TE Recruit adds this information to your Campaign from the Privacy Policy URL field. Please make sure that your Privacy Policy URL leads to a policy that describes that mobile opt-in data will not be shared with 3rd parties for any purpose. If your policy already contains the required language, make sure the URL you provided is correct before your resubmit.
Call-to-action does not contain a robust age gate for age-restricted message program (alcohol/firearms/tobacco)	3010A	Message content related to age-restricted goods, such as alcohol or tobacco, is not permitted without an age gate mechanism. TE Recruit does not currently support age-gated Campaign use-cases. Please contact us at a2p@topechelon.com for assistance.
Call-to-action is missing/inaccessible	3011A	TE Recruit adds this information to your Campaign from the Sample Consent Call-to-Action (CTA) field. Please make sure that the CTA URL you provide leads to a page where your website consent call-to-action is directly displayed. Usually this is a Job Board or Careers Page job "Apply" page, where the "Do you consent...?" question is immediately displayed. Please make sure the Sample CTA link you provide meets these requirements before resubmitting. Please contact us at a2p@topechelon.com if you're unable to provide a link directly to your consent call-to-action.
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	You cannot collect consent for texting in the same call-to-action with other communication types, like email. Please ensure that your Message Flow field describes consent collection for texting as separate from email or other types of consent, and resubmit.

Call-to-action (Opt-in experience as seen on page from Sample Consent Call-to-Action (CTA))

When you submit your Campaign in TE Recruit, you must provide a URL in the Sample Consent Call-to-Action (CTA) field, and the page at this URL must show an example of how recipients can opt-in to receive texts from you. Campaign reviewers will visit this URL to ensure that your consent collection practices are compliant with A2P 10DLC requirements. Most TE Recruit customers use an "apply" page for any of their jobs from their Careers Page or Job Board, where a compliant consent call-to-action is automatically included, by default.

The following errors will require you to make changes to the page you submitted, or to submit a different page under Sample Consent Call-to-Action (CTA) when you resubmit. See the "Actions to resolve" column for suggested next steps.

Rejection reason	Code	Action to resolve
Call-to-action (on website, or provide via screenshot/media file) does not obtain sufficient consent	3001B	All CTA's must obtain consent via proper consent mechanism. The consent collection shown on the page at your Sample Consent CTA URL must be brought into compliance, or a different URL with a compliant CTA provided before you resubmit. Learn more about compliant consent collection, here.
Call-to-action does not contain registered/DBA brand name	3002B	The company/brand name must be included in the CTA and must match the registered Brand or be easily recognizable as the same entity. For example, if you ask a "Do you consent...?" question, it must specify that texts will come from your Brand's name. Update the call-to-action and resubmit.
Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions	3003B	The call-to-action must include instructions on how to receive further support from you ("Reply HELP for help"), or this information must be present in the your terms and conditions. Update the call-to-action and resubmit.
Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel)	3004B	The call-to-action must include instructions on how to opt-out of the message program ("Reply STOP to opt-out"). Update the call-to-action and resubmit.
Call-to-action does not contain message frequency disclosure for recurring message program	3005B	The call-to-action must include the frequency at which messages will be sent ("Msg frequency varies", recurring messages, etc.). Update the call-to-action and resubmit.
Call-to-action does not contain "message and data rates may apply" disclosure	3006B	The call-to-action must include the message and data rate disclosure, as mandated by U.S. carriers. ("Msg & data rates may apply.") Update the call-to-action and resubmit.
Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions	3007B	The call-to-action must include a link to the message program Terms & Conditions, or show the complete message program T&C language. Update the call-to-action and resubmit.
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	Mobile opt in data (that is, the end user's phone number) cannot be shared with third parties. The call-to-action must include a link to the message program Privacy Policy, or language referring to the Privacy Policy, that indicates that mobile opt-in data will not be shared. Update the call-to-action and resubmit.
Call-to-action does not contain robust age gate for age-restricted message program (alcohol/firearms/tobacco)	3010B	Message content related to age-restricted goods, such as alcohol or tobacco, is not permitted without an age gate mechanism. An acceptable age gate would consist of, at minimum, a recipient entering a day, month, and year confirming their age at messaging opt-in prior to receiving messaging. If the call-to-action indicates that the message program will be sending this type of content, and no age gate is in place, the campaign will be rejected. Implement age gate and resubmit.
Call-to-action is missing/inaccessible	3011B	There is no call-to-action URL provided in the campaign description, or the URL provided is inaccessible. You must provide evidence of a compliant opt-in process via either a live opt-in URL, or a URL to a hosted opt-in image (screenshot or mock-up). Update the Sample Consent Call-to-Action (CTA) to include the URL of a live page showing your compliant CTA, or a link to a screenshot of your CTA, and resubmit.
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	You cannot collect consent for texting in the same call-to-action with other communication types, like email. Please ensure that your consent call-to-action obtains consent-to-text separately from any other consent types, and resubmit.

7/7/25: We're working to update this section ASAP. Please email us at a2p@topechelon.com if your error code is not shown. Thank you for your patience!

DCA2 Vetting Errors