Bulk SMS service providers: pricing models and what gets hidden

Every bulk SMS provider puts a number on its pricing page, and almost none of those numbers is what you pay. The real cost of sending a campaign to a few thousand opted-in contacts depends on segments rather than messages, on carrier fees that may or may not be in the quoted rate, on monthly registration charges, and on throttling that decides whether your Tuesday promo lands Tuesday morning or Tuesday night.

This post compares the three pricing models you'll run into and shows where costs hide in each. It works through one campaign in real dollars and ends with a list of questions to send any provider before you sign. We make Ready, so we'll show our own numbers too, including where we aren't the lowest per-segment option.

The three pricing models you'll actually see

Most bulk senders fall into one of three models, sometimes blended.

Per-message (or per-segment) pricing

You pay a rate for each unit sent. The catch is the unit. "Per message" and "per segment" sound alike, but carriers bill segments, and a single long or emoji-heavy message can be two, three or four segments. A provider quoting "per message" either absorbs that difference (rare) or counts segments on the invoice anyway.

Raw CPaaS APIs sit at the low end. Twilio is around $0.0083 a segment, and GoHighLevel's LeadConnector is around $0.0083 a message, roughly $0.0128 all-in. Both are lower per unit than our Standard rate. What you give up at that price is everything around the send: registration paperwork, opt-out handling, quiet hours and scrubbing. You build those yourself or bolt them on.

Plan-based (subscription) pricing

Tools like EZ Texting and SimpleTexting sell monthly plans with a bundle of credits. Per-seat business texting tools like Salesmsg and OpenPhone charge by user, with messaging bundled or capped. Plans are easy to budget for, and they work fine for a steady, predictable sender.

They hide cost in the gaps:

• Unused credits. Check whether they roll over or expire at the end of the month.
• Overage. Ask what one credit costs once you pass the plan, and whether it's higher than the in-plan rate.
• Credit math. Ask whether one credit equals one segment, or whether an emoji message eats several credits.
• Seats you don't need. A per-seat price makes a one-person bulk sender pay for collaboration features.

Carrier-fee pass-through pricing

The provider charges its own rate and lists the carrier fee as a separate line. This is the most legible model because you can see what the provider keeps and what the carriers take. It also looks more expensive at first glance, because the headline rate leaves the carrier fee out. Our longer breakdown of the carrier line item most providers bake into their per-message price covers this in detail.

Ready uses this model. Standard is $0.0075 per segment, sent or received, plus a $0.0045 carrier fee itemized separately. It's one flat rate. Billing is prepaid credits through Stripe, with carrier fees itemized on their own line.

The costs that don't show up on the pricing page

These apply regardless of model.

Segments, not messages

A GSM-7 SMS segment holds 160 characters. Past that, each segment holds 153. One emoji or other non-GSM character switches the whole message to unicode, which holds 70 characters per segment, or 67 when it's split. Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so those don't silently change your count. An emoji still does.

Inbound replies

Many providers bill replies. Ready bills a received reply like a sent text, at the per-segment rate plus the carrier fee. If your campaign asks people to reply, budget for it. Engaged, opted-in lists reply a lot, which is real volume.

Registration and numbers

Unregistered 10DLC traffic gets carrier-filtered, so registration isn't optional. On Ready it's $25/mo for registration and $2 per number. The first month, $25, is charged when you submit, and there is no setup fee. Most approvals take 2 to 7 days. Other providers charge similar underlying carrier fees but may add markup or a setup charge, so ask. Our 10DLC cost breakdown lists every fee line.

Compliance add-ons

TCPA exposure runs $500 to $1,500 per text, so scrubbing is worth pricing out. On Ready, litigator/DNC scrubbing and landline validation are each $0.003 extra per segment when switched on for an account. Both are off by default. The standalone TCPA and DNC Litigator Scrub is $0.005 per contact if you'd rather clean a list once. Scrubbing reduces risk but doesn't make you lawsuit-proof. Consent is still the sender's responsibility.

What you're not charged for

This is worth asking every provider about. Ready refuses opt-outs and numbers on your Ban list up front and doesn't charge for them. A held text is charged only when it actually sends. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.

A worked example: one campaign, real math

Assumptions: 5,000 opted-in contacts and a 175-character promo with one emoji, sent on Ready Standard.

• With the emoji, the message is unicode. 175 characters ÷ 67 per multipart segment = 3 segments.
• 5,000 × 3 = 15,000 segments.
• Ready rate: 15,000 × $0.0075 = $113, plus 15,000 × $0.0045 in carrier fees.

Now remove the emoji. 175 GSM-7 characters ÷ 153 = 2 segments.

• 5,000 × 2 = 10,000 segments.
• Ready rate: 10,000 × $0.0075 = $75, plus 10,000 × $0.0045 in carrier fees.

One emoji costs a third of the campaign. Neither total includes the compliance surcharge if you switch scrubbing on, or replies, which are billed on top.

The segment math works the same on any provider. Run your own template through it before comparing quotes, because a lower per-unit price multiplied by more segments can still lose.

Throttling: the cost nobody puts in dollars

Carriers don't publish an official rate card. Treat these as round approximations:

• Per-second rate. A fresh standard campaign with no vetting typically gets about 1 to 4 segments per second, per campaign. Higher use-case tiers get tens, roughly 10 to 75.
• T-Mobile daily brand cap. It scales with trust score: 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 rather than with a hard daily cap.

Here's how that plays out. The 15,000-segment emoji campaign above, at an assumed 3 segments per second, takes 5,000 seconds, which is about 83 minutes. Fine for a promo, but a problem for a "doors open at 9 AM" alert. At the lowest T-Mobile trust tier, T-Mobile recipients beyond roughly 2,000 that day wait.

Brand vetting ($79 Standard / $179 Enhanced, one-time) raises the trust score. It moves the daily cap only when it crosses a tier, and it doesn't change the per-second rate. Most senders don't need it. See when brand vetting is worth $79 for the break-even.

Questions to ask any bulk SMS provider

Send these before you sign. Vague answers are the answer.

Pricing

1. Is your rate per message or per segment? How do you count an emoji message?
2. Is the carrier fee included, and is it itemized on the bill?
3. Are inbound replies billed? At what rate?
4. Do I pay for messages to opted-out or invalid numbers?
5. For plans, do unused credits roll over, and what is the overage rate?

Registration

6. Who files the brand and campaign registration: me or you?
7. What are the monthly brand, campaign and per-number fees, and is there a setup fee?
8. How long do approvals usually take, and can I send anything while mine is pending?
9. What happens if a campaign is rejected? Do you help rewrite and resubmit?

Throttling and delivery

10. What per-second rate should I expect on a new campaign?
11. What's my T-Mobile daily cap at my trust score, and how do I see it?
12. If a campaign exceeds my throughput, is it queued or dropped?
13. Are quiet hours enforced automatically, based on the recipient's area?

For reference, here's how Ready answers questions 8 and 13. An account can send up to 500 texts a month before it registers, at its normal per-text rate. An account that bought its number before registering sends on Ready's shared registration while its own is in review. Quiet hours are enforced on campaigns, drip campaigns, automations, one-to-one texts and API sends, based on the recipient's area (a reply to someone who texted you in the last 24 hours can go out at any hour), and STOP replies propagate across all campaigns.

Where each kind of provider makes sense

• Raw CPaaS (Twilio, Telnyx, Plivo): the lowest per-segment price. This is the right pick if you have engineers to build registration flows, opt-out storage and quiet-hours logic yourself.
• GoHighLevel's LC Phone: lower per message and already inside GHL. It's fine for many agencies. Ready installs natively into GoHighLevel as an alternative if you want self-serve registration and itemized carrier fees.
• Plan-based tools: a good fit for steady senders who value a fixed bill over a per-unit price.
• Ready: a fit for businesses and platforms that want registration, compliance controls, an Inbox and bulk campaigns included, with an auditable bill. Platforms sending for their own customers get sub-accounts and a REST API. The bulk endpoint takes up to 100 recipients per call (docs).

The practical takeaway

Ignore the headline rate until you've done three things: counted your real segments, priced the monthly registration, and asked how replies and throttling are handled. The provider with the lowest number on the page isn't always the one with the lowest invoice, and the provider with the clearest invoice isn't always the lowest one either. Decide which tradeoff you're making on purpose.

If you want to test Ready, sign up with a card on file. Your first 20 one-to-one texts are free, so use them before you register. Campaigns are paid from the first text. Our pricing page shows the Standard rate, and what to check before picking a mass texting service covers the non-price side of the decision.