SMS template variables make segment counts drift: the same template can be one segment for most contacts and three for a few, because a name, date or business field changes the length, and a single accented letter can switch the whole message to unicode. You pay per segment, so the price of a template isn't one number. It's a range, and you should know the top of it before launch.

This post walks through the math with one template, shows what a name like "Zoë" does, and gives a short routine for computing the worst case per template.

The two limits that matter

A GSM-7 message holds 160 characters in one segment, then 153 per segment once it's split. A message with any character outside GSM-7, such as an emoji or a letter like ë, becomes unicode: 70 characters in one segment, then 67 per segment. Ready swaps curly quotes, long dashes and ellipses for plain ones before sending, so those never change the count. The deeper rules are in SMS character limits and segments.

Common accented letters such as é, ü and ñ are in GSM-7. Others, like ë, ç in lowercase or any Polish or Vietnamese letter, are not. Don't guess. Test the characters you expect.

A worked template

Assume this template (the fixed text is 76 characters):

Hi {first_name}, this is {business}. Your visit is on {date} at {time}. Reply C to confirm or R to reschedule.

Typical fields: a 4-character name, "Acme Dental" (11), "Tue, Mar 3" (10) and "2:30 PM" (7). That's 108 characters. The worst case I'll assume: a 20-character name, a 30-character business, a 23-character date and an 8-character time, which gives 157.

Ready adds "Reply STOP to opt out" and the business name to the first text to each contact, unless the account turns that off. I'll assume the footer adds 23 characters. Count the real footer on a real first text before you trust the number.

CaseCharactersGSM-7 segmentsWith one ë (unicode)
Typical10812
Typical, first text with footer13112
Worst case15713
Worst case, first text with footer18023

The same template ranges from 1 to 3 segments. One accented name turned a 108-character text from 1 segment to 2.

What it costs

Segments are billed at $0.0075 plus a $0.0045 carrier fee, $0.012 all-in per segment, which excludes screening. For 10,000 sends a month: 10,000 x 1 x $0.012 = $120.00 if every send is one segment. At the worst case of 3 segments, 10,000 x 3 x $0.012 = $360.00. A budget built on the typical row can be off by 3x. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing; the current card is on the pricing page.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Emoji and the UTF-16 trap

One emoji flips the entire message to unicode, and many emoji take two code units, so each one eats two of your 70. If your counter uses string length in JavaScript, that matches. If it counts visible characters, it'll undercount. For a working counter, see an SMS segment counter in code.

Estimate the worst case per template

You can do this at template save time, before anything is sent. The idea in pseudocode:

function worstCase(template, maxLength, alphabet, footerLength):
    fixed = length(template without its {fields})
    total = fixed + sum(maxLength[f] for each field f in template) + footerLength
    unicode = any field f where alphabet[f] allows non-GSM characters
              or template contains a non-GSM character
    return segments(total, unicode)

function segments(n, unicode):
    single = unicode ? 70 : 160
    part = unicode ? 67 : 153
    if n <= single: return 1
    return ceil(n / part)

You need a maximum length per field, which is a decision about your data: cap names at 20 and business names at 30, or truncate when you fill the template. The alphabet flag is where you decide whether a field can hold characters outside GSM-7. When in doubt, assume it can, since names are the usual source. Show the result in your template editor as a range: "1 to 3 segments".

If a worst case is more expensive than you like, shorten the fixed text, truncate fields, or drop the emoji. Fewer characters is the cheapest fix.

Frequently asked questions

Does one accented character change the whole message?

Only if it's outside GSM-7. Then every character in the message counts against the 70 limit, not just that one.

Does the opt-out footer count?

Yes. Unless the account turns it off, Ready adds "Reply STOP to opt out" and the business name to the first text to a contact and again from time to time, and those characters count.

Should I plan for the worst case or the average?

Budget on the average, alert on the worst case. The worst case tells you what a bad day costs.

Next step

Run your five most-used templates through the routine above. If you want to send them, sign up and check the counts in a real send.