GoHighLevel SMS Segments: Character Limits & Cost (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 8 October 2026 · 9 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.
GoHighLevel SMS segments are the quiet line item that decides whether your agency's messaging is a profit centre or a slow leak. You're billed per segment, not per message, so one stray emoji or curly apostrophe can turn a single text into three billable units without anyone noticing.
This guide explains how the HighLevel SMS character limit actually works, why GSM-7 and Unicode behave so differently, how merge fields push templates over the line, and how to audit every client template before it eats your rebilling margin.
Quick Facts
| Billing unit | LC Phone calculates SMS charges per segment (HighLevel Help Centre, 2026) |
| GSM-7 single SMS | Up to 160 characters (Twilio docs, 2026) |
| GSM-7 per segment (long message) | 153 characters (Twilio docs, 2026) |
| UCS-2 / Unicode single SMS | Up to 70 characters (Twilio docs, 2026) |
| UCS-2 per segment (long message) | 67 characters (Twilio docs, 2026) |
| Twilio recommended SMS length | No more than 320 characters (Twilio docs, 2026) |
| Twilio maximum message body | 1,600 characters (Twilio error 21617 docs, 2026) |
What a GoHighLevel SMS segment actually is
A segment is a single unit of SMS transmission. When a message is too long to fit in one, the network splits it into several segments and the recipient's phone stitches them back together into what looks like one text.
HighLevel's own help article, How to Calculate SMS and MMS Costs, describes a segment as the unit LC Phone uses to calculate SMS charges. Its example is simple: a 160-character GSM-7 message is one segment, and a 161-character message is two.
The same article notes that once a delivery attempt has been made, charges apply whether or not the message is delivered. So a bloated template costs you on every send, including the ones that bounce.
HighLevel SMS character limit: GSM-7 vs Unicode (UCS-2)
Every SMS is encoded in one of two character sets. Which one your message lands in depends on every single character in it, not just most of them.
- GSM-7 covers standard English letters, numbers and common punctuation. It is the cheap, roomy option.
- UCS-2 (Unicode) covers emoji, curly quotes, many accented letters and non-Latin scripts. It holds far fewer characters per segment.
Long messages lose a few characters per segment because each part carries a header that tells the phone how to reassemble it. Twilio's SMS character limit documentation (2026) explains that this header leaves 153 GSM-7 characters or 67 UCS-2 characters per segment.
| Encoding | Single-segment limit | Per segment when split | 2 segments hold | 3 segments hold |
|---|---|---|---|---|
| GSM-7 (plain text) | 160 characters | 153 characters | 306 characters | 459 characters |
| UCS-2 (Unicode) | 70 characters | 67 characters | 134 characters | 201 characters |
Source: Twilio documentation (2026). Twilio also notes an exception for toll-free multi-segment messages to the US and Canada (152 and 66 characters per segment), which won't affect most Australian sends but matters if you run US clients.
The extended GSM-7 characters that count double
Some characters stay in GSM-7 but need an escape code, so they take two slots instead of one. Twilio's GSM-7 glossary (2026) gives braces and square brackets as examples.
They won't flip a message to Unicode, but a few in a near-full template can still force a second segment.
How one emoji or smart quote flips the whole message
This is the part that surprises agency owners. Twilio's documentation (2026) states that if any non-GSM-7 character appears in the body, the entire message falls back to UCS-2, not just the character itself.
The usual culprits are rarely deliberate. Twilio specifically calls out text editors that swap a straight quote for a "smart" curly quote, cutting the single-message limit from 160 to 70 characters.
- Emoji added for "friendliness" in reminder templates
- Curly apostrophes and quotes pasted from Google Docs, Word or Notion
- Long dashes (en and em dashes) that editors insert automatically
- Accented names pulled in via a merge field, such as a client called Zoë or Renée
- Bullet symbols or ellipsis characters copied from a website
Twilio's Smart Encoding can swap some of these for GSM-7 equivalents, but don't assume it is doing that work inside HighLevel. Clean the template at the source.
Worked examples: message → encoding → segments
Here is the same dental appointment reminder written five ways. The counts assume the GSM-7 and UCS-2 limits above.
| Message version | Characters | Encoding | Segments |
|---|---|---|---|
| "Hi Sarah, your appointment at Bright Smiles Dental is confirmed for Tue 14 Oct at 10:30am. Reply C to confirm or R to reschedule. Reply STOP to opt out." | 152 | GSM-7 | 1 |
| Same message with a smiley emoji replacing the full stop after "10:30am" | About 153 | UCS-2 | 3 |
| Same message rewritten to start "Hi Sarah, we're confirming…" with a curly apostrophe in "we're" | 156 | UCS-2 | 3 |
| Plain-text version where the merge fields resolve to "Alexandra-Louise" and "Bright Smiles Family & Cosmetic Dental Clinic" | 188 | GSM-7 | 2 |
| "Hi Sarah, appt confirmed: Tue 14 Oct, 10:30am, Bright Smiles Dental. Reply C to confirm, R to reschedule, STOP to opt out." | 122 | GSM-7 | 1 |
Rows two and three are the expensive lesson. A message that comfortably fits in one GSM-7 segment needs three UCS-2 segments, because anything over 134 Unicode characters spills into a third.
How custom values and merge fields lengthen messages
What you see in the template editor is not what gets sent. Merge fields like the contact's first name, a business name or a booking link are replaced with real values at send time, and the segment count is based on the rendered message.
That means the same template can be one segment for "Sam" and two for "Alexandra-Louise". Twilio's error documentation (2026) makes the same point: check the rendered body after template substitution, not the template itself.
If you manage business names, addresses and booking URLs through GoHighLevel custom values, audit them too. A long business name in a custom value adds characters to every SMS that uses it, across every workflow in that sub-account.
Why segments multiply LC Phone and Twilio cost
Because billing is per segment, segment count is a straight multiplier on your messaging spend. A campaign to 1,000 contacts at one segment is 1,000 billable units; the same campaign at three segments is 3,000.
The per-segment rate depends on the destination country, number type and provider, so we won't quote one here. Check your current LC Phone rates in Settings, and if you're weighing providers, our breakdown of LC Phone vs Twilio cost and setup walks through the trade-offs.
Where segment counts really hurt is in high-volume automations: appointment reminders, nurture sequences, review requests and especially a database reactivation campaign that blasts thousands of old leads in a day.
What it does to your rebilling margin
If you resell messaging to clients, segment bloat affects you in two ways. If you rebill usage with a markup, clients see a bigger bill and start asking questions. If you bundle messaging into a flat monthly fee, the extra segments come straight out of your margin.
Either way, the fix is the same. Set up rebilling with a sensible markup, then make sure every template your snapshot ships with is segment-efficient before it reaches a client sub-account.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
How to audit your GoHighLevel SMS templates
- List every SMS source. Workflow SMS actions, saved templates, campaign steps, trigger links and auto-replies like your missed call text back.
- Paste each message into a plain-text editor. Look for emoji, curly quotes, long dashes, ellipsis characters and bullet symbols.
- Retype quotes and dashes by hand. Replace curly quotes with straight ones and long dashes with a hyphen.
- Estimate the rendered length. Swap merge fields for the longest realistic values in that account, not the shortest.
- Send a test to yourself. Check the message details in the conversation to confirm the segment count before going live.
- Record the target. Note "1 segment" or "2 segments" against each template so future edits get checked against it.
Twilio also offers a Message Segment Calculator that flags characters forcing UCS-2 encoding, which is handy for checking a template before you paste it into HighLevel.
MMS vs SMS: when a picture is worth the price
MMS lets you send images, and HighLevel's cost article covers MMS separately because it isn't priced the same way as SMS segments. Check your current LC Phone rates in Settings for both before choosing.
- Use MMS when the image does the selling: a product photo, an event flyer or a before-and-after shot.
- Use SMS for reminders, confirmations, two-way follow-up and anything transactional.
Writing short: the one-segment habit
Twilio recommends keeping SMS to no more than 320 characters for deliverability and user experience. For agency templates, aim tighter: one GSM-7 segment for reminders and confirmations, and two at most for campaigns.
- Lead with the action: what, when and what to reply.
- Cut greetings and sign-offs that repeat what the sender name already shows.
- Use abbreviations people recognise, like "appt" or "Tue", but not jargon.
- Keep the opt-out wording clear and short; don't trim compliance text to save a segment.
- Drop the emoji. Warmth comes from the wording, not the smiley face.
Common mistakes to avoid
- Testing templates with a short merge-field value like "Sam" and assuming every send will match.
- Drafting SMS copy in Google Docs or Word and pasting in curly quotes and long dashes.
- Adding emoji to high-volume reminders where one segment becomes three.
- Shipping snapshots with unchecked templates into every new client sub-account.
- Bundling unlimited SMS into a flat retainer without knowing your average segments per message.
- Cutting opt-out wording to squeeze into one segment and creating a compliance problem.
If you want an SMS template audit and rebilling setup that protects your margins, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
How many characters fit in one GoHighLevel SMS segment?
A plain-text GSM-7 message fits up to 160 characters in a single segment. If the message is longer, it is split into segments of 153 characters each. If the message contains any Unicode character, the limits drop to 70 characters for a single segment and 67 per segment when split, according to Twilio's documentation.
Why did my 150-character SMS cost three segments?
It almost certainly contains a Unicode character such as an emoji, curly quote or long dash. One non-GSM-7 character switches the whole message to UCS-2 encoding, which holds only 67 characters per segment once a message is split. A 150-character Unicode message therefore needs three segments.
Do merge fields affect the HighLevel SMS character limit?
Yes. Segments are counted on the message after merge fields and custom values are replaced with real data. A template that fits one segment for a short first name can become two segments for a long name, business name or URL.
Am I charged for SMS that fail to deliver?
HighLevel's help article on SMS and MMS costs says LC Phone does not charge if an internal error happens before the message is handed to the carrier. Once a delivery attempt has been made, charges apply whether or not the message is delivered. That makes cleaning templates before sending even more important.
What does LC Phone charge per SMS segment?
Rates vary by destination country, number type and over time, so check your current LC Phone rates in Settings rather than relying on a figure from a blog post. Whatever the rate, your total cost is that rate multiplied by the number of segments sent.
Is MMS cheaper than a long SMS?
Not necessarily. MMS is priced differently from SMS segments, so compare your current LC Phone rates for both in Settings. Use MMS when an image genuinely improves the message, and keep transactional messages as short SMS.
How do I check how many segments a message used?
Send a test message to your own phone from HighLevel and review the message details in the conversation. You can also paste the text into Twilio's Message Segment Calculator, which flags any characters forcing Unicode encoding.
Related Articles on HL Growth Partner
Agency billing and margins
- GoHighLevel agency wallet and auto-recharge
- GoHighLevel SaaS mode setup and pricing
- GoHighLevel premium workflow actions and costs
