Executive Summary
The Campaign Registry (TCR) is the centralized US registry used in the A2P 10DLC ecosystem so mobile carriers can see who is sending business SMS/MMS over 10-digit long codes and what those programs are for. Campaign Service Providers (CSPs)—messaging platforms such as major CPaaS vendors—register Brands (business identity) and Campaigns (use-case packages) into TCR. Most end businesses never log into TCR directly; they supply data through their CSP console or API. Critically, TCR’s own FAQ states that TCR does not review, approve, or reject Campaigns—CSPs and upstream connection partners do that work. Registration improves transparency and is required for sanctioned 10DLC delivery; it does not replace TCPA consent, STOP/HELP handling, or accurate sample messages.
Short answer: The Campaign Registry is the shared Brand + Campaign database behind US A2P 10DLC. You register through your messaging provider (CSP). TCR stores identity and campaign metadata for carriers; approval decisions happen outside TCR’s review desk.
Who This Is For / Who It Is Not For
Who this is for
- Businesses sending (or planning to send) US A2P SMS/MMS from local 10-digit numbers
- Compliance, legal-ops, and marketing-ops owners asked to “do TCR” or “register 10DLC”
- Developers and ISVs integrating Brand/Campaign onboarding into a product
- Teams confused about TCR vs Twilio/Bandwidth/Telnyx vs carrier approval
- Leaders comparing 10DLC registration to toll-free verification or short codes
Who this is not for
- Pure consumer person-to-person texting with no business application layer
- Programs that only use verified toll-free or short codes and never touch 10DLC (different registration paths)
- Anyone seeking invented search volumes, guaranteed approval rates, universal MPS, or unsourced fine amounts
- Brands expecting to open a consumer login on campaignregistry.com and self-register without a CSP
Definitions
| Term | Meaning |
|---|---|
| The Campaign Registry (TCR) | Central hub where CSPs register Brands and Campaigns for the sanctioned 10DLC ecosystem |
| A2P 10DLC | Application-to-person messaging over US 10-digit long codes that requires Brand + Campaign registration |
| Brand | Registered business identity (who is sending)—typically verified with tax ID except Sole Proprietor cases |
| Campaign | Registered messaging use-case package (what is being sent)—description, samples, opt-in flow, attributes |
| CSP (Campaign Service Provider) | Messaging platform that is the primary TCR user and registers Brands/Campaigns |
| CNP (Connectivity Partner) | Upstream partner in the sharing/connection chain toward carrier networks |
| DCA | Downstream/campaign review entity in some connection chains that reviews campaign content |
| MNO | Mobile Network Operator (carrier) such as AT&T, T-Mobile, Verizon |
| Standard vs Special use cases | Standard campaigns are generally available; Special use cases may need vetting or MNO approval |
| Trust / brand score / vetting | Identity and risk signals that can affect throughput tiers—confirm current mechanics with your CSP |
TCR in Plain English
US carriers moved A2P traffic on local long codes into a sanctioned channel: 10DLC. To operate that channel, they need declared identity and declared purpose. According to Twilio’s A2P 10DLC overview, anyone sending SMS/MMS over a 10DLC number from an application to the US must register. Toll-free and short codes are not part of the A2P 10DLC system—they use separate verification or provisioning paths.
TCR’s About page describes TCR as the hub where CSPs register customers’ brands and the campaigns linked to those brands. TCR’s 2026 introductory materials likewise frame TCR as the centralized platform consolidating Brand and Campaign information so carriers can deliver more dependable business messaging.
What “TCR” means in business conversations
In SMS compliance conversations, TCR almost always means The Campaign Registry, not an unrelated corporate finance acronym. Related phrases:
| Phrase people say | What they usually mean |
|---|---|
| “Do TCR” / “TCR registration” | Complete Brand + Campaign registration for 10DLC via your CSP |
| “TCR Brand” | The registered business identity in the registry |
| “TCR Campaign” | The registered messaging use-case package |
| “TCR compliance” / “campaign registry compliance” | Meeting carrier/CSP registration and content rules for 10DLC |
| “Campaign Registry Inc.” / “TCR registry” | Informal reference to the registry operator / platform |
| “TCR SMS” / “TCR texting” | Using 10DLC after Brand/Campaign registration |
| “TCR legal meaning” / “TCR meaning in business” | Usually “The Campaign Registry” in messaging compliance context |
Who Uses TCR: Brands vs CSPs vs Carriers
Brands are companies (or sole proprietors) that want to text customers or employees. TCR’s resources FAQ states that if you are a business that wishes to use SMS to communicate with customers or employees, you are considered a Brand, and registration directly with TCR is not the correct path—talk to your messaging service provider or a listed partner.
CSPs operate SMS messaging platforms and are the primary TCR users. They register Brands and Campaigns through the CSP portal or APIs, then work with connectivity partners so campaigns can be published toward carrier networks.
Carriers (MNOs) use registered Brand/Campaign metadata (and their own policies) to provision, filter, rate, and sometimes manually review traffic.
Practical implication: your “TCR login” is usually your Twilio, Bandwidth, Telnyx, Sinch, or other CSP console—not campaignregistry.com as an end-brand user.
Role map
| Role | What they do | What Brands should expect |
|---|---|---|
| Brand | Provide legal identity, website, use-case truth, consent evidence | Supply accurate data; fix content when rejected |
| CSP | Submit Brand/Campaign to TCR; collect fees; surface status | Primary support contact for registration |
| CNP / upstream partners | Share/review campaigns in the connection chain | May add review latency |
| DCA / reviewers | Content review against messaging principles | Rejection reasons often surface here via CSP |
| TCR | Registry of Brand + Campaign records | Does not itself approve/reject Campaigns (per TCR FAQ) |
| MNO | Network provisioning, filtering, commercial terms | Carrier-specific timelines and policies |
Brand vs Campaign: The Two Registration Layers
TCR’s model is intentionally split into who and what.
Brand = who
A Brand record typically includes legal business name, tax identifier (EIN for US entities; Sole Proprietors without EIN are handled differently), address, contacts, website, and entity type. TCR’s FAQ explains that EIN/Tax ID is required (Sole Proprietors excluded) so TCR can verify Brand identity—and that the EIN must match the legal company name. Each registered Brand receives a unique Brand ID (CSP materials describe a 7-digit alphanumeric ID starting with “B”).
Twilio’s collect business information guide is a practical field checklist for what CSPs often collect before submitting into the registry ecosystem.
Campaign = what
A Campaign describes the messaging program: use case, detailed description, message flow / call-to-action (how people opt in), sample messages, help/opt-out behavior, and content attributes (links, phone numbers, age-gated content, and similar flags). TCR’s FAQ asks for Campaign descriptions that paint an accurate picture; lack of clarity can result in rejection by reviewers in the chain.
A Brand may have multiple Campaigns (for example, OTP separate from Marketing). Mixing promotional samples into a “Customer Care” Campaign is a classic rejection pattern.
Standard vs Special Campaigns
Per TCR’s resources FAQ:
- Standard Campaigns are generally available to TCR-registered Brands and typically do not require pre/post-registration approval from MNOs in the same way Special cases do.
- Special Campaigns are sensitive or critical and may require vetting or MNO approval before a Brand can register them (examples commonly include political, charity, emergency, agents/franchises, and similar categories—confirm the current list with your CSP).
What TCR Does — and Explicitly Does Not Do
What TCR does
- Provides a centralized place for CSPs to declare Brand identity and Campaign metadata
- Supports identity verification workflows (including Sole Proprietor OTP-style flows and public-company contact attestation in CSP docs)
- Enables carrier transparency into messaging origins and intended content categories
- Supports campaign sharing toward connectivity partners and carrier provisioning
- Distinguishes Standard vs Special use-case paths and carrier terms previews in the CSP portal
What TCR does not do
Per TCR’s resources FAQ:
- TCR does not review, approve, or reject Campaigns. That work is done by CSPs and their upstream connection partners. Approval time varies by use case and CSP; more partners in the chain often means longer timelines.
- TCR is not your consent database. TCPA prior express written consent (where required) remains your legal obligation.
- TCR does not magically increase throughput when you buy more phone numbers. TCR’s FAQ states throughput is based on who (Brand) and what (Campaign), not the number of numbers on the Campaign; vetting is the path discussed for higher throughput needs.
- TCR registration does not replace carrier filtering, CSP acceptable-use policies, or state/federal privacy rules.
Decision Framework: How Brands Should Operate “TCR Registration”
Use this numbered operating procedure:
- Confirm you need 10DLC. If traffic is US A2P on local long codes, plan Brand + Campaign. If you only use toll-free or short code, follow those verification paths instead (or in addition).
- Pick / confirm your CSP. Registration happens through that provider’s console or API.
- Assemble Brand evidence. Legal name matching tax docs, EIN/CBN as applicable, address, website, authorized contacts. See related draft guidance on website requirements.
- Map real message programs to Campaign use cases. Separate Marketing from OTP/account alerts when the content differs.
- Write truthful
message_flowand samples. Include Brand identification and opt-out language in samples as your CSP requires. - Submit Brand first; wait for Verified / Vetted_Verified (or CSP equivalent) before Campaign. CSP user guides require Brand verification status before Campaign registration.
- Monitor Campaign status through the CSP—not by emailing TCR as a Brand.
- If rejected, remediate with the CSP’s reason codes, then resubmit. See MyTCRPlus guides on rejection root causes and rejection code troubleshooting.
- After approval, associate numbers and test on major carriers before full ramp.
- Maintain ongoing compliance—consent records, STOP processing, and content aligned to the registered Campaign.
Requirements Comparison Table
| Topic | Brand layer | Campaign layer | Outside TCR |
|---|---|---|---|
| Legal identity / EIN | Core | Inherits Brand | Tax docs retention |
| Website | Common Brand field | Policies linked in opt-in evidence | Hosting / microsite |
| Use case selection | Eligibility may depend on Brand type/vetting | Required | Product roadmap |
| Sample messages | N/A | Required | Production templates must match |
| Opt-in description | N/A | Required (message_flow / CTA) |
Consent ledger / CRM |
| Approval decision | Identity verification / vetting states | CSP + upstream partners (not TCR desk) | Carrier provisioning |
| Throughput | Brand score / vetting influences | Use case + Brand tier | Carrier daily caps / MPS |
| Fees | CSP-quoted Brand fees | CSP-quoted Campaign fees | Pass-through carrier fees vary by provider |
Do not invent universal fee tables. Twilio, Bandwidth, Telnyx, and others publish provider-specific Brand and Campaign fees that change; always read your CSP’s current pricing page.
Timeline Expectations (Labeled Uncertainty)
TCR’s FAQ: campaign approval time varies by use case and CSP; TCR does not approve campaigns. TCR Intro 2026 materials similarly note that time-to-ready varies and that ensuring complete Brand information and correct use-case detail speeds the process; they cite a practical range of roughly 1–4 weeks for campaign review in some materials—treat that as guidance, not an SLA.
Carrier provisioning after registration can add additional business days per MNO (provider docs sometimes cite different windows per carrier). Plan launches with buffer; do not promise executives a fixed calendar date unless your CSP gives you a written estimate for your specific submission.
Risk / Failure Modes and Mitigations
| Risk / failure mode | Symptom | Mitigation |
|---|---|---|
| Wrong mental model (“TCR rejected us”) | Confusion; wrong support ticket path | Ask CSP for the actual rejecting party and reason code |
| EIN / legal name mismatch | Brand stuck Unverified | Use IRS CP 575 / 147C exact legal name; wait for new EIN propagation if recently issued |
| Sole Prop vs EIN confusion | Wrong Brand type; fees/throughput issues | If EIN exists, register Low-Volume/Standard per CSP docs |
| Vague Campaign description | Rejection | Write who/what/why in plain English; align to samples |
| Marketing content in non-marketing use case | Rejection or filtering | Split Campaigns; obtain marketing-grade consent |
| Buying more numbers for throughput | No capacity gain | Pursue vetting / correct use case per TCR FAQ |
| Re-registering Brand already with another CSP without coordination | Duplicate Brand friction | Each CSP registers Brands it works with; import vetting token when applicable (TCR FAQ) |
| Ignoring consent | Legal exposure even if Campaign “approved” | Maintain TCPA-compliant opt-in evidence separate from TCR |
| Unregistered sending | Blocking / non-delivery | Complete Brand + Campaign before production US 10DLC traffic |
Implementation Checklist (Owner + Artifact)
| Step | Owner | Artifact |
|---|---|---|
| Confirm 10DLC vs TFN vs short code path | Messaging architect | Channel decision memo |
| Select CSP / confirm account | Ops | CSP account ID |
| Collect legal name, EIN, address, contacts | Finance + legal | Brand packet |
| Publish functional website + policies | Web / compliance | Live URLs |
| Draft Campaign description + message_flow | Compliance + marketing | Campaign worksheet |
| Draft 2–5 sample messages with Brand ID + STOP | Messaging owner | Sample set |
| Submit Brand; record Brand ID | Ops | Brand ID screenshot |
| Submit Campaign after Brand verified | Ops | Campaign ID / status |
| Remediate rejections with CSP | Compliance | Rejection reason log |
| Attach numbers; carrier smoke test | Engineering | Test matrix |
| Archive consent + registration package | Legal-ops | Audit folder |
How TCR Relates to “TCR Compliance” Tools and Software
Search queries like “tcr software,” “tcr system,” or “tcr compliance website” often mix three different needs:
- Registry access — CSP portal/API into TCR (CSP-only for Brands)
- Preparation software — checklists, trust-score preflight, microsites, policy templates
- Ongoing compliance ops — consent storage, opt-out webhooks, content governance
MyTCRPlus focuses on preparation and education for Brands navigating CSP-mediated registration. Soft CTA: use MyTCRPlus tools such as the TCR trust score preflight simulator to pressure-test Brand consistency before you pay for submission cycles—without treating any score as a guaranteed carrier outcome.
Internal Linking Suggestions
- Draft peers:
do-i-need-a-website-for-10dlc-registration,tcr-campaign-approval,tcr-use-case-types,tcr-vetting-and-brand-score,tcpa-vs-10dlc-registration
Reseller, ISV, and Multi-CSP Realities
TCR’s FAQ defines a Reseller as an entity (typically another messaging platform) that sits between a CSP and the Brand being registered—Brand → Reseller → CSP. During Campaign registration, CSPs must enter reseller details in the responsible-parties section when applicable.
ISVs and agencies should collect Brand identity from the end business, not substitute the ISV’s website or EIN. Duplicate or mismatched identity is a frequent cause of Brand verification failure. If a Brand already completed secondary vetting with another CSP, ask whether a vetting token can be imported rather than paying to re-vet blindly—TCR’s FAQ contemplates that pattern, and your CSP will confirm whether it applies.
Multi-CSP strategies (primary plus backup provider) are common for resilience, but each CSP still registers Brands it serves. Coordinate Brand displays names, websites, and Campaign narratives so reviewers see one coherent business story across providers.
How to Read CSP Status Without Panic
When a console says “pending,” “rejected,” or “unverified,” decode the layer:
- Brand identity state — tax ID match, Sole Prop OTP, public-company email attestation, or secondary vetting outcome
- Campaign content review — samples, message_flow, privacy URLs, use-case alignment
- Sharing / upstream acceptance — CNP or DCA declined sharing
- MNO provisioning — Campaign exists in TCR but a specific carrier has not enabled it yet
Treat “TCR rejected us” as a shorthand that is often inaccurate. Ask: Which system produced the reason code, and what exact field failed? Then remediate that field—not the entire program—unless the use case itself is wrong.
FAQ
What is The Campaign Registry in one sentence?
It is the centralized registry where messaging providers register Brands and Campaigns so US carriers can identify A2P 10DLC traffic.
Do I register directly on campaignregistry.com?
Usually no. Brands register through a CSP. TCR’s materials say direct Brand registration is not the correct path for end businesses.
Does TCR approve my Campaign?
No. TCR’s FAQ states TCR does not review, approve, or reject Campaigns; CSPs and upstream partners do. Speak to your CSP for rejection reasons.
What is the difference between Brand and Campaign?
Brand = who you are. Campaign = what you send and how people opt in. You need both for 10DLC.
Why do people say “TCR compliance”?
They usually mean completing 10DLC Brand/Campaign registration and keeping content, consent, and opt-out behavior aligned with carrier and CSP rules—not a separate federal “TCR license.”
Is TCR the same as TCPA?
No. TCR/10DLC is a carrier registration framework. TCPA is a federal consent and calling/texting statute. You typically need both perspectives: registered traffic and lawful consent.
Can I raise throughput by adding more 10DLC numbers to one Campaign?
TCR’s FAQ says throughput is based on Brand and Campaign, not the count of numbers. Vetting is discussed as the path for higher throughput needs.
What are Standard vs Special Campaigns?
Standard use cases are generally available. Special use cases may require vetting or MNO approval because they are sensitive or critical.
My Brand is already registered with another provider. Do I register again?
TCR’s FAQ: each CSP must register the Brands they work with. If already vetted elsewhere, you may be able to import a vetting token—ask your CSP.
How long does Campaign approval take?
It varies by use case and CSP. TCR does not publish a single SLA because it does not perform the approval. Build schedule buffer and track status in your CSP console.
Key Takeaways
- The Campaign Registry is the Brand + Campaign hub for US A2P 10DLC transparency.
- Brands almost always register through a CSP, not as direct TCR consumers.
- Brand = identity; Campaign = use case, samples, and opt-in narrative.
- TCR stores and routes registry data; it does not itself approve/reject Campaigns.
- Throughput is not multiplied by buying more numbers on the same Campaign.
- EIN/legal name accuracy and clear Campaign descriptions reduce friction.
- Registration does not replace TCPA consent or STOP/HELP operations.
- Use CSP status, reason codes, and remediation playbooks—not guesswork—when blocked.
Disclaimer
This article is for informational purposes only and is not legal advice. TCR, CSP, and carrier rules change. Confirm current Brand/Campaign fields, fees, and approval paths with your messaging provider. MyTCRPlus does not guarantee registration approval or message delivery.