Dis one important especially for time reminders, notifications, and bulk messages. Na hard to judge from di short sentence wey you see for di editor how many SMS parts go go out. Check di final text with di sending service own counter, include di name wey dem replace, di date, and any unsubscribe text.
Wetin di 160, 70, 153 and 67 numbers mean?
Di usual capacity for one-part SMS wey dem send with GSM-7 character set na 160 units. For di Unicode encoding wey SMS providers dey mark as UCS-2, 70 na di usual limit. For multiple concatenated parts, di data wey dem need to assemble dem take space: so usually you fit calculate 153, or 67 units per part. Twilio dey document exceptions for some routes. Source: Twilio – How long can a message be?
| Usual encoding case | Capacity of one part | Capacity of one part of concatenated message |
|---|---|---|
| GSM-7 | 160 units | 153 units |
| Unicode, wey providers dey often mark as UCS-2 | 70 units | 67 units |
Di “unit” here no always mean one visible character. For example, for di GSM-7 extension set, di { and di ] brackets each take two units. So di provider counter na more accurate guide than letters wey you count by hand. Source: Twilio – GSM-7 character encoding
Check for Hungarian accents too
No just watch di emoji. Certain accented letters, typographic quotation marks, and other special characters fit cause encoding change. So for Hungarian text, after you remove di emoji, check di counter again. Di GSM-7 and di simple ASCII character set no be di same. Source: Twilio – What is UCS-2 Character Encoding?
Try dis three short samples one after another for your provider preview:
Holnap 14:00-kor talalkozunk.Holnap 14:00-kor találkozunk.Holnap 14:00-kor találkozunk. 🙂
First only di accent dey change, then di emoji enter. Watch di encoding and di number of message parts separately: for dis kind of short text, di encoding change no necessarily increase di number of parts yet. Di provider automatic character replacement fit influence di result too.
When you dey shorten, keep di data wey di recipient need. If you leave out di time or di cancellation option, e fit make di notification useless. Better remove one unnecessary introduction or repetition, then read di message back as standalone text.
One smile fit be more than one technical unit
For di provider interface, you often see di label “UCS-2”. But strictly speaking, UCS-2 no fit show all modern emojis. UTF-16 dey handle characters outside di basic plane with two 16-bit code units; check di support for di specific sending system for their own documentation. Technical background: Twilio – UCS-2 and UTF-16
One simple example wey easy to check: 🙂 na one Unicode code point, two code units for UTF-16. 👩💻 get three code points, five code units for UTF-16. Both fit appear as one image. Di numbers dey follow from how di sequences dey built; so counting di visible images no enough to determine di sending size. Di article about composite emojis dey break down di difference in detail.
Check di actual sending method
For phone conversation, SMS, RCS, and other messaging methods fit work with different rules. Use di table for SMS only when you dey really send SMS. For business system, check di possible fallback method from di provider documentation too: wetin happen if di channel wey you originally choose no dey available?
Check di price based on your own package. Plenty parts no dey mean say extra cost na same for every subscription. Before you send am for real, send one message wey get real length go your own test address, plus check di provider log, e go give useful feedback.
Carry di main thing with you
Three-question quiz
Try how you go apply wetin you read. Select one answer for each question; every correct answer dey worth one point. Di evaluation dey give feedback for dis three situations, wey no dey store or send your answers.
Try di three short SMS samples, and watch di encoding and di number of parts separately.
Try di three short SMS samples, and watch di encoding and di number of parts separately.
Check which character or filled-in data wey miss from di counting.
For di three examples, you examined di text wey you actually sent; check one of your own SMS templates too.
Solutions and explanations
- Di encoding for di remaining characters and di number of message parts. Other characters fit make different encoding necessary.
- You no fit decide from di visible shape alone: you must measure di encoding units. One single visible shape fit contain multiple code points and code units.
- You dey check di full substituted text and di number of provider parts. Di actual length of di sent version dey decide how di message fit.
Count your correct answers: each one dey worth one point. Skipped answer na zero point.
- 3 points: For di three examples, you check di text wey actually sent; check one of your own SMS templates too.
- 2 points: Check which character or substituted data miss from di counting.
- 0–1 points: Try di three short SMS samples, and watch di encoding and di number of parts separately.
