Solo businesses register 10DLC once and move on. Agencies hit a structurally different problem: ten, thirty, a hundred clients, each texting their own customers, each needing to be compliant, and a registration model that was designed around one brand per business. Get the structure wrong and you either cap every client's throughput or create a compliance liability with your agency's name on it.

The core decision: brand-per-client, not one mega-brand

The tempting shortcut is registering one brand, yours, and sending every client's traffic under it. It's cheaper on paper and it's the wrong call for three reasons:

  1. Throughput is per-brand. Carriers allocate daily message throughput by brand trust score. One shared brand means all your clients split one allocation, your biggest client's campaign eats your smallest client's speed-to-lead window.
  2. Reputation is shared. One client with sloppy list hygiene drags spam-rate metrics for every client riding the brand. You've built a compliance contagion machine.
  3. Content mismatch risk. Campaigns describe specific use cases. Thirty different businesses' messages under one brand's campaign is exactly the pattern reviewers and carrier audits flag.

The correct structure is one brand per client (their legal entity, their EIN), each with its own campaign. Each client gets their own throughput, their own reputation, and a registration that survives your relationship ending.

The real cost math at N clients

Per client, monthly fees run roughly $10/mo for the brand registration + $20/mo per campaign registration + $5/mo per number, call it $35/mo per client, plus a one-time vetting fee ($79) only where a client actually needs higher throughput (when vetting pays).

At 20 clients, that's 20 sets of brand, campaign and number fees every month. The question isn't whether that's a lot, it's who pays it. Which brings us to rebilling.

Rebilling registration defensibly

Registration fees are the easiest line item you'll ever rebill, because they're real, external, per-client, and documented. The standard patterns we see:

  • Pass-through on the invoice ($35/mo, labeled "A2P registration fees"), simplest, builds trust, and positions your margin in the messaging rate instead.
  • Compliance-as-a-service markup, e.g. $50-75/month covering registration fees plus your handling of the paperwork, rejections, and opt-out compliance. Defensible because the alternative is the client doing carrier homework themselves.

Either works; what doesn't work is hiding it inside an inflated per-message rate, because sophisticated clients comparison-shop per-message pricing. (The same logic applies to the messaging spread itself, we broke that down in rebilling SMS without churn.)

The onboarding-lag problem (and the fix)

The classic agency complaint: "every new client waits a week before their campaigns can send." That lag is optional. On Ready, a new client sub-account sends on Ready's shared registration while their own brand and campaign register in the background, and most approvals take 2 to 7 days (the per-segment rate stays the same the whole time; how the bridge works). Client onboarding day and first-campaign day can be the same day.

Batching the registrations

A campaign cannot exist without an approved brand, so file every brand first, in parallel, and queue each campaign behind its brand as it clears. Most of the delay is waiting on clients, not carriers, so collect everything in one intake wave before you register anything. Per client you need: the exact legal business name and EIN, the business address, a live website with a privacy policy, the use case, the opt-in flow (a screenshot or description) and two real sample messages. Give clients a sample-message template instead of a blank field, with the brand name, an opt-out line and no SHAFT content, and fewer campaigns bounce. Clients who answer late go in a second wave instead of holding up the rest.

Mistakes that quietly cap agencies

  • One brand for all clients, the throughput and contagion problems above. The savings are a rounding error; the ceiling is real.
  • Registering clients under your agency's EIN, ties their compliance standing to you and breaks portability when they leave.
  • Copy-pasting one campaign description across clients, reviewers notice; per-client descriptions with the client's actual use case and opt-in flow approve faster and audit cleaner.
  • Skipping opt-out infrastructure: STOP handling has to be enforced platform-side, per client. On Ready it's automatic on every sub-account; if your current stack leaves it to workflow builders, that's a lawsuit lottery ticket.

Do agencies need a separate 10DLC brand for each client?

Yes, that's the correct structure: each client registers as their own brand (their legal entity and EIN) with their own campaign. It gives every client independent throughput and reputation, and it's what carriers expect, one brand fronting many businesses' traffic is a flag, not a hack.

How much does 10DLC cost per client?

Roughly $35/mo in registration and number fees per client ($10 brand + $20 campaign + $5 for the sending number), plus an optional one-time $79 vetting fee where higher throughput is needed. Most agencies rebill it as a pass-through or fold it into a compliance-service fee.

How fast can a new client start texting?

Immediately on Ready: each sub-account's own number sends on Ready's registered shared campaign immediately while the client's own registration processes (most approvals take 2 to 7 days). No onboarding dead-air week.

Can I manage all client registrations in one place?

That's the point of doing this on a platform instead of carrier portals: Ready handles brand + campaign filing per sub-account in-app, including for GoHighLevel agencies, where it installs as a native GHL integration and replaces LC Phone per sub-account.


The agency version of 10DLC done right: brand-per-client, ~$35/mo rebilled transparently, registrations filed for you, and zero onboarding lag because the shared registration bridges the wait. See pricing.

Frequently asked questions

Can an agency register its clients' 10DLC brands under the agency's EIN?

It shouldn't. Each client's brand should use the client's own legal business name and EIN. Registering clients under your agency's EIN ties their compliance standing to you and breaks portability when they leave, so a client who switches agencies loses the registration they've been sending on. A brand built on the client's own entity survives the relationship ending and keeps that client's throughput and reputation separate from everyone else's.

What do I need from a client to register their 10DLC brand and campaign?

You need the exact legal business name and EIN, the business address, a live website with a privacy policy, the use case, the opt-in flow (a screenshot or description) and two real sample messages. Collect all of it in one intake wave before you file anything, since most delays come from waiting on clients. A sample-message template with the brand name, an opt-out line and no SHAFT content means fewer campaigns bounce.

Should agencies charge clients for 10DLC registration fees?

Yes, and it's one of the easiest fees to rebill because it's real, external, per-client and documented. The two common patterns are a straight pass-through labeled as A2P registration fees, or a compliance-as-a-service fee that covers registration plus your handling of paperwork, rejections and opt-out compliance. What doesn't work is hiding the cost inside an inflated per-message rate, since sophisticated clients comparison-shop per-message pricing.

Is brand vetting worth it for every agency client?

No. Brand vetting is an optional, one-time upgrade that raises a brand's trust score and daily throughput limits, so it's only worth paying for when a client actually needs higher volume. Standard brand and campaign registration is all most senders need. Vetting moves a brand's daily cap only when it pushes the trust score across a tier, and it doesn't change the per-second rate, so check a client's real sending volume before you buy it.