Best email to SMS providers in Australia

How email to SMS works

An email to SMS gateway turns an approved message into a text using the recipient address and the content the provider is configured to send. The gateway address, subject handling and body rules differ, so follow the setup page for your provider.

Textmagic offers subject only, body only or both, while ClickSend offers configurable content, so some setups can send the body alone. Before relying on SMS from a computer for short updates inside an email workflow, check your configured content and the actual received text.

Choose by published setup

Choosing by setup means reading the workflow your staff will actually use, not the headline price. The cheapest bulk SMS page compares published rates, but email to SMS cost depends on the billing currency and the actual message parts a provider counts, not a per-email assumption. Two workflows dominate. In the first, staff reply from an owned mailbox and the provider returns SMS replies to that address. In the second, an existing alert email is converted to text, so sender authorisation, subject or body handling, reply destination and account restrictions matter more than mailbox habits. Filter rows on those documented conditions. An exclusion from a filter can mean the evidence is missing, not that the feature is unsupported.

Authorise the sending address

Gateways that authorise addresses check the actual From address your mail system sends, including aliases and app support addresses. ClickSend Allowed Addresses asks for an address you own or control, and cannot match a generic third-party service address.

ClickSend also accepts a wildcard domain, which gives every address on that domain sending access, so choose that breadth deliberately. Confirm control of any shared mailbox before relying on it.

160 works differently, because its Subject carries the sender international-format mobile number, then @ and the account SMS secret from the profile. Treat that secret like a password and keep it out of shared templates.

Recipient and content setup

Recipient addressing follows each provider pattern. ClickSend asks for an international E.164 number with the plus sign before @sms.clicksend.com, Textmagic uses the number before @textmagic.com, and 160 uses the number before @160.com.au.

MessageWorks documents a different pattern from recipient-number addressing. You send to the trigger address [email protected], place the recipient numbers in the Subject line and put the SMS text in the body. Other trigger addresses on the same domain handle group sends and file imports. Do not reuse one provider's recipient or subject syntax with another, because the fields carry different meanings and a wrong field can send to nobody or to the wrong list.

Textmagic can send the subject, the body, or both, and it can also cap message length and remove extra line breaks. Set those options in its settings before your first live send.

Textmagic can also convert text to Latin-only characters, an optional step that may change names or required wording, so test the result. Its custom cut phrases remove the phrase itself and everything after it.

Cellcast publishes two separate email to SMS routes. The Classic knowledge base documents the [email protected] address and says replies automatically return to the inbox that originally sent. Cellcast Enterprise documentation instead describes global subject options of subject plus body, body only or subject only, and SMS Start Tags and SMS End Tags that send only the text between them. Do not combine the two into one proved same-account setup, because independent proof that each platform carries the other's features is missing. The Notifyre support guide works differently again. Its Subject line becomes a report message ID or campaign name, not the SMS body, auto signatures must be removed manually, and reply email notifications are enabled under SMS Notifications Settings. Its current sender options include a shared system number, an Australian virtual number or a custom sender ID, so a virtual number is not always a prerequisite.

ClickSend Start and Stop rules cut content, and a Stop trigger removes the trigger plus everything after it. 160 uses a literal [end] after the message to remove a following signature or disclaimer.

Pick a cut marker no normal word could match, so an ordinary term does not remove useful text. Signatures can add parts, so check the received text rather than assuming they always raise a bill.

Encoding and message parts

Standard GSM-7 encoding carries 160 characters in a single message, or 153 per part once a message is concatenated. UCS-2 encoding used for other scripts carries 70 in one part, or 67 per concatenated part.

A single smart quotation mark or emoji can switch the whole message to UCS-2, and some visible characters consume more than one encoding unit. Run an SMS character counter on real messages before you send volume.

SMS is billed per segment rather than per email, and message parts depend on encoding and length, with some visible characters consuming more than one encoding unit. Check the parts with the character counter already linked in the preceding paragraph, then confirm what the actual received text shows.

Reply workflow

A name or alphanumeric sender supports one-way messaging only, and recipients cannot reply directly to it. When a conversation matters, choose a reply-capable numeric sender with documented routing, never a name sender paired with a random number.

ClickSend and Textmagic collect replies in an inbox and in Messenger, and Textmagic also emails them to you. On 160, a leading ! in the Subject enables two-way replies, while a bracketed business name sender cannot receive them.

Businesses register the sender ID through their provider, and unregistered names are labelled Unverified in Australia. A recipient cannot reply directly to a name sender, and registering it does not create reply capability, so when replies are needed, choose a reply-capable numeric sender with supported routing.

Sending to a contact list

Several providers let an email drive a list send, but the addresses do different jobs. MessageWorks separates import actions from send actions, and mixing them up can update a list when you meant to message it.

• MessageWorks contacts@ and addgroup@ addresses import or update contacts from a CSV, with addgroup@ creating or updating a group and preserving STOP preferences. They do not send. The MessageWorks trigger guide assigns sending to file@, which takes a CSV attachment and template name in the Subject, and sendgroup@, which takes a group name in the Subject and SMS text in the body.
• The Mobile Message email guide uses one list-specific address. The send must come from an authorised sender, duplicate numbers receive one message, and unsubscribed contacts are skipped. If credits are insufficient for the whole list, nothing is sent and you receive an email notice.
• Before sending, check the intended list, the final text after any substitutions, and that your configured unsubscribe suppression is selected.
• For complex templates or scheduling, move to the web platform or the documented API rather than assuming every email workflow behaves the same.

Our guide on How to send bulk SMS in Australia covers the import preparation steps in more depth if your lists are not yet clean.

First test and troubleshooting

Run one controlled test before moving staff across. Use a consenting contact you own, inside your trial or account restrictions, and check each point against the published documentation for your edition.

1. Confirm the actual From alias is authorised and you are on the account edition you think you are, because Classic and Enterprise routes differ at Cellcast.
2. Put deliberate content in the Subject where the provider uses it, include a safe cut marker, and compare the received text against what you intended.
3. Check the SMS character counter of the expanded final text including your unsubscribe wording, since parts drive cost.
4. Where replies matter, confirm the numeric sender accepts replies and that they arrive in the staff mailbox you expect.
5. Verify the dashboard or failure notice reflects the send and that your settings saved.

A sent email is not proof of delivery. For a failed send, check the allowed address list and required syntax first, then settings, available credit and any returned error. Do not broaden sender access just to make an error disappear. Providers do not all expose the same errors or delivery data, so compare against your own provider's published behaviour.

Leaving Telstra Desktop Messaging

Telstra Desktop Messaging has closed in stages. New customers were closed on 30 June 2025 and the small business route withdrew on 10 November 2025. Existing enterprise customers have been unable to add or change services since 6 August 2026. The enterprise withdrawal date is 9 November 2026. These dates cover Desktop Messaging only, and no replacement product is assumed.

Before moving staff, test the sending address each person uses, the reply destination customers need and a sender name they recognise. Run that test against your chosen provider before you cut over.