10DLC Messaging Overview & Registration
Table of Contents
Scope
Intended Audience: All Users
This article gives an overview of 10DLC messaging, where it comes from, and how it affects end users, including white label partners.
PLEASE READ
Beginning February 1st, 2025 the MNOs will begin blocking any unregistered traffic. Ensure that your brands and campaigns have been approved. Messaging will not be sent or received until both are approved. Unapproved messaging may also be subject to fines by TCR. For questions please reach out to support.
General Overview
In 2020, major MNOs including Verizon, AT&T, and T-Mobile launched 10DLC programs according to guidelines found in the CTIA's Messaging Principles and Best Practices to protect consumers against unwanted spam messages. These programs are now referred to as A2P/10DLC (App to Person/10-Digit Long Code) and Toll-Free Message Verification and it applies to all A2P messaging service providers throughout the US and Canada. Unlike other messaging compliance mandates which are regulated by the FCC, the A2P/10DLC initiative is regulated and managed by major MNOs, and this includes passing through steep non-compliance fines.
The major MNOs appointed The Campaign Registry (TCR) to manage the 10DLC registration initiative, with the requirement that each organization must register a Brand and Campaign with the TCR. MNO’s use the TCR’s verification and vetting process to determine campaign message throughputs.
Effect on Users
All messaging traffic originating from the PBX is considered A2P and must comply with A2P/10DLC carrier policies. This includes all messaging applications made via API. As such, all numbers must be registered according to the campaign and brand registration process.
Unregistered A2P traffic is subject to being blocked by the receiving MNO, or Non-Compliance Fees imposed by MNOs.
Non-Compliance Fees
Fees for non-compliance are levied by TCR and the individual MNOs. We do not have any control of the fees nor do we have any say in their outcome. Fees and violations are the responsibility of the WLP or end user
| Violation Type | Fee | Description |
|---|---|---|
| Text Enablement | $10,000 | This pass-through fee applies if T-Mobile receives a complaint where you or your message sender text-enables a 10-digit NANP telephone number and sends messages prior to verification of message sender ownership. |
| 10DLC Long Code Messaging Program Evasion | $1,000 | The pass-through fee will apply per-incident if a program is found to use evasion techniques such as snowshoeing, unauthorized number replacement, and dynamic routing. |
| Content Violation | $10,000 | T-Mobile may charge this pass-through fee for each unique instance of the third or any subsequent notification of a content violation involving the same content provider. Defined as sending messages in violation of the rules in the code of conduct, and are usually SHAFT violations (sex, hate, alcohol, firearms or tobacco) but also includes spam or phishing, or messaging which meets the threshold of a severity 0 violation per the CTIA shortcode monitoring handbook. |
Glossary
-
Application-to-Person (A2P) Messaging: Also known as business SMS or enterprise SMS, this refers to text messages sent from a business to a person.
There are three types of A2P Messages: 10 Digit Long Code (10DLC), Toll-Free Messaging, and Short Codes - Person-to-Person (P2P) Messaging: Typical human to human text messaging
- 10 Digit Long Code (10DLC): Long code numbers which are registered with mobile network operators to allow A2P messaging.
- Toll-Free Messaging: Toll-Free numbers used for A2P messaging
- Short Code: Abbreviated phone numbers (5 or 6 digits in length) which are authorized for business messaging
- Mobile Network Operator (MNO): Also known as a wireless carrier or celllular company, MNOs control the entire infrastructure for mobile communications involving their customers. The most well-known MNOs include AT&T, T-Mobile, Verizon, and U.S. Cellular
- Cellular Telecommunications Industry Association (CTIA): An international industry trade group representing all wireless communication sectors including cellular, personal communication services, and enhanced specialized mobile radio
- The Campaign Registry (TCR): Entity created by MNOs to manage the 10DLC registration initiative. This registry tracks what entities use 10DLC phone numbers and the use case for each one.
- Brand: A company entity representing an organization
- Campaign: A specific situation in which a product/service can be used, also referred to as a ‘Use Case’. Examples include 2FA (Two-factor authentication), Marketing, Security Alert, Social, Political, and more.
10DLC Brand and Campaign Registration Process
Overview & Timelines
The registration process will take place in various phases. You can check the progress in the Manager Portal. The steps will be:
- Create a brand
- Create a campaign
- Assign number to a campaign
While a company may have multiple of each, a company generally has one brand and one campaign.
Note: 10DLC is specific to each carrier and must be registered again, even if it was previously registered with a different carrier
Timelines
Brand approvals can take up to four business days depending on the campaign use case.
Campaigns must be approved by both TCR and the underlying carrier to which the SMS number belongs. Campaign approval by TCR can take up to four business days. Approval by underlying carriers is expected to take up to 5 business days normally, however, due to the volume of requests as providers work to get all of their campaigns registered, we have been advised that this process can take up to 3 weeks.
Once a campaign has been approved by both TCR and the underlying carrier, SMS numbers assigned to the campaign can be used immediately.
Create a Brand
This is the first step in the process and is only needed once for each business entity. TCR validates the EIN, Legal Company Name, and Legal Company Address with third-party independent sources and confirms the existence of the Brand with a verification “Status” (Verified/Unverified). Being a “Verified” Brand is a requirement to message on 10DLC, and Identity Verification is a crucial step for each registered Brand. We suggest paying close attention in entering correct and up-to-date information to allow the Brand to be swiftly verified. Upon Brand verification, TCR will assign available Classes (AT&T) or Tiers (T-Mobile) according to whether or not a verified Brand is part of the Russell 3000 list. Verified Brands who are not part of the Russell 3000 list can improve their Class/Tier assignment through vetting. TCR provides the ability for “Vetting” of Brands to gain access to special use cases or improve quality of service. Campaigns cannot be created until a Brand has been Verified in TCR.
All businesses will need the information below to register a brand. Public companies, charities/non-profit organizations, and sole proprietors have additional requirements which are listed below.
Refer to the Campaign Registration Tips >> Common Issues section on how to get the registered LEGAL NAME

- Legal company name
- Country of registration
- Employer ID Number (EIN)/Tax ID
NOTE: For Sole Proprietors, only Reference ID is needed, not EIN. - Address
- Vertical
- Website
- A website must be included in the brand registration. If unavailable, provide an alternative online presence, such as a social media page or Google search result link.
- Contact Details
- Stock symbol
- Stock exchange
- Reference ID
- First/Last Name
- One campaign is allowed per Brand, with a maximum of 5 associated TN.
- Standard use cases are not available for Sole Proprietor brands
- 1000 msg/day limit (T-Mobile) and 15msg/minute limit (AT&T) per Campaign.
- Log in to the Manager Portal
- Select Integrations at the top right
- Select CSP Campaign Registry
- Click Register Brand
- Complete the requested fields
- Type of Legal Form
- Country of Registration: The country where the company is located
- Legal Company Name
NOTE: This is not needed for Sole Proprietors - DBA or Brand Name (Optional)
- Tax Number/ID/EIN Issuing Country
NOTE: This is not needed for Sole Proprietors - Tax Number/ID/EIN
NOTE: This is not needed for Sole Proprietors - Alternative Business Identifier Type (Optional): Users can choose to provide a DUNS, GIIN, or LEI number for additional verification
- DUNS or GIIN or LEI Number (Optional): Users can choose to provide a DUNS, GIIN, or LEI number for additional verification
- Vertical Type: The market in which the business operates
NOTE: This is optional for Sole Proprietors - Reference ID: Client's domain name
- Click Next
- Complete the following fields
- First Name (Sole Proprietors Only)
- Last Name (Sole Proprietors Only)
- Email: The email address will receive a verification notification once the brand is created
- Phone Number
- Address
- Website
- Domain: Enter the client's domain name as needed
- Stock Exchange (Publicly Traded Companies Only)
- Stock Symbol (Publicly Traded Companies Only)
- Click Save
- A confirmation message will appear and the brand will be listed in Pending status. Once the brand is approved, an email notification will be sent, and users may proceed with creating a campaign
Create a Campaign
This step involves registering a "Use Case" for which the numbers will be used and requires several pieces of information. SMS numbers within a campaign may only be used to send messages relevant to the use case selected. Refer to the Campaign Registration Tips section for reference while completing the below steps.
- Log in to the Manager Portal
- Select Integrations at the top right
- Select CSP Campaign Registry
- Navigate to the Campaign tab
- Click Register Campaign
- Select the previously created brand
- Select the use case as determined in requirements and click Next
- Click Next
- Complete the following fields:
- Vertical: Choose the vertical in which the business operates
- Campaign Description: Enter a description of what the campaign will be used for (appointment reminders, support communication, etc)
- Call-to-Action/Message: List all the ways customers may opt-in to receiving text message notifications (by texting the phone number, agreeing to it on the website, calling in, etc)
- Sample Message 1: Enter an example of a text message that will be sent to the client
Important!
Please be sure to reference the below sample CTA, sample messages and subscriber messages in Campaign Registration Tips. You will be charged for each vetting, attempt so please be sure to provide all information as shown in the samples.
- Click Next
- Make sure the following boxes are checked:
- Subscriber Opt-In
- List the opt-in keywords in CAPITAL LETTERS. List one word and press enter. Max of 6 words
- Client opt-in message should be 20 characters or more
- Subscriber Opt-Out
- List the opt-out keywords in CAPITAL LETTERS. List one word and press enter. Max of 6 words
- Client opt-out message should be 20 characters or more
- Subscriber Help
- List the help keywords in CAPITAL LETTERS. List one word and press enter. Max of 6 words
- Client opt-in message should be 20 characters or more
- Subscriber Opt-In
- Place Privacy Policy Link and Terms and Conditions link. These should be valid websites.

- If no link is available or the client is unable to update their Privacy Policy and Terms and Conditions, you can attach the updated files in Supporting Documents.
- Note: CTA will change depending if the Policy and Terms have a link or to attach files.
- If no link is available or the client is unable to update their Privacy Policy and Terms and Conditions, you can attach the updated files in Supporting Documents.
- Attach how the clients are informed about the opt-in
- Website opt-in – Attach a screenshot of the webform page
- Keyword/text opt-in - Attach a screenshot where the keyword is provided
- Verbal opt-in does not require this option as customers are being informed directly
- Click on the required information

- Note: Select Embedded Link – If the Sample Messages has a website link. Embedded Phone Number – if the Sample Messages has a phone number.
- Click on “I confirm that this campaign will not be used for affiliate marketing” then click Save
- A confirmation message will appear and the campaign will be listed in Pending status. Once the campaign is approved, an email notification will be sent and users can assign an SMS number to the campaign
NOTE: Campaigns require manual vetting by carriers, which can take 5 business days or more.
- For campaigns that require modifications, especially those declined. Once the campaign with modifications has been resubmitted in the portal, please send an email to telco services or support to import the changes to our carrier. Example subject line: Import Campaign Changes - <campaign ID>.
Assign SMS Number to a Campaign
In this step, SMS numbers will be assigned to the related campaign. You can have multiple Telephone Numbers (TNs) associated with one Campaign, however, you cannot have multiple Campaigns associated with a TN.
Note: A maximum of 49 TNs can be assigned per campaign. You will need to another campaign for the next set to TNs
- Log in to the Manager Portal
- Navigate to Inventory
- Select the SMS Numbers tab
- Edit the desired number
- Select the campaign and click Save
- Once the campaign has been approved, users can send and receive SMS/MMS messages normally
Campaign Registration Tips
By adhering to these guidelines and providing the necessary information, you can ensure your SMS campaign complies with 10DLC requirements and is approved efficiently.
Website Privacy Policy
All message senders must have an acceptable Privacy Policy when registering 10DLC campaigns. The most important aspect of the Privacy Policy mandates clearly describing how consumer data will be used and shared (if applicable), and how consumers can contact the message sender. A compliant Privacy Policy for 10DLC messaging should include the points below to help ensure that campaign registration and vetting are successful.
Please also ensure you are linking to your privacy policy and terms and conditions in the Campaign Details section when registering your campaign. This will allow for quicker location of these items resulting in a more streamlined vetting process.
Consent
When a campaign is being vetted, the language presented in a sender's Privacy Policy is heavily scrutinized to ensure the message sender doesn't improperly claim to have the consumer’s consent to share end-user data with third parties for marketing purposes. While it's permissible for a business to share end-user data essential for business operations, the fundamental practice of sharing data to sell consumer information (leads) to third parties is a prohibited campaign type and will be rejected.
Privacy Policies are reviewed during vetting to ensure consumer data isn't transferred among various organizations. To successfully address these requirements, we recommend adopting and including a process in the Privacy Policy that demonstrates senders will refrain from sharing information consumer data.
Example: "Mobile information / mobile opt-in information will not be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties."
Opt-out instructions
Message senders are required to acknowledge the consumer's right to opt out of a messaging campaign to ensure that message recipients’ consent remains intact. The Privacy Policy must also include instructions on how to opt out of future communications.
Example: “If you wish to be removed from receiving future communications, you can opt out by texting STOP.”
It is strongly suggested that each brand create a personalized Privacy Policy with accompanying SMS disclosures as discussed above. We cannot provide guidance on what is legally required within a Privacy Policy. It's the responsibility of the message sender to research and ensure the Privacy Policy meets TCPA laws, as well as, individual carrier compliance requirements. For new, non-established brands entering the messaging space, there are online resources that can help you develop the required operational processes and Privacy Policy templates that will fit the unique needs of your business.
Note: If you're using online resources, your Policy, Practices, and Procedures must still include the above SMS disclosures and functions. Failure to adopt these practices may result in receiving a registration and vetting rejection (i.e., “805 - Compliant privacy policy is required on website”).
Terms & Conditions
All message senders must have compliant Terms & Conditions made available to their consumers/recipients. This document must be provided as a part of the campaign registration. Often, the Terms & Conditions are found on a brand's website. If the brand does not have a website, you can attach a hard copy as a PDF in the campaign registration.
The Terms & Conditions page must contain the following details:
- Brand name
- Types of messages the consumer can expect to receive
- Message frequency disclosure
- "Message and data rates may apply" disclosure
- Customer care contact information (Text HELP for help, contact [email address] for support, etc.)
- Opt-out information (Text STOP to cancel)
An example might look like this:
- SMS Opt-In Method
You may enroll by following:- (if Keyword Opt-in)
Text Command – Text START to xxx-xxx-xxxx
By opting in, you authorize BRAND NAME (“we,” “our,” “us”) to send you recurring SMS messages related to [type of messages based on Use Case].
- (if Webform Opt-in)
By submitting our webform https://xxxxx.com/contact-us/ and providing your number you consent to receive messages related to [type of messages based on Use Case].
- (if Verbal Opt-in)
We gather SMS opt-in verbally. By providing your phone number and you agree to receive messages related to [type of messages based on Use Case].
- (if Keyword Opt-in)
- Message Frequency
Message frequency varies.
- Cost
Message & data rates may apply. Carriers are not liable for delayed or undelivered messages.
- Opt-Out
Text STOP to xxx-xxx-xxxx at any time to cancel. After you text STOP, we will send a single confirmation text and you will no longer receive messages.
- Help
Text HELP for assistance, or contact us at xxx@xxxxx.com or call xxx-xxx-xxxx
- Contact Us
If you have any questions or concerns about these terms and conditions or our data practices, please reach out to us at:
Phone: xxx-xxx-xxxx Email: xxx@xxxxx.com
How are Customers Informed of the Opt-in Method
Requirement
Explain how the customers are informed on how to opt-in for messaging. This should be attached in the campaign registration. All opt-in methods are required to contain the following disclosures:
- Brand name
- Types of messages being sent
- Message frequency disclosure
- "Message and data rates may apply" disclosure
- Help information
- Stop information
- Link to the Privacy Policy
- Link to the Terms and Conditions
- Website opt-in – Attach a screenshot of the webform page
- A disclaimer should be included
- By providing your phone number you consent to receive conversational messages from [Brand Name]. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Unsubscribe at any time by replying STOP. Reply HELP for help. Privacy Policy [link] & Terms [link].
- Keyword/text opt-in - Attach a screenshot where the keyword is provided. This should be integrated to the client website. Or sent via email or is advertised etc.
- With links
- No links available for Privacy and Terms
- Verbal opt-in does not require this option as customers are being informed directly
- With links
Campaign Use Cases
- Standard Use Cases are immediately available for all ‘Verified’ Brands and do not require Vetting or pre/post-approval by MNOs.
- Special Use Cases are sensitive or critical in nature and may require Vetting or pre/post-registration approval by MNOs. Requirements may vary according to each MNO.
- Verified Non-Profit Brands with 501c3 status will be able to register Standard Use Cases in addition to "Charity" and "Emergency." Carrier terms for the "Charity" Use Case will also apply to other registered Standard Use Cases for these Brands.
- TCR allows registration for Political use case campaigns for Sole Proprietor (SP) Brands, provided they have a valid political vet. This is to support political candidates who do not have an EIN to have access to Political use-case. Some restrictions apply:
- FEC or Federal level CV token cannot be imported into SP brand.
- CV token with EIN cannot be imported into the SP brand.
- A SP brand will not be granted “Section 527” status.
- SP brand with CV token will have access to POLITICAL use-case only if the political locale is state, local, or tribal.
The following table gives a definition for each Use-Case
| Use Case | Description |
|---|---|
| 2FA | Any authentication, verification, or one-time passcode. |
| Account Notifications | Standard notifications for account holders, relating to and being about an account |
| Customer Care | All customer care interaction, including but not limited to account management and customer support |
| Delivery Notifications | Notification about the status of the delivery of a product or service. |
| Fraud Alert Messaging | Notifications regarding potential fraudulent activity on a user's account. |
| Higher Education | Messaging created on behalf of Colleges or Universities, including School Districts and education institutions. This use case is NOT for the "free to the consumer" messaging model. |
| Low Volume/Mixed | For Brands that have multiple use cases and only need very low messaging throughput. Most companies can be served by ‘Low Volume Mixed’ use case, which includes less than 2,000 messages per day or 75 Texts Per Minute. Examples include demo accounts, small businesses (single Hair Salon, Doctor's office, single Pizza shop, etc.). |
| Marketing | Any communication that includes marketing and/or promotional content. Marketing use case will require a written consent thus the only option for opt-in is through a webform. |
| Mixed | Any messaging campaign containing 2 to 5 standard use cases . |
| Polling and Voting | The sending of surveys and polling/voting campaigns for non-political arenas. |
| Public Service Announcement | Informational messaging to raise an audience's awareness about important issues. |
| Security Alert | A notification that the security of a system, either software or hardware, has been compromised in some way and there is an action you need to take. |
| Agents and Franchises | Agents; franchises; local branches Post-registration approval by MNO is required for this Use Case. |
| Carrier Exemptions | Exemption by Carrier Post-registration approval by MNO is required for this Use Case. |
| Charity | Communications from a registered charity aimed at providing help and raising money for those in need. 501c3 Tax-Exempt Organizations only. Note: If registering as a Non-Profit with a 'Charity' Special Campaign Use Case, you must also use the EIN and Legal Company name that matches your Federal Government Registration as a Non-Profit, and you must have a 501(c)(3) tax-exempt status to qualify as a Non-Profit Organization. |
| Emergency | Notification services designed to support public safety/health during natural disasters, armed conflicts, pandemics, and other national or regional emergencies. Post-registration approval by MNO is required for this Use Case. |
| Sweepstakes | All sweepstakes messaging Post-registration approval by MNO is required for this Use Case. |
| Political (Election Campaigns) | Part of an organized effort to influence the decision-making of a specific group. Available only to registered 501(c)(4/5/6) and Orgs with a Campaign Verify token. |
| Social | Communication between public figures/influencers and their communities. Examples include: YouTube Influencers' alerts or Celebrity alerts Post-registration approval by MNO is required for this Use Case. |
| Sole Proprietor | Limited to entities without an EIN / Tax ID. |
| Platform Free Trial | Platform Free Trial offers strict controls and MNO audit rights (MO opt-in). |
Campaign Description
Requirement:
Explain the campaign's objectives and intended use. The campaign description should clearly explain for what purpose the messaging is being used by the company.
Key Elements to Include:
-
Business Type: Describe your industry and services.
-
Message Frequency: State how often messages will be sent.
-
Message Content: Detail the nature of the messages (e.g., reminders, alerts). If donations are collected, it must be clearly stated.
- Audience: Identify who will receive the messages (e.g., subscribers, customers).
-
Use Case: If multiple use cases are registered, describe all use cases in the description (i.e., Low
volume mixed campaign that includes 2FA and Marketing use cases. Both use cases
should be mentioned in the campaign description.)
Example Description:
[Your Brand Name] is a [type of organization, e.g., healthcare provider, retailer, service provider] offering [key services, e.g., telemedicine services, product updates, support notifications]. Recipients will receive [type of messages, e.g., appointment reminders, promotional updates, or tips] up to [frequency, e.g., twice a week/month]. Messages may include [specific content examples, e.g., appointment confirmations, promotional offers, or helpful tips]. These communications are sent only to [target audience, e.g., registered users, subscribed customers, or opted-in recipients].
Call-to-Action (CTA) Disclosure
Key Elements to Include
- Brand Name: Clearly state your organization or company name.
-
Mobile Opt-In: Clearly describe how the user opted into messages from you (ie. verbally, website, written form)
- If a verbal opt-in is collected, include the script used to describe the opt-in flow.
- If a verbal opt-in is collected, include the script used to describe the opt-in flow.
-
Message Purpose: Describe the type of messages being sent.
-
Message & Data Rates Notice: Include “Message and data rates may apply.”
-
Message Frequency: Indicate how often users can expect messages.
-
HELP Information: Add instructions like “Reply HELP for help.”
-
STOP Information: Add instructions like “Reply STOP to unsubscribe.”
- Privacy Policy Link and Terms and Conditions Link: Provide a direct link to your Privacy Policy and Terms & Conditions.
-
Without a Link: Privacy Policy and Terms & Conditions or the client is unable to update their website at the moment
- Online presence required - Provide a link to client website or social media link
- Example: Visit us at [website]
- Provide information on how customers be able to obtain a copy of the Policy and Terms
- Example: For details on our Privacy Policy and Terms, call us at [phone number] or [email].
- Note: Make sure to attach the updated PDF file of the Policy and Terms
- Online presence required - Provide a link to client website or social media link
-
Provide how customers are informed about the opt-in method
- Website opt-in – Provide the link of the webform
- By submitting our webform [https://weblinkform] and providing your number
- Keyword/text opt-in - Attached screenshot
- Example: Customers are informed of the keyword opt-in with the attached SMS advertisement or to this [link] and in the Terms [link]
- Verbal opt-in does not require this option as customers are being informed directly
- Website opt-in – Provide the link of the webform
Example CTA Message:
Website/Online opt-in:
Note: Website opt-ins will require
- A SMS disclosure shown just below the webform. The CTA below the same as your SMS disclosure
- A check box. The check box is required to avoid a forced opt-in consent.
CTA / SMS disclosure
- With a Policy and Terms Link
By submitting our webform [https://weblinkform] and providing your number, you consent to receive conversational text messages related to customer care support and account updates from [BRAND] at the number provided. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Unsubscribe at any time by replying STOP. Reply HELP for help. Privacy Policy [LINK] and Terms and Conditions [LINK]. Please check on the box if you accept this SMS disclosure.
-
Without a Policy and Terms Link
By submitting our webform [https://weblinkform] and providing your number, you consent to receive conversational text messages related to customer care support and account updates from [BRAND] at the number provided. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Unsubscribe at any time by replying STOP. Reply HELP for help. Visit us at [website]. For details on our Privacy Policy and Terms, call us at [phone number] or [email]. Please check on the box if you accept this SMS disclosure.
Keyword Opt-in:
- With a Policy and Terms LINK
Customers opt-in by texting START to [phone number], you consent to receive conversational messages from [Brand Name]. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Unsubscribe at any time by replying STOP. Reply HELP for help. Privacy Policy [link] & Terms [link]. Customers are informed of the keyword opt-in with the attached SMS advertisement or to this [link] and in the Terms [link].
- Without a Policy and Terms LINK
Customers opt-in by texting START to [phone number], you consent to receive messages from [Brand Name] regarding account updates or related questions. Consent is not a condition of purchase. Message frequency varies; expect up to 2 messages per week. Message and data rates may apply. Reply HELP for help, STOP to unsubscribe. Visit us at [website]. For details on our Privacy Policy and Terms, call us at [phone number] or [email]. Customers are informed of the keyword opt-in with the attached SMS advertisement or to this [link] and or when the customers requests for our Terms.
Verbal opt-in:
- With a Policy and Terms LINK
[BRAND] will only be collecting opt-ins verbally from their customers. The customers will be able to opt in to receive messages either in person at their physical location, or over a phone call if the customer calls. During an in person or over the phone meeting, [BRAND] staff will ask if the customer if they want to be signed up for text updates about their account. When a customer is registered for the first time, they are asked to provide the phone number. Staff is trained to ask If the customer would like to opt in to SMS-based notifications and updates about their account. They will be verbally informed that "Message and data rates may apply", "Message frequency may vary", and they can "text HELP for support or more information and STOP to unsubscribe at any time." They will also be informed that their phone number will not be shared with third parties for marketing or promotional purposes. Staff are also trained to read the Privacy Policy & Terms and Conditions upon verbal agreement to receive text messages and will also get the option to get a copy of the Privacy Policy and Terms & Conditions. Privacy Policy [link] & Terms [link].
- Without a Policy and Terms LINK
[BRAND] will only be collecting opt-ins verbally from their customers. The customers will be able to opt in to receive messages either in person at their physical location, or over a phone call if the customer calls. During an in person or over the phone meeting, [BRAND] staff will ask if the customer if they want to be signed up for text updates about their account. When a customer is registered for the first time, they are asked to provide the phone number. Staff is trained to ask If the customer would like to opt in to SMS-based notifications and updates about their account. They will be verbally informed that "Message and data rates may apply", "Message frequency may vary", and they can "text HELP for support or more information and STOP to unsubscribe at any time." They will also be informed that their phone number will not be shared with third parties for marketing or promotional purposes. Staff are also trained to read the Privacy Policy & Terms and Conditions upon verbal agreement to receive text messages and will also get the option to get a copy of the Privacy Policy and Terms & Conditions. Visit us at [website]. For details on our Privacy Policy and Terms, call us at [phone number] or [email].
Important Notes:
-
Voluntary Opt-In: Users must opt in voluntarily; forced opt-ins are prohibited.
-
Optional Phone Number Field: The phone number field must be optional on forms.
- Separate Consents: Separate opt-ins are required for emails or calls.
-
Website/Online opt-in: If the CTA mentions the opt-in collected on a website, the website must be provided. If it's not provided, the campaign will be declined.
Sample Messages
Requirement:
Provide examples of the SMS messages you plan to send. Each sample must:
- Include your business name in the first message.
- Be at least 20 characters long.
- Contain clear opt-out language.
- Example: Reply STOP to unsubscribe
- Sample Messages must correspond to the registered use case. If a campaign is registered under multiple use cases (mixed), a sample message for each use case should be provided.
- For example, if you register under the marketing use case, state in the description the use of texts for promotional purposes and the sample message should reflect a typical marketing message you would send.
- For example, if you register under the marketing use case, state in the description the use of texts for promotional purposes and the sample message should reflect a typical marketing message you would send.
Examples:
-
Initial Message:
-
Welcome to [Your Company Name] updates. You'll receive weekly health tips. Reply STOP to unsubscribe. [Privacy Policy Link]

Subscriber Messages
Opt-in
Requirements
-
Brand Name: Identifies the sender of the messages.
-
Message Purpose: Clearly states what types of messages will be sent.
-
Message Frequency: Discloses how often the consumer can expect to receive messages.
-
Standard Message and Data Rates Notice: Alerts users that their carrier rates may apply.
-
HELP and STOP Instructions: Provides clear instructions for assistance or opting out
Example:
"Thank you for opting in to receive messages from [Your Brand Name]. You will receive [message purpose, e.g., updates, appointment reminders, promotional offers]. Message frequency varies; expect up to [X messages per week/month]. Standard message and data rates may apply. Reply HELP for help or STOP to unsubscribe."

Opt-out
Requirements
Brand Name: Identifies the sender of the messages to ensure clarity for the consumer.
Acknowledgment of Opt-Out Request: Confirms the consumer's request to unsubscribe has been received and processed.
Final Confirmation Message: Notifies the consumer that they have successfully opted out and will no longer receive messages for the specific campaign.
STOP Instructions: Clearly states the standardized keyword (e.g., STOP) used to initiate the opt-out process.
Support for Natural Language Variations: Accepts opt-out requests with normal language (e.g., "Please stop," "Unsubscribe me") regardless of case or punctuation.
No Further Messaging After Confirmation: Ensures no additional messages are sent after the opt-out confirmation message.
Support Contact Information (Optional but Recommended): Provides a way for consumers to contact support for additional assistance, such as an email, phone number, or website.
No Marketing Content: Confirms the opt-out without including promotional or marketing content in the confirmation message.
Example
"You have successfully unsubscribed from [Your Brand Name]. You will no longer receive messages from this campaign. For assistance, contact [support email or phone number]. Reply START to resubscribe."

Help
Requirements
1. Brand Name: Clearly identifies the sender (e.g., "[Your Brand Name]").
2. Support Contact Information: Includes at least one support option:
3. STOP Instructions: Provides the option for the consumer to unsubscribe if needed.
4. Clear Purpose: Explains that the message is for assistance only.
Example
"For assistance with [Your Brand Name], visit [Support Website Link], email [Support Email], or call [Support Phone Number]. Reply STOP to unsubscribe."

Common Issues
Legal Name
The overwhelming majority of identification check failures are due to improperly entering the company's legal name. Please have the client provide a screenshot of the official letter (CP-575) from the IRS to ensure the information is logged correctly.
Review the section that lists the name and address at the top of the letter. This is almost always two lines such as:
NAME LINE 1
NAME LINE 2
123 MAIN ST
SPRINGFIELD, IL 55443
Enter the legal name as the first line of the name field (NAME LINE 1), this should work most of the time. In some cases, however, you will also need to enter the second line as well. This would look like - NAME LINE 1 NAME LINE 2.
Omit any special characters that are part of the business name with the exception of hyphens (-) and ampersands (&).
For White Label Partners, have them resubmit the changes. If the legal name is not editable, have them delete the Brand ID and resubmit a new one.
Note: It can take up to 15 minutes for the status to change to Verified.
10DLC Vetting Rejection Reasons
10DLC Vetting Rejection Reasons
Scope
Intended Audience: All Partners
As 10DLC continues to evolve, the wireless carriers have identified a gap in the registration process - campaigns are not being registered appropriately and do not adhere to the carriers’ codes of conduct. As a result, every newly created 10DLC campaign must go through manual vetting. If a campaign is not approved, it will be given one of the following rejection reasons.
Note: The vetting rejections may include multiple reasons for denial. Do reach out to ports@oit.co for clarifications or guidance.
DCA2 Vetting Rejection Reasons
| Error Description | Error Code |
Action to Resolve |
| Unable to translate; for proper review, the campaign must be in English. | 506 |
Please ensure that all content in your campaign submission, including Call To Action (CTA), Message Flow, and Sample Messages, is in English. |
| Campaign Attributes do not match the website and/or sample message content. | 601 |
Please re-create the campaign, making sure to select the correct campaign and content attributes under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Example: If a customer selects "no" for the embedded link, but the sample content provided clearly shows links. They will need to resubmit their campaign with "yes" selected for the embedded link. |
| Inaccurate Registration. Inconsistency between the sample message and the use case. | 602 |
Ensure that the selected use case is consistent with the sample messages. Example: If they select charity as their use case but are sending appointment reminders, they would be rejected. They either need to update their sample messages or change their use case to better align with the content they are sending. |
| Inaccurate Registration. Inconsistency between the website, brand name, and/or sample messages, or inconsistent sample messages. | 603 |
Ensure that the content on the website, sample messages, and brand are all consistent. Example: If the Brand name is ABC Physicians, they would be rejected if they had sample content sent out regarding sales for a clothing shop, or had a website for a marketing firm. A good example would be the brand ABC Physicians, sending appointment reminders, and a link to their practice's webpage. |
| Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website). | 611 |
Please review your keyword response messages (Opt-in/JOIN, Opt-Out/STOP, and HELP). The opt-in confirmation message must contain the brand name, instructions on how to request help, message frequency, "message and data rates may apply" disclosure, and instructions on how to opt out. The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. The STOP/opt-out confirmation message must contain the brand name, confirmation of opt-out, and confirmation that they will receive no further messages. |
| Prohibited Content; Cannabis. | 701 |
Do NOT resubmit. Cannabis/hemp/CBD is not allowed over 10DLC, and campaigns related to this content will be rejected. Note: This content is not allowed to be on the customer's website at all. Example: If a chiropractor's office has CBD oils on its website, this is prohibited, and the campaign will be denied, even if not directly related to CBD marketing. |
| Prohibited Content; Guns/Ammo {Failure to age gate}. | 702 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
| Prohibited Content; Explicit sexual. | 703 |
Do NOT resubmit. Explicit sexual content is not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Prohibited Content; Gambling. | 704 |
Do NOT resubmit. Gambling content is not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Prohibited Content; Hate. | 705 |
Do NOT resubmit. Hate speech is not allowed over 10DLC, and campaigns related to this content will be rejected. |
|
Prohibited Content; Alcohol {Failure to age gate}. |
706 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
| Prohibited Content; Tobacco / Vape {Failure to age gate}. | 707 |
Please only resubmit once there is proper proof of age gating. The best practice would be a manual entry of MM/DD/YYYY collected prior to accessing the opt-in page. The website will be checked for age-gating. |
| Lead Gen/Affiliate Marketing prohibited; other. | 708 |
Do NOT resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Lead Gen/Affiliate Marketing prohibited; high-risk financial services. | 709 |
Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Reseller / Non-compliant KYC. Register the brand info, not the agency or software provider behind the brand. | 710 |
Make sure that Know Your Customer (KYC) is clearly laid out in the campaign. Remember the brand is the message sender – the EIN and company information should reflect the message sender, not necessarily you as the reseller. Example: If the band name is ABC Wireless Reseller, but their sample content is all appointment reminders for a doctor's office, they will be rejected. Instead of the software company (ABC Wireless Reseller), the brand should be the doctor's office sending appointment reminders. |
| Repeated use of the same EIN for multiple different brands. | 711 |
Only register one brand per EIN. Do not resubmit unless the brand has been updated to reflect the actual sender (EIN, legal company name, etc) and the EIN and is not a duplicate of other brands. |
| Misleading Registration. Based on the details submitted, Campaign appears to be a Direct Lending Arrangement, but the appropriate Content Attribute was not selected. | 712 |
Please re-create the campaign, making sure to select "direct lending or loan agreement" under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Please note that any campaign for a lender will need this attribute checked. Example: If the campaign type is Marketing but the sample messages ask questions about qualifying someone for a loan and the campaign/content attributes do not indicate lending (i.e., sample message that asks "Can you please provide your first and last name, and either the year, make and model of your vehicle or the last 4 digits of your SSN?"). |
| Appears to be a large company or a company that would have an official email domain. Check for fraud, and use the official/working email domain. | 713 |
Please check to make sure that the correct email address was added. It is expected that if the legal company name is well-known and recognized that it will have an official company email domain. Example: A large bank (ABC BANK) would not be using an email address like jsmith@gmail.com. We would expect the email to match the business, such as jsmith@abcbank.com. |
| Invalid Opt-In. Permission to text users via a court order does not meet the carrier's code of conduct. | 714 |
If you can obtain opt-in via another method, this can be resubmitted. If not, please do not resubmit, as opt-in will never be compliant. |
| Not Sole Proprietor. Does not meet small business Sole Prop (EIN) criteria set by TCR and mobile carriers. | 801 |
At this time, new Sole Proprietor campaigns are not being accepted. Please find another use case for the campaign. |
| Sole Proprietor. Not yet authorized. | 802 |
Bandwidth is not supporting Sole Proprietor use cases at this time. Please reach out to your Bandwidth Support Team with any questions. |
| Call to Action forces an opt-in consent because it's missing the checkbox. The checkbox is either not present or mandatory, causing a forced opt-in. | 803 |
Opt-in cannot be forced. Please provide details on the collection process for opt-in to verify that participation is optional and not compulsory. Utilizing an optional checkbox mechanism for opt-in is recommended. |
| Unable to verify, need a website/ working website, or complete CTA information if opt-in occurs outside of the website. | 804 |
We have often seen campaigns rejected for insufficient call-to-action sections. Please provide a working website link and a clear and concise description of how an end user signs up to receive messages. Opt-in must be 1 to 1, can't be shared with third parties, and can't be implied. . |
| A compliant privacy policy is required on the website. | 805 |
Per 5.2.1 of the CTIA Guidelines, message senders are to maintain a privacy policy that is easily accessible by the consumer. It should be referenced in the call-to-action/opt-in. You may receive this denial if there is no privacy policy present, OR if the privacy policy is non-compliant. The non-compliance generally would be around the sharing of consumer information with third parties for marketing purposes. Steps toward approval would be adding a compliant privacy policy or editing the non-compliant privacy policy. |
| Unable to verify, needs compliant and accurate CTA information. Update with specific path for mobile opt-in. | 806 |
Either the CTA is inaccurate and doesn't explain where the customers opt into the campaign (website, verbal, written, etc.), or the opt-in is on the website, but there is no phone field to add the phone number. |
| Unable to verify inauthentic website. | 807 |
Please ensure any references to websites in your brand and campaign registration are working links and pertain to the specific business being registered. |
| The campaign has been declined 5+ times. | 808 |
The campaign has been declined 5+ times without sufficient updates. Each denial incurs a vetting fee. For questions, please reach out to your Direct Connect Aggregator (DCA). |
| A compliant privacy policy is required to be attached to registration if not available on the website. | 809 |
A compliant privacy policy example is required to be attached to registration in TCR or emailed to your Direct Connect Aggregator (DCA) when opt-in is collected either in person or over the phone, and not via a website. |
| Add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties). Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website). | 851 |
Ensure there is a compliant privacy policy available (in the privacy policy link field, CTA/Message Flow field, or attached as a document. Please review your keyword response messages (Opt-in/JOIN, Opt-Out/STOP, and HELP). The opt-in confirmation message must contain the brand name, instructions on how to request help, message frequency, "message and data rates may apply" disclosure, and instructions on how to opt out. The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. The STOP/opt-out confirmation message must contain the brand name, confirmation of opt-out, and confirmation that they will receive no further messages. |
| Needs a compliant Privacy Policy. Add link and/or verbiage for compliant Privacy policy disclosures (state that no mobile opt-in data will be shared with third parties). Include instructions on how the end user can receive further support from the brand regarding the message program (for example, Reply HELP for help), or this information must be present in the brand's terms and conditions. | 852 |
Provide Terms and Conditions link (include a link to the message program terms and conditions, or the complete message program terms and conditions language). Provide a Privacy Policy link (include a link to the message program privacy policy, or language referring to the privacy policy, that indicates that mobile opt-in data will not be shared). |
| Needs compliant and accurate CTA information. Opt-in message/Confirmation MT must contain brand name, HELP, opt-out, message frequency, and associated fees disclosures. The opt-out message must contain the brand name and indicate that no further messages will be sent. HELP message must contain the brand name and support contact (email, phone number, or support website). | 861 |
Ensure the CTA/Message Flow field explains exactly how the brand collects consent. It must also include a link to the Terms and Conditions (or the link can be provided in the Terms Link field). Please ensure your keyword responses are compliant with the requirements listed in rejection code 611. |
Invalid Call to Action
| Rejection Description | Rejection Code |
Action to Resolve |
| Invalid Call to Action: No form of opt-in whatsoever was found in the description or message flow. | 2100 |
Either the CTA is inaccurate and doesn't explain where the customers opt in to the campaign (website, verbal, written, etc.), or the opt-in is on the website, but there is no phone number field to add the phone number. |
| Invalid Call to Action: This was determined to be a promotional campaign, but there was no mention of a written opt-in. | 2101 |
Marketing/promotional content requires prior express written consent. Update the campaign with a valid opt-in collection method. |
| Invalid Call to Action: This was determined to be an informational campaign, but no explicit means of opt-in was given. | 2102 |
Informational messaging requires express consent from the consumer. The consumer needs to agree to receive texts for a specific informational purpose. Update the campaign with a valid opt-in collection method. |
| Invalid Call to Action: Received a "certificate verify failed" error for the opt-in URL. | 2103 |
Ensure the opt-in URL provided leads to the direct opt-in form. |
| Invalid Call to Action: No website or domain was found with the given opt-in URL. | 2104 |
Ensure the opt-in URL provided leads to the direct opt-in form. |
| Invalid Call to Action: This campaign has verbal opt-in, but does not contain an explicit script of what the company says. | 2105 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures: brand name, types of messages being sent, message frequency disclosure, "message and data rates may apply" disclosure, HELP information, STOP information, and a link to the privacy policy and terms and conditions. |
| Invalid Call to Action: The script for verbal opt-in must contain instructions on how to reach the privacy policy. | 2106 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include a link to the privacy policy and terms and conditions. |
| Invalid Call to Action: The verbal opt-in script does not contain the brand name. | 2108 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the brand name. |
| Invalid Call to Action: The verbal opt-in script has no information about the type of messages being sent. Examples include but are not limited to: Marketing, MFA, reminders, etc. | 2109 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the types of messages being sent. |
| Invalid Call to Action: The verbal opt-in script contains no disclosure about the frequency of message delivery. | 2110 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as message frequency disclosure. |
| Invalid Call to Action: The verbal opt-in script has no disclosure that message and data rates will apply to messages sent. | 2111 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as the "message and data rates may apply" disclosure. |
| Invalid Call to Action: The verbal opt-in script has no information detailing how a customer can stop receiving messages. | 2112 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such as STOP information. |
| Invalid Call to Action: The brand name could not be found in the opt-in form. | 2113 |
Ensure the opt-in form includes all of the necessary disclosures, such as the brand name. |
| Invalid Call to Action: The opt-in form should mention the types of messages a customer can expect to receive. | 2114 |
Ensure the opt-in form includes all of the necessary disclosures, such as the types of messages being sent. |
| Invalid Call to Action: The opt-in form must mention message frequency. | 2115 |
Ensure the opt-in form includes all of the necessary disclosures, such as message frequency disclosure. |
| Invalid Call to Action: The opt-in form has no disclosure that message and data rates will apply to messages sent. | 2116 |
Ensure the opt-in form includes all of the necessary disclosures, such as the "message and data rates may apply" disclosure. |
| Invalid Call to Action: The opt-in form must include information on how a customer can receive help. | 2117 |
Ensure the opt-in form includes all of the necessary disclosures, such as HELP information. |
| Invalid Call to Action: The opt-in form must include information on how a customer can opt out. | 2118 |
Ensure the opt-in form includes all of the necessary disclosures, such as STOP information. |
| Invalid Call to Action: There is no HELP message available in the verbal opt-in script. | 2119 |
If the brand utilizes a verbal opt-in collection, the verbal script read to consumers at the time of opt-in collection must be provided in the campaign. It must include all of the necessary disclosures, such a HELP information. |
| Invalid Call to Action: No opt-in URL was found in the campaign submission. | 2120 |
If the opt-in is collected online, the direct URL to opt in must be provided. If the online opt-in is obscured behind a log-in or application, you can provide a screenshot and explain that the opt-in screenshot is attached. |
| Invalid Call to Action: The opt-in form must provide instructions on how to find the privacy policy. | 2121 |
Ensure the opt-in form includes all of the necessary disclosures and links to the privacy policy and terms and conditions. |
| Invalid Call to Action: The webpage used for opt-in does not contain an opt-in form. | 2125 |
Ensure the webpage listed in the message flow contains an opt-in form with all necessary opt-in disclosures. |
| Invalid Call to Action: Opt-in information in the description or message flow implies that opt-in is acquired through a court order, which is disallowed. | 2126 |
If you can obtain opt-in via another method, this can be resubmitted. If not, please do not resubmit as opt-in will never be compliant. |
| Invalid Call to Action: The attachment used for opt-in does not contain an opt-in form. | 2129 |
Ensure the attachment used for an opt-in form contains an opt-in form with all necessary opt-in disclosures. |
| Invalid Call to Action: The attachment used for opt-in does not contain a script for verbal opt-in. | 2130 |
Ensure the attachment used for a verbal opt-in scripts contains a verbal script with all necessary opt-in disclosures. |
| Invalid Call to Action: SMS consent must be optional on a multi‑purpose form. | 2131 |
The phone number or opt in checkbox must be optional. |
| Invalid Call to Action: The instructions provided for a customer to give SMS opt-in are not sufficient. | 2132 |
Add additional information to clearly describe the method of opt-in (verbal, web form, etc). Customer initiated opt-in methods must identify how customers are notified on how to opt in and feature all required disclosures. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain the brand name. | 2133 |
Add the brand name into the CTA/Message Flow field. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in should mention the types of messages a customer can expect to receive. | 2134 |
Add in the type of messages the end user can receive from this brand in the CTA/Message Flow field. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain a disclosure about the frequency of message delivery. | 2135 |
Add in the frequency of messages the end user can expect in the CTA/Message Flow field. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain a disclosure that message and data rates will apply to messages sent. | 2136 |
Add in the “message and data rates may apply” in the CTA/Message Flow field. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain information about how a customer can receive help. | 2137 |
Add in the “HELP” disclaimer in the CTA/Message Flow field. |
| Invalid Call To Action: The instructions provided for a customer to give SMS opt-in do not contain information on how a customer can opt-out. | 2138 |
Add in the “STOP” disclaimer in the CTA/Message Flow field. |
| Invalid Call To Action: The provided opt-in form does not contain any phone number input field. | 2139 |
Add in a phone number field to the current opt-in method. |
| Invalid Call To Action: The verbal opt-in script must provide instructions on how to find privacy policy or provide necessary privacy disclosures. | 2140 |
Add instructions to the call to action on how to find privacy policy or provide necessary privacy disclosures. |
| Invalid Call To Action: The keyword opt-in instructions must provide instructions on how to find privacy policy, or provide necessary privacy disclosures. | 2141 |
Add details to the keyword call to action disclosures that include instructions on how to find privacy policy or provide necessary privacy disclosures. |
| Invalid Call To Action: The message flow or opt in mentions promotional or marketing messages, but the use cases do not include marketing. | 2200 |
Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the message flow if it will not be used. |
Invalid Campaign Description/Attributes
| Rejection Description | Rejection Code |
Action to Resolve |
| Invalid Campaign Description/Attributes: The campaign was detected as having relations to high-risk financial services in the description or message flow, which is prohibited. | 3100 |
Do NOT resubmit. High-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow and description, and also featured high-risk financial loans on the website, which is prohibited. | 3101 |
Do NOT resubmit. Lead generation, affiliate marketing, and high-risk financial services are not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Invalid Campaign Description/Attributes: This campaign was detected to involve affiliate marketing in the message flow or description. | 3102 |
Do NOT resubmit. Lead generation and affiliate marketing are not allowed over 10DLC, and campaigns related to this content will be rejected. |
| Invalid Campaign Description/Attributes: The campaign has content related to direct lending in the description, message flow, or website, but the directLending field is set to False. | 3103 |
Please re-create the campaign making sure to select "direct lending or loan agreement" under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Please note that any campaign for a lender will need this attribute checked. Example: If the campaign type is Marketing but the sample messages ask questions about qualifying someone for a loan and the campaign/content attributes do not indicate lending (i.e., sample message that asks "Can you please provide your first and last name, and either the year, make and model of your vehicle or the last 4 digits of your SSN?"). |
|
Invalid Campaign Description/Attributes: Not all required fields populated. |
3105 |
Please re-create the campaign, making sure to select the correct campaign and content attributes under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Example: If a customer selects "no" for the embedded link, but the sample content provided clearly shows links. They will need to resubmit their campaign with "yes" selected for the embedded link. |
| Invalid Campaign Description/Attributes: Either a phone number or link was found in the sample messages, but the associated embedding field was not set to true. | 3106 |
Please re-create the campaign, making sure to select the correct campaign and content attributes under campaign and content attributes. Currently, these fields are not editable in existing campaigns. Example: If a customer selects "no" for the embedded link, but the sample content provided clearly shows links. They will need to resubmit their campaign with "yes" selected for the embedded link. |
| Invalid Campaign Description: The Direct Lending field for the campaign was set to true, but the campaign description, sample messages, or website did not have content about lending. | 3107 |
Add a sample message that includes data related to lending that aligns with the brand and use case OR update the attribute to 'No' if you do not intend to send messages related to lending or financing. |
| Invalid Campaign Description: The Embedded Phone Number was set to true, but no phone number found in the sample messages. | 3108 |
Add a sample message that contains a phone number OR update the attribute to 'No' if you do not intend to send messages that include a phone number. |
| Invalid Campaign Description: The Embedded Link was set to true, but no link found in the sample messages. | 3109 |
Add a sample message that contains a link OR update the attribute to 'No' if you do not intend to send messages that include a link. |
| Invalid Campaign Description: Campaigns may only use the charity use case if they solicit donations. | 3110 |
Register a new campaign with a more relevant use case if donations will not be solicited OR add proper disclaimers to the description if donations will be solicited. |
| Invalid Campaign Description: The description describes a promotional or marketing use case, but the use cases do not include marketing. | 3200 |
Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the description if it will not be used. |
Disallowed Content Detected
| Rejection Description | Rejection Code |
Action to Resolve |
| Disallowed Content Detected: Sample message contents violate SHAFT-C requirements. | 4100 |
Do NOT resubmit. The use case is disallowed and will be rejected. |
Missing Mandatory Message Terminology
| Rejection Description | Rejection Code |
Action to Resolve |
| Missing Mandatory Message Terminology: The opt-out message must contain the brand name. | 5100 |
The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages. |
| Missing Mandatory Message Terminology: No valid opt-out keywords are listed. Valid opt-out keywords are: STOP, END, UNSUBSCRIBE, and CANCEL. | 5101 |
Please let all opt-out keywords be supported. At minimum, STOP must be supported. |
| Missing Mandatory Message Terminology: The opt-out message must contain a confirmation that no more messages will be sent. | 5102 |
The STOP/opt-out confirmation message must contain the brand name and confirmation that they will receive no further messages. |
| Missing Mandatory Message Terminology: HELP is not listed as a help keyword. | 5103 |
Please let all opt-out keywords be supported. At a minimum, HELP must be supported. |
| Missing Mandatory Message Terminology: The opt-in message must contain the brand's name. | 5104 |
The Opt-in confirmation message must include the brand name. |
| Missing Mandatory Message Terminology: The opt-in message must contain disclosures on message frequency. | 5105 |
The Opt-in confirmation message must include the message frequency disclosure. |
| Missing Mandatory Message Terminology: The opt-in message must contain disclosure mentioning data rates may apply. | 5106 |
The Opt-in confirmation message must include the "message and data rates may apply" disclosure. |
| Missing Mandatory Message Terminology: Opt-in message does not contain HELP keyword. | 5107 |
The Opt-in confirmation message must include HELP information. |
| Missing Mandatory Message Terminology: The opt-in message must contain the provided opt-out keywords. | 5108 |
The Opt-in confirmation message must include a keyword to opt out. |
| Missing Mandatory Message Terminology: The help message must contain the brand's name. | 5109 |
The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. |
| Missing Mandatory Message Terminology: The help message must contain a website, phone number, and/or email for customers to contact you. | 5110 |
The HELP response must include the brand name and a toll-free number, email, or website where the consumer can reach out for help. |
Other Invalid Campaign Feature
| Rejection Description | Rejection Code |
Action to Resolve |
| Invalid Brand Info: Sole proprietors are not yet supported. | 6100 |
Bandwidth does not support Sole Proprietor use cases at this time. Please reach out to your Bandwidth Support Team with any questions. |
| Other Invalid Campaign Feature: A campaign was previously processed with the same description, company name, website, message flow, and sample messages, but with a different campaign ID. Duplicate campaigns: {duplicate_campaigns} | 6101 |
Identical campaigns without differentiation are disallowed and viewed as snowshoeing. If you need more than 49 numbers, please submit a Number Pool request. If your need differs, please open an appeal ticket with the use case for identical campaigns. |
| Other Invalid Campaign Feature: The email and/or phone number must not contain any spaces. | 6102 |
Check contact details for extra spaces before or after your inputs. |
| Other Invalid Campaign Feature: No campaign field may contain emojis. | 6103 |
Remove emojis from any fields where they are included. |
| Other Invalid Campaign Feature: We could not complete your CNP migration as your Bandwidth account has not been configured to accept the migration. Please reach out to Bandwidth support to remediate before trying again. | 6104 |
Please reach out to Bandwidth support to configure your account for CNP migrations. |
| Other Invalid Campaign Feature: This campaign has been submitted 4+ times with the same unresolved errors. To prevent further fees, it will be placed in a PENDING state the next time you submit it. Please initiate an Appeal Request for review, and our team will assist you. | 6105 |
Please open a ticket with our support team for campaign review and next steps. |
| Other Invalid Campaign Feature: The help message contains a URL from a public URL shortener, which is not allowed. | 6106 |
Please remove the public URL shortener in favor of a full link or branded shortener and resubmit the campaign for review. |
| Other Invalid Campaign Feature: The opt-in message contains a URL from a public URL shortener, which is not allowed. | 6107 |
Please remove the public URL shortener in favor of a full link or branded shortener and resubmit the campaign for review. |
| Other Invalid Campaign Feature: The opt-out message contains a URL from a public URL shortener, which is not allowed. | 6108 |
Please remove the public URL shortener in favor of a full link or branded shortener and resubmit the campaign for review. |
Invalid Privacy Policy
| Rejection Description | Rejection Code |
Action to Resolve |
| Invalid Privacy Policy: No privacy policy URL was found in the campaign submission. | 7100 |
Please provide the link to the privacy policy in the Privacy Policy Link field. |
| Invalid Privacy Policy: No website or domain was found with the given privacy policy URL. | 7101 |
Please confirm the link to the Privacy Policy leads to the direct page. |
| Invalid Privacy Policy: The link or attachment used to analyze the privacy policy does not appear to show an actual privacy policy. | 7102 |
Please ensure the link provided directs to the brand's Privacy Policy. |
| Invalid Privacy Policy: The privacy policy does not mention that mobile opt-in will not be shared, and appears to allow for the sharing of data with other companies. | 7103 |
Update the Privacy Policy to make it clear that text messaging opt-in is not shared with any third parties. |
| Invalid Privacy Policy: Received a 'certificate verify failed' error for the privacy policy URL. | 7105 |
Please confirm the link to the Privacy Policy leads to the direct page. |
| Invalid Privacy Policy: The verbal opt-in script does not contain a valid privacy policy disclaimer or link to a valid privacy policy webpage. | 7107 |
Add a privacy policy disclaimer to the script or add mention of the link to locate the privacy policy to the script. |
| Invalid Privacy Policy: The privacy policy must prohibit the sharing of SMS opt-in data with third parties for marketing purposes, even with consent. | 7108 |
Messaging originator opt-in data may never be shared, sold, or rented even with consumer consent. Please review your client’s privacy policy to remove exception reasons for sharing, and add specific disclosures found here. Please open a support ticket for additional assistance. |
| Invalid Privacy Policy: The privacy policy contains a disallowed exception for the sharing of SMS opt-in data. | 7109 |
Messaging originator opt-in data may never be shared, sold, or rented. Please review your client’s privacy policy to remove exception reasons for sharing, and add specific disclosures found here. Please open a support ticket for additional assistance. |
| Invalid Privacy Policy: The privacy policy mentions promotional or marketing messages, but the use cases do not include marketing. | 7200 |
Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the privacy policy if it will not be used. |
Invalid Sample Messages
| Rejection Description | Rejection Code |
Action to Resolve |
| Invalid Sample Messages: At least one sample message must contain opt-out language. | 8100 |
Update at least one of the sample messages to include opt-out language (Reply STOP to stop). |
| Invalid Sample Messages: All sample messages must contain the brand name. | 8101 |
Ensure each sample message includes the Brand name. |
| Invalid Sample Messages: A sample message must be provided for each use case and sub-use case. | 8102 |
Ensure each use case selected in the Use Case Selection is represented in at least one of the sample messages (i.e., if you have a Mixed Use Case with Account Notifications, Customer Care, and Marketing, you will need a sample message for each of the three use cases). |
| Invalid Sample Messages: One or more sample messages are for promotional or marketing purposes, but the use cases do not include marketing. | 8200 |
Register a new campaign which features marketing as a selected use case OR remove marketing verbiage from the sample messages if it will not be used. |
| Invalid Sample Messages: One or more sample messages contain a URL from a public URL shortener, which is not allowed. | 8201 |
Please remove the public URL shortener in favor of a full link or branded shortener and resubmit the campaign for review. |
Campaign Registry Integration Tips
Our campaign registry integration makes it easy to be complaint, right in the manager portal.
Campaign Status Email Notification
To change where your campaign status notifications are emailed, click the envelope modal in the brands tab:
Note all campaigns for this brand will be updated

Update to notification email(s) if need be. The address will default to your logged in users email. This will immediatley take effect for any campaigns registeres under this brand.

Declined Reason in the Manager Portal
To quickly check campaign decline reasons, you can hover over the tooltip in the decline cell

File Upload and Links
If you do not have Terms of Service or a Privacy Policy on your website, you can upload them here:
- Make sure to rename your file
- [Brand]- Privacy Policy
- [Brand] – Terms and Conditions
- [Brand] - Advertisment

While you are not currently required to provide Terms of Service or Privacy Policy links, it will be in the future. We recomend that you add them now if you have them.
Inactive Campaigns
Campaigns showing inactive are not able to be re-activated or edited. Please create a new Campaign

Clients cannot send SMS/MMS until the brand and campaign are submitted and verified, which can take 7-14 days from submission as long as nothing is wrong with the application.