Most senders need one number per area code they want to look local in, and no more. Adding numbers does not make texts go out faster, because US throughput is set per registered campaign, not per number.
That surprises people who come from the old long-code days, when more numbers meant more speed. Under 10DLC, every number attached to a campaign shares that campaign's per-second rate and its brand's daily cap. So the real question is not "how many numbers for volume?" It is "how many numbers for the way my customers see me?"
Throughput belongs to the campaign
Carriers publish no official rate card, so treat these as round approximations. A fresh standard campaign with no vetting sends at about 1 to 4 segments per second. Higher use-case tiers reach tens, roughly 10 to 75. T-Mobile also caps a brand's daily volume by trust score, at about 2,000, 10,000, 40,000, 100,000 or 200,000 messages a day, lowest score first. AT&T throttles per second and per minute instead of a hard daily cap.
None of that changes when you add a number. Ten numbers on one campaign still send at the campaign's rate. Brand vetting ($79 Standard, $179 Enhanced) raises the trust score, and it moves the daily cap only when it crosses a tier. It does not change the per-second rate. If you need more speed, the lever is the campaign's use case, not the pool. Our 10DLC explainer covers how those tiers work.
What a number does cost
A number is $2 a month. Registration is a separate line: $25 a month for registration, which covers the brand and its first campaign, and $20 a month for each extra campaign. The numbers are cheap. The registration is the part you do not want to multiply by accident.
Worked example, with assumptions: a business wants to look local in 6 area codes and has one campaign. Numbers: 6 x $2 = $12 a month. Add the $25 registration and the fixed cost is $37 a month, before any texts. Going from 6 numbers to 20 adds $28 a month and zero extra speed.
Reasons to add numbers
- Area-code matching. A contact in Denver is more likely to pick up a 303 number than a stranger's 212. That is the whole case for local presence.
- Separating traffic. A reminder line and a sales line should not share a number if you want clean reputation signals for each.
- Different brands. Each customer of a platform needs its own sub-account, numbers and registration. That is not pool sizing, it is tenancy.
Reasons not to add numbers
- Speed. Covered above: the campaign sets it.
- Dodging filtering. Spreading one campaign over many numbers to look smaller is the pattern carriers filter. We wrote up why number rotation backfires.
- Per-contact variety. A contact should see one number. If a customer texts you back and the reply goes to a different number than the one they got, the thread breaks.
Per-contact stickiness
Once a contact texts with a number, they should keep texting with it. On Ready, the contact keeps the number it already texts with, and an API send with no from uses that number first, then falls back to your number closest to their area code.
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true} That is the whole request. You do not pick numbers in your code unless you want to. Docs: send a message.
Sizing rule of thumb
- Count the area codes where most of your contacts live. One number each.
- Add one number per distinct purpose (support, sales, reminders) if you want separate threads.
- Stop. Raise throughput through the campaign's use case or vetting, not more numbers.
Local presence is off until you turn it on. It costs $0.0015 for each segment of a delivered text, on top of the text. Accounts made before November 16, 2026 keep it free. It picks among numbers you already have and does not buy new ones. Every number still sits on the registered campaign, so local presence does not bypass registration.
Where to go next
If you are sizing a pool for a GoHighLevel sub-account, read how #from:local# and #from:rotate# split a three-metro setup. If you are ready to try it, sign up and register one campaign first. The numbers can follow the area codes you actually see in your contact list.
Frequently asked questions
Do more numbers mean more texts per second?
No. Per-second rate is a property of the registered campaign, so ten numbers on one campaign send at that campaign's rate.
Is one number enough to start?
Yes, for most small senders. Add numbers when you want to look local in other area codes or keep separate lines for separate purposes.
Does local presence skip registration?
No. Every number sits on the account's registered 10DLC campaign, and local presence only chooses among your registered numbers.
Will contacts get texts from different numbers?
A contact keeps the number it already texts with. A first text goes from your number closest to their area code if local presence is on.