SMS billing depends on encoded character count, not just visible words.
Marketing, CX, and Ops teams using Broadcast → Create Campaign who need to predict SMS parts/credits and avoid accidental Unicode.
Encoding determines your character budget.
Message type | 1‑part limit | Multi‑part unit size* | Billing |
GSM‑7 (standard English + basic symbols) | 160 | 153 per part | 1 credit per part |
Unicode (regional scripts like Hindi/Bengali, or any emoji) | 70 | 67 per part | 1 credit per part |
* In multi‑part SMS, a small header is added so networks can stitch parts together, reducing the effective characters per part.
If your text exceeds 160 (GSM‑7) or 70 (Unicode) characters, it is sent as concatenated SMS (multi‑part). In concatenated mode:
Heads‑up: Very near the limit? Even adding a single character (or a hidden character) can push the message into 2 parts.
Any of the following switches your message from GSM‑7 to Unicode:
Tip: Compose in a plain‑text editor first, or replace smart characters with straight equivalents (" ' - ...).
1) Short English announcement (GSM‑7)Reminder: Your appointment is today at 5 PM. Reply YES to confirm.
Length well under 160 → 1 part (GSM‑7).
2) Over the GSM‑7 limit by 1 character
160‑char text + 1 extra → 2 parts of 153 each (total capacity 306).
3) Emoji includedSale today → 50% off! 🎉 includes an emoji → switches to Unicode → 70 chars max for 1 part.
4) Regional scriptआपका OTP 123456 है uses Devanagari → Unicode rules apply (70/67).
5) Smart punctuation from Word
Curly quotes/em‑dash may trigger Unicode. Replace with straight quotes/hyphen to stay on GSM‑7 where possible.
Message split unexpectedly
• Check for hidden Unicode (emoji, curly quotes, bullets, NBSP).
• Use a plain‑text editor or “Paste as plain text”.
Counter shows fewer characters than you typed
• In multi‑part mode the header reduces capacity per part (153/67). This is expected.
Counts differ from another tool
• Tools may normalize whitespace/line breaks differently. Rely on the in‑product counter.
Long URLs/UTMs blow up the length
• Use a link shortener. Avoid copy‑pasting formatted links from docs.
Variables/merge tags expand
• If you use placeholders (), preview with sample values to ensure you stay within expected parts.
Keep costs predictable
• Aim for ≤160 GSM‑7 or ≤70 Unicode whenever possible.
• Avoid emojis in high‑volume campaigns unless necessary.
Q: Do line breaks count as characters?
Yes. Newlines and spaces are characters and count toward the limit.
Q: Are delivery charges different for Unicode?
Billing is typically per part, regardless of encoding. The key difference is fewer characters per part in Unicode.
Q: Why did my 161‑character English message cost 2 credits?
Because exceeding 160 (GSM‑7) triggers multi‑part: now each part holds 153 characters.
Q: Can I force GSM‑7 if I need emoji?
No. Any emoji or non‑GSM character requires Unicode encoding.
Q: Does the preview show exact billing?
It shows parts/credits based on the text you enter. Final billing uses the same calculation.
Replace these with links to your live KB pages once available.