The phrase “TCR approval issues” covers four structurally distinct failure modes, and most operators diagnose the wrong one. They receive no approval notification, or a rejection, and assume the problem is their privacy policy — because that’s the fix that appears first in search results. Sometimes it is the privacy policy. But the same symptom — an unregistered campaign that isn’t delivering — can trace back to a brand vetting failure, a campaign use case error, a downstream DCA rejection that TCR never surfaces, or a carrier-level hold that no resubmission will resolve until a separate process completes. Identifying which stage is blocking approval before taking corrective action is what separates a two-day fix from a three-week loop.
Categorizing TCR Approval Issues by Pipeline Stage
TCR approval issues do not all originate at the same layer. The 10DLC registration pathway is a sequential four-stage pipeline: brand registration → campaign submission → DCA review → carrier acceptance. Each stage can fail independently, and a failure at any earlier stage blocks all subsequent stages. A brand that has not cleared TCR vetting will not have any campaigns approved, regardless of campaign submission quality. A campaign that clears TCR review but is rejected by the DCA will not achieve carrier acceptance, and that rejection may not generate a notification visible to the operator.
Brand registration is evaluated by TCR directly, with trust score and entity classification assigned based on the data submitted. Campaign submission is reviewed by TCR’s vetting system using use case classification, sample message content, opt-in documentation, and website verification. DCA review is conducted by the Direct Connect Aggregators — Syniverse handles AT&T traffic, KORE Wireless handles T-Mobile, iconectiv handles Verizon — each of which applies its own supplemental review criteria beyond TCR’s base vetting. Carrier acceptance is the final state where the originating number is provisioned for A2P traffic at the network layer.
Operators experiencing a stalled 10DLC campaign approval should first determine at which stage the pipeline stopped moving before submitting corrections. Applying a campaign-level fix to a brand-level block does nothing.
Brand-Level TCR Approval Issues
TCR brand vetting failure reasons fall into three primary categories. The first is entity data mismatch: the legal business name submitted to TCR does not match the name on file with the IRS for the provided EIN. Even a minor formatting discrepancy — “LLC” vs “L.L.C.”, a DBA name submitted instead of the legal entity name — flags the submission for manual review or outright rejection. The legal name and EIN must correspond exactly to IRS registration records. State-registered entities whose names differ from their IRS filing names must use the IRS name in the brand registration.
The second category is website-brand inconsistency. TCR vetting agents verify that the submitted brand name and business website are attributable to the same entity. A brand registration using a personal email address, a mismatched domain, or a website that does not reference the registered business name will stall at the brand stage. Free or generic email addresses — gmail.com, outlook.com, yahoo.com — are not accepted for brand contact validation; a domain-specific business email is required.
The third category is Authentication+, the enhanced identity verification layer that TCR introduced in late 2024. Authentication+ requires additional documentation: tax registration records, company formation documents, domain-verified email, and in some configurations two-factor authentication for the submitting CSP account. Brands that submitted before November 2024 under prior vetting criteria may need to satisfy Authentication+ requirements if they are re-vetted or if their trust score falls below a threshold that triggers re-evaluation. The TCR Brand Consistency Checker at MyTCRPlus verifies that all brand-level fields — name, EIN structure, website attribution, email domain — are internally consistent before a brand registration is submitted or resubmitted.
TCR Brand Vetting Failure Reasons: What the Trust Score Tells You
A brand that completes TCR registration receives a trust score. This score, assigned on a scale that determines throughput tier and campaign approval likelihood, reflects the quality of the entity data submitted. A low trust score is not a rejection — the brand is registered — but it flags the entity for closer scrutiny during campaign vetting and caps the throughput available to approved campaigns. Operators whose brand registered but whose campaigns are being held or rejected at a rate disproportionate to their submission quality should check the trust score assigned to their brand. A score below the standard tier threshold indicates the brand vetting itself needs remediation, not the individual campaigns.
Campaign Submission Failures: Use Case, Content, and Documentation
Why is my TCR campaign not approved is a question that resolves differently depending on which campaign-level field failed. TCR campaign rejection codes identify the specific vetting criterion that triggered the hold. The four codes that account for the majority of campaign-level TCR approval issues are:
Error 9108: Privacy policy deficiency. The submitted website’s privacy policy does not explicitly address SMS data collection, third-party data sharing, and consumer consent for text messaging. Generic privacy policies generated for web data collection without an SMS-specific clause consistently trigger this code. The policy must name SMS as a communication channel, state that message data is not sold to third parties, and reference the opt-out mechanism. Full diagnosis of 9108 variants is available through the TCR Rejection Code Analysis resource at MyTCRPlus.
Error 9106: Missing or insufficient opt-out language. Sample messages submitted in the campaign registration do not include an opt-out mechanism. Every marketing message sample must contain “Reply STOP to opt out” or equivalent explicit opt-out instruction. Transactional campaign samples must include opt-out instructions in the initial opt-in confirmation message, even if individual transactional messages do not repeat it in every send.
Error 30887: Opt-out workflow deficiency. The STOP response confirmation message does not satisfy carrier requirements — it must include the brand name and confirm that the subscriber will receive no further messages. A confirmation message that says only “You have been unsubscribed” without naming the sending entity fails this check.
Error 30909: Call-to-action verification failure. TCR could not verify the opt-in mechanism described in the campaign submission. The submission indicated that opt-ins occur via website, but vetting agents could not locate an operational opt-in form at the submitted URL. This code fires when the opt-in page is behind a login, when the URL has changed since submission, or when the opt-in mechanism is described incorrectly in the registration. The full taxonomy of campaign-level error codes is indexed in the TCR Error Codes & Rejections Hub.
Use case misclassification is a less visible but equally common campaign submission failure. Submitting a mixed-purpose campaign — guest transactional and loyalty promotional content under a single use case code — triggers vetting holds because the sample messages don’t match the declared use case. The TCR Use Case Selector maps message content to the correct TCR use case classification before submission, preventing the mismatch that triggers this hold.
DCA Downstream Rejection: Where Carrier Approval Diverges from TCR Approval
A campaign that passes TCR vetting is not necessarily approved for carrier delivery. Each DCA — Syniverse for AT&T traffic, KORE Wireless for T-Mobile, iconectiv for Verizon — applies supplemental review criteria that extend beyond TCR’s base vetting. DCA rejections do not always generate a visible notification to the submitting operator. The campaign may sit in a “pending” state indefinitely, or it may show as approved at the TCR level while traffic remains blocked at the carrier network layer.
DCA rejection causes overlap with TCR rejection causes but include additional criteria: content category restrictions specific to individual carriers (AT&T’s content policies on certain financial products, T-Mobile’s stricter review of political and nonprofit campaigns), volume anomalies that trigger enhanced scrutiny on newly registered numbers, and entity verification failures that the DCA conducts independently from TCR’s brand vetting process.
Fixing TCR approval rejection at the DCA layer requires identifying which carrier network is blocking traffic and reviewing that DCA’s supplemental requirements. An operator experiencing delivery failures on T-Mobile traffic specifically, while AT&T and Verizon traffic routes correctly, has a KORE Wireless DCA issue, not a TCR campaign issue. Resubmitting the TCR campaign will not resolve a DCA-layer hold. The Stop TCR Rejections vetting guide at MyTCRPlus covers DCA-specific review criteria and the escalation path for carrier-layer holds.
Resubmission Strategy: Edit Existing vs. New Campaign Filing
TCR campaign approval issues that are resolved at the campaign layer require a decision on whether to edit the existing campaign registration or file a new campaign. The correct answer depends on the rejection type. For content corrections — fixing a privacy policy URL, updating sample messages, correcting opt-out language — editing the existing campaign and resubmitting is the appropriate path. The campaign retains its registration history, and the correction triggers a re-vetting cycle without incurring a new $15 vetting fee.
For use case misclassifications, where the entire campaign type needs to change, filing a new campaign under the correct use case is the operationally cleaner approach. Editing a campaign’s use case classification mid-review can generate additional scrutiny. A new filing under the correct use case code with accurate sample messages from the outset clears vetting more reliably than a corrected submission against a prior rejection record.
For brand-level issues — EIN mismatch, entity name discrepancy, Authentication+ gaps — corrections must be applied at the brand level before any campaign resubmission will succeed. Submitting corrected campaigns against an unresolved brand issue generates the same result as the original submission.
Resolving TCR Approval Issues Before They Repeat
TCR approval issues are preventable when the pipeline stage is diagnosed correctly before submission. Brand data must match IRS records exactly, website and email must be attributable to the registered entity, and Authentication+ documentation must be prepared in advance. Campaign submissions must use the correct use case code, supply complete opt-in and opt-out workflows, include error-code-compliant privacy policy language, and present sample messages that reflect actual message content within the declared use case. DCA-layer holds require carrier-specific investigation, not TCR-level resubmission.
The pattern underlying most persistent tcr approval issues is mismatching the corrective action to the wrong pipeline stage. An operator who keeps correcting sample messages when the actual block is a brand EIN mismatch will cycle through multiple rejections without progress. Confirming the stage first, then applying the stage-specific fix, is the only path to a clean approval.
Run the Rejection Remediation Tool at MyTCRPlus to identify the exact failure point across all four pipeline stages — brand, campaign, DCA, and carrier — and generate a corrected submission package with documentation verified against current TCR and carrier requirements. Run the Rejection Remediation Tool.
