One of the most common support questions goes like this: two campaigns with the same text, sent to the same list, and the second one cost two or three times more. The texts were not the same. Somewhere between the two, the copy went through a word processor or a design tool, and a straight apostrophe came back curly.
Why one character changes the price
SMS has two encodings. GSM-7 holds 160 characters (153 per part when concatenated); it covers unaccented Latin letters, digits, common punctuation and a few accented letters. UCS-2, the Unicode encoding, holds 70 characters (67 per part when concatenated). A message is encoded as a whole: one character outside the GSM-7 alphabet switches every character of the message to Unicode.
A 150-character text fits in one GSM-7 segment. The same text with a single curly apostrophe needs three Unicode segments, because 150 characters at 67 per part make three parts. Since every segment is billed, the message costs three times as much, on every number of the list.
The usual suspects
These characters look harmless and are not in GSM-7:
- Curly quotes and apostrophes: ‘ ’ “ ” instead of ' and ".
- Long dashes: – and — instead of a hyphen.
- The ellipsis character … instead of three dots.
- Non-breaking and other special spaces, invisible in most editors.
- Bullets such as • and arrows such as →.
- Emoji of any kind.
- Accented letters outside the GSM-7 set, such as á, í, ó, ú, â, ê or ô.
A second trap is the GSM extension table: the characters ^ { } \ [ ] ~ | and € are allowed in GSM-7 but each one takes two positions, so a text full of brackets reaches the limit sooner than its length suggests.
What the composer does
The segment counter in the composer shows the encoding and the number of segments as you type. When a character forces Unicode, it names the character and offers to replace the usual suspects, curly quotes, long dashes, the ellipsis character and special spaces, with their GSM-7 equivalents in one click. The API never rewrites your text; it returns encoding and segments in the response so your own code can decide.
Checklist for single-segment copy
- Write in a plain-text editor, or paste as plain text.
- Straight quotes, plain hyphen, three dots rather than the ellipsis character.
- No emoji in transactional messages.
- Preview with the longest real row, not the template: a long name or address can tip a message over the limit.
- Check the segment count of the preview before every send, not only the first one.
Non-Latin scripts
For languages written in Cyrillic, Arabic, Chinese, Thai and most other scripts, none of this applies: Unicode is the cost of the script. The right move there is to write for one or two clean segments, 70 or 134 characters, rather than one and a half. The guide to GSM-7 and Unicode has the full character tables and worked examples.


