TCR Rejection Codes - Complete Index Table

When you submit a TCR (The Campaign Registry) registration through Textr Team, your application goes through a compliance review. If your submission does not meet carrier requirements, it will be rejected with a specific error code.

This article lists all rejection codes and their corresponding solutions. Find your code and jump to the matching solution.

For a complete registration guide, see  The Campaign Registry (TCR) Ultimate Guide .

If you need further assistance, contact our support team at  team.support@textrapp.com .

Solution Quick Reference

Tip: Press Ctrl + F (Windows) or Command + F (Mac) to search for your rejection code, then click to jump to the corresponding solution. 

SolutionApplicable CodesJump
Solution A: Fix Your Website Opt-In803, 804, 806, 2100, 2101, 2102, 2113, 2114, 2115, 2116, 2117, 2118, 2121, 2122, 2123, 2124, 3001A, 3001B, 3002A, 3002B, 3003A, 3003B, 3004A, 3004B, 3005A, 3005B, 3006A, 3006B, 3007A, 3007B, 3008A, 3008B, 3012A, 3012B, CR4002, CR4003, CR4004, CR4005, CR4006, CR4007, CR4008, CR4009, 9103, 9104, 9107, 9109, 9112, 9505, 9604, 9607→ Solution A
Solution B: Fix Your Keyword Messages611, 861, CR7001, CR7002, CR7003, CR7004, CR7005, CR7006, CR8001, CR8002, CR8003, CR9001, CR9002, 9403, 9606→ Solution B
Solution C: Fix Your Verbal Consent Script2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2119→ Solution C
Solution D: Fix Your Opt-In URL or Website2103, 2104, 2120, 3000, CR4015, 3011A, 3011B, 9105, 9110, 9304→ Solution D
Solution E: Implement Age Verification3010A, 3010B, 7007, CR4014, CR3016, CR2017, 702, 706, 1001, 7006, 9202→ Solution E
Solution F: Fix Your Sample Messages9106, 9302, 9503, CR1101, CR1103, CR1104, 6012, 6013, 6014, 8100, 8101, 8102, 9401, 9610, 9611→ Solution F
Solution G: Fix Your Privacy Policy and Terms & Conditions9108, 9608, 805, 809, 851, 852, CR5001, CR5002, CR5003, CR5004, CR5005, CR5007, CR5010, CR5011, CR6001, CR6002, CR6003, 7100, 7101, 7102, 7103, 9102 (Terms portion)→ Solution G
Solution H: Fix Your Campaign Attributes9301, 601, 3105, 3106, 712, 9212, 1002→ Solution H
Solution I: Fix Your Campaign Description, Use Case & Message Flow1100, 1101, 2001/CR3001, 2002/CR3002, 2003/CR3003, 2004/CR3004, 2005, 2006, CR3010, CR3011, CR3017, CR3018, 9102 (description portion), 3002, 6100, 6101, 9502, 603, 710, 711, 713, 714, 801, 802, CR1106, CR1107, 6001–6011, 8001–8004, 9001, 9210, 9303, 9609, 9612→ Solution I
Solution J: Fix Your Brand & Website InformationCR2001, CR2002, CR2003, CR2004, CR2005, CR2010, CR2011, CR2018, CR2019, CR2020, CR2021, CR2022, CR2023→ Solution J
Solution K: Prohibited Content (Do Not Resubmit)701/9901, 703, 704, 705, 707, 708, 709, 3100, 3101, 3102, 4100, 7001, 7008–7012, 9208, 9209, CR3005, CR3008, CR3009, CR3012–CR3015, CR1105, CR1110–CR1114, CR2006, CR2009, CR2012–CR2016, CR4010–CR4013, CR5011→ Solution K
Solution L: Fix Your Message Terminology5100, 5101, 5102, 5103, 5104, 5105, 5106, 5107, 5108→ Solution L
Solution M: Miscellaneous Errors807, 808, 1003, 1004, 9501, 9999→ Solution M

Solution A: Fix Your Website Opt-In

Use this solution if your website consent form is missing, incomplete, or non-compliant.

Applies to codes: 803, 804, 806, 2100, 2101, 2102, 2113, 2114, 2115, 2116, 2117, 2118, 2121, 2122, 2123, 2124, 3001A, 3001B, 3002A, 3002B, 3003A, 3003B, 3004A, 3004B, 3005A, 3005B, 3006A, 3006B, 3007A, 3007B, 3008A, 3008B, 3012A, 3012B, CR4002, CR4003, CR4004, CR4005, CR4006, CR4007, CR4008, CR4009, 9103, 9104, 9107, 9109, 9112, 9505, 9604, 9607

What Your Opt-In Form Must Include

  • A phone number field (for SMS consent collection)
  • An optional checkbox that is unchecked by default (pre-checked boxes are not allowed)
  • Business name
  • STOP instructions (e.g., "Reply STOP to opt out")
  • HELP instructions (e.g., "Reply HELP for support")
  • Message frequency disclosure (e.g., "Messaging frequency may vary")
  • Rates disclosure ("Message and data rates may apply")
  • Privacy Policy URL (accessible online link)
  • Terms & Conditions URL (accessible online link)

Compliant Consent Language Template

Copy and adapt the following for your website form:

☐ By checking this box, I consent to receive SMS from [Business Name]. Reply STOP to opt out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [Privacy Policy URL] for our Privacy Policy and [Terms URL] for our Terms of Service.

Submission Steps

  1. Add or update the opt-in language on your website using the template above.
  2. Provide the exact URL where the opt-in language appears in your campaign registration submission form.
  3. Ensure the URL is publicly accessible (no login required, no VPN needed, no geographic restrictions).

Code-Specific Notes

CodeAdditional Requirement
803Your website must display the opt-in language. If message types are mentioned (e.g., "promotional"), they must match the use case selected during registration.
2101Marketing/promotional campaigns require written consent. Verbal consent alone is not sufficient. Provide a website form URL or a screenshot of a paper/electronic form.
2102Informational campaigns also require explicit consent. Implied consent (e.g., "the customer provided their number at checkout") is not sufficient.
2113Add your brand/business name to the consent language.
2114Add the message type (e.g., "order updates," "promotional offers") to the consent language.
2115Add "Messaging frequency may vary" to the consent language.
2116Add "Message and data rates may apply" to the consent language.
2117Add "Reply HELP for support" to the consent language.
2118Add "Reply STOP to opt out" to the consent language.
2121Add a reference to your Privacy Policy in the consent language.
2122Add a clickable link to your Privacy Policy in the consent language.
2123Add a reference to your Terms & Conditions in the consent language.
2124Add a clickable link to your Terms & Conditions in the consent language.
3012A / 3012BSeparate SMS consent from other communication consent options. References to other communication types must be completely independent of the SMS consent checkbox and language.
CR4009For marketing use cases, "verbal consent" is not a valid response. Update your CTA and consent collection method before resubmitting.
9109SMS consent must be collected using a separate checkbox dedicated specifically to SMS messaging. Consent for email, calls, marketing, or other communications must not be combined with the SMS consent checkbox.
9112The SMS consent checkbox must be optional and unchecked by default.
9505Marketing and promotional campaigns require written and verifiable consent. Verbal consent is not sufficient.

Other Consent Collection Methods

If you do not collect consent through a website form:

MethodWhat to Submit
Paper/electronic formScreenshot showing the consent language (must include all required disclosures)
Customer texts firstScreenshot showing where your number is publicly displayed and the disclosure text
Email consentComplete email script including all required disclosures
Verbal consentComplete verbal consent script (see Solution C)

Solution B: Fix Your Keyword Messages

Use this solution if your opt-in confirmation, HELP reply, or STOP confirmation messages are missing required disclosures.

Applies to codes: 611, 861, CR7001, CR7002, CR7003, CR7004, CR7005, CR7006, CR8001, CR8002, CR8003, CR9001, CR9002, 9403, 9606

Opt-In Confirmation Message

Must include: brand name, HELP instructions, STOP instructions, frequency disclosure, rates disclosure.

Thank you for opting into SMS messages from [Business Name]. Reply HELP for support. Reply STOP to opt out. Message & data rates may apply. Messaging frequency may vary.

HELP Reply Message

Must include: brand name, support contact information (phone, email, or website).

Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].

Opt-Out (STOP) Confirmation Message

Must include: brand name, unsubscribe confirmation, confirmation that no further messages will be sent.

Thank you for opting out of SMS messages from [Business Name]. To opt back in at any time, reply START. You will receive no additional messages.

Submission Steps

  1. Update the three keyword messages in your submission form using the templates above.
  2. Resubmit your materials in the campaign registration form.

Code-Specific Notes

CodeAdditional Requirement
861This code indicates both your consent collection method (Solution A) and keyword messages (Solution B) have issues. Both must be fixed before resubmitting.
CR7001The brand name in your opt-in message must match the registered brand name or DBA name. A shortened version may be used if it is still clearly identifiable as the same business.
CR8003The email in your HELP message must match the registered campaign support email and should use your company domain (e.g., support@yourbrand.com, not gmail, hotmail, or similar).
CR9001Update your opt-out message to include the company or brand name that matches the registered brand name.
CR9002Update your opt-out message to clearly confirm that the user will no longer receive SMS messages.
9403Use "START," "STOP," and "HELP" as your opt-in, opt-out, and help keywords.

Solution C: Fix Your Verbal Consent Script

Use this solution if you collect consent verbally (by phone or in person) and your script is missing or incomplete.

Applies to codes: 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2119

Complete Verbal Consent Script Template

Your script must include all of the following elements:

☐ Do you consent to receive [message type, e.g., order updates and promotional offers] SMS from [Business Name]? Reply STOP to opt out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [Privacy Policy URL] for our Privacy Policy and [Terms URL] for our Terms of Service.

Missing Element by Code

CodeMissing ElementWhere to Add
2105No script providedSubmit the complete script above
2106Privacy Policy referenceAdd "Visit [Privacy Policy URL] for our Privacy Policy"
2107Terms referenceAdd "Visit [Terms URL] for our Terms of Service" (if Terms are included in Privacy Policy, reference the Privacy Policy URL)
2108Brand nameAdd "from [Business Name]"
2109Message typeAdd specific message types, e.g., "order updates and promotional offers"
2110Message frequencyAdd "Messaging frequency may vary"
2111Message/data ratesAdd "Message and data rates may apply"
2112STOP instructionsAdd "Reply STOP to opt out"
2119HELP instructionsAdd "Reply HELP for support"

Submission Steps

  1. Write your complete verbal script using the template above.
  2. Enter the script in the "How do you obtain consent?" field in the registration form.
  3. Resubmit your materials in the campaign registration form.

Solution D: Fix Your Opt-In URL or Website

Use this solution if your opt-in URL has technical issues (SSL certificate errors, broken links, or inaccessible pages).

Applies to codes: 2103, 2104, 2120, 3000, CR4015, 3011A, 3011B, 9105, 9110, 9304

Code 2103: Certificate Verification Failed

Your SSL certificate is expired, misconfigured, or the URL cannot load over HTTPS.

How to fix:

  1. Renew or fix your SSL certificate so the page loads properly over HTTPS.
  2. Verify the URL loads correctly in a browser before resubmitting.

Codes 2104 / 9105 / 9110 / 2120: Invalid or Missing Opt-In URL

The URL is broken, returns an error, or is not publicly accessible.

How to fix:

  1. Verify the URL loads correctly. If you are outside the US, test from a US network connection.
  2. Ensure the page requires no login, no VPN, and has no geographic restrictions.
  3. Provide the exact URL where the opt-in language appears (do not just provide the homepage unless the opt-in is on the homepage).

Codes 3000 / CR4015 / 3011A / 3011B: CTA Website Inaccessible or Missing URL

The website form in the "How do you obtain consent to send text messages?" question must provide the exact URL where the SMS opt-in language appears.

How to fix:

  1. Provide the exact URL where the opt-in language appears.
  2. Ensure the website is publicly accessible with no login or geographic restrictions.

Code 9304: Website Missing Business Information or Broken Links

Your website must clearly provide information about your business, including the products or services offered, business address, and contact information. All website references included in your brand registration or campaign registration must belong to the business being registered, and all website links must be active and accessible at the time of submission.

If Your Opt-In Is Located in a Section of a Larger Page

  • Provide the URL of that page.
  • Add an additional consent method in the registration form and select "Other."
  • Include instructions explaining where the opt-in form is located. Example: "Consent is collected through the contact form at the bottom of our homepage: [URL]."

Solution E: Implement Age Verification

Use this solution if your campaign involves age-restricted content (alcohol, firearms) and lacks proper age verification.

Applies to codes: 3010A, 3010B, 7007, CR4014, CR3016, CR2017, 702, 706, 1001, 7006, 9202

Requirements

At least two age gates are required:

  • Website entrance age verification
  • SMS consent form age verification

Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or SMS opt-in form. Your website will be reviewed for age-gating compliance.

Important Notes

  • Tobacco- and vaping-related content is prohibited and not allowed under SMS/MMS content policies.
  • For alcohol- or firearm-related campaigns, resubmission is only allowed after proper age verification has been implemented.

Solution F: Fix Your Sample Messages

Use this solution if your sample messages are missing, insufficient, or do not match your campaign.

Applies to codes: 9106, 9302, 9503, CR1101, CR1103, CR1104, 6012, 6013, 6014, 8100, 8101, 8102, 9401, 9610, 9611

Requirements

  1. Submit at least 3 unique sample messages representing the messages you send in your day-to-day business activities.
  2. Include the registered brand name or DBA brand name in every sample message.
  3. Include opt-out language (e.g., "Reply STOP to opt out") in at least one sample message.
  4. Do not use public URL shorteners (bit.ly, tinyurl, etc.), use full website URLs instead.
  5. Sample messages must match the selected campaign use case.

Example

Do not use:

You have a consultation appointment at 8:30 AM on 2/19. Reply STOP to opt out.

Please use:

This is Edward Law Office. You have a consultation appointment at 8:30 AM on 2/19. Reply C to confirm. Reply STOP to opt out.

Code-Specific Notes

CodeAdditional Requirement
9302Verify that your campaign description, sample messages, and website disclosures all match the selected use case.
CR1103Public URL shorteners are prohibited by carriers. Use full website URLs instead.
CR1104Sample messages must reflect the selected use case. Conversational campaigns should not reference promotional or marketing content.
8102If multiple use cases are selected, at least one sample message must be provided for each use case.
9611Ensure your opt-in language clearly describes the types of SMS messages being sent and matches the selected use case.

Solution G: Fix Your Privacy Policy and Terms & Conditions

Use this solution if your Privacy Policy or Terms & Conditions are missing or non-compliant.

Applies to codes: 9108, 9608, 805, 809, 851, 852, CR5001, CR5002, CR5003, CR5004, CR5005, CR5007, CR5010, CR5011, CR6001, CR6002, CR6003, 7100, 7101, 7102, 7103, 9102 (Terms portion)

Privacy Policy Requirements

Your website must include an easily accessible Privacy Policy, available from the homepage or Contact Us page. A compliant Privacy Policy must:

  • Explain what personal information is collected and how it is collected, used, and shared.
  • Clearly state that SMS consent and phone numbers are not shared with third parties or affiliates for marketing purposes.
  • Be publicly accessible to consumers.

If you do not have a Terms and Conditions section dedicated to SMS disclosures, include the following SMS disclosure in your Privacy Policy:

☐ By consenting to receive SMS from [Business Name], you agree to receive [message types, must be consistent with selected use case] SMS messages from us. Reply STOP to opt out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [Privacy Policy URL] for our Privacy Policy and [Terms URL] for our Terms & Conditions.

Terms & Conditions Requirements

Your Terms & Conditions must include the following SMS disclosures:

  • Types of SMS messages being sent
  • Message frequency disclosure
  • "Message & data rates may apply"
  • HELP and opt-out instructions
  • Links to your Privacy Policy and Terms & Conditions

Example:

☐ If you consent to receive SMS from [Business Name], you may receive messages related to [message type]. Messaging frequency may vary. Message & data rates may apply. Reply STOP to opt out or HELP for support. Visit [Privacy Policy URL] and [Terms URL] for more information.

Code-Specific Notes

CodeAdditional Requirement
805Your Privacy Policy must be accessible from the homepage or Contact Us page.
809If your Privacy Policy is not publicly available on your website, contact your service provider to submit it as an attachment.
851Fix both your Privacy Policy and keyword messages (see Solution B).
852Add customer support instructions to your Terms & Conditions. Provide a valid Privacy Policy URL and confirm that mobile opt-in data is not shared.
CR5001Ensure your Terms & Conditions URL is publicly accessible.
CR5002The company name in your Terms must match the registered brand name or DBA name.
CR5003Add a message frequency disclosure to your Terms.
CR5004Add a program description to your Terms.
CR5005Add support contact information to your Terms.
CR5007Add STOP instructions to your Terms.
CR5010Add a Privacy Policy link to your Terms.
CR5011Sweepstakes campaigns require sweepstakes terms in your Terms & Conditions. Note: Sweepstakes messaging is prohibited unless properly registered.
CR6001Verify your Privacy Policy URL is valid and publicly accessible.
CR6002 / CR6003Your Privacy Policy must clearly state that SMS consent and phone numbers are not shared with third parties.
7100Provide a valid Privacy Policy link.
7101Verify your Privacy Policy URL is correct and uses a valid domain.
7102Ensure the linked page is an actual Privacy Policy.
7103Add language stating SMS consent is not shared with third parties.
9102 (Terms)Add "Message & data rates may apply" to your Terms & Conditions.

Solution H: Fix Your Campaign Attributes

Use this solution if your campaign attribute selections do not match your actual content.

Applies to codes: 9301, 601, 3105, 3106, 712, 9212, 1002

Requirements

Verify that your campaign settings match your sample messages and website content:

  • If your sample messages contain phone numbers, select "Yes" for phone numbers.
  • If your sample messages contain URLs, web links, or email addresses, select "Yes" for links.
  • If your website contains age-restricted content, select "Yes" and ensure proper age verification is implemented.
  • If your business offers direct lending or loan agreements, select "Yes" for lending-related content.

Solution I: Fix Your Campaign Description, Use Case & Message Flow

Use this solution if your campaign description is insufficient, your use case selection is incorrect, or there are brand/content inconsistencies in your message flow.

Applies to codes: 1100, 1101, 2001/CR3001, 2002/CR3002, 2003/CR3003, 2004/CR3004, 2005, 2006, CR3010, CR3011, CR3017, CR3018, 9102 (description portion), 3002, 6100, 6101, 9502, 603, 710, 711, 713, 714, 801, 802, CR1106, CR1107, 6001–6011, 8001–8004, 9001, 9210, 9303, 9609, 9612

Campaign Description Requirements

Provide a clear summary of your business and how SMS will be used in the campaign.

Example:

Our business is a medical office specializing in primary healthcare services. This campaign will be used to send appointment reminders and conversational messages related to patient care.

Use Case Consistency Requirements

  • Your campaign description, sample messages, and website disclosures must match the selected use case.
  • Sample messages must reflect the selected use case. For example, if the use case is two-factor authentication, sample messages must contain authentication-related content.
  • Your opt-in language, Privacy Policy, and Terms & Conditions must also align with the selected use case. For example, conversational campaigns should not reference automated, promotional, or marketing SMS messages.

Code-Specific Notes

CodeAdditional Requirement
1100Provide a valid and publicly accessible website URL for your brand.
1101Verify the submitted website URL is correct and active.
2001 / CR3001Make sure the campaign is unique and not previously submitted. If submitting multiple campaigns, include location-specific details.
2003 / CR3003Update either the campaign description or use case so they align correctly.
2005Verify that your campaign description is accurate and that all applicable use cases are correctly selected.
2006Ensure the business name used in messages, website, and campaign matches the registered brand or DBA name.
CR3010If soliciting charitable donations through SMS, the use case must be Charity. Update the description or select the correct use case.
CR3011If sending political content through SMS, the use case must be Political. Update the description or select the correct use case.
CR3017M2M is restricted to non-subscriber-facing message programs only. Register again with the correct use case.
CR3018Make sure your website, sample messages, and brand information are all consistent with the same business.
3002Charity campaigns must include: organization name, EIN, charity website, and accreditation or nonprofit verification listing.
6100Verify that a valid and active website URL was entered in the registration form.
6101Verify the submitted website URL is correct, active, and contains a valid domain.
9502Resubmit using a use case that matches your sample messages and campaign description.
603 / 9303Make sure your website, brand, and sample messages are all consistent with the same business.
710Register the exact brand that sends the messages.
711Each brand must have its own unique EIN.
713Use a company domain email (e.g., support@yourbrand.com, not gmail, hotmail, or similar).
714Court Order consent is not accepted. Use a valid consent method.
801 / 802TCR does not accept applications from businesses that are not officially registered as an LLC or Corporation with the IRS or Canada Revenue Agency.
CR1106The use case must be Charity. Update before resubmitting.
CR1107The use case must be Political. Update before resubmitting.
6001Register the exact brand that sends the messages.
6002Add "Reply HELP for support" to the opt-in message.
6003Add "Reply STOP to opt out" to the opt-in message.
6004Add a frequency disclosure to the opt-in message.
6005Add "Message and data rates may apply" to the opt-in message.
6006Provide complete opt-in, HELP, and opt-out messages (see Solution B).
6007Add the registered or DBA brand name to the HELP message.
6008Add an email, phone number, or website to the HELP message.
6009The email must match the registered support email and use a company domain.
6010Add the registered or DBA brand name to the opt-out message.
6011Clearly state that the user will no longer receive SMS messages.
8001Update the use case to Charity.
8002Update the use case to Political.
8003Update the use case to Marketing.
8004Select all applicable use cases.
9001Political campaigns must include: politician/organization name, FEC Committee ID, official website.
9210The registered brand must be the actual message sender (KYC requirement).
9609Court Order consent is not accepted. Use a valid consent method.
9612Informational campaigns require explicit consent. Implied consent is not permitted.

Solution J: Fix Your Brand & Website Information

Use this solution if there are issues with your brand information or website.

Applies to codes: CR2001, CR2002, CR2003, CR2004, CR2005, CR2010, CR2011, CR2018, CR2019, CR2020, CR2021, CR2022, CR2023

Code-Specific Notes

CodeReasonHow to Fix
CR2001Free email domain usedUse a branded company email instead of Gmail or other public email domains.
CR2002Physical address cannot be verifiedVerify that your physical address is accurate before resubmitting.
CR2003Brand not eligible for DCA campaignsConfirm the brand is eligible before resubmitting.
CR2004Registered brand is reseller or ISV instead of senderThe registered brand must match the business identified in the message content.
CR2005Website missing or inaccessibleVerify the website URL is correct and active.
CR2010Charity content with incorrect use caseProvide: organization name, EIN, website, accreditation/nonprofit listing.
CR2011Political content with incorrect use caseThe use case must be Political. Update before resubmitting.
CR2018Missing or invalid support emailProvide a valid support email and verify it's working.
CR2019Missing or invalid support phoneProvide a valid support phone number and verify it's working.
CR2020Brand name mismatchMake sure your website, sample messages, and brand information are all consistent with the same business.
CR2021Sole Proprietor brand does not qualifyTCR does not accept applications from businesses that are not officially registered as an LLC or Corporation with the IRS or Canada Revenue Agency.
CR2022Brand vetting score too lowImprove business legitimacy and branding before resubmitting.
CR2023Brand email associated with spam complaintsUse a clean, trustworthy business email address.

Solution K: Prohibited Content (Do Not Resubmit)

The following codes correspond to strictly prohibited content. Do not resubmit your campaign.

Applies to codes: 701/9901, 703, 704, 705, 707, 708, 709, 3100, 3101, 3102, 4100, 7001, 7008–7012, 9208, 9209, CR3005, CR3008, CR3009, CR3012–CR3015, CR1105, CR1110–CR1114, CR2006, CR2009, CR2012–CR2016, CR4010–CR4013, CR5011

Prohibited Content Types

Content TypeDescription
GamblingAny form of gambling-related content
High-risk financial servicesHedge funds, stock investments, crypto, NFTs, etc.
Illegal substancesCannabis, kratom, and other illegal substances
SHAFT contentSex, Hate content
Lead generation / affiliate marketingLead generation and affiliate marketing content
Third-party job boardsThird-party job board related campaigns
Sweepstakes (not properly registered)Prohibited unless properly registered as a sweepstakes use case
Competitive marketingContent promoting services competing with US mobile operators
Illegal weaponsWeapons not legal in all 50 states
Third-party debt collectionDebt forgiveness, consolidation, reduction, or credit repair programs
Credit repair / debt reliefCredit repair or debt relief/collection services
Tobacco / vapingTobacco and vaping-related content

This content is prohibited and is not eligible for reconsideration. Do not resubmit.

Solution L: Fix Your Message Terminology

Use this solution if your keyword messages are missing required terminology.

Applies to codes: 5100, 5101, 5102, 5103, 5104, 5105, 5106, 5107, 5108

STOP/Opt-Out Message Requirements

Must include:

  • Registered brand name (business name)
  • Confirmation that the user has unsubscribed
  • A statement that no further messages will be sent

Example:

Thank you for opting out of SMS messages from [Business Name]. To opt back in at any time, reply START. You will receive no additional messages.

Opt-In Message Requirements

Must include:

  • Brand name (business name)
  • HELP instructions (e.g., "Reply HELP for support")
  • Opt-out instructions (e.g., "Reply STOP to opt out")
  • Message frequency disclosure (e.g., "Messaging frequency may vary")
  • Rates disclosure ("Message and data rates may apply")

Example:

Thank you for opting into SMS messages from [Business Name]. Reply HELP for support. Reply STOP to opt out. Message & data rates may apply. Messaging frequency may vary.

Code-Specific Notes

CodeMissing ElementHow to Fix
5100STOP message missing brand nameAdd the registered brand name
5101No valid opt-out keyword providedUse STOP, END, UNSUBSCRIBE, or CANCEL
5102STOP message missing unsubscribe confirmationAdd unsubscribe confirmation and no-further-messages statement
5103HELP keyword missingAdd HELP as a supported keyword
5104Opt-in message missing brand nameAdd the registered business name
5105Opt-in message missing frequency disclosureAdd "Messaging frequency may vary"
5106Opt-in message missing fees disclosureAdd "Message and data rates may apply"
5107Opt-in message missing HELP keywordAdd HELP instructions
5108Opt-in message missing STOP keywordAdd STOP instructions

Solution M: Miscellaneous Errors

Applies to codes: 807, 808, 1003, 1004, 9501, 9999

CodeReasonHow to Fix
807Unable to verify website authenticityYour website must clearly provide business information including products/services, physical address, and contact information. Ensure all links are active.
808Campaign declined five or more timesEach denial may incur a vetting fee. Review and update campaign information carefully before resubmitting. Contact support if needed.
1003Brand website inaccessible or invalidVerify the website URL entered in the brand registration form is correct and confirm the website is active and accessible.
1004Website not available in EnglishYour website must be accessible in English to allow proper compliance review.
9501Duplicate campaign submission detectedDuplicate registrations are not permitted. If multiple registrations are needed, include location information.
9999Registration rejected per customer requestThe campaign was rejected at the request of the customer or support agent to allow updates before resubmission. No action needed.

Notes for Businesses Outside the US

If your business is based outside the US (e.g., a Chinese cross-border e-commerce company), pay special attention to the following:

  1. Business name consistency. Your brand name in the TCR registration must exactly match the legal name on your business documents. Even a small spelling difference can cause rejection.
  2. Website accessibility. Your opt-in URL must be publicly accessible from the US without VPN, login, or regional restrictions. Test your URL from a US-based browser before submitting.
  3. Privacy Policy and Terms. Both must be live pages with active URLs. Placeholder pages or pages behind a login will be rejected.
  4. Use case alignment. Make sure your campaign description, sample messages, and website content all describe the same use case. Inconsistency is one of the most common reasons for rejection among foreign-based sellers.

For detailed guidance on registering as a foreign-based business, see  TCR Registration for Foreign-Based Businesses .

How to Resubmit After a Rejection

  1. In your Textr Team dashboard, enter Setting > Register SMS Campaign > Local Numbers > Campaign Registration to identify the rejection code.
  2. Find the corresponding solution in the index table above.
  3. Fix the issue using the templates in that solution section.
  4. Update your campaign registration form with the corrected information.
  5. Resubmit through the Textr Team portal.

Most rejections can be resolved without deleting your campaign. You do not need to start over.

Note: Please resubmit your Brand Registration within 30 calendar days and your Campaign Registration within 60 calendar days of rejection. Failure to do so may result in the application expiring, requiring you to restart the registration process.

Frequently Asked Questions

 Q1: How long does it take to get approved after resubmitting? + 

Resubmissions typically take 7-14 business days to review. The timeline depends on the complexity of your campaign and the completeness of your submission.

 Q2: Can I register a new campaign instead of fixing the rejected one? + 

Yes. You can deactivate the rejected campaign and register a new one. If you choose this approach, we recommend selecting a use case that better matches your actual message content. Note that all resubmitted materials must strictly comply with carrier requirements. If your previously rejected campaign had a specific rejection code, make sure to follow the fix instructions before resubmitting. Also note that each active campaign has associated fees.

 Q3: Will a rejection affect my brand registration? + 

No. A campaign rejection only affects that specific campaign registration. Your approved brand registration status is not affected.

 Q4: What if I receive a code that is not listed here? + 

Contact our support team at team.support@textrapp.com with the rejection code and details shown in your portal. We can help interpret the reason and guide you through the fix.

For more common registration questions, see  The Campaign Registry (TCR) FAQs .