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.
Soft CTA
Organize Brand evidence and public SMS disclosures with MyTCRPlus tools as preparation aids—not approval or legal guarantees. Pair with the TCR registration guide.
Operating Model and RACI (continued 0)
Treat compliance as an operating system. Assign owners who remain accountable after launch:
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Brand legal identity | Finance | Controller | Legal | Ops |
| Campaign samples and descriptions | Marketing ops | Growth lead | Compliance | Support |
| Consent capture UX | Product | Product lead | Legal | Engineering |
| STOP suppression SLA | Engineering | Eng lead | Support | Compliance |
| CSP invoice and fee review | Finance | Controller | Ops | Leadership |
| Incident response for blocks | Messaging ops | COO | CSP support | All senders |
When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.
Evidence Binder and Audit Readiness
Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.
Technical Controls Matrix
| Control | Why it matters | Validation |
|---|---|---|
| Attach numbers only to approved Campaigns | Stops unregistered A2P | Quarterly console audit |
| Immutable production templates | Prevents silent sample drift | RBAC review |
| Dual-write opt-outs to CRM and messaging platform | Closes sync gaps | Automated integration test |
| Link-domain allowlist | Avoids public shortener filters | CI template linter |
| Quiet hours by recipient timezone | Reduces nuisance complaints | Platform config review |
| Fail closed if Campaign inactive | Blocks accidental sends | Pre-send API check |
| Rate caps per Campaign | Avoids burst abuse patterns | Load test and alerts |
| Alert on carrier error spikes | Faster incident response | Observability dashboard |
Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.
Governance Cadence (continued 3)
Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.
Vendor and ISV Diligence
If an agency, ATS, EHR, CRM, or ISV sends on your behalf, contract for your organization as Brand of record unless a deliberate reseller model applies; notice within an agreed window of Campaign rejection or suspension; shared dashboards or weekly status exports; STOP propagation into your system of record within minutes; prohibition on mixing unrelated customers onto your Campaign; and an annual security and compliance questionnaire. Many filtering events originate in reseller infrastructure. Diligence is cheaper than silent non-delivery during peak season. Keep a vendor inventory that lists every system capable of emitting SMS.
Legal Overlay (Not Legal Advice)
Registration and consent are related but distinct. An approved Campaign does not prove TCPA consent for a particular send; perfect consent records do not move unregistered traffic through carrier blocks. Coordinate with counsel on when prior express written consent is required, how revocation must be honored under 47 CFR section 64.1200 and related FCC guidance, which state mini-TCPA rules apply to your footprint, retention periods for consent artifacts, and vendor liability terms. Do not invent statutory penalty figures in training decks—cite primary sources and counsel memos instead. Revisit the overlay whenever marketing launches a new list source or message purpose.
Soft CTA (continued 6)
Prepare Brand packets, public SMS disclosures, and pre-submission diagnostics with MyTCRPlus tools at https://mytcrplus.com/tools/ and related microsite options. They help you organize evidence for your CSP—they do not guarantee approval, throughput, or legal compliance. Pair preparation with the step-by-step TCR registration guide at https://mytcrplus.com/how-to-register-with-tcr-the-complete-step-by-step-process-for-10dlc/ and troubleshooting pages for unregistered traffic blocks when deliverability collapses.
Change-Control Playbook
When templates, vendors, or CSP rules change: log the source URL and timestamp; classify impact across Brand, Campaign, consent UX, billing, and API; freeze related sends if resubmission is likely; assign one incident owner with a clear due date; notify support and marketing with non-speculative language; retest major US carriers after the fix; and write a short postmortem that updates the runbook. Controlled change beats reactive copy edits during an outage. Store playbook outcomes beside the evidence binder so audits show both prevention and response.
Launch and Scale Checklist
| Step | Owner | Artifact |
|---|---|---|
| Inventory senders and templates | Ops | Spreadsheet |
| Classify marketing vs operational | Compliance | Matrix |
| Confirm Brand legal entity | Finance | EIN docs |
| Publish SMS disclosures | Web / legal | Live URLs |
| Draft Campaign packet | Ops | Samples and flow |
| Submit Brand and Campaign via CSP | Admin | IDs and status |
| Configure STOP and HELP | Engineering | Test log |
| Train staff | Manager | Sign-off |
| Carrier smoke test | Engineering | Delivery matrix |
| Quarterly audit | Compliance | Memo |
Do not skip the smoke test. A Campaign can show approved while a single MNO still has not provisioned the share, producing carrier-specific failures that look like random filtering to marketers.
Decision Framework Recap
- Confirm you are sending US A2P over local 10DLC (vs toll-free or short code).
- Map each template to marketing or operational purpose.
- Assemble accurate Brand identity and public website evidence.
- Write Campaign narratives and samples that match production truth.
- Submit through your CSP and wait for Brand eligibility before Campaign create.
- Attach numbers only after Campaign approval and provisioning.
- Enforce STOP globally and monitor error codes.
- Audit consent artifacts and sample drift on a fixed calendar.
- Escalate CSP reason codes with evidence—not guesses.
- Keep TCPA counsel in the loop for new message purposes.
This framework applies whether you run healthcare reminders, staffing shift fills, nonprofit fundraising, or retail promotions.
Operating Model and RACI (continued 10)
Treat compliance as an operating system. Assign owners who remain accountable after launch:
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Brand legal identity | Finance | Controller | Legal | Ops |
| Campaign samples and descriptions | Marketing ops | Growth lead | Compliance | Support |
| Consent capture UX | Product | Product lead | Legal | Engineering |
| STOP suppression SLA | Engineering | Eng lead | Support | Compliance |
| CSP invoice and fee review | Finance | Controller | Ops | Leadership |
| Incident response for blocks | Messaging ops | COO | CSP support | All senders |
When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.
Risks and Failure Modes
| Risk / failure mode | Impact | Mitigation |
|---|---|---|
| Unregistered or mismatched Campaign traffic | Blocking or filtering | Register accurately; align samples to production |
| Consent gaps on marketing sends | Legal and complaint exposure | Capture purpose-specific consent; retain artifacts |
| Slow or partial STOP handling | Carrier and TCPA risk | Automate suppression across all senders |
| Website or policy URL failures | Brand/Campaign rejection | Keep public HTTPS pages live and consistent |
| Sample drift after approval | Filtering or re-review | Change-control templates; version samples |
| Treating TCR status as legal safe harbor | False confidence | Maintain separate TCPA/compliance program |
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.