Receiving tcr rejection codes without a clear framework for interpreting them is a predictable bottleneck in the 10DLC registration process. The Campaign Registry issues rejection codes across multiple vetting layers, each carrying different implications for resubmission eligibility, remediation effort, and timeline. Not all TCR rejection codes are equal — and treating terminal codes the same way as fixable ones costs real money in re-vetting fees.
This guide organizes the major TCR rejection codes by vetting layer and category, classifies each as fixable or terminal, and gives the specific remediation action required before resubmission.
How TCR Rejection Codes Are Structured
TCR rejection codes originate from three distinct vetting layers. Understanding which layer issued a code determines where the fix must happen.
Brand vetting is performed by The Campaign Registry itself when a brand record is submitted. This layer validates business identity: EIN accuracy, legal business name, website presence, and brand-to-sender alignment. Brand-level TCR rejection codes must be resolved before any campaign can proceed — a rejected brand blocks all downstream campaign submissions.
Campaign vetting is conducted by carrier aggregators after brand registration succeeds. AT&T, T-Mobile, Verizon, and their designated vetting partners evaluate campaign descriptions, sample messages, opt-in disclosures, content type classifications, and use-case accuracy. Campaign-level TCR rejection codes span multiple numeric ranges: 600-series for attribute mismatches, 700-series for prohibited content, 9000-series for URL and documentation failures, and 30000-series for carrier vetting outcomes.
CSP-level validation is applied by some connectivity service providers before a submission reaches TCR at all. This layer catches formatting errors and missing required fields early, before vetting fees are charged.
Brand-Level Rejection Codes
The 1000-series codes address failures in brand identity and are issued before campaign vetting begins.
Code 1100 — No Online Presence Found. TCR could not verify a live website associated with the registered business entity. This is one of the most common brand-level TCR rejection codes. Resolution requires publishing a live, accessible business website at the URL entered in the brand record. The site must include a privacy policy, contact information, and content consistent with the brand name and EIN. Once the site is live, resubmit the brand record.
Code 1101 — Brand Inconsistency. The business name, EIN, and website do not align with one another. This rejection frequently appears when a parent company registers while the actual message sender is a subsidiary, franchise location, or affiliated entity operating under a different name. Correct by registering the entity whose legal name, tax ID, and website content match what subscribers will see in message traffic.
Campaign Attribute Mismatch Codes
The 600-series TCR rejection codes indicate that submitted campaign attributes do not match the content, website, or use-case classification. These are among the most resubmittable rejection codes because the underlying business is typically eligible — the error is in how the campaign was classified and described.
Code 601 — Campaign Attributes Do Not Match Content. The use-case category, content type attributes, or subscriber opt-in method selected does not align with what the sample messages and website demonstrate. Audit every selected attribute against the actual message flow and resubmit with accurate classifications.
Code 602 — Use Case / Sample Message Inconsistency. The use-case category chosen does not reflect what the sample messages actually contain. If samples describe appointment reminders but the campaign is registered under a Marketing use case, the vetting system flags the mismatch. Align the use-case with the actual message type, rewrite samples to clearly represent that use case, and resubmit.
Code 603 — Three-Way Inconsistency: Website, Brand, and Sample Messages. Website content, brand name, and submitted samples do not present a coherent identity. This frequently occurs when resellers submit campaigns on behalf of end-customer businesses without updating brand and content fields to reflect the actual sender. All three elements must be consistent before resubmission.
Prohibited Content Codes
The 700-series TCR rejection codes are the most consequential because many are terminal. The underlying content or business type is categorically ineligible for 10DLC — resubmission after correction is not possible because no correction can change the category.
Code 701 — Cannabis / Hemp / CBD. Cannabis, hemp, and CBD content is not permitted over 10DLC regardless of state-level legality. This is a terminal rejection code. Campaigns for cannabis-related brands cannot be resubmitted through standard 10DLC channels.
Code 702 — Firearms / Ammunition Without Age Gating. Firearm-related campaigns require compliant age-gating on the opt-in landing page. This code is fixable: document and implement the required age verification mechanism, then resubmit with the age-gate URL and implementation details included.
Code 703 — Explicit Sexual Content. Prohibited on 10DLC. Terminal rejection — not resubmittable.
Code 708 and 709 — Lead Generation / High-Risk Financial Services. Lead generation campaigns that sell or transfer consumer data to third-party buyers are not permitted. High-risk financial categories — payday loans, credit repair, debt consolidation — are similarly blocked. These are terminal codes. If the business model involves consumer data resale or falls under a prohibited financial category, 10DLC is not a viable channel.
Code 710 — Wrong Brand Entity / KYC Failure. The registered brand is not the entity actually sending messages. This is a fixable code triggered when an agency or platform registers under its own name while sending on behalf of client businesses. Each business sending its own messages must register its own brand. Resolution: register the correct legal entity as the brand and resubmit all associated campaigns.
URL and Documentation Codes
The 9000-series TCR rejection codes address failures in URL submission and supporting documentation.
Code 9401 — Public URL Shortener Detected. Sample messages contain a shortened URL from a public service such as bit.ly or tinyurl. Public URL shorteners are prohibited because they obscure the destination domain and are strongly associated with spam traffic. Replace with the full destination URL or a branded short domain tracked through compliant analytics.
Code 9402 — URL Referenced But Not Included. A sample message references a link without including the actual URL in the submission. Every URL referenced in sample messages must appear in full.
Code 7100 / 7101 — Privacy Policy URL Missing or Non-Functional. The privacy policy URL submitted either does not exist or returns an error when loaded. A live, accessible privacy policy URL is required for all 10DLC campaigns. Publish or fix the URL, verify it loads without redirects or errors, and resubmit.
Carrier Vetting Outcome Codes
The 30000-series TCR rejection codes reflect decisions from carrier-level vetting rather than submission formatting failures. These codes are issued after the brand record is accepted and campaign content reaches the carrier vetting layer.
Code 30882 — Terms and Conditions Rejection. The opt-in flow does not adequately present program terms to subscribers. Compliant opt-in disclosure must include: program name, message frequency, standard data rates language, STOP and HELP instructions, and a link to the privacy policy. Update the opt-in page to include all required elements, document the updated page URL, and resubmit.
Code 30886 — Invalid Campaign Description. The campaign description submitted to TCR is insufficient for vetting review. An approvable description must explain who is sending, what the messages will contain, how subscribers opted in, and what opt-out mechanisms are available. Rewrite to address all four elements explicitly and resubmit.
Code 30887 — Opt-Out Workflow Error. The opt-out flow does not comply with CTIA requirements for honoring STOP commands. Carriers require that a STOP reply triggers a compliant confirmation message and that the subscriber is immediately removed from the active list. Document the full STOP/HELP workflow in the campaign submission and verify the platform behavior matches what is submitted.
Code 30909 — Call to Action Verification Failure. The opt-in mechanism described in the campaign cannot be verified against the submitted website URL or supporting documentation. The opt-in must be directly observable on the website URL provided and must match the mechanism described in the campaign record. Align the submission description with what is actually live on the opt-in page before resubmitting.
The Fixable vs. Terminal Framework
The most important classification when working through TCR rejection codes is whether resubmission is viable. Submitting a corrected campaign against a terminal rejection wastes vetting fees and can generate additional review flags.
Terminal codes — 701 (cannabis), 703 (explicit content), 708–709 (lead gen and prohibited financial) — reflect business types or content categories that are categorically ineligible. No correction to the submission changes eligibility. If the campaign falls into one of these categories, alternative messaging channel strategies must be evaluated.
Fixable codes include 601–603 (attribute mismatches), 710 (wrong brand entity), 7100–7101 (privacy policy), 9401–9402 (URL errors), 30882 (terms and conditions), 30886 (campaign description), 30887 (opt-out workflow), and 30909 (opt-in verification). Each of these can be corrected by addressing the documented failure and resubmitting.
Before resubmitting any campaign, verify five checkpoints against the original submission: brand-to-sender alignment, live privacy policy linked from the opt-in page, sample messages that match the selected use-case, no public URL shorteners in any sample, and an opt-in page that matches what is described in the campaign record.
The TCR Error Codes & Rejections Hub provides the full reference index of rejection codes organized by range. The TCR Rejection Code Analysis breaks down which codes appear most frequently by industry vertical and identifies the submission patterns that most reliably trigger each category.
Building a Pre-Submission Workflow That Avoids Rejection
Most TCR rejection codes are preventable. The majority of 600-series and 30000-series rejections occur when campaigns are submitted before verifying that brand identity, website content, opt-in disclosures, sample messages, and use-case classifications are internally consistent.
A structured pre-submission review addresses five checkpoints in sequence: (1) brand entity matches the actual sender, (2) website is live with an accessible privacy policy, (3) opt-in mechanism is documented and visible on the submitted URL, (4) sample messages match the selected use-case and contain no public URL shorteners, and (5) campaign description explicitly covers sender identity, message content, opt-in method, and opt-out mechanism. The Provider-Specific 10DLC Registration Checklists translates these checkpoints into CSP-specific format requirements for major connectivity service providers.
For a deeper look at which TCR rejection codes produce the highest resubmission failure rates and why, the Campaign Rejection Analysis documents real-world patterns across campaign types and identifies the preparation gaps that produce the most expensive repeat rejections.
When a TCR rejection code lands on your submission, the fastest path to approval is a structured diagnostic that maps your specific code to exact documentation requirements — not a generic resubmission attempt. The Rejection Remediation Tool runs a pre-flight diagnostic against your submitted campaign data, identifies the documentation failures behind your TCR rejection codes, and generates a remediation checklist tied to your use case and provider.
