We've seen a steady uptick in signups from Australia over the last few months, and the pattern behind them is consistent: it isn't marketing teams building broadcast campaigns, it's developers and operators wiring one line of SMS into something that already runs itself. A booking system, a cron job, an AI agent. The message just needs to land in a pocket at the right moment.
That shift is worth digging into, because it changes what "an SMS provider" needs to be good at. It's less about a bulk-send dashboard and more about a reliable API that a script — or increasingly, an AI agent — can call without a human in the loop.
The growth of AI is turning "notify someone" into an API call
Automated procedures used to mean a scheduled script with a hard-coded message. Increasingly it means an AI agent deciding, in the moment, that a human needs to know something — and reaching for SMS because email gets filtered and push notifications get ignored. We built our Claude Code MCP server for exactly this: an AI assistant with the WebSMS tools attached can send a message, check a delivery status, or look up a number as part of whatever it's already doing, with no glue code in between.
The same shape shows up across the no-code side of the stack — Zapier, Make, and n8n-style workflows increasingly have an AI step deciding whether and what to send, then an SMS step delivering it. The API underneath doesn't change; what's changed is how many things are now capable of calling it without a person clicking send.
Reminders and tasks are still the highest-value use case
Underneath the automation trend, the actual jobs SMS gets used for haven't changed much — they've just gotten more automated:
- Appointment and booking reminders — cut no-shows by texting the day before and the hour before, without staff manually working a call list. See our appointment reminders solution.
- Task and job reminders — a field team, a rostered shift, or a to-do that's about to go overdue. Useful anywhere a task-tracking tool or AI agent needs to nudge a specific person rather than post to a channel nobody's watching.
- Parking reminders — a text 15 minutes before a paid parking session expires is a small thing, but it's the kind of automated nudge that only works if it's genuinely automated: triggered by a timer against the original booking, not a person remembering to send it.
- Travel and itinerary alerts — gate changes, shuttle pickup times, delay notifications. Travel is inherently event-driven, which makes it a natural fit for a system that sends the moment a status changes rather than on a fixed schedule.
What ties parking and travel together with appointment reminders is timing precision: the value of the message decays fast, so it has to be sent by something that's watching the clock or the event feed, not by someone remembering to do it manually. That's the whole case for an API over a dashboard.
What it looks like in code
A reminder sent from a script, a cron job, or an AI agent's tool call is one HTTP request:
curl -X POST https://api.websms.co.nz/api/connexus/sms/out \
-H "Authorization: Bearer wst_your_token..." \
-d "to=61412345678" \
-d "body=Reminder: your parking at Wilson St expires in 15 minutes" \
-d "messageClass=transactional"Sending to Australian numbers
Australian mobile numbers are treated as a standard destination on WebSMS, not routed through pricier international rates — the same API, the same account, the same per-message pricing from $0.10 that applies to New Zealand sends. If you already have a WebSMS account for NZ traffic, sending to 61… numbers needs no separate setup.
See the full breakdown on the international pricing page.
Automate your first reminder
Get an API token and send your first automated SMS in minutes.