Let your business connect and communicate even better through messaging with an added feature of smart encoding. Enrich your capabilities by letting your software do all the heavy lifting for you through the integration of an SMS API into your business. And, improve SMS delivery with a phone number and content intelligence. 

‍

Messaging has never been this convenient and secure. Because we want our messages to remain in the hands of the right person, group, or conversation, how amazing would it be to have a way to prevent unnecessary linking and sharing of messages to other individuals? Another concern with messaging is the difference of the devices we use that’s why there’s a possibility that we might not understand a term or a portion of the message. The sender may have added an emoji or character which the recipient doesn’t have on his/her device that may lead to misinterpretation or a loss in the actual meaning or concept conveyed. 

‍

The only way to check whether a message contained an unintentional Unicode character in the past was to paste the text into a tool that informs you how we will encode your message or we can send a test message to check for segments in your logs. This entire process adds an extra step that makes your development lifecycle even longer. 

‍

Developments made just recently on the new Smart Encoding feature will enable your messaging service to automatically translate Unicode characters into GSM7/ASCII characters for you if there are any GSM7/ASCII alternatives and no characters that can’t be converted in the message, ex. emoji or language based characters. 

‍

Just picture this - for instance, if you have spent all night crafting the perfect 159 character message & your CEO loves it. Then, you copy and paste it from Google docs into your IDE and sent 1000 messages. You log into the Console to see your message queue decrease as your messages are being delivered. The next step would be to check the logs in order to view the delivery steps and encoding for individual messages when, amazingly, you discover that your messages are being sent in two segments! Then, you ask yourself: Why is my message divided into two segments and costing me the price of two messages? 

‍

This is because when a message contains even a single Unicode character, it gets segmented at 70 characters instead of the normal 160 characters. Often these characters – a smart quote ( 〞), a long dash (—), or a Unicode whitespace – slip in and are hard to identify as the cause of your message being split up. 

‍

Smart Encoding is now available & is enabled by default for all new Messaging Services. 

‍

If you have an existing Messaging Service, you’ll probably need to enable them for Smart Encoding. You just need to simply log in to the console and navigate to your Messaging Services to enable it. 

‍

If you’re not using a Messaging Service to send your messages, now is the perfect time to begin!

 

And Why Would I think So?

Because it offers a lot of benefits for you & your business such as: 

• Phone number & data analytics
• Global Fraud Detection
• Traffic Pattern Recognition
• Machine Learning
• Usage velocity
• And most of all, Actionable Risk Assessment  

All these could help you achieve more and do more as you will be able to grow your user base responsibly, identify fake & suspicious users, as well as protect your brand reputation & value. In order to learn more about how the complete messaging service works, visit our site at iConnectEdit.com or leave your comments below & we’ll get back to you for further details.