TCR Registration Requirements: What You Need Before You Submit

Executive Summary

TCR registration requirements are the Brand identity fields and Campaign packaging fields your Campaign Service Provider (CSP) submits into The Campaign Registry (TCR) ecosystem so US carriers can recognize sanctioned A2P 10DLC traffic. Brands generally need a legal name, tax ID (EIN for most US entities; Sole Proprietor rules differ), address consistent with tax records, website, and contacts. Campaigns need a clear description, use case, sample messages, verifiable opt-in (CTA/message flow), opt-out/HELP handling, and consistent public policy URLs. TCR’s own FAQ states that TCR does not review/approve/reject Campaigns—CSPs and upstream partners do—and that approval time varies. This guide is a board-ready requirements checklist, not a fee schedule and not legal advice.

Short answer: Before you submit, gather accurate Brand identity (legal name, EIN/tax ID where required, IRS-consistent address, website, contacts) and a complete Campaign package (who/whom/why description, use case, 2–5 aligned samples, 1:1 opt-in proof, STOP/HELP, privacy/terms URLs). Submit through your CSP—not by treating TCR as a DIY consumer portal for most brands.

Who This Is For / Who It Is Not For

Who this is for: Ops/compliance teams preparing first or remediation submissions; ISVs collecting client data; counsel reviewing packaging.
Who this is not for: Teams seeking guaranteed approval times or invented universal fees; pure TCPA litigation strategy.

Definitions

Brand Requirements (Core)

Per TCR resources:

Sole Proprietor: TCR FAQ describes Sole Proprietor as an individual without EIN—constraints on numbers/Campaigns apply at CSP level (e.g., Twilio documents one 10DLC number for Sole Prop Campaigns).

Already vetted elsewhere? Each CSP still registers the Brand; vetting tokens may be importable per TCR FAQ.

Campaign Requirements (Core)

Requirements Matrix: Standard vs Special vs Sole Prop

Decision Framework: Ready to Submit?

1. Confirm you send US A2P on 10DLC (else consider TFN/short code paths).
2. Choose Brand type (Standard / Low-Volume / Sole Prop) with CSP.
3. Collect tax letter / legal docs; align website legal footer.
4. Draft Campaign description answering who/whom/why.
5. Capture live opt-in evidence.
6. Publish SMS privacy section.
7. Write 2–5 samples; set attributes.
8. Submit Brand → wait verified → submit Campaign.
9. On rejection, fix live assets then edit/resubmit.
10. Attach numbers only after approval; soak test.

Risks of Incomplete Requirements

Implementation Checklist

Soft CTA

Preflight trust/packaging with MyTCRPlus tools and follow step-by-step registration. No approval guarantees.

FAQ

Do I register directly on campaignregistry.com as a brand?

Typically brands register through a CSP. TCR FAQ directs businesses to messaging providers.

Is EIN always required?

Required for typical Brands; Sole Proprietor path excludes EIN per TCR FAQ definition.

How long for Campaign approval?

Varies by use case and CSP; TCR does not itself approve/reject.

Does adding numbers increase throughput?

TCR FAQ: throughput is based on Brand and Campaign, not number count; vetting helps higher throughput.

What belongs in Campaign description?

Clear detailed outline of exact use—lack of clarity risks rejection.

What is a Reseller in TCR?

Entity between CSP and Brand; populate reseller fields when applicable.

Are Special Campaigns different?

Yes—sensitive/critical; may need vetting or MNO approval.

Do requirements replace TCPA?

No.

Canadian or foreign Brands?

TCR FAQ lists tax ID guidance by region—follow CSP forms.

Where do I get rejection reasons?

From your CSP, not a public TCR consumer ticket.

Key Takeaways

• Requirements = accurate Brand identity + complete Campaign packaging via CSP.
• EIN/name/address consistency drives verification.
• Description, samples, CTA, and privacy URLs drive Campaign approval.
• TCR does not approve Campaigns; CSPs/upstream do.
• More numbers ≠ more throughput.
• Keep TCPA consent parallel.
• Use MyTCRPlus for packaging preflight only.

Operating Appendix

Expanded Operating Playbook

90-day compliance calendar

RACI snapshot

Evidence pack

Dated opt-in screenshots, privacy PDF/HTML captures, sample version IDs, Brand/Campaign IDs, STOP test logs, rejection exports, number association audits, and a change log for From numbers.

Executive Q&A model answers

More numbers do not multiply 10DLC throughput. Registration does not equal TCPA consent. Fees are CSP-specific—use current provider docs. Approval timelines are not fixed SLAs. Snowshoeing risks carrier enforcement.

Submit quality gate

Legal name/EIN match; website live; privacy/terms public; opt-in 1:1 unchecked; samples match use case with Brand name and STOP; attributes match samples; HELP/STOP configured; owner assigned for number association after approval.

First 24 hours after SMS outage

Freeze marketing; pull error codes; classify failure layer; notify stakeholders; open CSP ticket with IDs; do not rotate unregistered numbers; write timeline memo; schedule postmortem.

Sustaining compliance

Quarterly template vs sample audits, STOP cross-system tests, privacy URL checks, and Brand identity reviews after M&A or DBA changes prevent most “surprise” blocks.

Extended Implementation Narrative

Treat registration and consent as a product launch, not a ticket. Assign a single program manager who can unblock legal, marketing, and engineering. Publish a shared folder with the Brand packet, Campaign drafts, and evidence captures. Run a tabletop exercise: “Our primary From number starts returning unregistered errors at 9 a.m.—what do we do?” Document the answer before it happens. When agencies manage dozens of Brands, productize the packet: same checklist, different EINs and websites. Resist the urge to submit incomplete Campaigns “just to get in line”—reviewers do not hold a place in queue for broken privacy URLs. After approval, keep the packet alive; the next promo calendar will try to drift samples. Schedule a 30-minute monthly sync between marketing ops and the messaging admin solely to compare live templates to registered samples. That habit alone prevents a large share of avoidable rejections and filter events. Finally, report to leadership using the two-layer risk model: carrier delivery risk versus TCPA consent risk, never conflated into a single green/red status.

Cross-Functional Training Outline

Module A — Why carriers care: Explain A2P vs P2P in plain language; show an unregistered block screenshot; emphasize that buying more numbers is not a throughput strategy.
Module B — Brand identity: Walk through EIN letter vs website footer mismatches using anonymized examples.
Module C — Campaign packaging: Workshop rewriting a vague description into a who/whom/why paragraph; critique sample messages for missing Brand name or STOP.
Module D — Consent: Contrast operational vs marketing checkboxes; practice verbal consent logging.
Module E — Incident response: Role-play a Friday marketing blast that generates STOP spikes and complaint emails.
Module F — Vendors: How to evaluate CRM claims of “we handle TCR,” including which Brand is actually registered.
Require quizzes for producers/agents who can trigger sends. Store completion records for audit. Refresh training after major FCC or CSP policy updates, and after any severity-1 messaging outage.

Metrics That Matter (Without Inventing Volumes)

Track operational metrics you can actually observe in your CSP and CRM—never invent search volumes or industry-wide fine totals for reporting:

Pair metrics with owners and review them in the same meeting as deliverability, not buried in a separate “compliance only” deck that executives skip.

Vendor and CSP Coordination Tips

Send your CSP a single well-structured ticket: Brand ID, Campaign ID, failure_reason text, links to live opt-in and privacy pages, and before/after screenshots. Avoid fragmented emails from five stakeholders. Ask explicitly whether a field is editable or requires recreate. Confirm how Sole Proprietor, Low-Volume, and Special use cases behave on that CSP—names and fees differ. If you use multiple CSPs, do not assume identical attribute enums. For ISVs, clarify reseller ID requirements early. Keep a shared FAQ for customer-success teams so they do not promise “24-hour TCR approval.” When a CSP publishes changelog entries about full blocking or new required Campaign fields, assign an owner to read them within one business day and update your internal runbook.

Documentation Templates (Illustrative)

Campaign description starter: “Messages are sent by [Legal Brand] to [customers who opted in at URL/process] for [specific purposes]. Recipients may reply STOP to opt out and HELP for help. Message frequency varies based on [orders/appointments/account activity].”
Opt-in disclosure starter: “By checking this box, you agree to receive [program] text messages from [Brand] at the number provided. Consent is not required as a condition of purchase. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. Privacy: [URL].”
Incident memo starter: Date/time detected; error codes; customer impact; layer failed (Brand/Campaign/number/consent); immediate containment; fix owner; ETA; prevention action.

Customize with counsel; do not paste blindly into regulated verticals (healthcare, finance, insurance) without review.

Extended Implementation Narrative

Treat registration and consent as a product launch, not a ticket. Assign a single program manager who can unblock legal, marketing, and engineering. Publish a shared folder with the Brand packet, Campaign drafts, and evidence captures. Run a tabletop exercise: “Our primary From number starts returning unregistered errors at 9 a.m.—what do we do?” Document the answer before it happens. When agencies manage dozens of Brands, productize the packet: same checklist, different EINs and websites. Resist the urge to submit incomplete Campaigns “just to get in line”—reviewers do not hold a place in queue for broken privacy URLs. After approval, keep the packet alive; the next promo calendar will try to drift samples. Schedule a 30-minute monthly sync between marketing ops and the messaging admin solely to compare live templates to registered samples. That habit alone prevents a large share of avoidable rejections and filter events. Finally, report to leadership using the two-layer risk model: carrier delivery risk versus TCPA consent risk, never conflated into a single green/red status.

Disclaimer

Informational only—not legal advice. Confirm current TCR/CSP forms and counsel guidance. MyTCRPlus does not guarantee approval.