Campaign rejection error codes reference
Complete technical reference for campaign rejection error codes, rejection reasons, and recommended remediation steps. Use this guide to understand why your campaign was rejected and how to fix it.
How to use this reference
When your campaign is rejected, you will receive:
- Error code (for example, 1003, 3001A, 7002)
- Rejection reason: Why the campaign failed
- Recommended action: How to fix it
Look up your error code in this reference to find:
- What caused it: The specific requirement that was not met
- How to fix it: Step-by-step remediation
- Reference material: Compliance docs and industry guidelines
Campaign configuration errors (1000-level)
Configuration and brand-related rejection errors occur when campaign attributes or brand details do not meet verification requirements.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 1001 | Campaign contains adult content but age gate attribute is not selected | Verify Age Gate attribute is selected for the campaign. If campaign is not age-gated, update campaign description to remove age-restricted references | USA messaging content requirements |
| 1002 | Campaign is for direct lending but missing direct lending content attribute | Verify direct lending/loan arrangement is selected. If campaign is not lending-related, update campaign description | TCR submission requirements |
| 1003 | Brand website is inaccessible, does not exist, or returns error status | Ensure brand website is live and accessible. Fix DNS issues, SSL errors, or 404/503 responses. Test by visiting the URL directly | Understanding brands |
| 1004 | Brand website lacks sufficient information about company and products | Add company description, product/service details, contact info, and business purpose to website. Ensure website fully reflects what company does | Understanding brands |
| 1005 | Service provider registered instead of final brand | Register the brand that will send messages to customers, not the service provider. The sender name must match the registered brand | Understanding brands |
Campaign description/program summary errors (2000-level)
Campaign description errors occur when the program summary is unclear, missing, or inconsistent.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 2001 | Campaign registration is not unique or is duplicate | Duplicate campaigns are not allowed. Create a new campaign with unique name/description or use existing campaign | TCR submission requirements |
| 2002 | Unclear campaign description | Provide clear, detailed description of your messaging program purpose. Include: what you are sending, why, frequency, target audience | Understanding campaigns |
| 2003 | Campaign description does not match declared use case(s) | Ensure description matches selected use case. If sending marketing, select Marketing use case. If transactional, select Transactional, or select whichever use case applies. | Understanding campaigns |
| 2004 | Campaign description does not match sample messages | Sample messages must demonstrate the use case described. If description says "transactional," sample messages must be transactional, not marketing | USA messaging content requirements |
| 2005 | Undeclared use case | Campaign description indicates a use case not selected. Select all use cases your campaign will support | Understanding campaigns |
| 2006 | Brand referenced in campaign description does not match registered/DBA brand | Ensure brand name in campaign matches registered brand name or DBA exactly. Update campaign or brand details | Understanding brands |
Call-to-action errors - US Sender Registration web interface (3000A-level)
CTA errors occur when the opt-in flow in the US Sender Registration web interface does not meet compliance requirements.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 3000 | CTA website is inaccessible, does not exist, or returns error status | Ensure CTA URL is live and accessible. Fix DNS, SSL, or HTTP errors. Verify URL by visiting directly | USA messaging content requirements |
| 3001A | CTA does not obtain sufficient consent | Implement proper consent mechanism. Require explicit affirmative action (checkbox, button click, keyword reply). Implied consent only for conversational programs | CTIA Messaging Principles and Best Practices 5.1; T-Mobile Code of Conduct V2.2 Section 2.4 |
| 3002A | CTA does not contain registered/DBA brand name | Include brand name in CTA. Name must match registered brand or be easily recognizable as same entity | CTIA Messaging Principles and Best Practices 5.1 |
| 3003A | CTA and Terms & Conditions do not contain HELP instructions | Add "Reply HELP for help" or similar to CTA, or include in T&Cs. Provide customer care contact (phone, email, website) | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3004A | CTA does not contain STOP instructions | Add "Reply STOP to opt out" or similar opt-out instructions to CTA | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3005A | CTA does not contain message frequency disclosure for recurring programs | Add frequency disclosure: "X msgs/mo" or "msg frequency varies" or "recurring messages" | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 3.6 |
| 3006A | CTA does not contain "message and data rates may apply" disclosure | Add carrier-mandated disclosure: "Message and data rates may apply" | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3007A | CTA does not contain complete T&Cs or link to T&Cs | Include full T&Cs in CTA or provide live link to T&Cs page that is accessible and complete | CTIA Messaging Principles and Best Practices 5.1 |
| 3008A | CTA does not contain privacy policy link or statement about data sharing | Add privacy policy link or statement: "Mobile opt-in data will not be shared with third parties" | CTIA Messaging Principles and Best Practices 5.1, 5.2.1 |
| 3009A | Privacy policy mentions data sharing/selling but excludes mobile opt-in data | Add explicit statement to privacy policy: "All above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties" | CTIA best practices |
| 3010A | CTA lacks robust age gate for age-restricted content (alcohol/firearms/tobacco) | Implement age gate requiring recipient to enter birth date (day/month/year) before opt-in. Minimum requirement: date-based age verification | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.2 Section 6.6 |
| 3011A | CTA is missing/inaccessible | Provide live CTA URL or upload screenshot/image of CTA showing compliant opt-in process | CTIA Messaging Principles and Best Practices 5.1 |
| 3012A | CTA has multiple opt-in types which does not make SMS consent optional or clear | Use single consent mechanism for SMS only. Do not combine SMS consent with email/phone opt-ins. Users must be able to consent to SMS separately | CTIA Messaging Principles and Best Practices 5.1 |
| 3013A | CTA uses implied consent but use case or message flow are not conversational | Only use implied consent for conversational messaging (customer support, two-way interaction). Use explicit consent for broadcast/marketing | Based on program precedence |
| 3014A | Campaign submitted as marketing but marketing disclosure is missing | Add marketing disclosure to CTA so users know they will receive promotional messages. Require express written consent | CTIA Messaging Principles and Best Practices 3.3.3 |
| 3015A | Campaign appears to solicit donations but donation disclaimer is missing | Add charitable solicitation disclaimer. Provide separate opt-ins for informational and solicitation messages | T-Mobile Code of Conduct V2 Section 6.7 |
| 3016A | Campaign uses verbal consent for marketing but requires express written consent | Replace verbal script with written consent form or add double opt-in confirmation. Marketing requires written + confirmation | CTIA Messaging Principles and Best Practices |
Call-to-action errors - in-market web/screenshot (3000B-level)
CTA errors for in-market websites or screenshot-based CTAs. For complete CTA requirements and guidelines, see USA messaging content requirements.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 3001B | CTA (on website or screenshot) does not obtain sufficient consent | Implement proper consent mechanism. Require explicit affirmative action (checkbox, button click, form submission). Implied consent only for conversational | CTIA Messaging Principles and Best Practices 5.1 |
| 3002B | CTA does not contain registered/DBA brand name | Include brand name in CTA. Name must match registered brand or be easily recognizable as same entity | CTIA Messaging Principles and Best Practices 5.1 |
| 3003B | CTA and T&Cs do not contain HELP instructions | Add "Reply HELP for help" to CTA or T&Cs. Provide customer care contact (phone, email, website) | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3004B | CTA does not contain STOP instructions | Add "Reply STOP to opt out" or similar opt-out instructions to CTA | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3005B | CTA does not contain message frequency disclosure for recurring programs | Add frequency disclosure: "X msgs/mo" or "msg frequency varies" or "recurring messages" | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 3.6 |
| 3006B | CTA does not contain "message and data rates may apply" disclosure | Add disclosure: "Message and data rates may apply" | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 2.5 |
| 3007B | CTA does not contain complete T&Cs or link to T&Cs | Include full T&Cs in CTA or provide live link to T&Cs page that is accessible and complete | CTIA Messaging Principles and Best Practices 5.1 |
| 3008B | CTA does not contain privacy policy link or data sharing statement | Add privacy policy link or statement: "Mobile opt-in data will not be shared with third parties" | CTIA Messaging Principles and Best Practices 5.1, 5.2.1 |
| 3009B | Privacy policy mentions data sharing/selling but excludes mobile opt-in data | Add explicit statement: "All above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties" | CTIA best practices |
| 3010B | CTA lacks robust age gate for age-restricted content (alcohol/tobacco) | Implement age gate requiring birth date (day/month/year) entry before opt-in | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.2 Section 6.6 |
| 3011B | CTA is missing/inaccessible | Provide live CTA URL or upload screenshot/image showing compliant opt-in process | CTIA Messaging Principles and Best Practices 5.1 |
| 3012B | CTA has multiple opt-in types which does not make SMS consent optional or clear | Use single consent mechanism for SMS only. Do not combine SMS with email/phone opt-ins | CTIA Messaging Principles and Best Practices 5.1 |
| 3014B | Campaign submitted as marketing but marketing disclosure is missing | Add marketing disclosure so users know they will receive promotional messages. Require express written consent | CTIA Messaging Principles and Best Practices 3.3.3 |
| 3015B | Campaign appears to solicit donations but donation disclaimer is missing | Add charitable solicitation disclaimer. Provide separate opt-ins for informational and solicitation messages | T-Mobile Code of Conduct V2 Section 6.7 |
Message flow errors (6000-level)
Message flow errors occur when confirmation, HELP, STOP, or sample messages do not meet compliance requirements.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 6001 | Opt-in/Confirmation MT does not contain registered/DBA brand name | Include brand name in confirmation message. Name must match registered brand exactly | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6002 | Opt-in/Confirmation MT does not contain HELP instructions | Add "Reply HELP for help" or similar in confirmation message | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6003 | Opt-in/Confirmation MT does not contain opt-out instruction | Add "Reply STOP to opt out" or similar in confirmation message | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6004 | Opt-in/Confirmation MT does not contain message frequency disclosure | Add frequency: "You will receive X msgs/mo" or "Message frequency varies" in confirmation | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6005 | Opt-in/Confirmation MT does not contain "message and data rates may apply" disclosure | Add "Message and data rates may apply" in confirmation message | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6006 | Opt-in/Confirmation MT not provided | Provide confirmation message for all recurring programs. Must include brand name, HELP, STOP, frequency, rates disclosure | CTIA Messaging Principles and Best Practices Section 2.1.2.1 |
| 6007 | HELP message does not contain registered/DBA brand name | Include brand name in HELP response. Name must match registered brand exactly | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 3.7 |
| 6008 | HELP message does not contain support contact | Add customer care contact to HELP response: email, phone, or website URL for support | Short Code Monitoring Handbook |
| 6009 | HELP message support contact email does not match registered support email | Ensure email in HELP message matches registered brand support email in TCR | Based on program precedence |
| 6010 | Opt-out/STOP message does not contain registered/DBA brand name | Include brand name in STOP response. Name must match registered brand exactly | Short Code Monitoring Handbook; T-Mobile Code of Conduct V2.2 Section 3.7 |
| 6011 | Opt-out/STOP message does not indicate no further messages will be sent | Add confirmation statement to STOP message: "You will not receive further messages from [Brand]" | CTIA Messaging Principles and Best Practices 5.1.3 |
| 6012 | Sample messages do not contain registered/DBA brand name | Include brand name in all sample messages. Name must match registered brand | Based on program precedence; T-Mobile Code of Conduct Section 3.7 |
| 6013 | Sample messages contain public URL shorteners (such as bit.ly or tinyURL) | Replace public shorteners with branded URL shorteners | T-Mobile Code of Conduct V2.2 Section 4.7; AT&T Code of Conduct |
| 6014 | Sample messages use case does not match declared use case(s) | Ensure sample messages demonstrate the declared use case. If declared Marketing, samples must be marketing messages | Inference from campaign submission requirements |
Disallowed content errors (7000-level)
Disallowed content errors occur when message content or brand activities violate carrier policies.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 7001 | Brand or program references third-party job boards | Remove references to third-party job boards. Job boards are disallowed content | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
| 7002 | Brand or program includes lead generation or affiliate marketing | Remove lead generation or affiliate marketing from program. These are disallowed content types | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
| 7003 | Brand or program includes gambling | Remove gambling content. Gambling messaging is not permitted | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
| 7004 | Brand or program includes high-risk financial services (short-term loans, crypto) | Remove high-risk financial services. Short-term loans, payday loans, cryptocurrency are disallowed | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
| 7005 | Brand or program includes illegal substances (cannabis, federally illegal drugs) | Remove references to illegal substances. Federally illegal drug content is not permitted | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.2 Section 5.2 |
| 7006 | Brand or program includes disallowed sexual content (age-restricted products) | Implement robust age gate (birth date verification) or remove adult/sexual content | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.6.6 |
| 7007 | Brand or program includes direct promotion of SHAFT (alcohol/tobacco/firearms) | Implement robust age gate (birth date verification) or remove age-restricted content. SHAFT = Smoking, Alcohol, Firearms, Tobacco | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.6.6 |
| 7008 | Brand or program includes competitive marketing (wireless services) | Remove competitive messaging. Programs promoting wireless/telecom services competitive to operators are not permitted | Based on program precedence |
| 7009 | Brand or program includes weapons not legal in all 50 states | Remove references to state-restricted weapons. Only weapons legal in all 50 states may be referenced | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.6.6 |
| 7010 | Brand or program includes third-party debt collection | Remove debt collection messaging (debt forgiveness, consolidation, reduction, credit repair). Third-party debt collection is not permitted | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
| 7011 | Brand or program includes marketing of CBD-related products | Remove CBD product marketing. CBD product content is not permitted | CTIA Messaging Principles and Best Practices 5.3.1; T-Mobile Code of Conduct V2.6.6 |
| 7012 | Brand or program includes hate speech | Remove hate speech content. Hate speech messaging is disallowed | T-Mobile Code of Conduct V2.2 Section 5.2; AT&T Code of Conduct |
Use case missing or mismatched errors (8000-level)
Use case errors occur when declared use case does not match campaign description, website, or message content.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 8001 | Brand website or campaign references charitable donations but use case is not Charity | If soliciting donations, select Charity use case. Reregister with correct use case | Campaign submission requirements |
| 8002 | Brand website or campaign references political content but use case is not Political | If sending political messaging, select Political use case. Reregister with correct use case. See Political campaigns guide | Campaign submission requirements |
| 8003 | Brand website or campaign references cart reminders but use case is not Marketing | If sending abandoned cart notifications, select Marketing use case. Reregister with correct use case | Campaign submission requirements |
| 8004 | Brand website or campaign references multiple use cases but only one is declared | If supporting multiple use cases, select all applicable use cases. Reregister with all use cases | Campaign submission requirements |
Use case submission requirement errors (9000-level)
Use case requirement errors occur when specialized use cases (Political, Charity) lack required information.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 9001 | Political campaign missing required information | Political campaigns must include: Politician/Organization Name, FEC Committee ID, Politician/Organization Website. Include in program summary | Political campaigns guide; T-Mobile Code of Conduct V2 Section 6.1 |
| 9002 | Charity campaign missing required information | Charity campaigns must provide: Organization Name, Tax ID (EIN), Charitable Organization Website, Accreditation Organization Website listing. Include in program summary | T-Mobile Code of Conduct V2 Section 6.7 |
| 9003 | Charity campaign missing donation solicitation disclaimer | Add donation solicitation disclaimer to CTA. Provide separate opt-ins for informational and donation solicitation messages | T-Mobile Code of Conduct V2 Section 6.7 |
Other errors (9999 & general)
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 9999 | Other reasons | Infobip Compliance team will provide custom rejection reason. Check rejection details provided and contact Infobip support with campaign ID | Custom feedback from Compliance team |
Toll-Free Number (TFN) specific errors (10000-level)
TFN-specific rejection errors apply to toll-free campaigns.
| Error code | Rejection reason | Recommended action | Reference |
|---|---|---|---|
| 10000 | Contact name must belong to business representative | Use full first and last name of authorized business representative. Generic names (Admin, Support, Info) not permitted | Understanding toll-free |
| 10100 | Business email must use official domain | Use business domain email when available (name@company.com). Generic services (Gmail, Yahoo, Outlook) acceptable only if business has no domain. Provide explanation in Comments field | Understanding toll-free |
| 10200 | Business address not found | Ensure address is complete, accurate, and publicly traceable. Address must be verifiable through public sources. Check for typos | Understanding toll-free |
| 10300 | More than one number for single business requires justification | If registering multiple numbers for same business, provide business justification in Additional Information field explaining why multiple numbers are needed | Understanding toll-free |
| 10400 | Submission content must be in English | All submission materials (website, CTA, message samples) must be in English for proper review and approval | Understanding toll-free |
| 10500 | Opt-in must be visible and independent | Opt-in cannot be hidden in pop-ups, T&Cs, privacy policies, or unrelated agreements. Must be clearly presented in main page content | Understanding toll-free |
| 10600 | Opt-in checkbox is pre-selected | Pre-selected checkboxes do not constitute valid consent. Users must actively select opt-in. Update opt-in to require affirmative action | Understanding toll-free |
| 10700 | Single opt-in for multiple programs not permitted | If program supports multiple use cases, each must have separate, optional opt-in. Provide distinct opt-ins for each use case | Understanding toll-free |
| 10800 | Separate opt-ins required for each communication channel | SMS opt-in cannot be combined with email, phone, or other channels. Each channel must have distinct CTA and opt-in method | Understanding toll-free |
| 10900 | Program includes non-secured URLs (http://) | Use HTTPS (encrypted) URLs only. http:// URLs expose users to security risks. Update all URLs to use https:// | Understanding toll-free |
| 11000 | Projected message volume exceeds use case limits | Reduce requested volume or justify why volume is appropriate for declared use case and business size | 10DLC throughput and carrier limits |
How to resubmit after rejection
- Read the rejection details: Review all error codes and reasons provided
- Look up each error code in this reference to understand the requirement
- Fix the issues: Update campaign details, CTA, messages, or other materials as needed
- Resubmit the campaign: Create new campaign or appeal if eligible
- Verify fixes before resubmit: Double-check all corrections before resubmission
Common rejection patterns
Multiple CTA errors (3000A/3000B): Your CTA is missing required disclosures
- Add all required elements: brand name, HELP instructions, STOP instructions, frequency, rates disclosure, T&Cs link, privacy policy
Multiple message flow errors (6000-level): Your confirmation/HELP/STOP messages are incomplete
- Ensure all auto-response messages include: brand name, HELP instructions, STOP instructions, contact info
Disallowed content (7000-level): Your campaign promotes prohibited content
- Review entire brand website and message samples for any prohibited references
- Implement age gates for age-restricted content (alcohol, tobacco, firearms, sexual content)
Use case mismatch (2000/8000-level): Your description, website, or messages do not match declared use case
- Ensure campaign description, sample messages, and brand website all align with declared use case
- Declare ALL use cases if program supports multiple types
Learn moreUnderstanding campaigns: Complete campaign setup guide
USA messaging content requirements: Message format and content rules
Understanding 10DLC: 10DLC concepts and carrier requirements
Understanding short code: Short code concepts and requirements
Understanding toll-free: Toll-free concepts and requirements
USA SMS compliance requirements: CTIA standards and carrier compliance
Brand vetting: Brand verification requirements
Political campaigns guide: Political campaign setup
Related pages
Get started with 10DLC
Create and resubmit your 10DLC campaign after fixing rejection issues.
Get started with short codes
Create and resubmit your short code campaign after fixing rejection issues.
Get started with toll-free
Create and resubmit your toll-free campaign after fixing rejection issues.
Infobip support ↗
Contact support with your campaign ID and rejection details for additional assistance.