An SMS segment is the unit carriers use to measure, deliver, and bill text messages. Each segment can hold a limited number of characters, which depends on the type of encoding used. Messages that exceed this limit are split into multiple segments, similar to sending a long letter across several postcards. Carriers treat each segment as a separate message for delivery and billing, so every segment is counted and charged individually. This billing method is determined by carriers and is not specific to MyTime. SMS segment rules apply to all messages sent to clients through Communicator, as well as automated notifications and marketing campaigns.
This article explains encoding standards, how segments are calculated, and how factors like message length and emojis can affect the total number of segments.
Things to know:
Encoding Standards
GSM Encoding:
GSM-encoded messages (standard letters, numbers, and symbols) allow up to 160 characters per segment.
If the message is longer than 160 characters, it will be split into concatenated segments of 153 characters each.
UCS-2 Encoding:
UCS-2 messages (special characters, emojis, or non-Latin alphabets) allow up to 70 characters per segment.
If the message is longer than 70 characters, it will be split into concatenated segments of 67 characters each.
Even a single emoji forces UCS-2 encoding, reducing per-segment capacity and potentially doubling the number of segments.
Note: Concatenation headers are hidden data that let the recipient’s phone reassemble multiple segments into a single message.
Segment Calculation & Billing:
SMS costs are calculated per segment, not per message.
Segments per message are based on length and encoding
Recipients: Each recipient receives their own copy, so the number of segments per message is multiplied by the number of recipients to calculate billing.
Example: A 2-segment message sent to 50 recipients counts as 100 billable segments. If each segment costs $0.02, the total cost would be 100 × $0.02 = $2.00.
CONTENTS
Sample Messages
Example 1 – Appointment Reminder
"Just a friendly reminder that your appointment with Spa & Beauty Salon is on Sept 9 at 3:00 PM.”
- Characters: 95
- Segments: 1
Example 2 – Appointment Confirmation with Emoji
“Thanks for booking with Spa & Beauty Salon ✨! We look forward to seeing you on Sept 9 at 3:00 PM.”
- Characters: 97 (UCS-2 due to ✨)
- Segments: 2 (67 + 30)
Example 3 – Long Marketing Message
Book your next appointment at Spa & Beauty and enjoy 20% OFF when you use promo code RELAX20 at checkout. Offer valid Sept 9–15, 2025, at our Lauderdale Lakes location, 2709 NW 30th Ave. Appointments are filling fast—reserve your spot today!
- Characters: 240
- Segments: 2
Calculating SMS Segments for Bulk Messages
The table below shows how the segments in the examples above are calculated. The cost is based on the assumption of $0.05 per segment. Please note that these values are for illustrative purposes only and do not reflect the actual amount you will be charged. Your actual cost will be determined by the rates stated in your contract.
Message Type | Characters | Encoding | Segments per Message | Recipients | Total SMS Segments | Cost $ |
---|---|---|---|---|---|---|
Appointment Reminder | 95 | GSM | 1 | 50 | 50 | $2.50 |
Appointment Confirmation with Emoji | 97 | UCS-2 | 2 | 50 | 100 | $5 |
Long Marketing Message | 240 | GSM | 2 | 50 | 100 | $5 |
Tips for Reducing SMS Segments
To minimize SMS segments and manage costs effectively:
- Keep messages short: Try to stay under 160 GSM characters whenever possible.
- Limit emoji use: Emojis switch the message to UCS-2 encoding, which drastically reduces the number of characters per segment.
- Test your campaigns: Check how many segments a message will consume before sending a bulk SMS blast.
- Balance clarity and cost: Ensure key information (date, time, location) fits within the first segment.
For more information, contact us at support@mytime.com or (385) 233-6964.
Related Articles:
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article