Check which characters push an SMS into another segment
Admin ·
Check which part consumes the last available slot before rewriting a message. Review the payload units and exact boundaries, especially when a draft includes smart punctuation, currency symbols or emoji.
Follow a euro sign across the multipart boundary
Choose One message and load the example. It contains 152 letters a, one euro sign and seven letters b. The screen reports 160 code points and 161 GSM septets.
For the 8-bit concatenation reference, part 1 uses 152 of its 153 septets. The euro sign needs two septets together, so part 2 begins with € and uses 9 septets. Download the JSON report and check that the first part contains only the letters a. Its UTF-16 offsets are 0 to 152, with the euro sign at offset 152 in part 2.
Switch the multipart profile to Separate messages without a header. The first standalone part can now hold 160 septets, ending after the sixth b. The second part contains the last b. Standalone parts are separate texts in the estimate.
3GPP TS 23.038, default alphabet and extension table3GPP TS 23.040, SMS user data and concatenation headers
Find the line that changes encoding
Choose One message per line and reload the example. Line 2 contains an em dash and reports Unicode. Expand Characters outside GSM-7 to see U+2014. Select Preview plain punctuation and check that line 2 switches to GSM-7 with one replacement. The input still contains the em dash.
Line 3 uses Arabic and an emoji. It remains Unicode. The emoji occupies two UTF-16 units and stays in one part. The split keeps code points together. A joined emoji sequence can still cross a boundary. Enable Strict checks to flag the line for a route that requires UCS-2.
3GPP TS 23.038, default alphabet and extension tableUnicode 17.0, character encoding forms
Choose the multipart header used by your route
The 140-octet SMS user data field supports 160 septets or 70 units of 16-bit text when there is no header. A concatenation header consumes part of that payload. The table assumes no other information elements and the default GSM alphabet plus its extension table.
Compare the provider's actual alphabet and headers with the profile before using the result as a delivery limit. National language shift tables, smart substitutions or extra protocol headers can change the count. Choose Part limit to flag a multipart message for review.
| Payload profile | GSM-7 septets per part | 16-bit units per part |
|---|---|---|
| Standalone without header | 160 | 70 |
| 8-bit concatenation reference | 153 | 67 |
| 16-bit concatenation reference | 152 | 66 |
3GPP TS 23.038, default alphabet and extension table3GPP TS 23.040, SMS user data and concatenation headers
Common questions
What happens to the empty rows in a message batch?
Empty lines are skipped, and the remaining messages keep their source line numbers. A line containing a space represents a message with that space.
Can the last part show unused capacity when a message splits?
Yes. The capacity report counts complete character encodings. A two-septet escape pair or a surrogate pair moves together if it cannot fit.