Executive Summary
How to register for TCR is one of the most searched questions in US A2P SMS—and the answer surprises many teams: most brands do not open a public “TCR account” the way they open a social login. You register an A2P Brand and one or more Campaigns through a Campaign Service Provider (CSP)—your messaging provider—into The Campaign Registry. TCR stores identity and use-case data so carriers can treat your local 10-digit traffic as sanctioned application-to-person messaging. Success depends less on finding a secret portal and more on preparing legal identity, website/privacy assets, honest use-case packaging, and consent flows before you click submit.
Short answer: Work through your CSP. Register the Brand (who you are—EIN/tax ID except Sole Proprietor paths), wait for verification/vetting status your CSP requires, then register each Campaign (what you send, how people opt in/out, samples). TCR FAQ materials state that TCR does not itself approve or reject Campaigns—CSPs and upstream partners do. Attach numbers only after Campaign approval. Registration does not replace TCPA consent.
Who This Is For / Who It Is Not For
Who this is for
- US businesses sending SMS/MMS from local 10-digit numbers via an app or CPaaS
- Ops and compliance leads preparing first-time Brand + Campaign packets
- ISVs/resellers registering on behalf of customers (with correct reseller fields)
- Teams remediating rejections and resubmitting cleaner packages
Who this is not for
- Brands seeking a consumer-style “sign up at campaignregistry.com” without a CSP (not the standard path)
- Pure toll-free or short-code programs (different verification paths)
- Anyone needing guaranteed approval SLAs, universal fee tables, or invented MPS
- Legal counsel substituting this guide for jurisdiction-specific advice
Definitions
| Term | Meaning |
|---|---|
| TCR | The Campaign Registry—central hub for 10DLC Brand/Campaign records |
| CSP | Campaign Service Provider—messaging platform that registers Brands/Campaigns |
| Brand | Registered business identity (legal name, tax ID where required, contacts, website) |
| Campaign | Registered use case (description, message flow, samples, attributes) |
| 10DLC | 10-digit long code used for sanctioned US A2P messaging |
| EIN / Tax ID | Employer Identification Number (or foreign equivalent) used to verify Brands |
| Sole Proprietor | In TCR framing, an individual without EIN—special constrained path |
| Vetting / Trust Score | Additional identity/reputation processing that can affect throughput eligibility |
| Message flow / CTA | Description of how end users opt in |
| Reseller | Entity between CSP and Brand in some registration chains |
What “TCR Registration” Actually Means
Per TCR introductory materials and the resources FAQ:
- Any business using SMS on 10DLC to communicate with customers or employees is expected to register.
- Mass marketing and individual business messages are treated as non-consumer (A2P) messaging.
- A Campaign is the use case (Marketing, Customer Care, etc.).
- Brands typically work through a CSP; CSPs operate messaging platforms and use the TCR portal or APIs.
Twilio’s docs state that anyone sending SMS/MMS over a 10DLC number from an application to the US must register for A2P 10DLC, creating a Brand and a Campaign.
Existing deep dive on MyTCRPlus: complete step-by-step TCR registration process.
Pre-Registration Document Checklist
Gather these before opening your CSP’s registration wizard:
| Item | Why reviewers care |
|---|---|
| Legal business name (exact IRS / registry spelling) | Must match EIN/tax records |
| EIN / Tax ID (unless Sole Proprietor path) | Brand verification input |
| Business address consistent with tax records | Identity matching |
| Support email + support phone | Troubleshooting contacts |
| Live website URL | Proves real business presence |
| Privacy policy URL (SMS-aware) | Opt-in and data-use transparency |
| Terms / SMS terms URL | Program rules, STOP/HELP, rates, frequency |
| Opt-in screenshots or live forms | Evidence for message flow |
| 2–5 sample messages with brand name | Content alignment |
| Use-case decision (Marketing vs Care vs Mixed, etc.) | Campaign category |
| Authorized representative details | CSP form requirements |
TCR FAQ guidance: US Brands should use the nine-digit EIN and legal name consistent with IRS registration (SS-4 confirmation is a common source of truth). Canadian and other foreign tax ID formats are documented on TCR’s resources page—follow the country-specific instructions rather than inventing formats.
Step-by-Step: Brand Registration
- Choose / confirm your CSP (Twilio, Bandwidth, Telnyx, or another TCR-connected provider). Brands do not typically self-serve TCR without a CSP relationship.
- Select Brand type with your CSP’s help: Sole Proprietor vs Low-Volume Standard vs Standard (naming varies by CSP UI). Tax ID requirements and throughput expectations differ.
- Enter identity fields exactly—legal name, EIN, address, website, vertical/industry, contacts.
- Submit Brand and wait for status such as Verified or Vetted_Verified (labels vary). Campaigns generally require Brand verification first.
- Optional secondary vetting if you need higher throughput or special use cases—confirm fees and process with your CSP (do not invent fee amounts).
Sole Proprietor vs EIN Brands
TCR materials: Sole Proprietor means an individual without an EIN. If you have an EIN, do not use the Sole Proprietor path just because you are small. Twilio documents tighter Campaign and volume limits for Sole Proprietor Brands. Confirm current constraints with your CSP.
Already registered with another provider?
TCR FAQ: each CSP must register the Brands they work with, even if another CSP already registered them. If already vetted elsewhere, you may be able to import a vetting token—ask your CSP.
Step-by-Step: Campaign Registration
Once the Brand is verified (or otherwise eligible per CSP rules):
- Select the Brand in the CSP portal.
- Choose the use case (Marketing, Customer Care, Account Notification, Mixed, Special categories, etc.).
- Write a Campaign description that answers who you are, who you reach, and why you message (Bandwidth’s who/who/why test).
- Document message flow / CTA in plain language: exact URL or POS/keyword path, what the consumer sees, and that opt-in is affirmative and not buried only in Terms.
- Provide sample messages that match the use case; include brand identification; include STOP language in at least one sample where required by your CSP.
- Set content attributes accurately (embedded links, phone numbers, age-gated content, etc.). Mismatches between attributes and samples cause declines.
- Submit and track CSP/upstream review. TCR FAQ: TCR does not review/approve/reject Campaigns—partners do. Time varies by use case and chain length.
- On approval, associate phone numbers / messaging services to the Campaign ID per CSP instructions.
Standard vs Special Campaigns
TCR FAQ distinguishes Standard use cases (generally available) from Special use cases (sensitive/critical; may need vetting or MNO pre/post approval). Charity, political, and similar categories often have extra steps—confirm with your CSP before selecting a Special use case you cannot support with documentation.
Agents & Franchises note
TCR FAQ: the agents/franchise use case is for corporate brands with many agents or franchisees—not something a single franchisee should request alone. Corporate should drive that registration.
Message Flow and Sample Quality Bars
Bandwidth best practices and CSP compliance guides converge on:
- Opt-in must be one-to-one in the CTIA sense for messaging programs—not shared freely to unrelated third parties as if it were open consent.
- Opt-in must not be merely implied or hidden only inside Terms.
- Website collecting numbers should disclose privacy/terms.
- Samples must look like real messages, not “Hello customer, this is a test.”
- Opt-out language should use spaced keywords (e.g., Reply STOP to unsubscribe)—avoid concatenated junk like
Stop2End.
Telnyx’s campaign compliance guide similarly emphasizes having compliant mechanisms live before submission and aligning samples to each use case (especially for Mixed/Marketing).
Decision Framework: Ready-to-Submit Gate
- Legal name + EIN match tax paperwork character-for-character.
- Website loads, matches Brand, and is not a parked domain.
- Privacy + SMS terms include mobile disclosures your CSP expects.
- Opt-in UI is live; screenshots stored; marketing unchecked if separate.
- Use case selected matches the majority of templates.
- Description passes the who/who/why test in two to four sentences minimum.
- Message flow narrates the real path a human takes to opt in.
- Samples include brand name and realistic content; attributes match samples.
- STOP/HELP auto-replies configured in the messaging platform.
- Number assignment plan documented (which numbers → which Campaign).
If any gate fails, fix assets first—resubmits waste calendar time.
Timelines and Fees (Uncertainty Labeled)
| Stage | What sources say | How to plan |
|---|---|---|
| Brand verification | Often days; can need manual docs | Do not schedule launch for “tomorrow” |
| Campaign approval | Varies by use case and CSP chain; TCR does not approve | Build multi-week buffer for first Marketing Campaign |
| Number attachment | After Campaign approval | Sequence soft-launch after attach |
| Fees | CSP-specific brand, campaign, vetting, and carrier pass-through charges | Ask your CSP for current schedule—never invent universal fees |
Twilio and other CSPs publish their own fee pages; Bandwidth publishes 10DLC fee articles; amounts change. Treat every public table as provider-specific and dated.
Risk and Failure Modes
| Risk | Symptom | Mitigation |
|---|---|---|
| EIN/name mismatch | Brand stuck unverified | Copy from SS-4 / tax docs |
| Parked website | Campaign rejection | Launch real site + policies |
| Marketing samples on Care use case | Rejection / filtering | Split Campaigns or use Mixed honestly |
| Vague description | “What do you send?” rejection | Rewrite with concrete message types |
| Privacy policy gaps | Codes like 9108-style privacy failures | Fix privacy before resubmit (9108 guide) |
| Assuming more numbers = more throughput | Still capped | TCR FAQ: throughput is Brand/Campaign based; vetting helps more than number spam |
| Snowshoeing | Filtering / trust damage | Do not rotate numbers to evade limits |
| Skipping consent | Legal exposure despite approval | Run TCPA program in parallel |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Select CSP / confirm TCR path | Ops | Provider account |
| Collect EIN + legal identity packet | Finance / legal | SS-4 or equivalent |
| Publish website + privacy + SMS terms | Web / legal | Live URLs |
| Build opt-in + screenshots | Product | Message flow evidence |
| Draft description + samples | Compliance | Campaign worksheet |
| Submit Brand | CSP admin | Brand ID |
| Complete vetting if needed | CSP admin | Vetting status/token |
| Submit Campaign | CSP admin | Campaign ID |
| Attach numbers | Messaging admin | Number map |
| Production smoke test | Ops | Delivery report |
| Document rejection remediations | Compliance | Ticket log |
After Approval: Operations That Keep You Compliant
Registration is a beginning, not a finish line. After Campaign approval:
- Lock template governance so marketing cannot ship new copy that contradicts the registered samples without a Campaign update review.
- Monitor delivery receipts and error codes for sudden filtering spikes after content or frequency changes.
- Revisit Brand data when you rebrand, change legal entity, or move headquarters—stale identity fields create future friction.
- Train support staff on HELP replies and escalation paths listed in your Campaign.
- Schedule a quarterly packet review comparing live opt-in pages to the message flow text stored with your CSP.
If you migrate CSPs, budget time to re-register Brand/Campaign under the new provider and to import vetting tokens when available. Do not assume numbers remain sanctioned without completing the new provider’s association steps.
Soft CTA
Preflight Brand consistency and sample alignment with MyTCRPlus tools and, if you need public disclosure pages, review the SMS compliance microsite offering. These help packaging quality; they do not guarantee carrier approval.
Internal Linking Suggestions
- Drafts:
06-what-is-the-campaign-registry.md,24-tcr-vetting-and-brand-score.md,23-tcr-campaign-rejection.md,32-10dlc-ein-requirements.md
FAQ
How do I register for TCR if I am not a CSP?
You generally cannot self-register as a Brand in the CSP portal. Choose a messaging provider that is a TCR CSP (or works through one) and complete Brand + Campaign registration in their console or via their API/support process.
What is the difference between Brand and Campaign registration?
Brand = who you are. Campaign = what you send and how consumers opt in/out. You need both for typical 10DLC sending.
How long does TCR registration take?
Brand verification and Campaign approval times vary. TCR states Campaign approval time varies by use case and CSP and that TCR itself does not approve Campaigns. Plan in days to weeks, not hours.
Do I need an EIN?
Standard Brand paths typically require EIN/tax ID. Sole Proprietor paths are for individuals without EIN—confirm eligibility with your CSP.
Can I register multiple Campaigns?
Many CSP docs allow multiple Campaigns per Brand (commonly discussed as up to five unless a valid business reason is shown—confirm current limits with your CSP).
What if my Campaign is rejected?
Ask your CSP for the rejection reason and remediation steps. TCR FAQ directs brands to their CSP. See MyTCRPlus rejection resources linked above.
Does registration replace TCPA consent?
No. Carrier registration and legal consent are separate obligations.
Will adding more phone numbers increase throughput?
TCR FAQ: throughput is based on Brand and Campaign, not the count of numbers. Vetting is the better path for higher throughput needs.
What should I write in the Campaign description?
A clear outline of exactly what the Campaign will be used for—concrete message types, audience, and purpose. Vague “we text customers” language is a common failure mode.
Is there a TCR login for my brand?
CSPs have portal logins. Brand employees usually access registration through the CSP’s UI or receive status from the CSP—not a universal public Brand login for every business.
Key Takeaways
- Register for TCR/10DLC through your CSP: Brand first, then Campaign, then attach numbers.
- Prepare EIN/legal name, website, privacy/terms, opt-in evidence, and samples before submitting.
- Write descriptions and message flows that a stranger can understand without a sales call.
- TCR does not approve Campaigns—your CSP and upstream partners do; timelines vary.
- Do not invent universal fees or MPS; ask your provider for current schedules and caps.
- Fix privacy and consent packaging early to avoid repeat rejections.
- Throughput comes from Brand/Campaign eligibility and vetting—not number spinning.
- Keep TCPA consent work on a parallel track.
Disclaimer
This article is informational only and is not legal advice. TCR, CSP, and carrier processes change. Confirm field requirements, fees, timelines, and consent obligations with your provider and qualified counsel before relying on any registration plan.