TCR error codes do not all come from the same place, and that distinction matters when you are trying to fix one. An error code returned during brand registration requires a different response than one issued during campaign vetting, which requires a different response than a message delivery failure code returned by a carrier. Treating them interchangeably — submitting a campaign fix for a brand error, or correcting opt-in documentation for a delivery filtering problem — wastes time and extends the disruption to your messaging program.
This guide maps the complete taxonomy of TCR error codes by origin layer, describes what each category signals, and routes each to the appropriate diagnostic and fix resource.
How TCR Error Codes Are Organized
The TCR system and the carrier ecosystem it connects to produce error codes at five distinct layers. Each layer has its own code ranges, its own issuing authority, and its own resolution path.
Brand vetting errors are issued by The Campaign Registry when a brand record submission fails identity verification. These codes block all downstream campaign work until resolved.
Campaign submission errors are issued by TCR and carrier aggregators when a campaign record is rejected during vetting. These are the codes most people mean when they search for TCR error codes — the numeric rejection codes returned after campaign submission.
Message delivery error codes are issued by carrier networks when a delivered or attempted message is flagged or blocked. These are distinct from submission rejection codes and are often harder to identify because they may not surface in the sending platform’s dashboard.
Carrier vetting outcome codes are issued at the aggregator layer during campaign vetting and represent carrier-specific compliance decisions. These appear in the 30000-series and reflect carrier policy evaluations that differ from TCR’s own submission validation.
API and system error codes are issued by TCR’s API or by the CSP’s platform layer when a programmatic submission contains formatting errors or missing required fields. These are typically developer-facing and do not reflect compliance failures in the underlying content.
Understanding which layer generated an error determines what kind of fix is required and who owns the remediation.
Brand-Level TCR Error Codes
Brand-level TCR error codes are issued before campaign vetting begins and represent failures in business identity verification. They are not submission formatting errors — they reflect a mismatch between the business entity registered and what the vetting system can verify about that entity.
The most common brand-level error codes fall in the 1000-series. Code 1100 indicates that no verifiable online presence was found for the registered business at the submitted website URL. The website must be live, display the registered business name, and contain a privacy policy and contact information. Code 1101 indicates a brand inconsistency — the business name, EIN, and website do not present a unified identity. This frequently occurs when a parent company registers while a subsidiary or franchise location is the actual sender.
Brand errors can also arise from EIN mismatches with IRS records, business name variations between the registration record and the website, or the use of a trade name without the associated legal entity name. The TCR Brand Consistency Checker runs a pre-submission diagnostic on brand record data to identify alignment gaps between business identity fields before a brand record is submitted.
Campaign Submission TCR Error Codes
Campaign submission error codes are returned when a campaign record fails vetting after brand registration succeeds. These are the most extensively documented TCR error codes and span several numeric series.
The 600-series covers attribute and classification mismatches. Code 601 indicates that campaign attributes do not match the website content or sample messages. Code 602 signals a use-case/sample inconsistency — the selected use case does not reflect what the samples actually contain. Code 603 indicates a three-way mismatch between website, brand identity, and message samples. All 600-series codes are fixable by correcting the classification and resubmitting.
The 700-series covers prohibited content. Codes 701 (cannabis), 703 (explicit sexual content), and 708–709 (lead generation and high-risk financial services) are terminal — the content or business type is ineligible for 10DLC regardless of how the submission is revised. Code 702 (firearms without age-gating) and code 710 (wrong brand entity) are fixable with the appropriate documentation correction.
The 7000- and 9000-series cover URL and documentation failures. Codes 7100 and 7101 indicate missing or broken privacy policy URLs. Codes 9401 and 9402 flag public URL shorteners in sample messages or referenced-but-missing URLs. All are fixable by correcting the URL and resubmitting.
The TCR Rejection Code Analysis provides pattern analysis across these submission error codes, identifying which ones appear most frequently by industry vertical and what submission characteristics most reliably trigger each category.
Carrier Vetting Outcome Codes (30000-Series)
The 30000-series TCR error codes originate from carrier vetting rather than TCR’s own submission validation. They represent compliance decisions by the carrier vetting layer and appear after brand registration succeeds and the campaign record reaches aggregator review.
Code 30882 signals that the opt-in terms and conditions presented to subscribers are insufficient. The opt-in page must display all required elements: program name, message types, frequency, data rates language, and STOP/HELP instructions. Code 30886 indicates an insufficient campaign description — the description must address sender identity, message content, opt-in method, and opt-out mechanism explicitly. Code 30887 indicates an opt-out workflow failure — STOP commands must trigger a compliant confirmation message and immediate list removal. Code 30909 means the call-to-action described in the campaign cannot be verified on the submitted website URL.
All 30000-series codes are fixable. They require updating the documented opt-in flow or campaign description and resubmitting. Because these codes come from carrier vetting rather than TCR directly, remediation timelines depend on the carrier aggregator’s review queue.
Message Delivery Error Codes
Message delivery error codes are distinct from campaign submission TCR error codes and represent a category many businesses encounter without recognizing as a compliance issue. These codes are returned by carrier networks when a message that was sent is flagged, filtered, or blocked at the delivery layer — after campaign registration has already been approved.
Common delivery error codes indicate spam filtering triggers (message content matched carrier spam detection patterns), throughput throttling (message volume exceeded the registered campaign’s allowed rate), and number-level filtering (the specific sending number has been flagged for suspicious traffic patterns independent of the campaign registration).
Unlike submission rejection codes, message delivery errors do not have a simple resubmission path. They require diagnosing whether the issue is content-based (message copy triggering filters), volume-based (throughput exceeding registered limits), or identity-based (the sending number itself has a filtering flag). Content-based delivery errors are resolved by revising message copy to eliminate patterns triggering carrier filters. Volume-based errors require operating within registered throughput limits or upgrading to a higher-trust-score registration tier. Identity-based errors may require replacing the sending number.
API and System Error Codes
API error codes are encountered by businesses using programmatic submission through TCR’s API or a CSP’s platform. These codes indicate formatting failures — missing required fields, invalid field values, duplicate submission attempts, or authentication errors — rather than compliance problems with the content being submitted.
Common API error codes include missing brand or campaign identifier fields, invalid use-case enum values, malformed phone number formats, and concurrent submission conflicts. These errors are resolved at the developer level by correcting the API call rather than by changing the underlying compliance documentation.
Using the Right Fix Resource for Each Error Type
The appropriate resolution resource depends entirely on which layer generated the TCR error code. Brand-level errors require brand record correction and resubmission — the TCR Brand Consistency Checker identifies the specific mismatch. Campaign submission errors require documentation correction and resubmission — the TCR Error Codes & Rejections Hub provides the full reference index. Carrier vetting outcome codes require opt-in documentation or campaign description updates.
For specific error codes from any layer, the Fix TCR Error Hub provides a lookup index covering 250+ specific TCR error codes with individual fix pages — each documenting the specific cause, the documentation change required, and the resubmission steps for that code.
For businesses experiencing persistent TCR error codes across multiple submissions — a pattern that suggests a systematic documentation gap rather than an isolated submission error — the Stop TCR Rejections resource addresses the underlying vetting preparation failures that produce repeated rejections.
Building a Pre-Submission Framework That Prevents Error Codes
Most TCR error codes at the brand and campaign submission layers are preventable. The systematic pattern in rejection data is that errors accumulate when businesses submit without verifying brand identity alignment, website compliance, opt-in documentation, sample message accuracy, and use-case classification — all five checkpoints — before submission.
A pre-submission verification workflow that addresses all five checkpoints converts the error code encounter from a common event into an exception. The brands that cycle through repeated TCR error codes are almost universally the ones that treat registration as a form-filing exercise rather than a documentation alignment exercise. The form fields are the output; the documentation is the input that determines whether those fields produce approvals or errors.
When a TCR error code lands on a submission or in a delivery report, the fastest path to resolution is a lookup that maps the specific code to the exact documentation requirement it flags. The Fix TCR Error Hub covers 250+ specific TCR error codes with individual fix guides — search your code, get the specific cause, and follow the documented remediation steps.
