SMSAPI
— Use case

Send SMS straight from email

Some systems can only send email — a monitoring tool, a legacy ERP, a no-code workflow. Email-to-SMS turns that email into a text message, so anything with an inbox can reach a phone without an API integration.

How email-to-SMS works

You send an email to a gateway address, and we convert it to an SMS — to the number encoded in the address or named in the body, with the subject or body as the message. Anything that can send an email, from a server alert to a CRM workflow to a spreadsheet macro, can now send an SMS with no code at all.

It earns its place in operations. A monitoring system that emails on an outage can text the on-call engineer; a legacy application that only speaks email can still reach a customer's phone. You get the speed and reliability of SMS through the one integration every system already has — the humble outbound email.

The SMS still goes through DLT, on a registered sender and an approved template, so email-to-SMS is a shortcut around integration, not around compliance. We map your gateway address to your registered header and template, so the message that leaves is exactly as compliant as one sent through the API.

Delivery receipts — and replies, where you use a two-way number — can come back to an email address, closing the loop for systems that live in an inbox. You control which senders are allowed through the gateway, so it's never an open relay.

What you get

— Gateway

Email in, SMS out

Send to a gateway address; we deliver it as an SMS.

— No code

No integration

Any system that sends email can now send SMS.

— Alerts

Built for monitoring

Outage and threshold alerts to an on-call phone.

— Compliance

DLT-mapped

Your gateway maps to a registered header and template.

— Loop

Receipts to email

Delivery — and replies, with a two-way number — back to an inbox.

— Control

Allowed senders only

Restrict who can send through the gateway.

Frequently asked

How does a system send an SMS by email?

It sends an ordinary email to a gateway address you're given, with the destination number and the message in the address or body. We convert it to an SMS and deliver it. There's nothing to integrate — if a tool can send email, it can send SMS this way.

What is email-to-SMS best for?

Operational alerts from systems that only do email — monitoring and observability tools, legacy ERPs, no-code automations, scheduled jobs. It's the fastest way to add SMS to something you can't or don't want to integrate with an API.

Is it still DLT-compliant?

Yes. The SMS goes out on your registered sender header and an approved template, the same as an API send. We map your gateway address to that registration, so email-to-SMS changes how the message is triggered, not whether it's compliant.

How is email-to-SMS priced?

Per SMS sent, with GST shown separately, the same as any other SMS on the route you use — there's no premium for the gateway. Because email-to-SMS is just a different way to trigger a normal SMS, your volume rates and route choice carry over unchanged. See the pricing page for current per-message rates.

Start a conversation.