Server monitoring + alerting
Nagios, Zabbix, Datadog, Sentry — anything that already pages by email. Point it at your BroadNet email-to-SMS address and the on-call gets a real SMS, including on roaming + low-data networks.
For systems that already send email
Send an SMS by sending an email.
Any system that can already send an email can now send an SMS — on BroadNet's operator-direct A2P routes, with the same sender-ID enforcement, DLRs and audit log as our REST API.
To: 447700900123@<gateway-domain>
Subject: (optional)
Body: Your verification code is 384921.
Subject: (optional)
Body: Your verification code is 384921.
Who uses it
When integration time
is the bottleneck.
Legacy ticketing systems
Older ITSM and helpdesk tools often ship with email-out but no SMS adapter. Email-to-SMS routes the ticket creation / SLA breach / escalation event into a verified A2P send without changing the source system.
Workflow apps without webhooks
If your workflow tool can send email but doesn't speak HTTP, email-to-SMS becomes the bridge. Bonus: every send still flows through BroadNet's delivery-receipt audit trail.
How it works
Four contract points.
Subject + body addressing
Address email to <msisdn>@<gateway-domain> — the body becomes the SMS. Optional Subject: lines become sender-ID overrides or scheduling instructions per a whitelisted-syntax we publish in the docs.
Authenticated sender domain
Only sends from your verified SPF / DKIM / DMARC-aligned domain get accepted. Stops a forged email from triggering an unauthorised A2P send.
Same A2P routes underneath
Email-to-SMS is a thin shim over the standard BroadNet A2P send. Operator-direct routes, sender-ID enforcement, DLRs and audit logs — all identical to the REST API surface.
DLR back as email
Delivery receipts come back as a reply email to the original sender (or to a configured DLR address). Same conversation thread as the original alert.
Authenticated.
Per-domain.
Email-to-SMS without SPF/DKIM/DMARC is a smishing waiting to happen. BroadNet rejects any inbound that doesn't pass DMARC alignment against your verified domain.
SPF check at SMTP receipt
DKIM signature verification
DMARC alignment enforced (default: reject)
Allow-list of sender addresses per BroadNet account
Audit-log entry per accepted email
TLS-required SMTP. Plain-text submission refused. Same audit-log retention as the REST API surface.
Related developer tools
One DNS record + a verified domain.
Talk to sales — we'll provision a unique email-to-SMS domain for your account, walk through SPF / DKIM / DMARC, and ship the allow-list.