What Ways Can I Send SMS with SMS Broadcast?
Updated
SMS Broadcast offers three ways to send and receive text messages: Online SMS (a web-based inbox), Developer API (HTTP or email API for system integration), and Email to SMS (send and receive from your existing email address). All three are available from a single account, and the Developer API is described as having no added cost. Which one suits you depends on whether you want a ready-made interface, a programmatic connection, or a familiar email workflow.
Online SMS: for teams that want a ready-made interface
This is the option to pick if you want to manage conversations directly in a browser without installing anything.
- What it is: A web-based inbox for managing SMS conversations.
- Input: Your contact lists and message content, entered in the browser.
- Action: Import contacts, create groups, set up templates, and send from the online inbox.
- Expected result: You send and receive messages and track conversations in one place, with no software download.
Reviewers on the site repeatedly mention the same practical points: importing multiple contacts and creating groups is straightforward, templates save time on repeat messages, and the setup is quick. One reviewer (David) specifically calls out importing contacts and creating groups; another (Paul) highlights templates and cost-effectiveness. If your team sends recurring campaigns to grouped audiences, this is the lowest-friction starting point.
Developer API: for integrating SMS into your own systems
Choose this if you need SMS triggered by your own software rather than typed by a person.
- What it is: An SMS gateway you integrate into your systems, offered as either a full-feature HTTP API or an email API.
- Input: Requests from your application to the SMS gateway.
- Action: Your system calls the API to send messages.
- Expected result: SMS becomes a function of your existing software, and the site states the API carries no added cost.
The key decision here is HTTP API versus email API. The HTTP API is the fuller option and fits applications that need to construct requests programmatically. The email API is the lighter path if your system already generates email and you want that to become an SMS. Both are described as available at no added cost, so the choice is about your architecture, not price.
A concrete scenario
For example, if you run a booking system and want a confirmation text the moment an appointment is made, the HTTP API lets your application fire that message automatically. If instead you have an internal tool that already emails staff, the email API can turn those emails into texts without new code.
Email to SMS: for sending from your existing inbox
Pick this if you want to keep working in email but have the message arrive as a text.
- What it is: Send and receive text messages from your existing email address.
- Input: An email you compose and send as usual.
- Action: Your email is routed to the recipient as an SMS.
- Expected result: You can communicate by text while on the go, without opening a separate SMS tool.
The site frames this as a way to "still communicate while on the go." It suits people who are already in their inbox all day and don't want a second interface for occasional messages.
How to choose
| Your situation | Best fit |
|---|---|
| You want to send campaigns and manage replies in a browser, no install | Online SMS |
| You need SMS triggered automatically by your own software | Developer API (HTTP) |
| Your system already sends email and you want it to become SMS | Developer API (email API) |
| You want to send occasional texts without leaving your inbox | Email to SMS |
The three methods are not mutually exclusive — they sit under one account, so you can start with Online SMS and add API integration later, or use Email to SMS alongside either.
What to check before committing
- Pricing and trial terms: The site advertises a free trial and a pricing page, and states you "only pay for what you send" with "no fixed term contracts." Check the pricing page for current per-message rates, since these are not specified in the material available here.
- Volume and use case: The "only pay for what you send" model suits variable or campaign-based sending. If you send at a steady high volume, confirm the rates still work for you.
- Integration effort: The API is the only method that requires development work. If you have no developer, Online SMS or Email to SMS will get you sending faster.
SMS Broadcast reports being trusted by 30,000 Australian businesses with a 4.7 out of 5 rating across 5,000 reviews, and the recurring themes in those reviews — ease of setup, contact import, templates, and support — map most directly to the Online SMS experience.