A2P 10DLC Trust Score & Throughput in GoHighLevel (2026)

A2P 10DLC Trust Score is a 0–100 number The Campaign Registry assigns when it vets a Standard (EIN) brand. It sets how fast you can send (MPS) and your T-Mobile daily cap: a 75–100 score unlocks the top tier — up to ~200,000 segments/day to T-Mobile — while a score under 25 holds you to ~2,000/day. Sole Proprietor and Low Volume brands get no score at all.

If you run a GoHighLevel agency, Trust Score is the number you start caring about the moment a client’s brand clears registration. Before approval, every question is “will this pass?” After approval, the question becomes “why can only some of my messages get through?” — and the answer is almost always Trust Score and the throughput tier it lands you in. This guide explains what the score actually is, who gets one (and who doesn’t), what counts as “good,” the exact throughput each band buys, why scores come back low, and the handful of things you can actually do about it.

The short version

1. Trust Score is a 0–100 brand-vetting number that The Campaign Registry (TCR) assigns through secondary vetting — and only to fully-vetted Standard (EIN) brands. Sole Proprietor and Low Volume brands skip secondary vetting and get no Trust Score at all.
2. The score sets two limits: your per-second throughput (MPS — message segments per second) and your T-Mobile daily message cap. Higher score, higher both.
3. It’s largely about your registration data, not your messaging behavior. Mismatches between your EIN, legal name, and address and what official records show are the most fixable cause of a low score. Some inputs — company size, years in operation, domain age — you can’t change.
4. The score is static. GHL’s documentation states Trust Scores “are static and do not automatically change over time” — sending great traffic for six months does not quietly raise it. To move it, you fix the underlying data and get re-vetted.

What a Trust Score actually is

When you register a Standard brand in GoHighLevel’s Trust Center, two vetting passes happen. Primary vetting confirms the brand exists. Secondary vetting is the one that produces a Trust Score: TCR “assigns a score from 0 to 100 and gives access to higher default throughput and message limits toward US mobile carriers”.

Two properties of that score trip up agencies:

• It’s static. Per GHL, Trust Scores “do not automatically change over time.” There is no slow climb you earn by behaving well. The number is set at vetting and stays put until you trigger a re-vet by fixing the inputs.
• It’s brand-level, not campaign-level. One score attaches to the brand. Every campaign you run under that brand inherits the throughput tier the score unlocks.

Who gets a Trust Score — and who doesn’t

This is the first thing to get straight, because two of the three tiers most GHL agencies use never receive a score:

So “how do I raise my Trust Score?” only has a meaningful answer for fully-vetted Standard brands. If your client is on Sole Proprietor or Low Volume Standard, there is no score to raise — their throughput is fixed by the tier, and the only way up is registering a fresh fully-vetted Standard brand. (For the Sole Prop caps and the EIN decision, see our Sole Proprietor A2P 10DLC guide.)

What counts as a “good” Trust Score?

There is no official “passing” number — TCR does not publish a threshold that means “approved.” What exists are the throughput bands the carriers actually apply, plus the rough “low / medium / high” framing the industry has settled on.

The industry framing (widely repeated, not a TCR-published cutoff): carriers and aggregators commonly describe roughly 70+ as “good” and 90+ as “excellent,” with 50 or below treated as poor. Treat those as rules of thumb, not a line you must clear.

What actually matters — the throughput bands. Forget the vibes; the real question is which band your score lands in, because the band is what sets your sending limits. GHL and the carriers cut the 0–100 range into these tiers:

• 75–100 — top throughput tier
• 50–74 — middle tier
• 25–49 — low tier
• 1–24 — lowest non-zero tier
• 0 — minimum

A score of 74 and a score of 51 buy the same throughput; a 75 and a 51 do not. So the practical goal isn’t “get the highest number” — it’s “clear the next band boundary,” especially the jump into 75–100.

How Trust Score controls throughput (the numbers that matter)

Throughput shows up in two separate limits. You can hit either one first.

MPS — how fast you can send per second

MPS (message segments per second) is GHL/TCR’s per-second send rate, allocated per carrier. Per GHL’s throughput documentation, for Declared use cases:

Mixed and Marketing use cases follow the same table, with one extra rule: a Low Volume Mixed campaign is fixed at 3.75 total MPS regardless of Trust Score — which is exactly why Low Volume tiers don’t need a score. Sole Proprietor campaigns sit even lower, around 2.25 total MPS.

The headline: moving from the 1–49 band into 50–74 is a 10× MPS jump (12 → 120), and clearing into 75–100 nearly doubles it again (120 → 225). That’s the difference between a blast that drains in minutes and one that crawls all afternoon.

T-Mobile daily cap — how many you can send per day

Separate from per-second MPS, T-Mobile enforces a hard daily segment cap that scales with Trust Score. The carrier-published tiers map to the score like this:

These limits are applied at the EIN level and reset at midnight Pacific each day. Blow past the cap and messages to T-Mobile numbers bounce with error 30023 (“daily message cap reached”) for the rest of the day — they don’t queue, they fail. The 200,000/day ceiling itself can only be lifted through T-Mobile’s separate Special Business Review process.

Notice the same boundary problem here: a low-tier brand (1–24) is capped at 2,000 T-Mobile segments/day. For an agency client running even a modest promo to a few thousand contacts, that single tier difference is the whole campaign getting throttled by mid-morning.

Why scores come back low

Most low scores aren’t about your messages — they’re about your brand data not matching official records. GHL’s brand-approval best-practices are explicit about what must line up:

• EIN + Legal Company Name must match the IRS exactly. GHL: the legal name must be “exactly as registered with the IRS, which can be found on the CP 575 EIN Confirmation Letter. An exact match between the Legal Company Name and the EIN as displayed on CP 575 is required.” A trailing “LLC,” an abbreviation, or a DBA used in the legal-name field is a mismatch.
• Business address must match official records. GHL warns that “submitting the address of a local branch or any address different from the official registered company address might produce a mismatch with a negative impact on the Trust Score.”
• Use an EIN, not a DUNS number. For US companies, a DUNS number is “unacceptable” for Standard brand registration.

Then there are the inputs you can’t control, which is worth telling clients up front so they don’t chase a number they can’t move: TCR’s score also weighs company size, years in operation, and domain age drawn from independent data sources. A brand-new one-person LLC with a six-month-old domain will score lower than a 20-year-old company with 200 employees — and no amount of clean copy changes that. The lever you do control is the data-match lever.

How to actually raise a Trust Score

Because the score is static, “improving” it means fixing the inputs and getting re-vetted, not waiting. The realistic playbook:

1. Reconcile your brand data to the source documents. Pull the CP 575 letter and make the Legal Company Name in Trust Center character-for-character identical to it. Confirm the EIN is right. Make the address match the officially registered company address, not a branch or a mailbox. (GHL now requires uploading the CP 575 PDF — max 5MB — for EIN brands, so the document is already in play.)
2. Pick the most specific Declared use case you legitimately can. Declared use cases draw from the full MPS table above; the Low Volume Mixed fallback is fixed at 3.75 MPS. Choosing the right category isn’t a Trust Score trick, but it determines whether the score you earn actually translates into throughput. (See How to Choose the Right A2P 10DLC Use Case.)
3. Resubmit for secondary vetting after you’ve fixed the data. Corrected brand details trigger a fresh vetting pass. Note GHL charges an $11 vetting appeal fee for the re-vet path on a disputed or low score — budget for it.
4. Don’t expect behavior to move it. Clean traffic, low opt-out rates, and high engagement are good for deliverability and your sender reputation, but they do not retroactively raise a static Trust Score. The number moves when the data does.

What you can’t do is buy or “boost” a score — anyone selling that is selling nothing. The honest mechanism is: accurate data in, fair score out, re-vet when you fix something.

The per-EIN cap trap most agencies miss

Here’s the one that bites agencies specifically: the T-Mobile daily cap is applied per EIN and shared across every brand and campaign registered under that EIN. If you register multiple campaigns under a single agency EIN, they don’t each get their own 200,000/day allowance — they split one. Two high-volume clients under the same EIN can starve each other on heavy days.

The cleaner pattern for agencies is one brand/EIN per client (each client registers under their own business identity), so each client’s throughput is its own. If you must consolidate under an agency EIN, plan the daily volume across all campaigns against a single shared cap, not one cap per campaign.

How use case interacts with the score

Two clients can have identical Trust Scores and different real-world throughput, because the use case selects which MPS row applies. Declared use cases use the full table (up to 225 MPS at 75–100); Mixed and Marketing share that table but inherit the Low Volume Mixed 3.75-MPS floor if registered Low Volume. So the score sets your ceiling; the use case decides how much of it you actually get. Picking the most specific category your messaging legitimately fits is how you keep a hard-earned 75+ score from being wasted on a low-throughput lane. We walk the full decision tree in How to Choose the Right A2P 10DLC Use Case in GoHighLevel.

Where Easy A2P fits

Be clear about what a copy-review tool can and can’t do here: Easy A2P does not set, raise, or guarantee a Trust Score — TCR does, and several of its inputs (company size, domain age, years in operation) are outside anyone’s control. Easy A2P also doesn’t approve your brand; TCR and the carriers make that call.

What it does do is keep a low score from turning into an outright rejection on top of it. Easy A2P reviews the registration copy you control — your sample messages, opt-in flow, opt-in confirmation, Privacy Policy, and Terms of Service — and flags the consistency problems that compound a weak brand: a legal name or DBA used inconsistently across your copy, a missing required ToS clause, sample messages that don’t match your declared use case. It runs checks and hands back paste-ready fixes before you submit, so the parts in your lane are clean and the only variable left is the vetting data itself.

In short: fix your CP 575-matched brand data to earn the best score TCR will give you, then run the campaign copy through Easy A2P so a clean submission isn’t undone by a sloppy one. See how the review works →