Please use a URL encoder to embed URLs within messages. 

 1. In Microsoft Excel, open the *.xlsx file.
 2. Select Menu | Save As.
 3. Enter any name for your file.
 4. Under “Save as type,” select Unicode Text.
 5. Click Save.
 6. Open your saved file in Microsoft Notepad.
 7. Replace all tab characters with commas (“,”).

  • Select a tab character (select and copy the space between two column headers)
  • Open the “Find and Replace” window (Press Ctrl+H) and replace all tab characters with comma .

 8. Click Save As.
 9. Name the file, and change the Encoding: to UTF-8.
10. Change the file extension from “*.txt” to “*.csv”.
11. Click Save.
12. Open the .csv file in Excel to view your data.

If you run into a problem in these step, don’t save your file in Excel because it’ll cause encoding issues. If you’re having trouble, use the troubleshooting steps below.


Troubleshooting steps if you’re still having encoding issues


1. Find the file.
2. Right click the file | select Open With | Notepad.
3. Select File | Save As.
4. Navigate to the folder where you want to save your file.
5. Enter a name for your file and append .csv to the end of the file name.
6. Select UTF-8 encoding.
7. Click Save.
8. Open the newly created file in Excel to view your data.

The title field is for when you send email messages via the XML API. If you’re sending SMS text messages, you can just leave the field empty. 

1. You can fill all the message information in the <MESSAGE_INDEX>0</MESSAGE_INDEX> field.

You should keep the subject entry empty:


So your full SMS text will be in the section: 



              <TEXT>sms message body</TEXT>


2. You can test your XML without coding by using this page

3. Be aware that you can change your SMS template (and other SMS settings) in the SMS settings inside your web account

You can messages with alphanumeric sender IDs through our web interface, the XML API or the REST API. If you would like to enable this feature in the web interface, please contact us first

Once you’ve been approved to send messages with alphanumeric IDs, go to Settings > Preferences and you will see the option enabled: 2015-04-01_13h09_46


If you would like to change the name displayed, go to Settings > User Profile to change your FIRST name (only what you set as the first name will be displayed as the sender ID). 

In XML, use the following code:

AlphanumericSender – the value of tag/element is the company name. The maximum allowed length of the AlphanumericSender value is 13 characters (digits and/or English characters). 

<?xml version="1.0" encoding="UTF-8" ?>
                <SUBJECT>enter your subject here</SUBJECT>
                            <USER_NAME>enter your user name here</USER_NAME>
                            <PASSWORD>enter your password here</PASSWORD>
                    <TEXT>enter your text here</TEXT>
                  <PROPERTY_VALUE>13 Character Sender</PROPERTY_VALUE>
                        <DEVICE_TYPE DEVICE_TYPE="SMS"/>

In REST, use the following code:

Gateway URI:

REST Example:

      "textMessage":"Hello dear, how are you? :-)",
            "description":"Mrs. Jane Doe",
      "properties": [
            "class": "",
            "name" : "AlphanumericSender",
            "value": "13 Character Sender"





If the reply source is in alphanumeric characters, it will override whatever was configured in the XML. Go to Settings > Preferences > SMS/IP > Replies. Make sure the source number is in digits only.

Any file you send via the TeleMessage APIs should be encoded using Base 64 encoding which converts binary files into ASCII format. You can use the TeleMessage Utilities which include code samples for performing the encoding.

There are 2 ways to receive replies: Pull method, i.e., polling messages from the TeleMessage server. This can be done periodically. Click here for the code sample. Push method, i.e., defining a forwarding rule for the replies, pointing to your service. You will need to create a web service which will process the replies and delivery status  sent to your URL by the TeleMessage service. The status and reply will be formatted in XML. Click here for the code sample.

Use our SOAP provisioning & reporting API. Contact us.

This is happening for two reasons:

1. You probably don’t have any message credits.

2. Your message settings are set to “IP Only”.

If you purchase message credits, you’ll still have to change your message settings manually to “IP & SMS”.

You can also invite others to download the app.


You can set and record a personal prefix, via your account on the web portal:

You can find it under Options->Preferences (left side menu). And click on Preferences->Voice Tab->Update Voice Prefix.

Just login with your username and password (the login credentials were sent to you as an SMS and should appear in the App).

This voice prefix will be played to users at the beginning of each message (and will replace the “you  have a text message from  XXXXX”).

We can also create a custom prefix and voice call for you, this is a paid service we provide customers that have recurring volume and commit to a monthly minimum.

We offer up to 10,000 recepients per message, but please contact us for more information.

For server code programming, we recommend you use the SOAP or XML API.

For Scripting languages, we recommend you user the REST API.

For legacy and alerts systems, we recommend you user the SMTP API.

For high throughput SMS delivery, we recommend you user the SMPP API.

For Pager replacement solutions, we recommend you user the WCTP, SNPP or TAP APIs.