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 by Bandwidth's Direct Connect Aggregator (DCA) partner.
Bandwidth utilizes a Proxy DCA for certain carriers. These rejection reasons will be formatted as "Proxy Connector" + the rejection reason when returned to you. Bandwidth also utilizes a secondary DCA for certain carriers. These rejection reasons can be found here.
Note: The vetting rejections may include multiple reasons for denial. Please do not resubmit the campaign until all rejection(s) are fully resolved, as there is a $15 fee for every vetting event.
Feel free to use the In this article section to the right for faster navigation.
Campaign attributes
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
1001 | Campaign appears to be for an age-gated content type but age gate attribute is not selected. | Verify if the Age Gate attribute is selected for the campaign registration. If the campaign is not related to age-gated content, update the campaign description. | TCR submission requirements dictate that appropriate attributes are selected that are in line with the campaign submission. |
1002 | Campaign is for direct lending or loan arrangement and is missing the content attribute indicating direct lending. | Verify direct lending or loan arrangement is selected for campaign registration. If the campaign is not related to direct lending or loan arrangement, update the campaign description. |
Campaign description / program summary
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
2001 | Campaign registration is not unique or duplicate campaign | Duplicate campaigns are disallowed. Campaigns should be uniquely registered. | |
2002 | Unclear campaign description | It must be clear from your campaign description what the purpose of your message program is. Add more details to the description and resubmit. | |
2003 | Campaign description does not match declared use case(s) | The use case described in the campaign description must match the registered use case. Update the description or register the campaign again with the correct use case and resubmit. | |
2004 | Campaign description does not match sample messages | The use case described in the campaign description must match the use case demonstrated in the sample message content. Update the description or sample message content and resubmit. | |
2005 | Undeclared use case | The campaign description indicates the campaign will be used for a use case that is not selected. Check your campaign description is accurate and all use cases are selected. | |
2006 | Brand referenced in campaign description does not match registered/DBA brand | The brand in the campaign and messaging should be consistent with the brand registered. Update and resubmit. |
Call-to-action (opt-in experience as described in campaign submission)
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
3001A | Call-to-action does not obtain sufficient consent | All CTAs must obtain consent via a proper consent mechanism. Update and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3002A | A Call-to-action does not contain registered/DBA brand name | The company/brand name must be included in the CTA and must match the registered Brand or be easily recognizable as the same entity. Update the call-to-action and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3003A | Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions. HELP for HELP or customer care contact information must be provided in either the CTA or the Terms & Conditions. | Update the CTA or T&Cs page to include HELP for HELP, HELP instructions, OR customer care contact information. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action customer care contact information |
3004A | Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel) | The call-to-action must include instructions on how the end user can opt out of the message program (for example, Reply STOP to opt out). Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action how to opt out |
3005A | Call-to-action does not contain message frequency disclosure for recurring message program | The call-to-action must include the frequency at which messages will be sent to end users (for example, #msgs/mo, msg frequency varies, recurring messages, etc.). Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency |
3006A | Call-to-action does not contain "message and data rates may apply" disclosure | The call-to-action must include the message and data rate disclosure, as mandated by U.S. carriers. Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency |
3007A | Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions | The call-to-action must include a link to the message program terms and conditions, or the complete message program terms and conditions language. Update the call-to-action and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3008A | Call-to-action does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties | Mobile opt in data (for example, the end user's phone number) cannot be shared with third parties. The call-to-action must include a link to the message program privacy policy, or language referring to the privacy policy, that indicates that mobile opt-in data will not be shared. Update the call-to-action and resubmit. | See the CTIA best principles for more information. 5.1 Consumer Consent and 5.2.1 and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3010A | Call-to-action does not contain a robust age gate for age-restricted message program (alcohol/firearms/tobacco) | Message content related to age-restricted goods, such as alcohol or tobacco, is not permitted without an age gate mechanism. An acceptable age gate would consist of, at minimum, a recipient entering a day, month, and year confirming their age at messaging opt-in prior to receiving messaging. If the call-to-action indicates that the message program will be sending this type of content, and no age gate is in place, the campaign will be rejected. Implement age gate and resubmit. | Messaging Principles and Best Practices 5.3.1 Short Code Monitoring Handbook SHAFT guidelines are applied to all US Messaging Programs See 3.5 PROGRAM CONTENT T-Mobile Code of Conduct V2.2 6.6 Controlled Substances and Adult Content Check out |
3011A | Call-to-action is missing/inaccessible | There is no call-to-action URL provided in the campaign description, or the URL provided is inaccessible. You must provide evidence of a compliant opt-in process via either a live opt-in URL or a URL to a hosted opt-in image (screenshot or mock-up). Update the call-to-action description to include the call-to-action URL and resubmit. | See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent |
3012A | Call-to-action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear. | All CTA's must obtain consent via the proper consent mechanism for SMS. Update and resubmit. | This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. CTA's for multiple types of communication are not considered clear and concise or an appropriate consent mechanism as the end user cannot select to ONLY receive SMS messages or NOT receive SMS |
Call-to-action (opt-in obtained via in-market on web URL or provided in screenshot/media file)
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
3001B | Call-to-action (on website, or provide via screenshot/media file) does not obtain sufficient consent | All CTA's must obtain consent via proper consent mechanism. Update and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3002B | Call-to-action does not contain registered/DBA brand name | The company/brand name must be included in the CTA and must match the registered Brand or be easily recognizable as the same entity. Update the call-to-action and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3003B | Call-to-action does not contain HELP instructions (for example, Reply HELP for help) or HELP instructions in Terms & Conditions | The call-to-action must 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. Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action customer care contact information |
3004B | Call-to-action does not contain STOP instructions (for example, Reply STOP to cancel) | The call-to-action must include instructions on how the end user can opt-out of the message program (for example, Reply STOP to opt-out). Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action how to opt out |
3005B | Call-to-action does not contain message frequency disclosure for recurring message program | The call-to-action must include the frequency at which messages will be sent to end users (for example, #msgs/mo, msg frequency varies, recurring messages, etc.). Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 3.6 Set Expectations on Frequency |
3006B | Call-to-action does not contain "message and data rates may apply" disclosure | The call-to-action must include the message and data rate disclosure, as mandated by U.S. carriers. Update the call-to-action and resubmit. | Short Code Monitor Handbook CTA guidelines are followed for all US Messaging programs for call-to-action requirements. See Short Code Monitoring Program Handbook Version 1.9 T-Mobile Code of Conduct V2.2 Section 2.5 Calls-to-Action; associated fees |
3007B | Call-to-action does not contain complete terms and conditions OR link to complete terms and conditions | The call-to-action must include a link to the message program terms and conditions, or the complete message program terms and conditions language. Update the call-to-action and resubmit. | See the CTIA Messaging Principles and Best Practices for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3008B | Call-to-action does not contain link to privacy policy OR state that mobile opt-in data will not be shared with third parties | Mobile opt in data (that is, the end user's phone number) cannot be shared with third parties. The call-to-action must include a link to the message program privacy policy, or language referring to the privacy policy, that indicates that mobile opt-in data will not be shared. Update the call-to-action and resubmit. | See the CTIA best principles for more information. 5.1 Consumer Consent and 5.2.1 and T-Mobile Code of Conduct V2.2 Section 2.4 Choice and Consent |
3010B | Call-to-action does not contain robust age gate for age-restricted message program (alcohol/firearms/tobacco) | Message content related to age-restricted goods, such as alcohol or tobacco, is not permitted without an age gate mechanism. An acceptable age gate would consist of, at minimum, a recipient entering a day, month, and year confirming their age at messaging opt-in prior to receiving messaging. If the call-to-action indicates that the message program will be sending this type of content, and no age gate is in place, the campaign will be rejected. Implement age gate and resubmit. | Messaging Principles and Best Practices 5.3.1 Short Code Monitoring Handbook SHAFT guidelines are applied to all US Messaging Programs See 3.5 PROGRAM CONTENT T-Mobile Code of Conduct V2.2 6.6 Controlled Substances and Adult Content Check out |
3011B | Call-to-action is missing/inaccessible | There is no call-to-action URL provided in the campaign description, or the URL provided is inaccessible. You must provide evidence of a compliant opt-in process via either a live opt-in URL, or a URL to a hosted opt-in image (screenshot or mock-up). Update the call-to-action description to include the call-to-action URL and resubmit. | See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent |
3012B | Call-to-action appears to have multiple types of opt ins in a single CTA which does not make SMS consent optional or clear. | All CTA's must obtain consent via the proper consent mechanism for SMS. Update and resubmit. | This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. CTA's for multiple types of communication are not considered clear and concise or an appropriate consent mechanism as the end user cannot select to ONLY receive SMS messages or NOT receive SMS messages but receive other types of messages. See the CTIA best principles for more information. 5.1 Consumer Consent and T-Mobile Code of Conduct V2.2 Section 2.5 Choice and Consent |
Message flow, campaign and content attributes, and sample messages rejections
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
6001 | Opt-in message/Confirmation MT does not contain registered/DBA brand name | The company name in the opt-in message must match the registered brand name. Update the opt-in message and resubmit. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages |
6002 | Opt-in message/Confirmation MT does not contain HELP instructions (for example, Reply HELP for help) | The Opt-in message/Outbound (MT) Confirmation response to the consumer must include instructions on how the end user can receive further support from the brand regarding the message program (for example, reply HELP for help). Update the opt-in message and resubmit. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages. |
6003 | Opt-in message/Confirmation MT does not contain opt-out instructions (for example, Reply STOP to stop) | The Opt-in message/Outbound (MT) Confirmation response to the consumer must include instructions on how the end user can opt-out of the message program (for example, Reply STOP to opt-out). Update the opt-in message and resubmit. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages. |
6004 | Opt-in message/Confirmation MT does not contain message frequency disclosure (#msgs/mo, msg frequency varies, recurring messages, and so on.) | The Opt-in message/Outbound (MT) Confirmation response to the consumer must include the frequency at which messages will be sent to end users (for example, msg frequency varies, recurring messages, and so on.). Update the opt-in message and resubmit. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages. |
6005 | Opt-in message/Confirmation MT does not contain clear and conspicuous language about any associated fees or charges and how those charges will be billed. (for example, "message and data rates may apply" disclosure) | The Opt-in message/Outbound (MT) Confirmation response to the consumer must include clear and conspicuous language about any associated fees or charges and how those charges will be billed. Add "message and data rate disclosure" in the opt in/confirmation response and resubmit. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages. |
6006 | Opt-in message/confirmation MT not provided | An Opt-in message/Outbound (MT) Confirmation response to the consumer is required for all recurring programs. Update the campaign to include the required message with all required elements as outlined in CTIA best practices. | CTIA Messaging Principles and Best Practices section 2.1.2.1 Confirm Opt-in for Recurring messages. |
6007 | HELP message does not contain registered/DBA brand name | The company name in the HELP message must match the registered brand name. Update the HELP message and resubmit | CTIA Short code Monitoring Handbook for HELP keyword response requirements. HELP Mobile Terminated Program (brand) name OR product description. Additional customer care contact information (for example, a toll-free number, 10-digit telephone number) T-Mobile Code of Conduct V2.2 section 3.7 Business Recognition |
6008 | HELP message does not contain support contact (email, phone number, or support website) | The HELP message must include customer care contact info (such as an email address, phone number, or link to a support website) informing the end user how they can receive further support. Update the HELP message and resubmit. | CTIA Short Code Monitoring Handbook for HELP keyword response requirements. HELP Mobile Terminated. Program (brand) name OR product description. Additional customer care contact information (for example, a toll-free number, or a 10-digit telephone number). |
6009 | HELP message support contact email address does not match the registered brand support email address | If an email address is provided in the HELP message as the customer care contact info, it should match the email address that was registered as the support contact email shown in TCR. Update the HELP message and resubmit. | This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. More information about customer care and HELP can be reviewed in various sections of many Industry Guidelines. |
6010 | Opt-out message does not contain registered/DBA brand name | The company name in the Opt Out message must match the registered brand name. Update the STOP response and resubmit. | CTIA Short Code Monitoring Handbook for STOP keyword response requirements. Opt-Out Mobile Terminated. Program (brand) name OR product description. Confirmation that no further messages will be delivered. See also CTIA Messaging Principles and Best Practices 5.1.3 Consumer Opt-Out. |
6011 | Opt-out message does not indicate that no further messages will be sent | The opt-out message must clearly indicate that the end user will no longer receive further messages from the brand/message program. Update the opt-out message and resubmit. | CTIA Messaging Principles and Best Practices 5.1.3 Consumer Opt-Out |
6012 | Sample message(s) do not contain registered/DBA brand name | The company name in the sample messages must match the registered brand name. Update the sample messages and resubmit. | This requirement is based on precedence (previously reviewed, approved, and rejected programs) and inference. Ensuring the brand name in all messages will also help reduce SPAM complaints and is in line with the T-Mobile Code of Conduct section 3.7 Business Recognition. |
6013 | Sample message(s) contain public URL shortener | Public URL shorteners such as bit.ly or tinyURL are not permitted to be sent in 10DLC message content. Update sample messages to use a branded URL shortener and resubmit. | See T-Mobile Code of Conduct V2.2 4.7 URL Cycling / Public URL Shorteners or AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messaging Techniques |
6014 | Sample message(s) use case does not match declared use case(s) | The use case indicated in the sample messages must match the registered use case. Update the sample messages or register the campaign again with the correct use case and resubmit. | Inference that sample messages should be in line with the remainder of the program to be clear and concise |
Disallowed content
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
7001 | This brand or program references third-party job boards | Messaging content related to third-party job boards is not permitted. This is considered disallowed content. | See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns |
7002 | This brand or program appears to be lead generation or affiliate marketing. | The brand website or messaging content examples appear to be lead generation or affiliate marketing. These are disallowed content types. | See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns. TCR Submission dictates you must attest that Affiliate Marketing will not be a part of this campaign. |
7003 | This brand or program appears to include disallowed content -gambling. | Message content related to gambling is not permitted. If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected. | See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns |
7004 | This brand or program appears to include disallowed content - high risk financial services | Message content related to high-risk financial services, such as short-term loans or cryptocurrency, is not permitted. If the brand's website indicates that their message program will be sending this type of content, the campaign will be rejected. | See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns |
7005 | This brand or program appears to include disallowed content - illegal substances | Message content related to federally illegal drugs, such as cannabis, is not permitted. If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected. | CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns |
7006 | This brand or program appears to include disallowed content - SHAFT (sex) with no robust age gate | Message content related to age-restricted products or content, such as sexually explicit items or images, is not permitted without a roust age gate. Implement age gate and a resubmit. | CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content |
7007 | This brand or program appears to include disallowed content - SHAFT (alcohol/firearms/tobacco/vape) with no robust age gate | Message content related to age-restricted products, such as alcohol or tobacco, is not permitted without a robust age gate. Implement age gate and a resubmit. | CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content |
7008 | This brand or program appears to include disallowed content -competitive marketing. | Message content that promotes or markets services that are competitive in nature to the US operators will be rejected. | Competitive Marketing programs (programs that promote or market services that would be deemed as competitive in nature by the US Operators, that is, wireless service) are not permitted. This requirement is based on precedence (previously submitted and rejected programs). |
7009 | This brand or program appears to include disallowed content - weapons that are not legal in all 50 states. | Message content related to certain weapons which are not legal in all 50 states is not permitted. If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected. | CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content 5.2 Disallowed Content |
7010 | This brand or program appears to include disallowed content - 3rd party debt collection | Third-party debt collection messages are not permitted. This includes messaging related to debt forgiveness, debt consolidation, debt reduction, or credit repair programs. Messaging related to debt forgiveness, debt consolidation, debt reduction, or credit repair programs is not permitted the campaign will be rejected. | T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns |
7011 | This brand or program appears to include disallowed content - firearms that are not legal in all 50 states. | Message content related to firearms which are not legal in all 50 states is not permitted. If the brand's website indicates that its message program will be sending this type of content, the campaign will be rejected. | CTIA Messaging Principles and Best Practices 5.3.1 Prevention of Unlawful Activities T-Mobile Code of Conduct V2.6.6 Controlled Substances and Adult Content 5.2 Disallowed Content |
7012 | This brand or program appears to include disallowed content – HATE speech | Messaging content related to HATE SPEECH is not permitted. This is considered disallowed content. | See T-Mobile Code of Conduct V2.2 5.2 Disallowed Content AT&T Code of Conduct for AT&T Short Code and 10-Digit A2P SMS Messages Prohibited Messages and Messaging Campaigns. |
3000 | Website provided for CTA is inaccessible/does not exist/error status. | The CTA website must be able to be accessed for appropriate review. | |
1003 | Brand website is inaccessible/does not exist/error status. | The brand website must be able to be accessed for appropriate review. | |
1004 | Website is not able to be translated to English | The website must be able to be accessed for appropriate review |
Use case missing or mismatched
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
8001 | Brand website or campaign references charitable donations and the declared use case is not charity | If the brand's website or campaign information indicates that they are soliciting charitable donations through their message program, then the campaign use case should be Charity. Register the campaign again with the correct use case and resubmit. | Campaigns require a complete, clear, and concise campaign submission for proper review per TCR and US operators. See the CTIA Messaging Principles and Best Practices and Review Operator Codes of Conduct. |
8002 | Brand website or campaign references political content and declared use case is not political | If the brand's website or campaign information indicates that they are sending political content through their message program, then the campaign use case should be Political. Register the campaign again with the correct use case and resubmit. | |
8003 | Brand website or campaign references cart reminders but declared use case is not marketing. | If the brand's website or campaign information indicates that they are sending abandoned shopping cart notifications through their message program, then the campaign use case should be marketing. Register the campaign again with the correct use case and resubmit. | |
8004 | Brand website or campaign references multiple use cases but only one declared use case is selected | If the program will support multiple use cases all use cases must be declared. Register the campaign again with the correct use cases and resubmit. |
Use case submission does not meet the requirements
Error code | Rejection reason | Recommended action | Reference or documentation to support the requirement |
9001 | Campaign submitted is POLITICAL but does not contain the required information for this use case | Political message programs must include:
These should be included in the program summary so we can confirm this information during the review | T-Mobile Code of Conduct V2. 6.1 Political Messaging |
9002 | Campaign submitted is CHARITY but does not contain the required information for this use case | CHARITY programs must provide the following information in the Campaign Description/Program Summary for appropriate review. Provide the following Charitable Organization information for proof of qualified as tax-exempt under Section 501(c)(3) of the Internal Revenue Code:
| T-Mobile Code of Conduct V2 6.7 Charitable Donation |