This GoHighLevel SMS segment calculator counts how many billable segments a text will use before you send it: paste the message, and it shows the encoding (GSM-7 or Unicode), the segment count, the characters that forced Unicode, and the cost at HighLevel's $0.00747 per segment. One curly apostrophe can turn a one-segment reminder into three. HighLevel shows a segment counter when you write a single message in Conversations, but a feature request from January 2025 notes there is none for bulk SMS, and workflow message boxes do not expand merge fields while you type. This calculator covers both gaps. It runs in your browser and sends nothing anywhere.
| Characters, as sent | 0 |
| Encoding | GSM-7 |
| Limit for one segment | 160 |
| Per part, if split | 153 |
| Merge fields found | 0 |
| Characters that forced Unicode | None |
| Segments for all recipients | 0 |
| LC Phone cost at $0.00747 a segment | $0.00 |
How does the GoHighLevel SMS segment calculator count segments?
The GoHighLevel SMS segment calculator applies the same carrier rules LC Phone bills by: 160 GSM-7 characters or 70 Unicode characters fit in one segment, and longer texts split into smaller parts.
| Encoding | One segment holds | Each part of a longer text holds | Toll-free numbers, per part (US and Canada) | Source |
|---|---|---|---|---|
| GSM-7 (plain letters, numbers, basic punctuation) | 160 characters | 153 characters | 152 characters | Twilio: SMS character limit |
| Unicode, UCS-2 (emoji, curly quotes, non-Latin scripts) | 70 characters | 67 characters | 66 characters | HighLevel: How to calculate SMS and MMS costs and Twilio |
| GSM-7 extended characters: ^ { } \ [ ~ ] | € | Each counts as 2 of the 160 | Each counts as 2 of the 153 | Same | GSM 03.38 character set |
A longer message holds fewer characters per part because each part carries a small header that tells the phone how to put the pieces back together. That is why 161 plain characters bill as two segments, and 307 bill as three. HighLevel's help article confirms the switch: "The platform automatically switches to UCS-2 encoding whenever an SMS includes characters outside the GSM-7 set." That article was modified on July 23, 2026.
The calculator also handles two details the simple "divide by 160" method misses. An extended GSM character such as € is never split across two parts, and an emoji takes two of the 70 Unicode slots, not one.
Why is my GoHighLevel text 2 segments when it looks short?
A GoHighLevel text that looks short usually bills as 2 or more segments because one character outside GSM-7 switched the whole message to Unicode, cutting the limit from 160 to 70.
| Symptom | Cause | Fix |
|---|---|---|
| A 100-character reminder bills as 2 segments | A curly apostrophe (’) or curly quote pasted from Word, Google Docs or a phone keyboard | Retype the apostrophe as a straight ' or press "Replace with plain characters" above, then paste the clean text back into the workflow |
| Adding one emoji triples the count | Emoji are Unicode, and each takes 2 of the 70 slots | Remove the emoji, or keep the whole message under 67 characters per part on purpose |
| A message with a dash bills as Unicode | An em dash (—) or en dash (–), often added by autocorrect or AI writing tools | Use a plain hyphen (-) or a comma |
| The count is higher than the characters you can see | Hidden characters such as a non-breaking space or a zero-width space from copied text | Paste the text here; hidden characters show by name in the "forced Unicode" row |
| Test sends are 1 segment, real sends are 2 | Merge fields such as {{contact.first_name}} expand to the real value at send time, and long names, company names or links push the text past 160 | Set "assumed characters per merge field" to your longest realistic value and trim the fixed text |
| A text with € or [ ] goes over 160 at 155 characters | Extended GSM characters count as 2 | Write "EUR" instead of €, and use ( ) instead of [ ] |
After you fix the text, confirm it in the account: open the contact's Conversations tab, paste the message into the reply box and read the segment counter HighLevel shows before you send. Then copy the same clean text into your workflow's Send SMS action.
What does each SMS segment cost in GoHighLevel?
Each SMS segment costs $0.00747 on LC Phone in the US and Canada, inbound and outbound, according to HighLevel's LC Phone pricing guide modified October 12, 2026.
The calculator multiplies segments by recipients by that rate. Carrier fees are charged on top of it by the recipient's carrier; HighLevel's guide gives examples of $0.0035 (AT&T) and $0.0045 (T-Mobile) per outbound text, and the calculator shows that range as a separate note instead of adding it to the total. MMS is priced differently, at $0.0220 per outbound segment. For every rate, A2P fees and a monthly worked example, see GoHighLevel SMS and email costs, and to price a whole month of usage use the GoHighLevel cost calculator.
Worked examples: one reminder, three different bills
The same dental appointment reminder sent to 500 patients costs $3.74, $7.47 or $11.21 at LC Phone rates, depending only on punctuation and one emoji.
| Version of the reminder | Characters | Encoding | Segments | 500 recipients at $0.00747 |
|---|---|---|---|---|
| "Hi Jennifer, this is Bright Smile Dental. Reminder: your cleaning is tomorrow at 10:30 AM. Reply C to confirm or R to reschedule." | 129 | GSM-7 | 1 | $3.74 |
| Same, with "Hi Jennifer! 😊" at the start | 131 (emoji counts as 2, so 132) | Unicode | 2 | $7.47 |
| Same wording rewritten as "you’re booked for a cleaning" with a curly apostrophe | 141 | Unicode | 3 | $11.21 |
| The plain version plus a directions link | 179 | GSM-7 | 2 | $7.47 |
Carrier fees are left out of the table. The names, wording and link are illustrative; the counts come from running each version through the calculator above. In a reminder workflow that sends two or three texts per booking, the difference compounds, which is why we check segment counts when we build GoHighLevel appointment reminders.
What is the GoHighLevel SMS character limit?
The GoHighLevel SMS character limit for one segment is 160 plain GSM-7 characters or 70 Unicode characters; longer texts still send, but bill as several segments.
A longer text arrives as one message on the recipient's phone in most cases, so the limit is about cost, not about delivery. Twilio recommends keeping SMS under 320 characters, which is about two plain segments, for deliverability and readability. Very long texts also make carrier filtering more likely when the wording looks promotional, so keep the message to one job: confirm, remind or ask one question. If texts are being blocked rather than billed high, the cause is usually registration, covered in GoHighLevel A2P 10DLC registration rejected.
GSM-7 vs Unicode SMS: which characters are safe?
GSM-7 safe characters are the English letters, digits, common punctuation and a short list of accented letters; anything else, including emoji and curly quotes, switches the message to Unicode.
- Safe, count as 1: A to Z, a to z, 0 to 9, space, line break, and @ £ $ ¥ ! " # % & ' ( ) * + , - . / : ; < = > ? _ § ¿ ¡, plus é è ù ì ò à Ç Ä Ö Ñ Ü ä ö ñ ü ø Ø å Å æ Æ ß É.
- Safe, count as 2: ^ { } \ [ ~ ] | €.
- Force Unicode: emoji, curly quotes and apostrophes (’ “ ”), em and en dashes, the ellipsis character (…), bullets (•), most accented letters not in the list above (for example á, í, ó, ú, ç), and non-Latin scripts.
If your audience reads Spanish, note that á, í, ó and ú are not in GSM-7, so a Spanish reminder will usually be Unicode. In that case write for 67 characters per part, or accept the extra segments as the cost of correct spelling.
What this calculator does not count
This calculator does not count MMS, carrier fees in the total, A2P registration fees, or inbound replies, so the figure is the outbound segment cost only.
Some carriers and providers also replace certain Unicode characters with plain ones automatically. Twilio calls this Smart Encoding. We could not confirm from HighLevel's documentation whether LC Phone does this for your account, so the calculator assumes no substitution and shows the worst case. Treat the result as an estimate, and check your actual usage in the account's billing report after the first send.
Sources and further reading
Checked at the time of writing; prices and limits change. Checked 2026-10-27.
- HighLevel: How to Calculate SMS and MMS Costs: 160 GSM-7 and 70 UCS-2 characters, 67 per part, automatic switch to UCS-2 (help article, modified July 23, 2026)
- HighLevel: LC Phone Pricing and Billing Guide: $0.00747 per SMS segment, carrier fee examples, MMS rate (help article, modified October 12, 2026)
- Twilio: What is the SMS character limit?: 153 and 67 per part, User Data Header, toll-free 152 and 66, Smart Encoding, 320-character guidance (read 2026-10-27)
- GSM 03.38 character set: the GSM-7 basic alphabet and the extension table (read 2026-10-27)
- HighLevel ideas board: Character and segment calculator for bulk SMS: request posted January 20, 2025, noting the counter exists only for individual messages in Conversations (read 2026-10-27)
Frequently asked questions about GoHighLevel SMS segments
How many characters is one SMS segment in GoHighLevel?
One SMS segment in GoHighLevel holds 160 characters when the text uses only GSM-7 characters, or 70 characters when it contains any Unicode character such as an emoji or a curly quote. Longer messages split into parts of 153 or 67 characters, and each part is billed as one segment.
Does GoHighLevel charge per message or per segment?
GoHighLevel charges LC Phone texts per segment, not per message. A text that splits into three segments is billed three times at $0.00747 each in the US and Canada, plus carrier fees. Inbound replies are billed per segment at the same rate, so long replies from contacts cost more too.
Do emoji cost more in GoHighLevel texts?
Emoji cost more in GoHighLevel texts because a single emoji switches the whole message to Unicode, which cuts one segment from 160 characters to 70. A 130-character reminder that would be one segment becomes two segments with one emoji added. Each emoji also uses two of the 70 slots.
Do merge fields change the segment count?
Merge fields change the segment count because HighLevel replaces them with the contact's real data at send time. The token {{contact.first_name}} is 22 characters in the editor but may become a 4-letter name or a 14-letter one. Count your longest realistic value, which is what the merge field setting in the calculator does.
Where is the segment counter inside GoHighLevel?
GoHighLevel shows a character and segment counter in the Conversations reply box when you send an individual text. A HighLevel ideas-board request from January 2025 notes there is no equivalent for bulk SMS, so check bulk and workflow messages by pasting them into a single conversation or into this calculator first.
Why did a text I copied from Google Docs cost three segments?
A text copied from Google Docs or Word often carries curly apostrophes, curly quotes and dashes that are not GSM-7 characters. One of them forces Unicode, so a 141-character message needs three 67-character parts instead of one 160-character segment. Retype the punctuation or use the replace button in the calculator.
Are carrier fees included in the calculator's cost?
Carrier fees are not included in the calculator's main cost, because they vary by the recipient's carrier. The calculator shows them as a separate range using HighLevel's own examples of $0.0035 for AT&T and $0.0045 for T-Mobile per outbound text. Your billing report shows the real fees after sending.
Can you check the texts in our workflows for us?
We can check the texts in your workflows on a free 30-minute call, reading the Send SMS actions and your usage report together to find messages that bill more segments than they should. The first call and the audit are free; see the GoHighLevel audit for what we review.