Transitioning from Aerialink Conversations to Email-to-SMS
If you are considering transitioning from Conversations application to Email-to-SMS, please review the following capabilities and limitations.
Email-to-SMS Gateway Capabilities
- Continue using the same phone numbers currently assigned to Conversations for both sending and receiving messages.
- Supports both Toll-Free and 10DLC numbers.
- Existing Toll-Free verified numbers remain verified.
- Existing 10DLC brands and campaigns remain registered.
- Enables migration with little to no SMS service disruption.
- Supports one-to-one conversational messaging.
- Allows either an individual email address or a shared email address to be associated with a hosted number.
- Messages are delivered as true SMS messages to mobile devices rather than through carrier email domains.
- Resellers can use their own custom-branded email domain for hosted numbers (one-time setup fee applies).
- Supports keyword-based autoreplies configured within the gateway.
Exclude Email Signature in the SMS message text
When sending email, mailers exclude content below a "delimiter". Use the following delimiter in the email body by copying and pasting it.
-----Original Message-----
You can include the delimiter in your email signature so that you do not have to paste it in every message you send. The delimiter is not shown in the SMS message text.
Email-to-SMS Gateway Limitations
- MMS messaging is not supported.
- Email threading is not maintained within the email client. Each inbound message is delivered as a new email. However, a web link is included that allows agents to view the complete conversation thread in a read-only format.
- Sending limits are subject to the policies of the email provider. For example, standard Gmail accounts are limited to 500 outbound emails per day.
- Message delivery latency may be higher than traditional SMS because email is part of the delivery path.
- Troubleshooting delivery failures is generally limited to visibility within the Aerialink network.
- Email subject lines are not transmitted; only the message body is delivered.
- Inbound emojis are supported by most email clients. Outbound messages use ASCII encoding, so emojis are automatically converted to supported ASCII characters during processing.
Character Limits
There is no hard character limit for inbound or outbound Email-to-SMS messages, and longer messages are supported. However, for best delivery results, we recommend keeping messages concise.
As a guideline:
- 459 ASCII characters (including spaces) equals approximately 3 SMS segments.
- Messages longer than 160 characters are delivered as multiple SMS segments, consistent with standard SMS behavior.
- Most modern smartphones automatically combine segmented messages into a single conversation thread.
- To avoid delivery issues when sending links, shortened URLs are recommended.
Need More Help?
If you have additional questions or need more information, our support team is ready to assist you.
- Contact Support Submit a ticket to our team for personalized help.
Comments
0 comments
Article is closed for comments.