Twilio SMS pricing: toll-free, short code and hidden costs decoded

Twilio's headline SMS rate is low, around $0.0083 per segment for US traffic. If you're building a budget for a product that texts on behalf of your customers, that number is real but incomplete. The full invoice also includes carrier fees, number rental, registration, inbound messages, and a sender type (10DLC, toll-free or short code) that changes the cost structure. Then there's the engineering work Twilio doesn't do for you.

This post goes through each line so you can estimate Twilio spend accurately. Then it compares that spend to a flat-rate platform like Ready, which we make. Twilio is lower per segment, and we'll say so directly. The comparison is about what each price includes.

The per-message API cost and the multiplier inside it

Twilio bills per segment. Every provider does, because carriers do. The per-message figure only means something once you know how many segments your messages use.

• A single segment is 160 GSM-7 characters.
• Longer messages split into 153-character parts, each billed.
• One emoji or other non-GSM character switches the message to unicode: 70 characters for a single segment, 67 per part for multipart.

A worked example, with the assumptions stated: a 175-character promo in plain text is 2 segments (153 + 22). Add one emoji and the same promo is 3 unicode segments (67 + 67 + 41). That's 50% more segments for one character, at any provider.

Curly quotes and long dashes pasted from a doc can cause the same jump. Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so on Ready they never change the count. Whatever you choose, check your templates, because segment count is usually a bigger cost lever than the provider's rate.

Inbound messages are also billed on most CPaaS platforms, Twilio included. If your use case is conversational, budget for replies as well as sends.

Carrier fees: the line that's never in the headline

The ~$0.0083 is Twilio's rate. US carriers add their own per-message fees for application-to-person traffic. Twilio passes these through as a separate line, and they vary by carrier and sender type.

This is normal across the industry, not unique to Twilio. The underlying carrier cost is similar wherever you send from. It matters because comparing headline rates across providers mixes "rate with carrier fees included" and "rate with carrier fees on top." We cover this in detail in the carrier fee post.

Ready lists the carrier fee separately as well: $0.0075/segment on the Standard rate, plus a $0.0045 carrier fee per segment, itemized on the bill.

10DLC vs toll-free vs short code on Twilio

The sender type affects your fixed costs, throughput and approval timeline. Here is the qualitative breakdown. Check Twilio's pricing page for its current figures, since we only cite the per-segment rate above.

Short codes: when the lease makes sense

A short code is the only option where the fixed fee can exceed your message spend for months. It makes sense when you send at volumes that would otherwise run into 10DLC daily caps. For context, T-Mobile caps 10DLC brands at roughly 2,000 to 200,000 messages a day depending on trust score. Short codes also suit cases where you need a memorable five- or six-digit code for keyword opt-ins.

For a platform sending on behalf of dozens or hundreds of small customers, a short code is usually the wrong tool. Each customer needs its own sender identity, and one shared short code doesn't provide that.

Toll-free: no 10DLC fees, but not free of process

Toll-free avoids the 10DLC brand and campaign fees, which makes it look cheaper up front. You still need verification, and unverified toll-free traffic faces heavy filtering. For a fuller comparison of when each sender type fits, see 10DLC vs toll-free vs long code vs RCS.

The hidden costs on a Twilio invoice

These are the lines buyers most often leave out of a first estimate:

1. Number rental, per number per month. A platform with local numbers for each customer multiplies this fast.
2. 10DLC registration fees for each brand and campaign, passed through from the carrier registry. These apply on any provider, and our 10DLC cost breakdown lists every one.
3. Inbound segments for every reply.
4. Failed-message handling. Check whether failed or undelivered messages carry a processing fee on your account.
5. Number lookup and validation, priced as a separate product.
6. Engineering time. This is the largest cost, and it never shows up on the Twilio invoice.

Point 6 deserves its own section.

What Twilio leaves for you to build

Twilio is a CPaaS. It gives you excellent primitives and expects you to assemble the product. For a platform texting on behalf of customers, the assembly list typically includes:

• Sub-account and registration flows: collecting each customer's brand details, submitting brand and campaign registrations, handling rejections and resubmissions, and showing status in your UI.
• Opt-out propagation: making sure a STOP to one campaign blocks that contact everywhere.
• Quiet hours: holding sends outside permitted hours in the recipient's local time.
• DNC and litigator scrubbing: screening numbers before a send, a common source of TCPA exposure at $500 to $1,500 per text.
• Landline validation, so you aren't paying to text numbers that can't receive SMS.
• Idempotency and retry logic, so a retried request doesn't double-send.

None of this is unusually hard. All of it costs engineer-weeks to build and ongoing time to maintain as carrier rules change. Price those weeks at your own loaded engineering rate before you compare invoices.

Worked example: a platform with 50 sub-accounts

Assumptions: a SaaS platform with 50 customers. Each has its own registered brand, one campaign and one number, and each sends 2,000 segments a month. That's 100,000 segments/month in total, with no emojis and replies included in the count.

Twilio messaging (rate only): 100,000 × $0.0083 = $830/mo, plus carrier fees, number rental and registration fees per the sections above.

Ready messaging (Standard rate): 100,000 × $0.0075 = $750/mo, plus 100,000 × $0.0045 carrier fee.

Ready registration (applies to each sub-account): $25/mo for registration and $2/mo per number, for each of the 50 sub-accounts

Registration and carrier fees exist on Twilio too, so the part of the gap that comes from the rate is about −$80 a month ($750 − $830). That's the real question to answer: is −$80 a month more or less than what it costs you to build and maintain registration flows, opt-out propagation, quiet hours, scrubbing and validation yourself?

Two notes on the Ready side:

• The all-in figure above (rate + carrier fee) excludes the compliance surcharge. DNC/litigator scrubbing and landline validation each cost $0.003 extra per segment when switched on for an account. Both are off by default.
• The standalone TCPA & DNC litigator scrub, used to clean a list before sending, is $0.005 per contact.

If your team has already built this infrastructure, or messaging is your core product and you want full control, Twilio's rate wins and you should stay. If you're a CRM or vertical SaaS where texting is one feature among many, the build cost is usually the larger number.

What the flat rate includes on Ready

For the platform buyer, this is what the $0.0075/segment Standard rate covers:

• Sub-accounts with their own numbers and 10DLC registration, submitted in-app or through the API (registration docs). Registration has no setup fee; the first month ($25) is charged at submit, and most approvals take 2 to 7 days.
• One REST API for SMS, plus the iMessage blue line as an add-on. Sends use POST /v1/messages with an Idempotency-Key header, so retries never double-send (messages API).
• Automatic STOP handling that propagates across campaigns. Opted-out and numbers on your Ban list are refused up front and not charged.
• Quiet-hours enforcement. Sends held during the recipient's quiet hours go out later and are only charged when they send. 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 with 409 QUIET_HOURS_BLOCK and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• Consent attestation logging for each bulk send and each API send that sets consent_attested, recording who sent, to how many and when. This builds an audit trail of your sends, not per-contact consent records; your opt-in source still holds those. Compliance remains the sender's responsibility, and these tools reduce risk rather than eliminate it.
• Validation and scrub endpoints (GET /v1/validate/:phone, GET /v1/scrub/:phone) when you want them.
• Local presence, which sends from the account's number closest to the contact's area code. Every number still sits on the registered campaign.

There's no volume discount and no tiers. Enterprise pricing is negotiated, so talk to us if you're at that scale. For other options in the same category, see our developer SMS API comparison and the honest Twilio alternatives cost breakdown.

The practical takeaway

To estimate Twilio spend properly:

1. Count segments, not messages, and audit templates for emojis and non-GSM characters.
2. Add carrier fees, number rental, registration and inbound to the headline rate.
3. Choose a sender type based on volume and fit. Short codes rarely make sense for a multi-tenant platform.
4. Price the engineering work for registration, opt-outs, quiet hours and scrubbing at your real rate.

If step 4 comes to less than the rate gap, Twilio is the right choice. If it doesn't, try Ready on your own traffic. The first 20 one-to-one texts are free (a card on file is required to send), so use them to test before you register. Create an account and send a few from the API.