Executive Summary
“TCR Campaign approval” is industry shorthand for getting a 10DLC Campaign into a state where major US carriers will accept A2P traffic for that use case. The Campaign Registry’s own FAQ states TCR does not review, approve, or reject Campaigns—CSPs and upstream connection partners perform that work. Timelines vary by use case, CSP, and how many partners sit in the sharing chain. Brands shorten cycles by submitting accurate identity data, clear descriptions, verifiable opt-in narratives, and samples that match production—including Brand name and STOP language as required.
Short answer: Expect Brand verification first, then Campaign review by your CSP/upstream partners (not a TCR approval desk). Plan days to weeks depending on use case; remediate with your CSP’s reason codes, not guesswork.
Who This Is For / Not For
For: Teams waiting on Campaign status; ISVs explaining timelines to customers; compliance owners fixing rejections.
Not for: Anyone seeking a guaranteed SLA from TCR itself; fabricated approval-rate marketing.
Definitions
| Term | Meaning |
|---|---|
| Campaign approval | CSP/upstream acceptance of a Campaign for carrier provisioning |
| Brand verified | Identity checks passed so Campaigns can be registered |
| Standard use case | Generally available; typically no MNO pre-approval |
| Special use case | Sensitive/critical; may need vetting or MNO approval |
| Sharing / CNP | Upstream connectivity partner review in the chain |
| DCA | Downstream campaign authorization / content review entity in some stacks |
What Actually Happens After You Click Submit
- Brand must be verified (or vetted_verified where applicable).
- You select a use case and preview carrier terms in CSP tooling when offered.
- You submit description, message flow, samples, and attributes.
- CSP and upstream partners review content and identity consistency.
- Carriers provision on their own clocks after acceptance.
- You attach numbers and test—approval ≠ instant global delivery.
TCR FAQ: approval time varies by use case and CSP; more partners usually means longer waits; ask your CSP for rejection reasons.
Readiness Matrix
| Artifact | Ready when… |
|---|---|
| Brand legal name / EIN | Matches tax docs exactly |
| Website | Live, related, no login wall |
| Privacy / terms | Public; SMS disclosures present when required |
| Message flow | Describes real opt-in path with URLs/screenshots |
| Samples | Match production; identify Brand; include opt-out as required |
| Use case | Matches content (no marketing disguised as care) |
Decision Framework
- Confirm Brand status is eligible for Campaign create.
- Choose accurate use case (Standard vs Special).
- Run preflight: URLs, samples, consent narrative.
- Submit via CSP; record Campaign ID.
- Monitor CSP status—not campaignregistry.com as an end brand.
- If rejected, map reason code → owner → fix → resubmit.
- After acceptance, verify MNO provisioning before major sends.
- Lock templates to approved samples; change control for material edits.
Common Blockers
| Blocker | Fix |
|---|---|
| Opt-in not verifiable | Host public form or screenshots; rewrite message_flow |
| Privacy policy gaps | Add non-sharing, frequency, rates language as required |
| Sample/use-case mismatch | Split Campaigns or rewrite samples |
| Brand website unrelated | Fix Brand URL / content |
| Special use case without eligibility | Provide vetting / MNO prerequisites or switch use case |
Timeline Expectations (Non-SLA)
CSP docs and TCR materials emphasize variance. Practical planning ranges cited in industry guides often span roughly one to several weeks for Campaign review—not a universal SLA. Special use cases and long partner chains trend longer. Build launch buffers.
Operating Model and RACI
Assign durable owners so messaging compliance does not depend on tribal knowledge:
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Brand legal identity | Finance | Controller | Legal | Ops |
| Campaign samples & description | Marketing ops | Growth lead | Compliance | Support |
| Consent capture UX | Product | Product lead | Legal | Engineering |
| STOP suppression SLA | Engineering | Eng lead | Support | Compliance |
| Fee / invoice review | Finance | Controller | Ops | Leadership |
| Incident response | Messaging ops | COO | CSP support | All senders |
Review RACI quarterly. Shadow sending through unsanctioned tools is a top root cause of filtering.
Evidence Binder
Keep versioned artifacts: Brand payloads, tax docs used, archived privacy/SMS URLs, opt-in screenshots, Campaign samples with version IDs, CSP status emails, STOP/HELP templates, and monthly opt-out exports. These records matter for CSP remediation and for legal discovery.
Technical Controls
| Control | Purpose | How to validate |
|---|---|---|
| Numbers only on approved Campaigns | Block unregistered sends | Console audit |
| Immutable production templates | Stop sample drift | Permission review |
| Dual-write opt-outs | Close sync gaps | Integration test |
| Domain allowlist for links | Reduce filter triggers | Template linter |
| Quiet hours by timezone | Lower complaints | Config review |
| Fail closed if Campaign inactive | Prevent accidental sends | Pre-send check |
Governance Cadence
Weekly deliverability review; monthly consent QA on new lead sources; quarterly Campaign-to-production alignment; annual Brand identity reconfirm. Publish a scorecard: registered traffic share, opt-out rate, open remediations.
How MyTCRPlus Can Help
Organize Brand evidence and public SMS disclosures with MyTCRPlus tools as preparation aids—not approval or legal guarantees. Pair with the TCR registration guide.
Worked example: moving a campaign from pending to approved
A property manager's campaign sits in a pending state for a week. Checking the CSP portal, it finds the campaign is waiting on DCA review, not rejected. Rather than resubmitting, which would reset its place in the queue, it confirms that its opt-in URL, privacy policy and terms all load publicly.
The campaign is approved, and the manager then links its numbers and sends test messages to handsets on each major carrier, because approval at the registry does not always mean every carrier has provisioned the campaign yet.
FAQ
Does TCR approve my Campaign?
No. TCR FAQ: CSPs and upstream partners review/approve/reject.
How long does approval take?
It varies by use case and CSP. Ask your provider for current estimates.
Why is my Campaign pending so long?
Long sharing chains and manual reviews add time. Confirm no action items in your CSP console.
Can I send while pending?
Generally no for registered A2P paths—wait for approval/provisioning per CSP rules.
What if carriers differ in provisioning speed?
Test per MNO; stagger launches if one carrier lags.
Do more numbers speed approval?
No. Throughput relates to Brand/Campaign, not number count (TCR FAQ).
Should I resubmit a new Campaign or edit?
Follow CSP guidance; some stacks require new submissions after rejection.
Where do I get the rejection reason?
From your CSP—not from a Brand login on TCR.
Key Takeaways
- TCR does not itself approve Campaigns—CSPs/upstream partners do.
- Brand verification precedes Campaign success.
- Clarity in description, flow, and samples shortens review.
- Special use cases may need extra vetting or MNO steps.
- Track status in the CSP console.
- Remediate with reason codes, then retest carriers.
- Approval is not TCPA consent.
- Lock production templates to approved samples.
Disclaimer
Informational only—not legal advice. TCR, CSP, carrier, FCC, and state rules change. Confirm requirements with your provider and qualified counsel. MyTCRPlus does not guarantee approval or delivery.