The single biggest myth keeping platforms locked into underperforming messaging providers: “we’d have to re-register everything.”
If you run your own CSP (Campaign Service Provider) account with The Campaign Registry, that’s simply not how it works. TCR’s architecture deliberately separates who registered a campaign from who carries its traffic — and the mechanism connecting them, Connectivity Partner (CNP) sharing, is a standard flow, not a special favor. Understanding it changes the economics of switching entirely.
The three-layer model
10DLC registration has three roles worth keeping straight:
- The brand — the business whose identity the messaging carries. Registered once, with verified corporate details.
- The CSP — the entity that registers campaigns on brands’ behalf. If you’re a platform with your own TCR account, this is you. Your brands, your campaigns, your customer relationships, recorded under your account.
- The Connectivity Partner (CNP) — the provider that actually connects the registered campaign to the carriers and moves its traffic.
The registration lives with the CSP. The traffic lives with the CNP. Switching providers is a CNP change — the registration doesn’t move, doesn’t reset, and doesn’t get re-reviewed as a new submission.
What sharing actually involves
Through TCR’s standard sharing flow, you elect Tychron as the Connectivity Partner for a campaign (or a portfolio of them). Everything the registration already earned comes along: the brand vetting, the campaign’s approved status, its use-case declaration, its throughput classification. There is no brand resubmission and no re-registration.
What does happen on our side: every shared campaign gets the same in-house review we give campaigns we register ourselves — checked against current carrier standards before it goes live on our connections. Standards evolve; a campaign approved eighteen months ago may predate a disclosure carriers now expect. Catching that proactively — rather than through a carrier enforcement action mid-migration — is part of what a carrier-grade migration means. Standard downstream vetting is billed at $15 per campaign, passed through at cost.
Numbers follow their own parallel track: port them fully, or use hosted messaging to move messaging while voice stays put — for platform migrations, hosted is usually the answer, because your customers’ voice service was never yours to move. Traffic flips when both tracks confirm, with no gap.
Why this matters more for platforms than anyone
A brand switching providers re-points one campaign. A platform switching CNPs re-points hundreds — which is exactly why TCR made it a portfolio operation rather than a per-campaign ordeal.
It’s also why we built our side of it the way we did. Platforms and resellers are some of Tychron’s largest customers: you keep your CSP account, your registrations, your customer relationships, and your margin — and point the traffic at source rates with a published surcharge schedule. The carrier layer is what we do; what you build on it is yours. Campaign lifecycle operations — registration, number assignment, status — can run through our API, so the migration ends with your provisioning flow intact, not rebuilt.
What if your provider registered the campaigns?
Then your campaigns live under their CSP account, and CNP sharing isn’t available to you directly — this is the fine print to check before you need it. In that case, campaigns are re-registered under Tychron as your CSP, with our review team making sure each passes on the first attempt. It’s more work than sharing (and worth knowing before you pick your next provider: with your own CSP account, you’re never locked in this way again).
Frequently asked questions
Does the campaign stop sending during the CNP change?
No — sequencing is the point. The share completes, the new path is confirmed live, and only then does traffic move. The old path keeps working until it does.
Do my campaigns get re-vetted by carriers when shared?
Sharing isn’t a new registration, but DCA vetting still applies when a campaign moves — the depth depends on whether the campaign is already at that DCA and was vetted within the last year. It’s billed at the standard $15 per attempt at cost, and our in-house review runs first so shared campaigns meet current standards before they’re submitted.
Which campaigns are eligible to share?
A campaign has to be active in TCR and already accepted by at least one carrier’s DCA — it doesn’t need to be fully vetted across every network first. The one blocker is an active suspension: while a campaign is suspended by a carrier or DCA, TCR declines the move until it’s lifted.
How long does a cutover take?
There’s no fixed number — it completes as each new party in the connectivity chain accepts its role, so the more new participants involved, the longer it can run. TCR gives the transfer a 30-day window; if it doesn’t finish in time the migration is automatically cancelled and your existing path is untouched, so you’d simply re-initiate rather than end up half-moved.
We have hundreds of campaigns. How is that priced?
Per campaign, at cost, quoted up front like everything else — no monthly minimums, no term commitments. Bring your portfolio size and current invoice and we’ll price the whole migration line by line.