Rejection code

Rejection Description

Action to Resolve

1100

Brand Inconsistencies: No website URL or attachment was found in the campaign submission.

The brand needs an online presence. Provide their online presence in the Brand Details.

1101

Brand Inconsistencies: No website or domain was found with the website URL.

Confirm the brand website URL provided leads to the direct page.

1103

Brand Inconsistencies: Received a 'certificate verify failed' error for the website URL.

Confirm the brand website URL provided leads to the direct page.

Rejection code

Rejection Description

Action to Resolve

2100

Invalid Call to Action: No form of opt-in whatsoever was found in the description or message flow.

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.

2101

Invalid Call to Action: This was determined to be a promotional campaign, but there was no mention of a written opt-in.

Marketing/promotional content requires prior express written consent.
Update the campaign with a valid opt-in collection method.

2102

Invalid Call to Action: This was determined to be an informational campaign, but no explicit means of opt-in was given.

The opt-in method must meet express consent requirements for informational messaging.
For example:

• The consumer must clearly agree to receive texts for a specific informational purpose (e.g., appointment reminders, account alerts)

Update the campaign with a valid opt-in collection method and resubmit.

2103

Invalid Call to Action: Received a "certificate verify failed" error for the opt-in URL.

The call-to-action/opt-in mechanism must include:

• A working URL that leads directly to the opt-in form (not a homepage or unrelated page)

Update the campaign with the correct URL and resubmit.

2104

Invalid Call to Action: No website or domain was found with the given opt-in URL.

The call-to-action/opt-in mechanism must include:

• A working URL that leads directly to the opt-in form (not a homepage or unrelated page)

Update the campaign with the correct URL and resubmit.

2105

Invalid Call to Action: This campaign has verbal opt-in, but does not contain an explicit script of what the company says.

If the brand uses a verbal opt-in method, the verbal script must be included in the campaign and contain all required disclosures:

• Brand name
• Types of messages being sent
• Message frequency disclosure
• “Message & Data Rates May Apply” disclosure
• HELP instructions
• STOP instructions
• Link to Privacy Policy and Terms & Conditions

Update the script and resubmit.

2106

Invalid Call to Action: The script for verbal opt-in must contain instructions on how to reach the privacy policy.

Declined reason: Verbal script missing when consumer receives link to Privacy Policy and Terms & Conditions.

Verbal opt-in requires a script in the campaign that includes:

• A link to the brand’s Privacy Policy
• A link to the Terms & Conditions

Note: These are typically provided to consumer on the “initial consent to text” message.
Update the script and resubmit.

2108

Invalid Call to Action: The verbal opt-in script does not contain the brand name.

Verbal opt-in requires a script in the campaign that includes:

• The brand name as part of the spoken disclosure

Update the script and resubmit.

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.

Verbal opt-in requires a script in the campaign that includes:

• A clear explanation of the types of messages the consumer will receive which must reflect the selected use cases

Update the script and resubmit.

2110

Invalid Call to Action: The verbal opt-in script contains no disclosure about the frequency of message delivery.

Verbal opt-in requires a script in the campaign that includes:

• A message frequency disclosure (e.g., “2 msgs/month” or “message frequency varies”)

Update the script and resubmit.

2111

Invalid Call to Action: The verbal opt-in script has no disclosure that message and data rates will apply to messages sent.

Verbal opt-in requires a script in the campaign that includes:

• A clear statement that message and data rates may apply

Update the script and resubmit.

2112

Invalid Call to Action: The verbal opt-in script has no information detailing how a customer can stop receiving messages.

Verbal opt-in requires a script in the campaign that includes:

• Clear opt-out instructions (e.g., “Reply STOP to opt-out”)

Update the script and resubmit.

2113

Invalid Call to Action: The brand name cannot be found in the opt-in form.

The call-to-action/opt-in mechanism must include:

• The brand name, clearly identifying who the user is consenting to receive messages from

Update the opt-in form with this information and resubmit.

2114

Invalid Call to Action: The opt-in form should mention the types of messages a customer can expect to receive.

The call-to-action/opt-in mechanism must include:

• A clear explanation of the types of messages the user will receive which must reflect the selected use cases

Update the opt-in form with this information and resubmit

2115

Invalid Call to Action: The opt-in form must mention message frequency.

The call-to-action/opt-in mechanism must include:

• How often the user will receive messages (e.g., “2 msgs/month” or “message frequency varies”)

Update the opt-in form with this information and resubmit.

2116

Invalid Call to Action: The opt-in form has no disclosure that message and data rates will apply to messages sent.

The call-to-action/opt-in mechanism must include:

• A clear statement that message and data rates may apply, as required by the MNO’s.

Update the opt-in form with this information and resubmit.

2117

Invalid Call to Action: The opt-in form must include information on how a customer can receive help.

The call-to-action/opt-in mechanism must include:

• Instructions on how users can request support (e.g., “Reply HELP for help”)

Update the opt-in form with this information and resubmit.

2118

Invalid Call to Action: The opt-in form must include information on how a customer can opt out.

The call-to-action/opt-in mechanism must include:

• Clear opt-out instructions (e.g., “Reply STOP to opt-out”)

Update the opt-in form with this information and resubmit.

2119

Invalid Call to Action: There is no HELP message available in the verbal opt-in script.

Verbal opt-in requires a script in the campaign that includes:

• Instructions on how the user can get support (e.g., “Reply HELP for help”)

Update the script and resubmit.

2120

Invalid Call to Action: No opt-in URL was found in the campaign submission.

If opt-in is collected online, campaigns must include:

• A direct URL to the online opt-in form
• Or, the opt-in is behind a login or app, provide screenshots of the opt-in process and state that the screenshots have been uploaded in the CTA (recommended to compile multiple screenshots into a single PDF for vetting)

Update the campaign with this information and resubmit.

2121

Invalid Call to Action: The opt-in form must provide instructions on how to find the privacy policy.

The call-to-action/opt-in mechanism must include:

• A link to the brand’s Privacy Policy and Terms & Conditions
• Or, for in-person or physical opt-in methods, a clear reference to where the consumer can view or obtain these documents (e.g., printed copies provided at time of opt-in)

Update the opt-in method with this information and resubmit.

2125

Invalid Call to Action: The webpage used for opt-in does not contain an opt-in form.

Ensure the webpage includes a functional opt-in form with the following required disclosures:

• Brand name
• Types of messages being sent (must reflect selected use cases)
• Message frequency disclosure
• “Message & Data Rates May Apply” disclosure
• STOP instructions
• HELP instructions
• Link to Privacy Policy
• Link to Terms & Conditions

Update the webpage and resubmit the campaign.

2129

Invalid Call to Action: The attachment used for opt-in does not contain an opt-in form.

Ensure the attachment includes an opt-in form with the following:

• Brand name
• Types of messages being sent (must reflect selected use cases)
• Message frequency disclosure
• “Message & Data Rates May Apply” disclosure
• STOP instructions
• HELP instructions
• Privacy Policy Language/Where to Locate (if not a link)
• Terms & Conditions Language/Where to Locate (if not a link)

Update the attachment and resubmit the campaign.

2130

Invalid Call to Action: The attachment used for opt-in does not contain a script for verbal opt-in.

Verbal opt-in requires a script in the campaign that includes:

• Brand name
• Types of messages being sent (must reflect selected use cases)
• Message frequency disclosure
• “Message & Data Rates May Apply” disclosure
• STOP instructions
• HELP instructions
• Privacy Policy Language/Where to Locate (if not a link)
• Terms & Conditions Language/Where to Locate (if not a link)

Update the script attachment and resubmit the campaign.

Rejection code

Rejection Description

Action to Resolve

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.

Do NOT resubmit.
Message content related to high-risk financial services is not permitted over 10DLC.
Examples of high-risk financial services include:

• Short-term loans
• Payday loans
• Credit repair
• Debt consolidation or debt relief
• Cryptocurrency investment or trading

Campaigns containing or promoting this type of content will be rejected.

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.

Do not resubmit.
The following content types are not allowed over 10DLC and will result in campaign rejection:

• Lead generation
• Affiliate marketing
• High-risk financial services

Examples of high-risk financial services include:

• Short-term loans
• Payday loans
• Credit repair
• Debt consolidation or debt relief
• Cryptocurrency investment or trading

Campaigns containing or promoting any of the above will be rejected.

3102

Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow or description.

Do not resubmit.

Lead generation and affiliate marketing are not permitted over 10DLC.

For example:

• Campaigns collecting consumer data to sell or share with third parties
• Marketing on behalf of other brands or partners without direct consumer consent

Campaigns containing or promoting this type of content will be rejected.

*NEW* 3103

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.

Campaign is missing the required “Direct Lending or Loan Arrangement” attribute.

If the campaign involves lending in any form, this attribute must be selected.

For example:

• Sample messages that qualify users for loans
• Requests for personal or financial details related to a loan offer

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?").

Please update the campaign and ensure “Direct Lending or Loan Arrangement” is selected under campaign and content attributes, then resubmit.

3105

Invalid Campaign Description/Attributes: Not all required fields populated.

Campaign is missing the correct selection under campaign and content attributes

If the campaign includes specific content types, the related attributes must be selected correctly.

For example:

• Embedded link content is present in sample messages, but “Embedded Link” is marked as “No”

Example: If a customer selects "No" for Embedded Link, but the sample messages include a URL, they must resubmit the campaign with “Yes” selected under Embedded Link.

Note: Make sure one of your sample messages includes the exact URL that would be send in messages from this campaign.

Please update the campaign and ensure all applicable content attributes are selected correctly, then resubmit.

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.

Campaign is missing the correct campaign and content attribute selections.

If the campaign contains specific content types, the corresponding attributes must be selected.

For example:

• Embedded link content appears in sample messages, but “Embedded Link” is set to “No”

Example: If the sample content includes a URL, the campaign must be resubmitted with “Yes” selected under the Embedded Link attribute.

Please update the campaign and ensure the correct campaign and content attributes selected, then resubmit.

*NEW* 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.

Campaign is missing lending-related content or has the incorrect attribute selected.

If the campaign is related to lending or financing, you must do one of the following:

• Add a sample message that reflects lending-related content and aligns with the brand and use case
• Or, if lending messages will not be sent, update the “Direct Lending or Loan Arrangement” attribute to “No”

Example: A sample message such as “Let us help you get pre-qualified today—submit your vehicle info or SSN to check your loan options” would require the lending attribute to be selected.

Update the campaign accordingly and resubmit.

Rejection code

Rejection Description

 Action to Resolve

4100

Disallowed Content Detected: Sample message contents violate SHAFT-C requirements.

Do NOT resubmit. The use case is disallowed and will be rejected.

Rejection code

Rejection Description

Action to Resolve

5100

Missing Mandatory Message Terminology: The opt-out message must contain the brand name.

The opt-out message must include:

• The brand name
• A clear statement confirming that no further messages will be sent

For example:
“You have opted out of messages from [Brand Name]. You will no longer receive messages.”

Update the STOP message with this information and resubmit.

5101

Missing Mandatory Message Terminology: No valid opt-out keywords are listed. Valid opt-out keywords are: STOP, END, UNSUBSCRIBE, and CANCEL.

Please let all opt-out keywords be supported. At minimum, STOP must be supported.

5102

Missing Mandatory Message Terminology: The opt-out message must contain a confirmation that no more messages will be sent.

The opt-out message must include:

• The brand name
• A clear confirmation that the user will no longer receive messages

For example:
“You have opted out of [Brand Name] messages. You will no longer receive further texts.”

Update the STOP message with this information and resubmit.

5103

Missing Mandatory Message Terminology: HELP is not listed as a help keyword.

 Please let all HELP keywords be supported. At a minimum, HELP must be supported.

5104

Missing Mandatory Message Terminology: The opt-in message must contain the brand's name.

The opt-in message must include:

• The brand name to clearly identify who is sending the messages

Update the opt-in confirmation message with this information and resubmit.

5105

Missing Mandatory Message Terminology: The opt-in message must contain disclosures on message frequency.

The opt-in message must include:

• A clear message frequency statement (e.g., “2 msgs/month” or “Message frequency may vary”)

Update the opt-in confirmation message with this information and resubmit.

5106

Missing Mandatory Message Terminology: The opt-in message must contain disclosure mentioning data rates may apply.

The opt-in message must include:

• A clear disclosure that standard carrier message and data rates may apply

Update the opt-in confirmation message with this information and resubmit.

5107

Missing Mandatory Message Terminology: Opt-in message does not contain HELP keyword.

The opt-in message must include:

• Clear instructions on how users can get assistance (e.g., “Reply HELP for help”)

Update the opt-in confirmation message with this information and resubmit.

5108

The opt-in message must contain the provided opt-out keywords.

The opt-in message must include:

• A clear opt-out keyword (e.g., “Reply STOP to opt-out”)

Update the opt-in confirmation message with this information and resubmit.

Rejection code

Rejection Description

Action to Resolve

6100

Invalid Brand Info: Sole proprietors are not yet supported.

Bandwidth does not support Sole Proprietor use cases at this time.

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}

Identical campaigns without meaningful differentiation are not allowed and are considered snowshoeing.

If more than 49 numbers are needed:

• Submit a Number Pool request through the appropriate process

Or, if there’s a valid reason for identical campaigns:

• Open an appeal ticket and clearly explain the use case

Do not resubmit without resolving through one of these methods.

6102 

Other Invalid Campaign Feature: The email and/or phone number must not contain any spaces.

Check contact details for extra spaces before or after your inputs.

Rejection code

Rejection Description

Action to Resolve

7100

Invalid Privacy Policy: No privacy policy URL was found in the campaign submission.

Please provide the link to the privacy policy in the Privacy Policy Link field.

7101

Invalid Privacy Policy: No website or domain was found with the given privacy policy URL.

Please confirm the link to the Privacy Policy leads to the direct page.

7102

Invalid Privacy Policy: The link or attachment used to analyze the privacy policy does not appear to show an actual privacy policy.

Please ensure the link provided directs to the brand's Privacy Policy.

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.

Update the Privacy Policy to make it clear that text messaging opt-in is not shared with any third parties.

*NEW* 7105

Invalid Privacy Policy: Received a 'certificate verify failed' error for the privacy policy URL.

Please confirm the link to the Privacy Policy leads to the direct page.

Rejection code

Rejection Description

Action to Resolve

8100

Invalid Sample Messages: At least one sample message must contain opt-out language.

Update at least one of the sample messages to include opt-out language (Reply STOP to stop).

8101

Invalid Sample Messages: All sample messages must contain the brand name.

Ensure each sample message includes the Brand name.

8102

Invalid Sample Messages: A sample message must be provided for each use case and sub-use case.

Not all selected use cases are represented in the sample messages.

Each selected use case must be reflected in at least one sample message.

For example:

• If the campaign includes Account Notifications, Customer Care, and Marketing, provide one sample message for each of those use cases

Update the sample messages to cover all selected use cases and resubmit.

Error code

Rejection reason

Recommended action

1001

The campaign appears to be for an age-gated content type, but age gate attribute is not selected.

Age-gated content flag is missing

If the campaign involves alcohol, tobacco, firearms, etc., set Age Gated Content Attribute to “Yes.”

If no, clarify that in the campaign description.

1002

Campaign is for direct lending or loan arrangement and is missing the content attribute indicating direct lending.

Missing direct lending content flag.
If this involves loans or lending, set Direct Lending Content Attribute to “Yes.”
If not, clarify in the campaign description.

Error code   

Rejection reason

Recommended action

2001

Campaign registration is not unique or duplicate campaign

Duplicate campaign detected for the same brand.

Duplicate campaigns under the same Brand are not allowed as it can imply “Snowshoeing” or “Spam” activity.

Revise the campaign to make unique case, content, or purpose.

2002

Unclear campaign description

Add a clear explanation of what messages will be sent.
Make sure it matches the selected use cases.

2003

Campaign description does not match declared use case(s)

 Update the description to align with the selected use case(s).

Or, if the use case(s) are wrong, submit a new campaign with correct use case(s).

2004

Campaign description does not match sample messages

 Update the description or sample messages so they are consistent with the selected use case(s).

Note: Must be at least 1 Sample Message per Use Case(s) Selected

2005

 
Undeclared use case

 If the description mentions a use case that wasn’t selected revise the description.

 
2006

 Update the campaign to match the registered brand or DBA name exactly.

Error code   

Rejection reason      

Recommended action          

MNO/CTIA Reference

3001A

Call-to-action does not obtain sufficient consent

All CTAs must obtain consent via a proper consent mechanism.

For example…

·         Public “Contact Us” webpage = Provide direct URL

·         Private Webpage/Login Required = Upload PDF of opt-in steps

·         Verbal Conversation Opt-In = Upload PDF Script of entire conversation

·         Advertisement = Upload/Provide URL of Advertisement

Review what is missing, update CTA with the details and resubmit.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3002A

A Call-to-action does not contain registered/DBA brand name

The company/brand name must be included in the CTA and must match the registered Brand. Update the campaign’s call-to-action with these details and resubmit.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3003A

Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions.

“Text HELP for HELP” or customer care contact information must be provided in either the CTA or the Terms & Conditions

Make sure the CTA and T&Cs page to include…

·         “Text HELP for HELP”,

·         OR, customer care contact information for help.

·         Or, HELP instructions,

Then update the campaign’s call to action to include this information and resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action customer care contact information

3004A

Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel)

The call-to-action must include instructions on how consumers can opt out of the message program

For example:

·         “Text  STOP to opt out.”

Update the call-to-action with this information and resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action how to opt out

3005A

Call-to-action does not contain message frequency disclosure for recurring message program

The call-to-action must include Frequency at which messages will be sent to end users

For example:

·         “Msg frequency varies”

·         “Weekly recurring messages”

·         “Frequency depends on your interactions”

Update the call-to-action with this information and resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency

3006A

Call-to-action does not contain "message and data rates may apply" disclosure

The call-to-action must include…

·         The message and data rate disclosure, as mandated by U.S. carriers.

Update the call-to-action with this information and resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency

3007A

Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions

The call-to-action must include…

·         A link to the message program T&C

·         or the uploaded document complete message program T&C and describe when consumer is provided it

Update the call-to-action with this information and resubmit.

Note: Privacy Policy and T&C must be visible to consumers before opt-in occurs.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3008A

Call-to-action does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties

Mobile opt-in data (for example, 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 referencing uploaded documents and description of when consumers are provided access to the privacy policy,

Update the call-to-action with this information and resubmit.

Note: Privacy Policy and T&C must be visible to consumers before opt-in occurs. Statements such as “Personal information will not be shared” is too general and will risk rejection.

See the CTIA best principles for more information. 5.1 Consumer Consent and 5.2.1 and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3010A

Call-to-action does not contain a robust age gate for age-restricted message program (alcohol/firearms/tobacco)

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.

Messaging Principles and Best Practices 5.3.1 Short Code Monitoring Handbook SHAFT guidelines are applied to all US Messaging Programs See 3.5 PROGRAM CONTENT T-Mobile Code of Conduct V2.2 6.6 Controlled Substances and Adult Content Check out

3011A

Call-to-action is missing/inaccessible

Add a working URL to the live opt-in page.

If the opt-in is behind a login or private URL, upload PDF of screenshots showing the full opt-in process.

Then update CTA and resubmit.

See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent

3012A

Call-to-action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear.

All CTAs must obtain consent with messaging disclaimers, privacy policy and terms & conditions via the proper consent mechanism for SMS.

Make sure all requirements are included in CTA with this information and resubmit.

This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. CTA's for multiple types of communication are not considered clear and concise or an appropriate consent mechanism as the end user cannot select to ONLY receive SMS messages or NOT receive SMS
messages but receive other types of messages. See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent

Error code   

Rejection reason      

Recommended action          

MNO/CTIA Reference

3001B

Website CTA doesn’t contain compliant consent requirements

Update the CTA to include full SMS disclaimer, links to Privacy Policy and T&C, and remove pre-filled consent. Opt-in must be optional.
Then resubmit with updated link or screenshots for private URL Opt-ins.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3002B

Brand name missing from CTA

Add the registered brand name or DBA name to the CTA mechanism.

It must match or clearly relate to the registered brand.

Update campaign information and resubmit.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3003B

Call-to-action/website opt-in does not contain HELP instructions or missing HELP instructions in Terms & Conditions

Add “Reply HELP for help” or similar support info to the CTA or Terms & Conditions.

Make sure the CTA and T&Cs page to include…

·         “Text HELP for HELP”,

·         OR, customer care contact information for help.

·         Or, HELP instructions,

 Then resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action customer care contact information

3004B

Call-to-action/website opt-in does not contain STOP instructions (for example, Reply STOP to cancel)

Add clear opt-out language like “Reply STOP to opt-out” to the CTA/opt-in mechanism. Then resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action how to opt out

3005B

Call-to-action/website opt-in does not contain message frequency disclosure for recurring message program

The call-to-action/opt-in mechanism must include outbound message Frequency at which messages will be sent to end users. For example:

·          “Msg frequency varies”

·         “Weekly recurring messages”

·         “Frequency depends on your interactions”

Update the call-to-action with this information and resubmit

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency

3006B

Call-to-action/website opt-in does not contain "message and data rates may apply" disclosure

The call-to-action/opt-in mechanism must include:

• “Message and Data Rates May Apply” disclosure

As mandated by U.S. carriers. Update the call-to-action/opt-in mechanism with this information and resubmit.

Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action; associated fees

3007B

Call-to-action/website opt-in does not contain complete terms and conditions OR link to complete terms and conditions

The call-to-action/opt-in mechanism must include:

• A link to the message program Terms & Conditions
• Or the full Terms & Conditions language directly in the opt-in experience

Update the call-to-action with this information and resubmit.

See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3008B

Call-to-action/website opt-in does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties

The call-to-action/opt-in mechanism must include:

• A link to the privacy policy or clear language referencing it
• A statement that mobile opt-in data (e.g., phone numbers) will not be shared with third parties

Update the call-to-action with this information and resubmit

See the CTIA best principles for more information. 5.1 Consumer Consent and 5.2.1 and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent

3010B

Call-to-action does not contain robust age gate for age-restricted message program (alcohol/firearms/tobacco)

The call-to-action/opt-in mechanism must include:

• A valid age gate if the message content involves age-restricted goods (e.g., alcohol, tobacco, firearms)
• At minimum, the user must enter day, month, and year of birth before receiving messages

If this content is present and no age gate is shown, the campaign will be rejected. Implement the age gate and resubmit.

Messaging Principles and Best Practices 5.3.1 Short Code Monitoring Handbook SHAFT guidelines are applied to all US Messaging Programs See 3.5 PROGRAM CONTENT T-Mobile Code of Conduct V2.2 6.6 Controlled Substances and Adult Content Check out

3011B

Call-to-action is missing/inaccessible

The call-to-action/opt-in mechanism must include:

• A working URL to the live opt-in page.
• Or for URLs behind a private login, provide screenshots of the opt-in process in a PDF for upload

Update the campaign with this information and resubmit.

See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent

3012B

Call-to-action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear.

The call-to-action/opt-in mechanism must include:

• A clear SMS consent mechanism (e.g., checkbox, keyword entry, or written acknowledgment)
• Consent must be explicit and not pre-filled or assumed

Update the call-to-action with this information and resubmit.

This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. CTA's for multiple types of communication are not considered clear and concise or an appropriate consent mechanism as the end user cannot select to ONLY receive SMS messages or NOT receive SMS messages but receive other types of messages. See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent

Error code   

Rejection reason      

Recommended action          

MNO/CTIA Reference

6001

Opt-in message/Confirmation MT does not contain registered/DBA brand name

The opt-in message must include:

• The company or brand name that matches the registered brand exactly
• Or is clearly recognizable
• Or updated to match TCR Registered DBA Brand Name

Update the opt-in message with this information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages

6002

Opt-in message/Confirmation MT does not contain HELP instructions (for example, Reply HELP for help) 

The opt-in message must include:

• Clear HELP instructions (e.g., “Reply HELP for help”) so users know how to get support

Update the opt-in message with this information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages.

6003

Opt-in message/Confirmation MT does not contain opt-out instructions (for example, Reply STOP to stop)

The opt-in message must include:

• Clear STOP instructions (e.g., “Reply STOP to opt-out”) so users know how to unsubscribe

Update the opt-in message with this information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages.

6004

Opt-in message/Confirmation MT does not contain message frequency disclosure (#msgs/mo, msg frequency varies, recurring messages, and so on.)     

The opt-in message must include message frequency disclosure

For example:

• “Message frequency varies”
• or “2 msgs/month”
• or “Once a week”

Update the opt-in message with this information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages.

6005

Opt-in message/Confirmation MT does not contain clear and conspicuous language about any associated fees or charges and how those charges will be billed. (for example, "message and data rates may apply" disclosure)     

The opt-in message must include:

• A clear “Message and Data Rates May Apply” disclosure to inform users of potential carrier fees

Update the opt-in message with this information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages.

6006

Opt-in message/confirmation MT not provided          

The campaign must include an opt-in confirmation message that contains:

• Brand name
• Message frequency disclosure
• Opt-out instructions (e.g., “Reply STOP to opt-out”)
• HELP instructions (e.g., “Reply HELP for help”)
• Message and data rate disclosure

Update the opt-in message with this complete information and resubmit.

CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages.

6007

HELP message does not contain registered/DBA brand name  

The HELP message must include:

• The company or brand name that matches the registered brand exactly
• or is clearly recognizable
• or match the TCR registered DBA Brand Name

Update the HELP message with this information and resubmit.

CTIA Short code Monitoring Handbook for HELP keyword response requirements. HELP Mobile Terminated Program (brand) name OR product description. Additional customer care contact information (for example, a toll-free number, 10-digit telephone number) T-Mobile Code of Conduct V2.2 section 3.7 Business Recognition

6008

HELP message does not contain support contact (email, phone number, or support website)         

The HELP message must include Customer support contact info so users know how to get assistance.
For example:

• A support email,
• or phone number,
• or support website URL

Update the HELP message with this information and resubmit.

CTIA Short Code Monitoring Handbook for HELP keyword response requirements. HELP Mobile Terminated. Program (brand) name OR product description. Additional customer care contact information (for example, a toll-free number, or a 10-digit telephone number).

6009

HELP message support contact email address does not match the registered brand support email address              

The HELP message must include:

• A support email that matches the one registered in The Campaign Registry (TCR)

Update the HELP message with the correct email and resubmit.

This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. More information about customer care and HELP can be reviewed in various sections of many Industry Guidelines.

6010

Opt-out message does not contain registered/DBA brand name  

The STOP response must include:

• The brand name that matches the registered brand or DBA exactly as registered in TCR or is clearly recognizable

Update the STOP response with this information and resubmit.

CTIA Short Code Monitoring Handbook for STOP keyword response requirements. Opt-Out Mobile Terminated. Program (brand) name OR product description. Confirmation that no further messages will be delivered. See also CTIA Messaging Principles and Best Practices 5.1.3 Consumer Opt-Out.

6011

Opt-out message does not indicate that no further messages will be sent             

The opt-out message must include:

• A clear confirmation that no further messages will be sent
• E.g., “You have successfully unsubscribed and will no longer receive messages from [Brand Name]”

Update the opt-out message with this information and resubmit.

CTIA Messaging Principles and Best Practices 5.1.3 Consumer Opt-Out

6012

Sample message(s) do not contain registered/DBA brand name  

The sample messages must include:

• The company or brand name that matches the registered brand exactly or is clearly recognizable

Update the sample messages with this information and resubmit.

This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. Ensuring the brand name in all messages will also help reduce SPAM complaints and is in line with the T-Mobile Code of Conduct section 3.7 Business Recognition.

6013

Sample message(s) contain public URL shortener               

The sample messages must include:

• A branded URLs

Public URL shorteners such as bit.ly or tinyURL are not permitted to be sent in 10DLC message content.
Update the sample messages with a compliant URL and resubmit.

See T-Mobile Code of Conduct V2.2 4.7 URL Cycling / Public URL Shorteners or AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messaging Techniques

6014

Sample message(s) use case does not match declared use case(s)              

The sample messages must include:

• Content that clearly reflects the registered use case(s)

If the messages don’t match the selected use case, update them or register a new campaign with the correct use case(s), then resubmit.

Inference that sample messages should be in line with the remainder of the program to be clear and concise

Error code              

Rejection reason        

Recommended action            

MNO/CTIA Reference

7001

This brand or program references third-party job boards             

Messaging content related to third-party job boards is not permitted.

This is considered disallowed content.            

See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns

7002

This brand or program appears to be lead generation or affiliate marketing.               

The brand website or messaging content examples appear to be lead generation or affiliate marketing.

These are disallowed content types. 

See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns. TCR Submission dictates you must attest that Affiliate Marketing will not be a part of this campaign.

7003

This brand or program appears to include disallowed content -gambling.               

Message content related to gambling is not permitted.

If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected.               

See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns

7004

This brand or program appears to include disallowed content - high risk financial services       

Message content related to high-risk financial services is not permitted.

For example:

• Short-term loans
• Cryptocurrency

If the brand's website indicates that their message program will be sending this type of content, the campaign will be rejected.

See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns

7005

This brand or program appears to include disallowed content - illegal substances    

Message content related to federally illegal drugs is not permitted.

For example:

• Cannabis
• Fentanyl
• Psychedelics

If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected.

CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns

7006

This brand or program appears to include disallowed content - SHAFT (sex) with no robust age gate              

Message content related to age-restricted products or content is not permitted without a robust age gate.

For example:

• Sexually explicit items or images

A valid age gate must be implemented before opt-in (e.g., day/month/year of birth). Update the opt-in process with this requirement and resubmit.     

CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content

7007

This brand or program appears to include disallowed content - SHAFT (alcohol/firearms/tobacco/vape) with no robust age gate     

Message content related to age-restricted products is not permitted without a robust age gate.

For example:

• Alcohol
• Tobacco

A valid age gate must be implemented before opt-in (e.g., day/month/year of birth). Update the opt-in process with this requirement and resubmit.

CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content

7008

This brand or program appears to include disallowed content -competitive marketing.          

Message content that promotes or markets services competitive with U.S. mobile carriers is not permitted.

For example:

• Over-the-top (OTT) messaging apps (e.g., WhatsApp, Telegram, Signal)
• SIM-less texting or calling apps (e.g., TextNow, Google Voice)
• Carrier replacement or bypass services (e.g., VoIP-only services that avoid mobile networks)

If such content is present, the campaign will be rejected. 

Competitive Marketing programs (programs that promote or market services that would be deemed as competitive in nature by the US Operators, that is, wireless service) are not permitted. This requirement is based on precedence (previously submitted and rejected programs).

7009

This brand or program appears to include disallowed content - weapons that are not legal in all 50 states.     

Message content related to certain weapons that are not legal in all 50 states is not permitted.

For example:

• Switchblades
• Brass knuckles
• Modified firearms

If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected.

CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content 5.2 Disallowed Content

7010

This brand or program appears to include disallowed content - 3rd party debt collection             

Message content related to third-party debt collection is not permitted.

For example:

• Debt forgiveness
• Debt consolidation
• Debt reduction
• Credit repair programs

If the campaign includes this type of content, it will be rejected.

T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns

7011

This brand or program appears to include disallowed content - firearms that are not legal in all 50 states.     

Message content related to firearms that are not legal in all 50 states is not permitted. For example:

• Modified or restricted firearms
• Firearms accessories banned in certain states

If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected.

CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content 5.2 Disallowed Content

7012

This brand or program appears to include disallowed content – HATE speech              

Message content related to hate speech is not permitted.

For example:

• Content that promotes violence, discrimination, or hostility toward individuals or groups based on race, religion, gender, sexuality, or nationality

This is considered disallowed content, and the campaign will be rejected.

See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns.

3000

Website provided for CTA is inaccessible/does not exist/error status.

The call-to-action/website must include:

• A working, accessible website that can be reviewed without errors (e.g., not blank, broken, or returning a 404/status error)

Update the campaign with a functional URL and resubmit.

1003              

Brand website is inaccessible/does not exist/error status.              

The brand website must be:

• Live, accessible, and free of errors (e.g., not returning a 404, blank page, or domain not found)

Update the campaign with a functional brand website and resubmit.

1004

Website is not able to be translated to English              

The brand website must be:

• Viewable in English, either by default or with a built-in translation option

If the website cannot be reviewed in English, the campaign will be rejected. Update the website and resubmit.

Error code   

Rejection reason      

Recommended action          

MNO/CTIA Reference

8001

Brand website or campaign references charitable donations and the declared use case is not charity            

If the brand’s website or campaign details show that charitable donations are being solicited through messaging, the correct use case must be selected.

For example:

• Nonprofit donation requests
• Fundraising messages

Register a new campaign using the Charity use case and resubmit.

Campaigns require a complete, clear, and concise campaign submission for proper review per TCR and US operators. See the CTIA Messaging Principles and Best Practices and Review Operator Codes of Conduct.

8002

Brand website or campaign references political content and declared use case is not political    

If the brand’s website or campaign details show that political content is being sent through messaging, the correct use case must be selected.

For example:

• Candidate promotion
• Political party messaging
• Advocacy or issue-based campaigns

Register a new campaign using the Political use case and resubmit.

8003

Brand website or campaign references cart reminders but declared use case is not marketing.      

If the brand’s website or campaign details show that abandoned cart notifications are being sent, the correct use case must be selected.

For example:

• Reminders to complete a purchase
• Promotions tied to abandoned carts

Register a new campaign using the Marketing use case and resubmit.

8004

Brand website or campaign references multiple use cases but only one declared use case is selected 

If the message program supports multiple use cases, all applicable use cases must be declared.

For example:

• Sending both account updates and promotional offers
• Providing delivery notifications and customer care responses

Register a new campaign with all correct use cases selected and resubmit.

Error code   

Rejection reason      

Recommended action          

MNO/CTIA Reference

9001

Campaign submitted is POLITICAL but does not contain the required information for this use case    

Political message programs must include:

• Politician/Organization Name
• FEC Committee ID
• Politician/Organization Website as part of the submission.

These should be included in the program summary so we can confirm this information during the review

T-Mobile Code of Conduct V2. 6.1 Political Messaging

9002

Campaign submitted is CHARITY but does not contain the required information for this use case    

CHARITY programs must provide the following information in the Campaign Description/Program Summary for appropriate review. Provide the following Charitable Organization information for proof of qualified as tax-exempt under Section 501(c)(3) of the Internal Revenue Code:

• Name of Company/Non-Profit Organization
• Tax Identification (EIN)
• Charitable Organization Website
• Accreditation Organization Website Listing Company/Non-Profit

T-Mobile Code of Conduct V2 6.7 Charitable Donation

Error Code

Error Description

Recommended action

506

Unable to translate; for proper review, the campaign must be in English.

Please ensure that all content in your campaign submission, including Call To Action (CTA), Message Flow, and Sample Messages, is in English.

601

Campaign Attributes do not match the website and/or sample message content.

Campaign is missing the correct campaign and content attribute selections.

If the campaign includes specific content types, the related attributes must be selected accurately.

For example:

• Sample content includes links, but “Embedded Link” is marked as “No”

Example: If “No” is selected for Embedded Link and the sample messages contain a URL, the campaign must be re-created with “Yes” selected for that attribute.

 Please update the campaign with the correct campaign and content attributes selected, then resubmit.

602

Inaccurate Registration. Inconsistency between the sample message and the use case.

Selected use case does not match the sample message content.

The selected use case must align with the content shown in the sample messages.

For example:

• If “Charity” is selected but the sample messages contain appointment reminders, the campaign will be rejected

To resolve, either:

• Update the sample messages to reflect the selected use cases
• Or, re-create the campaign with use cases that matches the content

Then resubmit.

603

Inaccurate Registration. Inconsistency between the website, brand name, and/or sample messages, or inconsistent sample messages.

Website, sample messages, and brand are not aligned.

All elements of the campaign must be consistent and clearly related.

For example:

• If the brand is ABC Physicians, sample messages should not promote clothing sales, and the website should not belong to a marketing firm
• A correct alignment would be: ABC Physicians as the brand, sending appointment reminders, with a link to their medical practice website

Update the campaign so that the brand, website, and messaging content are all consistent, then resubmit.

611

Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website).

Required keyword response messages are missing mandatory disclosures.

Please review your keyword responses for Opt-in (JOIN), HELP, and STOP. Each must include the following:

Opt-in confirmation (JOIN):

• Brand name
• HELP instructions (e.g., “Reply HELP for help”)
• Message frequency disclosure (e.g., “2 msgs/month”)
• “Message & Data Rates May Apply” disclosure
• STOP instructions (e.g., “Reply STOP to opt-out”)

HELP message must include:

• Brand name
• A valid support contact (toll-free number, email, or support website)

STOP confirmation message must include:

• Brand name
• Confirmation that the user has opted out
• Confirmation that no further messages will be sent

Update all keyword response messages with these required elements and resubmit.

701

Prohibited Content; Cannabis.

Do not resubmit.

Cannabis, hemp, and CBD content is strictly not allowed over 10DLC, and campaigns containing or associated with this content will be rejected.

For example:

• A chiropractor’s office listing CBD oils on its website will be denied, even if the campaign is for appointment reminders

Remove all cannabis/hemp/CBD references from the brand’s website and messaging presence to be eligible for 10DLC registration.

Note: This restriction applies to the brand’s website as well — even if the messaging does not promote CBD directly.

702

Prohibited Content; Guns/Ammo {Failure to age gate}.

Campaign is missing proper proof of age gating for age-restricted content.

Please only resubmit once proper age verification is in place.

Best practice:

• Require users to manually enter their MM/DD/YYYY birthdate before accessing the opt-in page

The website will be reviewed for a valid age gate. Ensure this is implemented and clearly shown before resubmitting.

703

Prohibited Content; Explicit sexual.

Do NOT resubmit. 

Explicit sexual content is not allowed over 10DLC, and campaigns related to this content will be rejected.

704

Prohibited Content; Gambling.

Do NOT resubmit. 

Gambling content is not allowed over 10DLC, and campaigns related to this content will be rejected.

705

Prohibited Content; Hate.

Do NOT resubmit. 

Hate speech is not allowed over 10DLC, and campaigns related to this content will be rejected.

706

Prohibited Content; Alcohol
{Failure to age gate}.

Age gate is missing or insufficient for age-restricted content.

Please only resubmit once proper proof of age gating is in place.

Best practice:

• Require users to manually enter their MM/DD/YYYY date of birth before they can access the opt-in page

The website will be reviewed for compliance. Do not resubmit until the age gate is clearly implemented.

707

Prohibited Content; Tobacco / Vape {Failure to age gate}.

Age gate is missing or insufficient for age-restricted content.

Please only resubmit once proper proof of age gating is in place.

Best practice:

• Require users to manually enter their MM/DD/YYYY date of birth before they can access the opt-in page

The website will be reviewed for compliance. Do not resubmit until the age gate is clearly implemented.

708

Lead Gen/Affiliate Marketing prohibited; other.

Do NOT resubmit. 

Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected.

709

Lead Gen/Affiliate Marketing prohibited; high-risk financial services.

Do NOT resubmit. 

High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected.

710

Reseller / Non-compliant KYC. Register the brand info, not the agency or software provider behind the brand.

Know Your Customer (KYC) details are not aligned with the actual message sender.

The brand listed in the campaign must be the entity sending the messages, not the reseller or software provider.

For example:

• If the brand is listed as ABC Wireless Reseller, but the sample messages are appointment reminders from a doctor’s office, the campaign will be rejected
• The brand should instead be the doctor’s office, since they are the actual sender of the messages

Update the campaign so that the brand name, sample messages, and business information all reflect the true message sender, then resubmit.

711

Repeated use of the same EIN for multiple different brands.

Only one brand should be registered per EIN, and it must reflect the actual message sender.

Do not resubmit unless:

• The brand has been updated to reflect the correct legal entity (EIN, company name, etc.)
• The EIN is not already used for another brand

Correct the brand information to avoid duplication and ensure compliance before resubmitting.

712

Misleading Registration. Based on the details submitted, Campaign appears to be a Direct Lending Arrangement, but the appropriate Content Attribute was not selected.

Campaign is missing the required “Direct Lending or Loan Arrangement” attribute. If the campaign involves lending in any form, this attribute must be selected.

For example:

• Sample messages that qualify users for loans
• Requests for personal or financial details related to a loan offer

Example: If the campaign type is marked as Marketing, but a sample message says, “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?”, the campaign must indicate lending under attributes.

Please update the campaign and ensure “Direct Lending or Loan Arrangement” is selected under campaign and content attributes. Then resubmit.

713

Appears to be a large company or a company that would have an official email domain. Check for fraud, and use the official/working email domain.

The support email address does not appear to match the brand or legal entity.

If the company is well-known or established, the email should use an official business domain.

For example:

• A large company like ABC BANK should not use jsmith@gmail.com
• Instead, it should use something like jsmith@abcbank.com

Please update the email to reflect the official domain of the business and resubmit.

714

Invalid Opt-In. Permission to text users via a court order does not meet the carrier's code of conduct.

The current opt-in method is non-compliant.

If you can obtain opt-in using a compliant method the campaign can be resubmitted.

For example:

·         Online form

·         Physical form

·         Keyword

·         Or verbal with script),

If no compliant opt-in method is available, do not resubmit.

For example:

• Implied consent (e.g., assuming opt-in because a customer provided their phone number) is not compliant and will be rejected.

801

Not Sole Proprietor. Does not meet small business Sole Prop (EIN) criteria set by TCR and mobile carriers.

At this time, new Sole Proprietor campaigns are not being accepted.

802

Sole Proprietor. Not yet authorized.

Bandwidth is not supporting Sole Proprietor use cases at this time.

803

Add a checkbox at Call to Action to avoid a forced opt-in consent.

Opt-in appears to be forced or mandatory, which is not compliant.

Opt-in must be voluntary, and users must have a clear choice to participate.

Please provide details on how opt-in is collected to confirm that:

• Participation is optional
• The consumer is not required to opt in to complete another action (e.g., submit a form or make a purchase)

Recommended fix: Use an optional checkbox for opt-in with all required disclosures. Update the campaign and resubmit.

804

Unable to verify, need a website/ working website, or complete CTA information if opt-in occurs outside of the website.

Call-to-action (CTA) is insufficient or unclear.

The CTA must clearly explain how the end user signs up to receive messages and meet all carrier requirements.

To resolve, ensure the campaign includes:

• A working website link to the opt-in page
• A clear, step-by-step description of how the user opts in
• Confirmation that opt-in is 1-to-1 (not shared, forwarded, or implied)
• No use of implied consent or third-party opt-in

Update the campaign with complete details and resubmit.

805

A compliant privacy policy is required on the website.

Privacy policy is missing or non-compliant.

Per CTIA Guidelines 5.2.1, message senders must maintain a privacy policy that is:

• Easily accessible to the consumer
• Referenced in the call-to-action or opt-in experience

You may receive this denial if:

• No privacy policy is provided
• Or, the privacy policy allows sharing consumer information with third parties for marketing

To move forward:

• Add a compliant privacy policy that prohibits sharing opt-in data with third parties for marketing
• Or, revise the existing policy to remove non-compliant language

Then update the campaign and resubmit.

806

Unable to verify, needs compliant and accurate CTA information. Update with specific path for mobile opt-in.

The call-to-action (CTA) is either inaccurate or incomplete.

This may occur if:

• The CTA does not clearly explain how and where the user opts in (e.g., online, verbal, written)
• Or, the opt-in form is on the website but does not include a phone number field, making SMS opt-in impossible

To resolve:

• Provide an accurate CTA that clearly describes the opt-in method
• Ensure the opt-in form includes a phone number field for message delivery

Update the campaign with these corrections and resubmit.

807

Unable to verify inauthentic website.

Website link is broken, inaccessible, or unrelated to the registered brand.

Please ensure that:

• All website URLs provided are active and accessible
• The website content is directly related to the brand being registered (not a parent company, third party, or unrelated entity)

Update the brand or campaign with a working and relevant link, then resubmit.

808

The campaign has been declined 5+ times.

The campaign has been rejected 5 or more times without sufficient corrections.

Before resubmitting:

• Carefully review all previous rejection reasons
• Ensure all issues are fully resolved

Each resubmission incurs a vetting fee, and repeated rejections suggest the core issues are not being addressed.

809

A compliant privacy policy is required to be attached to registration if not available on the website.

Privacy policy not provided for non-website opt-in.

When opt-in is collected in person or over the phone (not via a website), a compliant privacy policy must be:

• Uploaded to the campaign registration in TCR, or
• Emailed to your Direct Connect Aggregator (DCA) for validation

Ensure the privacy policy clearly states that consumer opt-in data will not be shared or sold, and reflects 10DLC compliance standards. Submit the privacy policy through one of the approved methods before resubmitting the campaign.

851

Add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties). Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website).

Missing compliant privacy policy (1) and/or incomplete keyword (2) response messages. To resolve:

#1 Privacy Policy: Ensure a compliant privacy policy is available in one of the following locations:

The policy must clearly state that consumer opt-in data will not be shared or sold.

• Privacy policy link field
• CTA/Message Flow field
• Or uploaded as a document

#2 Keyword Response Messages: Review and update the following messages to meet compliance:

Opt-in (JOIN) confirmation message must include:

·         Brand name

·         Instructions for HELP (e.g., “Reply HELP for help”)

·         Message frequency disclosure (e.g., “2 msgs/month”)

·         “Message & Data Rates May Apply” disclosure

·         Instructions to opt out (e.g., “Reply STOP to opt-out”)

HELP message must include:

·         Brand name

·         Support contact info (toll-free number, email, or support website)

STOP message must include:+

·         Brand name

·         Confirmation of opt-out

·         Confirmation that no further messages will be sent

Update the privacy policy placement and keyword messages as required, then resubmit.

852

Needs a compliant Privacy Policy. Add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties). Include instructions on how the end user can receive further support from the brand regarding the message program (for example, Reply HELP for help), or this information must be present in the brand's terms and conditions.

Missing Terms and Conditions and/or Privacy Policy.

To resolve, provide the following in the campaign registration:

Terms and Conditions:

• A direct link to the message program’s Terms and Conditions
• Or, include the complete Terms and Conditions language directly in the campaign

Privacy Policy:

• A direct link to the message program’s Privacy Policy
• Or, include language that clearly states mobile opt-in data will not be shared or sold

Update the campaign with both items and resubmit.

861

Needs compliant and accurate CTA information. Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website).

 CTA/Message Flow field is incomplete or unclear, and keyword responses are non-compliant.

To resolve, ensure the following: