Does TCR Review Your A2P Campaign? No — Here's Who Does

No. The Campaign Registry (TCR) does not review, approve, or reject A2P 10DLC campaigns — its own materials say so plainly. That work is done by the CSPs, CNPs, and Direct Connect Aggregators in the “campaign sharing chain,” where a DCA such as Syniverse, Sinch, or Infobip manually reviews each submission and the mobile carriers make the final call.

If you run a GoHighLevel agency, you’ve almost certainly said “my TCR campaign got rejected” — everybody does, and this guide won’t tell you to stop. But when you actually go to fix a rejection, it helps to know who is really on the other side of the glass. Because the party you’re picturing — a single “Campaign Registry” that reads your samples and stamps them approved or rejected — isn’t the one doing the reviewing at all.

Here’s the sentence straight from The Campaign Registry’s own introduction deck:

“The Campaign Registry does not review, approve, or reject campaigns. This is done by the various CSPs, CNPs, or DCAs involved in the campaign sharing chain.”

So who does what? Let’s map the whole chain to what a GoHighLevel agency actually touches — and, just as important, pin down the one thing TCR really does decide.

The short version

• TCR is a registry, not a reviewer. It stores brand and campaign data and hands it to the parties who evaluate it. It does not approve or reject the campaign itself.
• The manual campaign review happens at the DCA — a Direct Connect Aggregator like Syniverse, Sinch, or Infobip — which checks your submission against carrier and CTIA guidelines. On the GoHighLevel stack (LeadConnector runs on Twilio under the hood), Twilio can act as its own DCA.
• The carriers (MNOs) — AT&T, T-Mobile, Verizon — have the final word on whether your traffic runs.
• The one thing TCR does run is brand identity verification. Your legal-name match, EIN check, and vetting score are TCR’s territory. Only campaign review is downstream.
• “TCR rejection” is fine as shorthand. It’s how GoHighLevel, Twilio, and every agency talks. Just know that when a campaign is rejected, the decision came from a DCA or carrier reading your copy — which is exactly why fixing your copy is the lever that matters.

The five roles in the campaign sharing chain

TCR defines a handful of ecosystem roles. Here they are, mapped to what you actually deal with as a GoHighLevel agency:

Per TCR’s description of the chain, the CNP forwards your campaign to a Direct Connect Aggregator, and “the DCA manually reviews each Campaign submission for compliance with [CTIA] and mobile carrier guidelines” (Campaign Registry intro deck).

Read that again: manually reviews. There’s a human (or a human-supervised process) at a DCA reading your campaign description and your sample messages against a rulebook. That’s the reviewer your rejection came from — not “TCR.”

So who actually reviews and rejects a campaign?

The DCA does the campaign review, and the carriers hold the final approval. TCR itself sits upstream of both, as the shared database everyone reads from.

On the Twilio side (which is what GoHighLevel uses to submit), Twilio spells out the same picture. Per Twilio’s A2P 10DLC Campaign Vetting FAQ, all US A2P 10DLC campaign registrations “are subject to a manual vetting process” and are charged a $15 campaign vetting fee at the time of vetting. Twilio names the three major DCAs handling 10DLC in North America — Syniverse, Sinch, and Infobip — and notes that Twilio itself can act as a DCA depending on the registration.

That $15 vetting fee is a Twilio-side charge tied to the DCA review. It’s worth separating from GoHighLevel’s own posture on resubmissions: per the GHL Help Center, resubmitting a rejected campaign in GoHighLevel is free — no additional Campaign Vetting Fee — so the real cost of a rejection is the waiting, not another charge. (The full breakdown of what a rejection actually costs an agency is in our every TCR rejection reason explained field reference.)

The practical takeaway: the standards your campaign is judged by are carrier and CTIA guidelines, applied by a DCA — so the way to pass is to make your copy clear those guidelines before you ever submit.

The one thing TCR does decide: your brand

Here’s the split that trips people up, and it matters: campaign review is downstream, but brand identity verification is TCR’s job.

When you register a brand, TCR is the party cross-referencing your submitted business details — legal name, EIN, address — against records like the IRS database to produce a vetting outcome and, for standard brands, a vetting score. That’s why a brand can come back “unverified” for an exact-match legal-name failure or an EIN that’s too new to have propagated yet: those are TCR-run identity checks, not DCA campaign reviews.

So the accurate mental model is two gates, run by two different parties:

1. Brand gate — TCR. Is this a real, verifiable business? (Legal name, EIN, address, vetting score.)
2. Campaign gate — DCA + carriers. Does this specific messaging program pass the content rules? (Use case, sample messages, opt-in flow, consent language, Privacy Policy, Terms of Service.)

A “rejection” can happen at either gate, and the fix is completely different depending on which one. Our rejection field reference splits every documented cause into brand-side and campaign-side buckets for exactly this reason. And if you want to understand how the brand vetting score itself is built and what it does to your throughput, that’s the subject of our A2P 10DLC trust score & throughput guide.

Then why does everyone say “TCR rejected my campaign”?

Because it’s useful shorthand, and we’re not here to make you talk like a telecom lawyer. GoHighLevel’s Trust Center, Twilio’s error codes, and every agency in the ecosystem all use “TCR rejection” to mean “my A2P 10DLC campaign came back rejected.” Keep saying it. The keyword you search is the keyword you’ll see in your dashboard.

The only thing worth internalizing is what the shorthand is standing in for. When your GoHighLevel Trust Center submission is rejected, the decision was made by a DCA (and, ultimately, the carriers) reading the copy you entered — the campaign description, the two sample messages, the opt-in confirmation message, the opt-in flow, and your linked Privacy Policy and Terms of Service. TCR passed that copy along; it didn’t judge it.

That’s not a pedantic distinction. It’s the difference between “I need to appeal to some faceless registry” and “I need to rewrite the specific fields a reviewer flagged so they clear the rules next time.” The second one is a problem you can actually solve.

What this means when GoHighLevel Trust Center rejects you

Since the review is a human-graded pass against known rules, the winning move is to make your submission clear those rules before it reaches a DCA. That’s the whole reason Easy A2P exists.

Easy A2P runs a pattern check across all ten sections an agency fills out in a GHL Trust Center submission — Brand Registration, Campaign Description, Sample Message 1, Sample Message 2, the Marketing and Non-Marketing consent checkboxes, the Opt-In Confirmation Message, the Opt-In Flow Description, and the Privacy Policy and Terms of Service SMS sections. A Review (1 credit) returns findings plus specific remediation guidance — what tripped a rule and how to fix it. A Draft (2 credits) writes a full review-ready packet from your business inputs. And Fix My Copy (1 credit) reworks the sections a review flagged and re-checks the result before you see it, so a Review + Fix costs the same 2 credits as drafting fresh.

What Easy A2P doesn’t do — and can’t, and neither can any tool — is approve your campaign. Approval belongs to the DCAs and carriers, exactly as this whole article lays out. What a good pre-submission review does is make sure that when the reviewer looks, they’re looking at copy that already clears the documented rejection triggers, so your odds on the first pass are as high as they can be.

You can start with 3 free credits on an instant signup — see how it works or pricing for the full breakdown.