# SMS encoding warning / encoding cleaning

**URL:** <https://forum.mautic.org/t/sms-encoding-warning-encoding-cleaning/19049>\
**Category:** Ideas and Feature Requests\
**Created:** [April 17, 2021, 3:06am UTC](https://forum.mautic.org/t/sms-encoding-warning-encoding-cleaning/19049 "2021-04-17T03:06:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [April 17, 2021, 3:06am UTC](https://forum.mautic.org/t/sms-encoding-warning-encoding-cleaning/19049/1 "2021-04-17T03:06:51Z")

</div>

My idea is: SMS encoding warning / encoding cleaning

Where we enter in an SMS text, allow a notification or cleaning to optimise the typed text where there are non-GSM characters present.

I think these groups of people would benefit from this idea:  
The cost calculation where a sms includes at least 1 non-GSM character doubles the cost of an sms, with a sms segment changed from 160 to 70 characters per cost segment

> **[What is the SMS Character Limit?](https://www.twilio.com/docs/glossary/what-sms-character-limit)**
>
> The character limit for a single SMS is 160 characters, but most networks segment up to 1600 characters. Non GSM-7 characters are limited to 67.

Why I think they would benefit from this idea:  
SMS are expensive, and when you type a 160 character sms with 1 character the cost of the SMS triples (160/70 = 2.3. rounded up to 3 cost segments)

Any code or resources to support this idea:  
[https://twiliodeved.github.io/message-segment-calculator/](https://twiliodeved.github.io/message-segment-calculator/)

> **[TwilioDevEd/message-segment-calculator](https://github.com/TwilioDevEd/message-segment-calculator)**
>
> JS-based tool to calculate and display message segmentation data for a given message body
