Page tree
Skip to end of metadata
Go to start of metadata

Welcome to Email to SMS!

Email to SMS allows you to send and receive SMS messages from your application with no additional software to install or manage. 

Accessing Email2SMS

To access to the Email2SMS application

First log into the platform:

Navigate to Email2SMS from your Dashboard in one of two ways, either via the Applications side menu

           

or the Email2SMS icon along the top of the Dashboard 

           

               


Depending on your set up and if you have multiple instances of Email2SMS you may be presented with the below page. If that happens you will need to select the Domain you wish to view. For example, if you wished to view Modica Demo then click on the hyperlinked domain liatest.sms-e.com.


Top of Page


Domain Tab

The 'Domain' tab in Email2SMS is able to be set by a permission that will restrict access to administrators of the customer account.  

It can be split out from all the other tabs, so users can still maintain recipients and senders without accessing the main application configuration tab. 

There are a number of configurable items on the domains page.  Each has inline help text to show you what all the items will do. 

Delivery Receipts via Email

You may choose to receive emailed delivery receipts to let you know whether the messages you send have been received. If you enable this function, you will receive a delivery receipt email for each message you send via Email2SMS. You can choose for delivery receipts to be returned to the sender of the original message or to a nominated email address.

Only final delivery statuses are sent. In some cases, we may not receive a final delivery status from the carrier. In those instances, a delivery receipt will not be sent.

Email Truncation Sequence

If you choose, you may define a sequence of characters which will define where in the email the end of the intended message is. This can be used to remove email signatures and disclaimer messages. A commonly used sequence is '---'.

Maximum Units

This allows you to restrict or extend the maximum message units that can be sent (per send). You can set the maximum number of units to be anywhere from 1 through to 10 message parts.

 For more info see:  Enabling Concatenation in Email2SMS for more detail. 

Source Masks

Source masks (also known as "alphas" or "Sender IDs) allow you to send messages using a custom, recognisable ID that is created using a combination of up to 11 alphanumeric characters (0-9, a-z, A-Z, _)

Source masks must adhere to the following rules:

  • 1-11 characters in length, any combination of characters or numbers.
  • No spaces at the start or end of a word, no symbols, hyphens, full stops, or any other special characters
  • Underscores are allowed

The Omni platform allows for messages sent via Email2SMS to include source masks, however, some mobile devices will display a source mask differently.

Apple devices: Apple devices will present all alphas as one word.

For example, if the alpha is set as ABC 123, Apple devices will drop the space in between both parts display the sender ID as ABC123

Android devices: Android devices will present all alphas exactly as they are entered into the Optus SMS platform.

For example, if the alpha is set to ABC 123, Android devices will keep the space in between both parts and display the sender ID as ABC 123

The character limit for source masks is 11 characters (spaces between words are acceptable and will make up 1 character)

Limitations

Countries including New Zealand the USA, do not support alphanumeric sender IDs. Some international delivery partners will replace the sender ID with a local number to ensure message delivery, however, we cannot guarantee this.

For New Zealand, we recommend all messages are sent with an Australian sender ID as currently, the standard behaviour is the Australian number is replaced with a New Zealand shortcode.

MO replies with Source Masks

Messages that are sent with a source mask (which can be either alpha or alphanumeric sender ID) are used for one-way communication only. Replies are not able to be processed to messages where a Source Mask is utilised.

Top of Page


Prefix Mapping

Prefix mapping allows you to automatically adjust the prefixes for destinations you're sending to once the email is received by Omni. Prefix mapping assists by adjusting chosen prefixes to accepted prefixes so that you don't necessarily need to change your data in your own system.

To add a prefix map, Go to the "Mobile Prefix Mappings" tab within Email2SMS:

Enter the prefix you would like to be mapped and the final prefix in the input boxes:

Select "Add Prefix"

Now, whenever you attempt to send a message to an "02X XXX XXXX" number it will be amended to "+64 2X XXX XXXX".



Before Sending Your First Message

First things first, have a chat to your Account Admin to see how you’ll need to get started. It will either be one of the following:

1a. Add senders/recipients in Email2SMS

            OR

1b. Use your email client to send a message with the standard formula:

  • Australia - email@domain.com.au or +61xxxxxxxxx@domain.com.au  (xxxxxxx is their mobile number)
  • New Zealand - email@domain.co.nz or +64xxxxxxxxx@domain.co.nz (xxxxxxx is their mobile number)

Top of Page


Adding Senders

First, click on the “Senders” tab.


Then click the “Add New” button. You’ll then have the option to either manually input recipients or import a CSV file of senders

 

Manually Adding A Sender

Type in the sender’s details under the “Add Sender” heading.

This will include their:

  • First Name 
  • Last Name 
  • Email Address
  • Reference (Optional). 

Click “Save" and repeat this process to add more senders.

 

Importing a Sender List

You can save a whole lot of time by importing a CSV file list of senders. 

First make sure your CSV file is formatted with the first column as First Name, the second column as Last Name, and the third column as Email Address.

Then you navigate to "Senders" and press the "Add new Senders" button.

On this page it will offer you the option to manually add a sender or load a CSV.

 

Then under the “Upload Senders” heading there will be a “Choose File” button.

Click this and find the CSV file you want to use.

If your header row is titles (e.g. First Name), check the ‘Ignore Header row’ box.

Then click “Save” to finish.

Top of Page


Adding Recipients

First, click on the “Recipient” tab.

Then click the grey “Add New” button. You’ll then have the option to either manually input recipients or import a CSV file of recipients.

 

Manually Adding Recipients

Type in the recipient’s details under the “Add Recipients” heading.

This will include their:

  • First Name 
  • Last Name 
  • Mobile Number (with Country Code)
  • Reference (Optional). 

Click the red “Create” button to save and repeat this process to add more recipients.

 



Each new Recipient’s details will be formatted to match your domain.


Importing a Recipient List


First make sure your CSV file is formatted with the first column as First Name, the second column as Last Name, and the third column as Mobile with the country code.

Then under the “Upload Recipients” heading there will be a “Choose File” button. Click this and find the CSV file you want to use.

 If your header row is titles (e.g. First Name), check the ‘Ignore Header row’ box.

Then click “Upload Recipients” to finish.

Top of Page


Using Your Email Client to Send a Message

Open up your email client and in the “To” box, enter either the mobile number (including area code. E.G NZ +64, AU +61) or the Email2SMS email (e.g. +641234567@demo.modicagroup.com.com.au OR johnsmith@demo.modicagroup.com.com.au).

Leave the Subject blank and enter your SMS message in the body of the email client. 

If the Subject is populated it will be added to the text in the SMS and count towards the character count of the message.

Click “Send” and voila! Easy as that.

 

In order for the message to be sent successfully, the email must contain a plain text element. HTML will not be recognised.

The Modica platform will not generate bounce emails in the event of a malformed email being received.






  • No labels