If your TCR campaign registration is rejected, don’t worry — most rejections can be resolved by updating your registration details, website content, opt-in flow, or compliance disclosures.
This guide explains the most common rejection codes, what they mean, and how to fix them before resubmitting your campaign.
Use the tables below to locate your rejection code and follow the recommended resolution steps.
Tips: To search for the specific code, press Ctrl + F (Windows) or command + F (Mac) and type the code.
If you need further assistance, please contact our support team at team.support@textrapp.com.
Common Registration Rejection Codes
Rejection Code | Reason | How to Resolve |
9108 | Missing Privacy Policy or non-compliant Privacy Policy on your website | Your website must include an easily accessible Privacy Policy, available from the homepage or Contact Us page. A compliant Privacy Policy must:
If you do not have a Terms and Conditions section dedicated to SMS disclosures, please 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 & Conditions.” |
9106 | Missing opt-out language in sample messages | Update your sample messages to include opt-out language, such as “Reply STOP to opt out,” in at least one message. |
9103 | Missing SMS opt-in language on the website form used to collect phone numbers. | If consent is obtained through a website form, provide the exact URL where the opt-in language appears. The opt-in form must meet the following requirements:
Example consent language: “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.” If your website references the type of SMS messages being sent, it must match the selected campaign use case. For example, campaigns registered as Conversational cannot mention promotional, marketing, or automated SMS messages. |
9104 | Insufficient explanation of how consent is collected from recipients outside of your website. | Provide a clear explanation of how consent is collected outside of your website. 1. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc.), submit a screenshot showing the consent language clearly visible. The disclosure must include the business name, STOP/HELP instructions, message frequency disclosure, “Message & data rates may apply,” Privacy Policy URL, and Terms URL. Example 1: “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.” 2. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 2: “Do you 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.” 3. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 3: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type (i.e. Conversational, Marketing, Notifications)] messages 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.” 4. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 4: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
9110 | Invalid or inaccessible website URL | Verify the website URL entered during registration is correct and publicly accessible. |
9606 | Invalid opt-in, HELP, or STOP messages | Update the opt-in, HELP, and opt-out messages in your registration form to meet the following requirements: 1. The opt-in message must include:
Example 1: “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.” 2. The HELP message must include:
Example 2: “Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].” 3. The opt-out message must include:
Example 3: “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.” |
9607 | Unable to verify customer consent process. Update your CTA information and consent flow to clearly explain how users opt in to SMS messaging. | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
9109 | The opt-in language on your website is not specific to SMS. | SMS 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 or disclosure language. |
9112 | SMS checkbox is prechecked or mandatory | SMS consent checkboxes must be optional and unchecked by default. |
9105 | Missing opt-in URL | If consent is collected through a website form, provide the exact URL where the SMS opt-in language appears. If the opt-in language is located in a small section of the homepage:
Example: “We obtain consent through the contact form located at the bottom left of our homepage: [Business URL].” |
9107 | Screenshot of SMS consent flow required | 1. If consent is collected through a paper or electronic form (such as intake forms, agreements, or employee handbooks), submit a screenshot showing the SMS consent language clearly visible. The disclosure must include the business name, STOP/HELP instructions, message frequency disclosure, “Message & data rates may apply,” Privacy Policy URL, and Terms URL. Example 1: “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.” 2. If consent is collected through a website that requires login, registration, or multiple steps to access, submit a screenshot showing where the SMS opt-in checkbox and disclosure language appear. Example 2: “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.” |
9301 | Campaign attributes do not match your website and/or sample message content | Verify that your campaign settings match your sample messages and website content:
Also verify that your website content matches the selected campaign attributes:
|
9608 | Terms & Conditions missing required SMS disclosures | Your Terms & Conditions must include the following SMS disclosures:
If your website references the type of SMS messages being sent, it must match the selected campaign use case. For example, Conversational campaigns cannot mention promotional, marketing, or automated SMS messages. 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.” |
9503 | Less than 3 unique sample messages provided | Submit at least 3 unique sample messages representing the messages you send in your day-to-day business activities. |
9304 | Website lacks sufficient business information and/or has broken links on the website | 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 or campaign registration must belong to the business being registered, and all website links must be active and accessible at the time of submission. |
9209 | High-risk financial services, lead generation, credit repair, or debt relief/collection content detected. | Your sample messages, Privacy Policy, or website contain prohibited high-risk financial services content, such as hedge funds, stock trading, crypto, NFTs, credit repair, debt relief, or similar financial products/services that violate SMS/MMS content policies. This content is prohibited and is not eligible for reconsideration. Do not resubmit the campaign. |
9604 | The opt-in message does not explain how users know to message you first. | Please provide a website URL or verifiable proof, such as a flyer, business card, or other public display, showing where users can find your phone number and how to text you. Example: “You can text [Business Name] at [Phone Number] for information regarding our services. By texting us, you agree to receive [Campaign Type] messages 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.” |
9999 | Registration rejected per customer request | The campaign was rejected at the request of the customer or support agent to allow updates before resubmission. |
Campaign Description & Use Case Errors
Rejection Code | Reason | How to Resolve |
1100 | Brand inconsistency detected: Missing a website URL or supporting attachment containing the website URL. | Provide a valid and publicly accessible website URL for your brand. An active website is required for TCR registration submission. |
1101 | Brand inconsistencies: Invalid website domain or no website found | Verify the submitted website URL is correct and active. |
2001 / CR3001 | Duplicate campaign registration | Make sure the campaign is unique and not previously submitted. If submitting multiple campaigns, include location-specific details in the “What service does your company or business provide to your customers?” section. |
2002 / CR3002 | Campaign description is insufficient | 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.” |
2003 / CR3003 | Use case does not match campaign description | Update either the campaign description or use case so they align correctly. |
2004 / CR3004 | Sample messages do not match campaign description | Verify that your campaign description, sample messages, and website disclosures match the selected use case.
|
2005 | Undeclared use case detected | Verify that your campaign description is accurate and that all applicable use cases are correctly selected. |
2006 | The brand referenced in the campaign description doesn’t match the registered or Doing Business As (DBA) brand name. | Ensure the business name used in messages, website, and campaign matches the registered brand or DBA name. |
CR3005 | Campaign description references third-party job boards | Third-party job board campaigns are prohibited. Please do not submit the campaign again. Third-party job board content was identified in your sample messages, Privacy Policy, or website, which is not permitted under SMS/MMS compliance policies. |
CR3008 | Campaign description references lead generation or affiliate marketing | Lead generation and affiliate marketing content are prohibited. Please do not submit the campaign again. |
CR3009 | Sweepstakes content detected in the campaign description, but the selected use case is not Sweepstakes | Sweepstakes-related messaging is prohibited. Please do not submit the campaign again. |
CR3010 | Charity-related content detected, but the selected use case is not Charity. | If your campaign description indicates that your business is soliciting charitable donations through SMS, the selected use case must be Charity. Update the campaign description or select the correct use case before resubmitting. |
CR3011 | Political-related content detected, but the selected use case is not Political. | If your campaign description indicates that your business sends political content through SMS, the selected use case must be Political. Update the campaign description or select the correct use case before resubmitting. |
CR3012 | Gambling content detected | Gambling-related content is prohibited. Please do not submit the campaign again. |
CR3013 | High-risk financial content detected | High-risk financial services (i.e. hedge funds, stock market investment, crypto, NFTs, etc.) are prohibited. Please do not submit the campaign again. |
CR3014 | Illegal substances detected | Cannabis, kratom, and illegal substance-related messaging is prohibited. Please do not submit the campaign again. |
CR3015 | SHAFT content detected (sex/hate) | Explicit sexual or hate-related content is prohibited. Please do not submit the campaign again. |
CR3016 | SHAFT content detected without age gate (alcohol/firearms/tobacco/vape) | For alcohol- or firearm-related campaigns, resubmission is only allowed after proper age verification has been implemented. At least two age gates are required:
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. Tobacco- and vaping-related content is prohibited and not allowed under SMS/MMS content policies. |
CR3017 | Invalid M2M use case selected for a subscriber-facing message program | Machine-to-Machine (M2M) use case is restricted to non-subscriber facing message programs only. Register the campaign again with the correct use case, then resubmit. |
CR3018 | The brand name referenced in the campaign description does not match the registered or DBA brand name. | Make sure the content on your website, sample messages, and brand information are all consistent with the same business. For example, if the brand name is Bright Smile Dental, the campaign may be rejected if the sample messages advertise real estate services or the website belongs to an e-commerce store. A dental clinic brand like Bright Smile Dental should include sample messages related to appointment confirmations or patient reminders, along with a link to the clinic’s official website. |
9102 | Campaign description was insufficient | Provide a clear summary of your business and how SMS will be used for the campaign. For example: “Our business is a primary healthcare clinic. This campaign will be used to send appointment reminders, patient updates, and conversational messages related to healthcare services.” |
9302 | Sample messages inconsistent with use case | Verify that your campaign description, sample messages, and website disclosures match the selected use case.
|
CTA (Call-to-Action) Errors
Rejection Code | Reason | How to Resolve |
611 | Keyword response messages (opt-in/START, HELP, opt-out/STOP) missing required disclosures | Update the opt-in, HELP, and opt-out messages in your registration form to meet the following requirements: 1. The opt-in message must include:
Example 1: “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.” 2. The HELP message must include:
Example 2: “Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].” 3. The opt-out message must include:
Example 3: “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.” |
803 | Website missing SMS opt-in language | Mobile carriers require businesses to obtain recipient consent before collecting phone numbers for SMS opt-in messaging. If consent is obtained through a website form, provide the exact URL where the opt-in language appears. The opt-in form must meet the following requirements:
Example consent language: “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.” If your website references the type of SMS messages being sent, it must match the selected campaign use case. For example, campaigns registered as Conversational cannot mention promotional, marketing, or automated SMS messages. |
804 | Unable to verify how customer consent is being collected. Your CTA or opt-in instructions are unclear, incomplete, or missing required details. | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
806 | Unable to verify customer consent. Your CTA information for customers to opt in to your brand is unclear or missing important details. | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
861 | Provide clear and compliant CTA instructions for customers to opt in to your SMS program, and make sure your keyword messages include all required disclosures. | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. Additionally, review and update the opt-in, HELP, and opt-out messages in your registration form to meet the following requirements: 6. The opt-in message must include:
Example 6: “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.” 7. The HELP message must include:
Example 7: “Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].” 8. The opt-out message must include:
Example 8: “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.” |
2100 | Invalid CTA: No opt-in language detected in the campaign description or message flow | Add explicit SMS opt-in consent language. The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
2101 | Invalid CTA: Promotional campaign missing written consent | Marketing campaigns require written, verifiable consent. The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
2102 | Invalid CTA: The campaign was identified as informational, but the required opt-in details are missing or unclear. | Informational SMS campaigns require explicit consumer consent. Recipients must clearly agree to receive messages for a specific informational purpose. Implied consent is not permitted for this use case. Update the campaign with a compliant opt-in collection method. |
2103 | Invalid CTA: A “Certificate verify failed' error was received on your website opt-in URL. | If consent is collected through a website form, provide the exact URL where the SMS opt-in language appears. If the opt-in language is located in a small section of the homepage:
Example: “Consent is collected through the contact form located at the bottom left of our homepage: [Business URL].” |
2104 | Invalid CTA: Invalid opt-in URL | If consent is collected through a website form, provide the exact URL where the SMS opt-in language appears. If the opt-in language is located in a small section of the homepage:
Example: “Consent is collected through the contact form located at the bottom left of our homepage: [Business URL].” |
2105 | Invalid CTA: Missing verbal consent script | If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2106 | Invalid CTA: Missing Privacy Policy reference in verbal script | If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2107 | Invalid CTA: Missing Terms reference in verbal script | The consent script must include a link to your Terms of Service, such as: “Visit [Terms URL] for our Terms of Service.” If your Terms of Service is included within your Privacy Policy, the script must include a link to your Privacy Policy instead. |
2108 | Invalid CTA: Brand name missing in verbal script | If consent is collected verbally, provide the complete verbal consent script including brand name (business name) and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2109 | Invalid CTA: Message type missing in verbal script | If consent is collected verbally, provide the complete verbal consent script including the types of messages being sent and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2110 | Invalid CTA: Missing message frequency disclosure in verbal script | If consent is collected verbally, provide the complete verbal consent script including message frequency and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2111 | Invalid CTA: Missing message/data rates disclosure in verbal script | If consent is collected verbally, provide the complete verbal consent script including a statement on message and data rates and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2112 | Invalid CTA: Missing STOP instructions in verbal script | If consent is collected verbally, provide the complete verbal consent script including how to opt out and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2113 | Invalid CTA: Brand name missing from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including your brand name (business name) and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2114 | Invalid CTA: Message type missing from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including the types of messages sent and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2115 | Invalid CTA: Missing message frequency disclosure from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including message frequency and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2116 | Invalid CTA: Missing message/data rates disclosure from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including a statement on message and data rates and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2117 | Invalid CTA: Missing HELP instructions from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including how to receive help and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2118 | Invalid CTA: Missing STOP instructions from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including how to opt out and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2119 | Invalid CTA: Missing HELP instructions in verbal script | If consent is collected verbally, provide the complete verbal consent script including how to get help and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2120 | Invalid CTA: Missing opt-in URL from website opt-in form | If consent is collected through a website form, provide the exact URL where the SMS opt-in language appears. If the opt-in language is located in a small section of the homepage:
Example: “Consent is collected through the contact form located at the bottom left of our homepage: [Business URL].” |
2121 | Invalid CTA: Missing Privacy Policy reference from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including how to find privacy policy and a link to your privacy policy and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.” |
2122 | Invalid CTA: Missing Privacy Policy link from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including a link to your privacy policy and all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.”. |
2123 | Invalid CTA: Missing Terms & Conditions reference from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including how to find Terms and Conditions and a link to your Terms and Conditions, as well as all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.”. |
2124 | Invalid CTA: Missing Terms & Conditions link from website opt-in form | If consent is obtained through a website form, provide the complete consent disclosure, including a link to your Terms and Conditions, as well as all required SMS disclosures. Example: “Do you consent to receive [types of messages (i.e. conversational, marketing, promotional, customer care, etc.)] 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.”. |
3000 / CR4015 | CTA website inaccessible | 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. If the opt-in language is located in a small section of the homepage:
Example: “Consent is collected through the contact form located at the bottom left of our homepage: [Business URL].” |
3001A / 3001B | CTA does not obtain sufficient consent | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
3002A / 3002B / CR4002 | CTA missing brand name | Update the CTA to include the company or brand name, and ensure the registered brand is clearly identifiable as the same business before resubmitting the campaign. |
3003A / 3003B / CR4003 | CTA missing HELP instructions | Update the CTA or Terms & Conditions page to include “Reply HELP for support,” HELP instructions, or customer support contact information before resubmitting the registration. |
3004A / 3004B / CR4004 | CTA missing STOP instructions | Update the CTA to include clear opt-out instructions, such as “Reply STOP to opt out,” before resubmitting the registration. |
3005A / 3005B / CR4005 | CTA missing message frequency disclosure | Update the CTA to include a message frequency disclosure, such as the number of messages per month, that messaging frequency may vary, or that recurring messages may be sent, before resubmitting the registration. |
3006A / 3006B / CR4006 | CTA missing message/data rates disclosure | Update the CTA to include a “Message & data rates may apply” disclosure, as required by US carriers, before resubmitting the registration. |
3007A / 3007B / CR4007 | CTA missing Terms & Conditions | Update the CTA to include either a link to your SMS Terms & Conditions page or the full SMS Terms & Conditions disclosure before resubmitting the registration. |
3008A / 3008B / CR4008 | CTA missing Privacy Policy link or data-sharing disclosure | You must maintain a Privacy Policy that is publicly accessible on your website. A compliant Privacy Policy must:
If your website does not have a dedicated SMS Terms & Conditions section, include the following SMS disclosure in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [message type(i.e. Conversational, Marketing, Notifications), 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 & Conditions.” |
3010A / 3010B / 7007 | Missing robust age gate(alcohol/firearms/tobacco) | Resubmit the campaign only after proper age verification has been implemented. At least two age gates are required:
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. Tobacco- and vaping-related content is prohibited and not allowed under SMS/MMS content policies. |
3011A / 3011B | Missing CTA website URL | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
3012A / 3012B | Multiple opt-ins combined in single CTA | Separate SMS consent from other communication consent options. References to any other types of communication must be completely independent of this SMS consent checkbox and language. |
CR4009 | Promotional messaging missing written consent | Promotional SMS campaigns require express written consent before promotional messages can be sent. For marketing use cases, “Verbal consent” is not a valid response to the “How do you obtain consent to send text messages?” question. Update the CTA and consent collection method before resubmitting. |
CR4010 | Gambling content detected in CTA | Gambling-related content is prohibited. Please do not submit the campaign again. |
CR4011 | High-risk financial content detected in CTA | High-risk financial services (i.e. hedge funds, stock market investment, crypto, NFTs, etc.) are prohibited. Please do not submit the campaign again. |
CR4012 | Illegal substances detected in CTA | Illegal substance-related messaging (i.e. Companies that promote, sell, or otherwise reference illegal drugs, such as marijuana, kratom, or similar substances) is prohibited. Please do not submit the campaign again. |
CR4013 | SHAFT (sex/hate) content detected in CTA | Explicit sexual or hate-related content is prohibited. Please do not submit the campaign again. |
CR4014 | Age-restricted content (alcohol/firearms/tobacco) without age gate | Resubmit the campaign only after proper age verification has been implemented. At least two age gates are required:
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. Tobacco- and vaping-related content is prohibited and not allowed under SMS/MMS content policies. |
CR7001 | Brand name missing from opt-in message | The company name referenced in your opt-in message must match the registered brand name or DBA name. A shortened version of the brand name may be used if it is still clearly identifiable as the same business. Update the Terms & Conditions and resubmit the campaign. |
CR7002 | HELP instructions missing from opt-in message | Update the subscriber opt-in message on the registration form to include:
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.” |
CR7003 | STOP instructions missing from opt-in message | |
CR7004 | Message frequency disclosure missing from opt-in message | |
CR7005 | Message/data rates disclosure missing | |
CR7006 | No opt-in message provided | |
CR8001 | Brand name missing from HELP message | The company name referenced in your HELP message must match the registered brand name or DBA name. A shortened version of the brand name may be used if it is still clearly identifiable as the same business. Update the Terms & Conditions and resubmit the campaign. |
CR8002 | Support contact missing from HELP message | Update the HELP message to include customer support contact information, such as an email address, phone number, or support website, before resubmitting the registration. |
CR8003 | HELP message support email mismatch | If an email address is included in the HELP message, it must match the support contact email registered for the campaign. The email address should also use your company domain. For example, support@acmecompany.com is acceptable, while support@gmail.com is not. Update the HELP message and resubmit the registration. |
CR9001 | Brand name missing from STOP message | Update your opt-out message to include the company or brand name that matches the registered brand name before resubmitting the registration. |
CR9002 | STOP message missing unsubscribe confirmation | Update the opt-out message to clearly confirm that the user will no longer receive SMS messages from the program before resubmitting the registration. |
9103 | Missing SMS opt-in language on the website form used to collect phone numbers. | If consent is obtained through a website form, provide the exact URL where the opt-in language appears. The opt-in form must meet the following requirements:
Example consent language: “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.” If your website references the type of SMS messages being sent, it must match the selected campaign use case. For example, campaigns registered as Conversational cannot mention promotional, marketing, or automated SMS messages. |
9104 | Insufficient explanation of how consent is collected from recipients outside of your website. | Provide a clear explanation of how consent is collected outside of your website. 1. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc.), submit a screenshot showing the consent language clearly visible. The disclosure must include the business name, STOP/HELP instructions, message frequency disclosure, “Message & data rates may apply,” Privacy Policy URL, and Terms URL. Example 1: “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.” 2. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 2: “Do you 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.” 3. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 3: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type (i.e. Conversational, Marketing, Notifications)] messages 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.” 4. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 4: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
9105 | Missing opt-in URL | If consent is collected through a website form, provide the exact URL where the SMS opt-in language appears. If the opt-in language is located in a small section of the homepage:
Example: “We obtain consent through the contact form located at the bottom left of our homepage: [Business URL].” |
9106 | Missing opt-out language in sample messages | Update your sample messages to include opt-out language, such as “Reply STOP to opt out,” in at least one message. |
9107 | Screenshot of SMS consent flow required | 1. If consent is collected through a paper or electronic form (such as intake forms, agreements, or employee handbooks), submit a screenshot showing the SMS consent language clearly visible. The disclosure must include the business name, STOP/HELP instructions, message frequency disclosure, “Message & data rates may apply,” Privacy Policy URL, and Terms URL. Example 1: “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.” 2. If consent is collected through a website that requires login, registration, or multiple steps to access, submit a screenshot showing where the SMS opt-in checkbox and disclosure language appear. Example 2: “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.” |
9109 | The opt-in language on your website is not specific to SMS. | SMS 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 or disclosure language. |
9112 | SMS checkbox is prechecked or mandatory | SMS consent checkboxes must be optional and unchecked by default. |
9403 | Provided incorrect opt-in/opt-out/help keywords or messages | Edit your messages to include opt-in, opt-out, and/or help keywords. We recommend "START", "STOP", "HELP" as opt-in, opt-out, and help keywords. |
9505 | Verbal consent is not sufficient for marketing or automated SMS campaigns | Marketing and promotional SMS campaigns require written and verifiable consent. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
9604 | The opt-in message does not explain how users know to message you first. | Please provide a website URL or verifiable proof, such as a flyer, business card, or other public display, showing where users can find your phone number and how to text you. Example: “You can text [Business Name] at [Phone Number] for information regarding our services. By texting us, you agree to receive [Campaign Type] messages 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.” |
9606 | Invalid opt-in, HELP, or STOP messages | Update the opt-in, HELP, and opt-out messages in your registration form to meet the following requirements: 1. The opt-in message must include:
Example 1: “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.” 2. The HELP message must include:
Example 2: “Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].” 3. The opt-out message must include:
Example 3: “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.” |
9607 | Unable to verify customer consent process. Update your CTA information and consent flow to clearly explain how users opt in to SMS messaging. | The response to the “How do you obtain consent to send text messages?” question is unclear, incomplete, or non-compliant. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
Message Flow & Content Attribute Errors
Rejection Code | Reason | How to Resolve |
601 | Campaign content does not match selected attributes | Verify that your campaign settings match your sample messages and website content:
Also verify that your website content matches the selected campaign attributes:
|
603 | Website, brand, and sample messages inconsistent | Make sure the content on your website, sample messages, and brand information are all consistent with the same business. For example, if the brand name is Bright Smile Dental, the campaign may be rejected if the sample messages advertise real estate services or the website belongs to an e-commerce store. A dental clinic brand like Bright Smile Dental should include sample messages related to appointment confirmations or patient reminders, along with a link to the clinic’s official website. |
710 | Brand name does not match registered or DBA brand | If you operate multiple brands or send messages on behalf of another business, you must register the exact brand sending the messages. For example, if a software company sends messages for a medical clinic, the clinic’s brand must be registered and associated with the campaign. |
711 | Duplicate EIN used across multiple brands | Each registered brand must have its own unique Employer Identification Number (EIN). If you own multiple brands, each brand must be registered separately using its corresponding EIN. |
712 | Direct lending or loan-related content detected | If your campaign involves direct lending or loan-related services, you must select “Yes” for the lending-related question in the registration form. If the campaign is not related to lending services, update the campaign description accordingly. |
713 | Support email does not use company domain | Your support email address must use your company domain. For example, support@acmecompany.com is acceptable, while support@gmail.com is not. |
714 | Court Order consent method is not accepted | You may resubmit the campaign using a valid consent method. Court Order consent is not accepted and will continue to be rejected. Other valid methods of obtaining consent: 1. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 1: “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.” 2. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 2: “Do you 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.” 3. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 3: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 4. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 4: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
801 | Sole Proprietor campaigns aren’t being accepted. | TCR does not accept applications from businesses that are not officially registered as an LLC or Corporation with the IRS or Canada Revenue Agency. |
802 | Trying to register as a sole proprietor | TCR does not accept applications from businesses that are not officially registered as an LLC or Corporation with the IRS or Canada Revenue Agency. |
CR1101 | Brand name missing from sample messages | Include the registered business name in all sample messages. |
CR1103 | Public URL shortener detected | Public URL shorteners (such as bit.ly or tinyurl, etc.) are prohibited by carriers. Update your sample messages to use full website URLs instead. |
CR1104 | Sample messages do not match use case | Verify that your campaign description, sample messages, and website disclosures match the selected use case.
|
CR1105 | Sweepstakes content detected | Sweepstakes messaging is prohibited unless properly registered. Please do not submit the campaign again. |
CR1106 | Charity content with incorrect use case | If your campaign description indicates that your business is soliciting charitable donations through SMS, the selected use case must be Charity. Update the campaign description or select the correct use case before resubmitting. |
CR1107 | Political content with incorrect use case | If your campaign description indicates that your business sends political content through SMS, the selected use case must be Political. Update the campaign description or select the correct use case before resubmitting. |
CR1110 | Third-party job board content detected | Third-party job board campaigns are prohibited. Please do not submit the campaign again. |
CR1111 | Gambling content detected | Gambling-related content is prohibited. Please do not submit the campaign again. |
CR1112 | High-risk financial services detected | High-risk financial services (i.e. hedge funds, stock market investment, crypto, NFTs, etc.) are prohibited. Please do not submit the campaign again. |
CR1113 | Illegal substances detected | Cannabis, kratom, and illegal substance-related content are prohibited. Please do not submit the campaign again. |
CR1114 | SHAFT (sex/hate) content detected | Explicit sexual or hate-related content is prohibited. Please do not submit the campaign again. |
CR3016 | Sample messages contain SHAFT content (alcohol, firearms, tobacco, or vaping) without proper age gating | Resubmit the campaign only after proper age verification has been implemented. At least two age gates are required: website entrance age verification and SMS consent 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. Tobacco- and vaping-related content is prohibited under SMS/MMS policies. |
2006 | Brand name does not match registered or DBA brand | If you operate multiple brands or send messages on behalf of another business, you must register the exact brand sending the messages. For example, if a software company sends messages for a medical clinic, the clinic’s brand must be registered and associated with the campaign. |
3002 | Charity campaign missing required information | Include the following charity information in the campaign description or program summary: organization name, EIN, charity website, and accreditation or nonprofit verification listing. |
3105 / 3106 | Campaign content does not match selected attributes | Verify that your campaign settings match your sample messages and website content:
|
6001 | Opt-in or confirmation message missing registered brand name | If you operate multiple brands or send messages on behalf of another business, you must register the exact brand sending the messages. For example, if a software company sends messages for a medical clinic, the clinic’s brand must be registered and associated with the campaign. |
6002 | Opt-in or confirmation message missing HELP instructions | Update the opt-in message to include “Reply HELP for support,” HELP instructions, or customer support contact information. |
6003 | Opt-in or confirmation message missing opt-out instructions | Update the opt-in message to include clear opt-out instructions, such as “Reply STOP to opt out.” |
6004 | Opt-in or confirmation message missing message frequency disclosure | Update the opt-in message to include the frequency at which messages will be sent to end users (for example, the number of messages per month, the message frequency varies, that recurring messages will be sent) and resubmit the registration. |
6005 | Opt-in or confirmation message missing message/data rates disclosure | Update the opt-in message to include clear and conspicuous language about any associated fees or charges for SMS and how those charges will be billed. Add a message and data rate disclosure to the opt-in message and resubmit the registration. |
6006 | Opt-in or confirmation message not provided | Update the opt-in, HELP, and opt-out messages in your registration form to meet the following requirements: Your opt-in message must include:
|
6007 | HELP message missing registered brand name | Update the HELP message to include the registered or DBA brand name. |
6008 | HELP message missing support contact information | Update the HELP message to include customer support contact information, such as an email address, phone number, or support website. |
6009 | HELP message support email does not match registered support email | If an email address is included in the HELP message, it must match the support contact email registered for the campaign. The email address should also use your company domain. For example, support@acmecompany.com is acceptable, while support@gmail.com is not. Update the HELP message and resubmit the registration. |
6010 | Opt-out message missing registered brand name | Update the opt-out message to include the registered or DBA brand name. |
6011 | Opt-out message does not confirm no further messages will be sent | Update the opt-out message to clearly state that the user will no longer receive SMS messages from the program. |
6012 | Sample messages missing registered brand name | Update all sample messages to include the registered or DBA brand name. |
6013 | Sample messages contain prohibited public URL shorteners | Public URL shorteners (such as bit.ly or tinyurl, etc.) are prohibited by carriers. Update your sample messages to use full website URLs instead. |
6014 | Sample messages do not match selected use case | Verify that your campaign description, sample messages, and website disclosures match the selected use case.
|
8001 | Charity-related content detected, but use case is not Charity | If your campaign solicits charitable donations through SMS, the selected use case must be Charity. Update the campaign use case and resubmit. |
8002 | Political content detected, but use case is not Political | If your campaign sends political content through SMS, the selected use case must be Political. Update the campaign use case and resubmit. |
8003 | Cart reminder content detected, but use case is not Marketing | If your campaign sends abandoned cart or shopping reminder messages, the selected use case must be Marketing. Update the campaign use case and resubmit. |
8004 | Multiple use cases detected, but only one use case selected | If your campaign supports multiple message types, all applicable use cases must be selected in the registration. |
8100 | Sample messages missing opt-out language | Add opt-out language such as “Reply STOP to opt out” to at least one sample message. |
8101 | Sample messages missing brand name | Carriers require the registered or DBA brand name to appear in every sample message. Make sure all sample messages clearly identify your business. Example: “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.” |
8102 | Missing sample message for one or more selected use cases | Verify that your campaign description and sample messages match the selected use case. Your sample messages must reflect the selected use case. For example, if the campaign is registered for two-factor authentication, the sample messages must contain authentication-related content. If multiple use cases or sub-use cases are selected (such as Customer Care and Marketing), at least one sample message must be provided for each use case. |
9001 | Political campaign missing required information | Political SMS campaigns must include the following information in the campaign submission:
This information should be included in the campaign description or program summary so it can be verified during review. |
9210 | Brand information does not match the actual message sender | Make sure your campaign complies with Know Your Customer (KYC) requirements. The registered brand must be the actual message sender, and the EIN and company information must match that business. Your sample messages, website, and website domain should also clearly reflect the registered brand name. |
9212 | Direct lending content detected but not declared | If your campaign includes direct lending or loan-related content, you must select “Yes” for the lending-related question in the registration form. If the campaign is not related to lending services, update the campaign description accordingly. |
9301 | Campaign attributes do not match website or sample message content | Verify that your campaign settings match your sample messages and website content:
Also verify that your website content matches the selected campaign attributes:
|
9302 | Sample messages do not match selected use case | Verify that your campaign description, sample messages, and website disclosures align with the selected use case.
|
9303 | Website, brand, or sample messages are inconsistent | Verify that your website content, sample messages, and registered brand all represent the same business. For example, if a software company sends messages on behalf of a medical clinic, the clinic’s brand must be registered and reflected in the website and sample messages. |
9304 | Website missing business information or contains broken links | Your website must clearly provide information about your business, including the products or services offered, physical address, and contact information. All website references in your campaign must relate to the registered business, and all website links must be active and working at the time of registration. |
9401 | Public URL shortener detected in sample messages | Public URL shorteners (such as bit.ly or tinyurl, etc.) are prohibited by carriers. Update your sample messages to use full website URLs instead. |
9502 | Invalid campaign use case selected | Resubmit the campaign using a use case that matches your sample messages and campaign description. |
9503 | Fewer than three unique sample messages provided | Submit at least three unique sample messages that reflect your normal day-to-day business messaging activities. |
9609 | Court Order consent method is not accepted | You may resubmit the campaign using a valid consent method. Court Order consent is not accepted and will continue to be rejected. Accepted consent methods include website forms, paper/electronic forms, verbal consent, consumer-initiated messaging, and email consent. 1. If consent is collected through a website form, provide the exact opt-in URL. The form must:
Example 1: “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.” 2. If consent is collected through a paper or electronic form (patient intake forms, attorney retainer agreements, employee handbooks, etc), submit a screenshot showing the consent language clearly visible and compliant with all required SMS disclosures. Example 2: “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.” 3. If consent is collected verbally, provide the complete verbal consent script including all required SMS disclosures. Example 3: “Do you 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.” 4. If consent is collected by customers texting first, provide proof showing where your phone number is publicly displayed and how customers are instructed to text you. Submit a screenshot or image showing the disclosure clearly visible. Example 4: “You can text [Business Name] for information regarding our services. By texting [Business Name], you agree to receive [Campaign Type(i.e. Conversational, Marketing, Notifications)] messages 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.” 5. If consent is collected through email, provide the complete email consent script including all required SMS disclosures. Example 5: “Do you 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.” If your consent form or script references the type of SMS messages being sent, it must match the selected campaign use case. For example, if you selected Conversations in your campaign, mentioning “promotional/marketing/automated SMS" on your website will result in a campaign rejection. |
9610 | Sample messages missing brand name | Carriers require the registered or DBA brand name to appear in every sample message. Make sure all sample messages clearly identify your business. 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.” |
9611 | Opt-in language does not describe message type or does not match selected use case | Make sure your website opt-in form or verbal consent script clearly describes the types of SMS messages being sent and that the message type matches the selected campaign use case. |
9612 | Informational campaign missing express consent | Informational SMS campaigns require explicit consumer consent for a specific informational purpose. Implied consent is not permitted. Update the campaign with a compliant opt-in collection method. |
Brand & Website Errors
Rejection Code | Reason | How to Resolve |
CR2001 | Free email domain used | Use a branded company email instead of Gmail or other public email domains. |
CR2002 | Physical address cannot be verified | Verify that your physical address is accurate before resubmitting the registration. |
CR2003 | Brand not eligible for DCA campaigns | Confirm the brand is eligible before resubmitting. |
CR2004 | Registered brand is reseller or ISV instead of sender | The registered brand must match the business identified in the message content. If you operate multiple brands or send messages on behalf of another business, you must register the exact brand sending the messages. For example, if a software company sends messages for a medical clinic, the clinic’s brand must be registered and reflected in the sample messages and website content. |
CR2005 | Website missing or inaccessible | Verify the website URL is correct and active. |
CR2006 | Third-party job board content detected | Third-party job board campaigns are prohibited. Please do not submit the campaign again. |
CR2009 | Sweepstakes content detected | Sweepstakes messaging is prohibited unless properly registered. Please do not submit the campaign again. |
CR2010 | Charity content with incorrect use case | Provide the following information to verify your organization’s 501(c)(3) tax-exempt status:
Include this information in the campaign description or program summary so it can be verified during review. |
CR2011 | Political content with incorrect use case | If your campaign description indicates that your business sends political content through SMS, the selected use case must be Political. Update the campaign description or select the correct use case before resubmitting. |
CR2012 | Lead generation or affiliate marketing detected | Lead generation and affiliate marketing content are prohibited. Please do not submit the campaign again. |
CR2013 | Gambling content detected | Gambling-related content is prohibited. Please do not submit the campaign again. |
CR2014 | High-risk financial services detected | Crypto, investment schemes, NFTs, and similar content are prohibited. Please do not submit the campaign again. |
CR2015 | Illegal substances detected | Cannabis, kratom, and illegal substance-related messaging is prohibited. Please do not submit the campaign again. |
CR2016 | SHAFT content detected | Explicit sexual or hate-related content is prohibited. Please do not submit the campaign again. |
CR2017 | SHAFT content detected without age gate (alcohol/firearms/tobacco/vape) | For alcohol- or firearm-related campaigns, resubmission is only allowed after proper age verification has been implemented. At least two age gates are required:
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. Tobacco- and vaping-related content is prohibited and not allowed under SMS/MMS content policies. |
CR2018 | Missing or invalid support email | Provide a valid support email address and verify it’s working, then resubmit. |
CR2019 | Missing or invalid support phone number | Provide a valid support phone number and verify it’s working, then resubmit. |
CR2020 | Brand name mismatch | Make sure the content on your website, sample messages, and brand information are all consistent with the same business. For example, if the brand name is Bright Smile Dental, the campaign may be rejected if the sample messages advertise real estate services or the website belongs to an e-commerce store. A dental clinic brand like Bright Smile Dental should include sample messages related to appointment confirmations or patient reminders, along with a link to the clinic’s official website. |
CR2021 | Registered as a Sole Proprietor brand that does not qualify as a small business or individual without an EIN. | TCR does not accept applications from businesses that are not officially registered as an LLC or Corporation with the IRS or Canada Revenue Agency. |
CR2022 | Brand vetting score too low | In some cases, a brand’s vetting score may not meet the minimum requirements for campaign approval. Improve business legitimacy and branding before resubmitting. |
CR2023 | Brand email associated with spam complaints | If the email address provided in the brand registration is known for sending spam and unwanted messaging, the campaign will be rejected. Use a clean, trustworthy business email address. |
Invalid Campaign Description or Attributes
Error Code | Reason | How to Resolve |
3100 | Campaign flagged for high-risk financial services content | This content is prohibited and not eligible for reconsideration. Please do not submit the campaign again. Your sample messages, Privacy Policy, or website contain lead generation or affiliate marketing content, which violates SMS/MMS content policies. |
3101 | Campaign flagged for affiliate marketing and high-risk financial loan content | This content is prohibited and not eligible for reconsideration. Please do not submit the campaign again. Your sample messages, Privacy Policy, or website contain high-risk financial services content, including hedge funds, stock investments, crypto, NFTs, or similar services, which violate SMS/MMS content policies. |
3102 | Campaign flagged for affiliate marketing content | This content is prohibited and not eligible for reconsideration. Please do not submit the campaign again. Your sample messages, Privacy Policy, or website contain lead generation or affiliate marketing content, which violates SMS/MMS content policies. |
6100 | No website URL found in campaign submission | Verify that a valid and active website URL was entered in the registration form before resubmitting. |
6101 | Invalid or missing website/domain in submitted URL | Verify that the submitted website URL is correct, active, and contains a valid domain before resubmitting. |
Missing Mandatory Message Terminology
Rejection Code | Reason | How to Resolve |
5100 | STOP message missing brand name | STOP/opt-out messages must include:
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.” |
5101 | No valid opt-out keyword provided | Use valid opt-out keywords such as STOP, END, UNSUBSCRIBE, or CANCEL. |
5102 | STOP message missing unsubscribe confirmation | STOP/opt-out messages must include:
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.” |
5103 | HELP keyword missing | Add HELP as a supported keyword. |
5104 | Opt-in message missing brand name | Add the registered business name to the opt-in message. Update the subscriber opt-in message on the website form to include:
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.” |
5105 | Opt-in message missing frequency disclosure | Add message frequency wording. Update the subscriber opt-in message on the website form to include:
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.” |
5106 | Opt-in message missing fees disclosure | Add “Message & data rates may apply.” Update the subscriber opt-in message on the website form to include:
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.” |
5107 | Opt-in message missing HELP keyword | Add HELP instructions. Update the subscriber opt-in message on the website form to include:
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.” |
5108 | Opt-in message missing STOP keyword | Add STOP instructions. Update the subscriber opt-in message on the website form to include:
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.” |
Prohibited & Disallowed Content Errors
Rejection Code | Reason | How to Resolve |
701 / 9901 | Marijuana or kratom content detected | Cannabis, kratom, and illegal substance-related messaging is prohibited. Please do not submit the campaign again. |
702 | Firearm-related content without age gate | Please only resubmit once you can provide proof of proper age-gating. At minimum, you must implement:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
703 | Explicit or sexual content detected | Explicit sexual content is prohibited. Please do not submit the campaign again. |
704 | Gambling content detected | Gambling-related messaging is prohibited. Please do not submit the campaign again. |
705 | Hate speech detected | Hate-related content is prohibited. Please do not submit the campaign again. |
706 | Alcohol-related content without age gate | You cannot submit alcohol-related sample messages without proof of proper age-gating, such as a date-of-birth verification page. Please only resubmit once robust age verification has been implemented. At minimum, you must have:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
707 | Tobacco or vaping content detected | Tobacco and vaping-related messaging is prohibited. Please do not submit the campaign again. |
708 | Lead generation or affiliate marketing detected | Lead generation and affiliate marketing content are prohibited. Please do not submit the campaign again. |
709 | High-risk financial services detected | High-risk financial services (i.e. hedge funds, stock market investment, crypto, NFTs, etc.) are prohibited. Please do not submit the campaign again. |
1001 | Age-gated content attribute not selected | Please only resubmit once you can provide proof of proper age-gating. At minimum, you must implement:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
1002 | Lending-related content attribute missing | You must select “Yes” for the direct lending or loan agreement question in the registration form. If your campaign is not related to direct lending or loan services, update the campaign description accordingly before resubmitting. |
4100 | SHAFT-C content violation detected | This content is prohibited and not eligible for reconsideration. Please do not resubmit. The campaign violates SHAFT-C content restrictions (Sex, Hate, Alcohol, Firearms, Tobacco, and Cannabis) and will be rejected under carrier policies. |
7006 | Sexual content without age gate | Message content related to age-restricted products or material, including sexually explicit content or imagery, is not permitted without proper age-gating. Please only resubmit once robust age verification has been implemented. At minimum, you must have:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
7007 | Alcohol/firearms/tobacco content without age gate | You cannot submit alcohol-related sample messages without proof of proper age verification, such as a date-of-birth entry page. Please only resubmit once robust age-gating has been implemented. At minimum, you must have:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
7008 | Competitive marketing detected | This content is prohibited and not eligible for reconsideration. Please do not resubmit. Message content that promotes or markets competitive services to U.S. mobile operators is prohibited and will be rejected. |
7009 | Weapons not legal in all states detected | This content is prohibited and not eligible for reconsideration. Please do not resubmit. Message content related to certain weapons that are not legal in all 50 U.S. states is prohibited under SMS/MMS content policies. Campaigns will be rejected if the brand’s website or messaging program indicates this type of content will be sent. |
7010 | Third-party debt collection detected | This content is prohibited and not eligible for reconsideration. Please do not resubmit. Your messages, Privacy Policy, or website reference third-party debt collection services, including debt forgiveness, debt consolidation, debt reduction, or credit repair programs, which violate SMS/MMS content policies |
7011 | Illegal firearm content detected | This content is prohibited and not eligible for reconsideration. Please do not resubmit. Message content related to firearms not legal in all 50 U.S. states is prohibited under SMS/MMS content policies. Campaigns will be rejected if the website or messaging program indicates this type of content will be sent. |
7012 | Hate speech detected | Hate-related content is prohibited. Please do not resubmit. |
9202 | Missing age gate for alcohol/firearm content | Please only resubmit once you can provide proof of proper age-gating. At minimum, you must implement:
Best practice is to require users to enter their full birth date (MM/DD/YYYY) before accessing the website or submitting the opt-in form. Your website will be reviewed for age-gating compliance. |
9208 | Lead generation or affiliate marketing detected | Lead generation and affiliate marketing content are prohibited. Please do not resubmit. |
9209 | High-risk financial services detected | High-risk financial services (i.e. hedge funds, stock market investment, crypto, NFTs, etc.) are prohibited. Please do not resubmit. |
Privacy Policy & Terms Errors
Rejection Code | Reason | How to Resolve |
805 | Missing or invalid Privacy Policy | You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
809 | Privacy Policy attachment required | If your Privacy Policy is not publicly available on your website, contact your service provider to submit your Privacy Policy so it can be attached to your campaign registration. |
851 | Missing SMS disclosure in Privacy Policy and keyword responses must comply with TCR requirements | Your website must include an easily accessible Privacy Policy, available from the homepage or Contact Us page. A compliant Privacy Policy must:
If you do not have a Terms and Conditions section dedicated to SMS disclosures, please 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 & Conditions.” Additionally, review and update the opt-in, opt-out, and help messages on the campaign form based on the following: 1. The opt-in message must include:
Example 1: “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.” 2. The HELP message must include:
Example 2: “Thank you for contacting [Business Name]. For support, please visit [Website], call [Phone Number], or email [Email Address].” 3. The opt-out message must include:
Example 3: “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.” |
852 | Missing support instructions in Terms | Add customer support instructions to Terms & Conditions. Provide a valid Privacy Policy URL and include language confirming that mobile opt-in data is not shared with third parties or affiliates. Also provide a valid Terms & Conditions URL that includes instructions on how users can get additional support. |
CR5001 | Terms & Conditions inaccessible | Ensure your Terms and Conditions URL is publicly accessible. Update the link and resubmit. |
CR5002 | Brand name missing from Terms | The company name listed in the Terms & Conditions must match the registered or DBA brand name. Shortened brand names may be used in messages only if the sender identity remains clear. Update the Terms & Conditions and resubmit the registration. |
CR5003 | Missing message frequency disclosure | Your website Terms & Conditions must include:
Any SMS content referenced in your Terms & Conditions must match the selected campaign use case. For example, Conversational campaigns must not reference promotional, marketing, or automated SMS messages. Example: “If you consent to receive text messages from [Business Name], you may receive SMS messages related to [example of message type]. Messaging frequency may vary. Message and data rates may apply. Reply STOP to opt out or HELP for support. Visit [Privacy Policy URL] and [Terms & Conditions URL] for more information.” |
CR5004 | Program description missing from Terms | |
CR5005 | Missing support contact information from Terms | |
CR5007 | Missing STOP instructions from Terms | |
CR5010 | Missing Privacy Policy link from Terms | |
CR5011 | Your use case is “sweepstakes” but your Terms and conditions don’t contain sweepstakes terms. | Sweepstakes-related messaging is prohibited. Please do not submit the campaign again. |
7001 | Your brand or program references third-party job boards. | Third-party job board campaigns are prohibited. Please do not submit the campaign again. |
CR6001 | Privacy Policy inaccessible | Verify the Privacy Policy URL is valid and publicly accessible. Include language stating that mobile opt-in data is not shared with third parties or affiliates. |
CR6002 / CR6003 | Privacy Policy allows data sharing | You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
7100 | Missing Privacy Policy URL | Provide a valid Privacy Policy link. You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
7101 | Invalid Privacy Policy domain | Verify the Privacy Policy URL is correct. You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
7102 | Invalid Privacy Policy content | Ensure the linked page is an actual Privacy Policy. You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
7103 | Missing SMS data-sharing restriction | Add language stating SMS consent is not shared with third parties. You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
9102 | Terms & Conditions missing message/data rate disclosure | Add “Message & data rates may apply.” to Terms & Conditions. Your website Terms & Conditions must include:
Any SMS content referenced in your Terms & Conditions must match the selected campaign use case. For example, Conversational campaigns must not reference promotional, marketing, or automated SMS messages. Example: “If you consent to receive text messages from [Business Name], you may receive SMS messages related to [example message type]. Messaging frequency may vary. Message and data rates may apply. Reply STOP to opt out or HELP for support. Visit [Privacy Policy URL] and [Terms & Conditions URL] for more information.” |
9108 | Missing or non-compliant Privacy Policy | Add a compliant Privacy Policy containing required SMS disclosures. You must maintain a Privacy Policy that is easily accessible to consumers on your website. A compliant Privacy Policy must:
If you do not have a separate Terms & Conditions section for SMS disclosures, include the following language in your Privacy Policy: “If you consent to receive SMS from [Business Name], you agree to receive [types of messages consistent with the 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] to view our Privacy Policy and Terms & Conditions.” |
9608 | Terms & Conditions missing SMS disclosures | Your website Terms & Conditions must include:
Any SMS content referenced in your Terms & Conditions must match the selected campaign use case. For example, Conversational campaigns must not reference promotional, marketing, or automated SMS messages. Example: “If you consent to receive text messages from [Business Name], you may receive SMS messages related to [example message type]. Messaging frequency may vary. Message and data rates may apply. Reply STOP to opt out or HELP for support. Visit [Privacy Policy URL] and [Terms & Conditions URL] for more information.” |
Miscellaneous Errors
Error Code | Reason | How to Resolve |
807 | Unable to verify website authenticity | Your website must clearly provide information about your business, including products/services, physical address, and contact information. Ensure all website references relate to the registered business and that all website links are active. |
808 | Campaign declined five or more times | The campaign has been denied five or more times without sufficient updates. Each denial may incur a vetting fee. Review and update the campaign information carefully before resubmitting. Contact your service provider for assistance if needed. |
1003 | Brand website inaccessible or invalid | Verify that the correct website URL was entered in the brand registration form and confirm that the website is active and accessible. |
1004 | Website not available in English | Your website must be accessible in English to allow proper compliance review. |
9110 | Missing or non-working website URL | Verify that the website URL entered in the brand form is correct, active, and accessible. |
9501 | Duplicate campaign submission detected | Duplicate campaign registrations are not permitted. If multiple registrations are needed, make sure you include location information in the What service does your company or business provide to your customers? section of the form. |
Best Practices Before Resubmitting
Disclaimer: The following examples are provided for informational purposes only and do not constitute legal advice. You should consult legal counsel regarding your website forms, Privacy Policy, and Terms & Conditions. Carrier and industry review requirements may change over time, and compliance with these examples does not guarantee campaign approval.
Website Form Requirements
Your website opt-in form must:
Include a phone number field
Use an SMS consent checkbox that is unchecked by default and not required
Include compliant SMS consent language
Example consent language:
“I consent to receive SMS from [Business Name]. Reply STOP to opt out; Reply HELP for support; Message and data rates may apply; Messaging frequency may vary.”
Privacy Policy Requirements
Provide a valid link to your online Privacy Policy. Your Privacy Policy must include:
The types of personal information collected
How personal information is used
Who personal information is shared with
A clear statement that SMS consent and phone numbers are not shared with third parties or affiliates
Example disclosure:
“SMS consent is not shared with third parties or affiliates for marketing purposes.”
Your Privacy Policy should be easy to access and prominently displayed on your website, including near the SMS consent language and preferably in the footer of all website pages.
Terms & Conditions Requirements
Your Terms & Conditions page or section must include:
Types of SMS messages being sent
Message frequency disclosures
Message and data rate disclosures
STOP and HELP instructions
Links to your Privacy Policy and Terms & Conditions
Example message types:
Customers and Guests: Order updates, delivery notifications, or service-related information
Job Applicants: Application updates, onboarding information, or employment-related notifications
Required SMS Disclosures
“Messaging frequency may vary. Message and data rates may apply. Reply STOP to opt out or HELP for support. Visit [Privacy Policy URL] for our Privacy Policy and [Terms of Service URL] for our Terms & Conditions.”
Still Need Assistance?
Our support team is here to help with any questions or issues you may have. Feel free to contact us anytime at team.support@textrapp.com.