Automation Services

SMS automation for reminders, confirmations and real replies

Text messages get read within minutes, which is exactly why they are easy to misuse. Built well, SMS reduces no shows and phone traffic. Built carelessly, it burns goodwill quickly.

What is SMS automation?

SMS Automation is the setup of automated text messaging from your business systems: appointment reminders, delivery and booking confirmations, alerts and campaign messages, with replies routed back into your CRM. It suits Australian organisations losing money to no shows or fielding the same phone enquiries repeatedly, where a text lands faster than email.

Get a fixed written quote
Typical timeline
2 to 5 weeks
What drives cost
Setup depends on how many message types you need, how many systems trigger them, and whether two-way reply handling is in scope.
Best for
Appointment based businesses, deliveries, service alerts and time critical updates
You own
The gateway account, the numbers, the message templates and the reply history
Built with
Gateway integration, dedicated numbers or registered sender IDs, reply routing, consent records

Your handover

Where SMS beats email, and where it irritates people

SMS wins on immediacy and on reach. There is no spam folder to fall into, no image blocking, no need for the recipient to be at a desk. For a reminder about an appointment in 24 hours, a tradesperson running late, a prescription ready for collection or a delivery arriving within the hour, nothing else performs as well. Appointment based businesses usually see the investment repaid through no shows alone, since a chair left empty for an hour is revenue that cannot be recovered later.

  1. 01Message inventory mapped across the customer journey
  2. 02Gateway account and numbers provisioned in your name
  3. 03Sender ID registration prepared and submitted
  4. 04Consent capture and opt out keyword handling
  5. 05Suppression list shared across SMS and email
  6. 06Triggers integrated with your CRM or booking system
  • Reply routing to records, queues and owners
  • Quiet hours and public holiday logic
  • Carrier test results and a delivery reporting dashboard
A newsletter by text is an intrusion

It loses on everything long, everything optional and everything that could have waited. A newsletter by text is an intrusion. A promotion at 7am on a Sunday is a complaint. Because the channel is intimate, the tolerance for irrelevance is far lower than in email, and people express displeasure by opting out permanently rather than ignoring you.

We start every SMS project by dividing the message list into two columns: messages the recipient would be annoyed to miss, and messages you would like to send. The first column is where the channel belongs. The second column mostly belongs in email, and we will argue that case during scoping rather than after your opt out rate spikes.

Both are provisioned under your account with the gateway, not ours.

Compliance: the Spam Act, the Do Not Call Register and timing

Marketing text messages are commercial electronic messages under the Spam Act 2003, which means the same three obligations that apply to email: consent, clear identification of the sender, and a functional unsubscribe that is honoured promptly. Unsubscribe by reply keyword is the norm, and it has to actually work, which means the keyword handler must be wired to your suppression list rather than to an inbox somebody skims.

Timing is the other discipline

A point worth clarifying, because it causes confusion: the Do Not Call Register covers telemarketing calls and marketing faxes, not marketing SMS. If your automation also triggers outbound calls, those numbers must be washed against the register and the wash stays valid for a limited period, so it has to be repeated. If your process is purely text, the Spam Act is the instrument that governs you. We build to both where a client does both, because a customer who complains does not care which act applies.

Timing is the other discipline. The telemarketing calling hours standard does not bind SMS, but sending a marketing message outside reasonable hours produces complaints regardless of legality. We build quiet hours into the sending logic, handle state based public holidays, and hold non urgent messages until the next acceptable window. Genuinely urgent operational alerts are exempted deliberately and documented as such.

How the engagement runs

How an SMS automation build runs

SMS projects are short, which makes it tempting to skip the design stage and start sending. The failure mode is predictable: duplicated messages when two systems both think they own reminders, or a customer receiving a confirmation, a reminder, a follow up and a review request in the same afternoon.

  1. 01Message inventoryEvery automated text a customer could receive, mapped across one full journey with timing
  2. 02Channel decisionWhich messages belong in SMS and which are better as email or in app
  3. 03ProvisioningGateway account in your name, sender ID registration or dedicated number, test credit
  4. 04Consent and suppressionCapture points updated, opt out keywords defined, suppression shared with other channels
  5. 05IntegrationTriggers wired from your CRM, booking or ordering system, with reply routing back to the record
  6. 06Test sendReal handsets across the major Australian carriers, including reply, opt out and unmatched number paths
  7. 07Launch and reviewVolume monitored, opt out rate tracked weekly, message set trimmed after 30 days
DiscoverDesignBuildTestHandover
Two decisions on your side that keep the project moving

So we map every message a single customer could receive across a full journey, on one page, before configuring anything. Almost every time, that exercise removes at least one message and re times another.

Choose the right level

Sender IDs, numbers and what Australian carriers allow

You have three ways to appear in someone's phone, and the choice determines what the message can do. An alphanumeric sender ID shows your business name instead of a number, which looks professional and is completely one way, because there is no number for the recipient to reply to. A dedicated virtual mobile number allows two-way conversation and lets the thread build up over time, which matters when a customer replies six weeks later. A shared number pool is cheaper and fine for pure notifications, but the number changes between sends so replies and threading become unreliable.

Option

01

Registered alphanumeric sender ID

Suits

One way notifications where showing your business name builds trust

The limitation

Replies are impossible, and registration is now required rather than optional

02

Dedicated virtual mobile number

Suits

Two-way conversations, reminders that accept a confirm or cancel reply

The limitation

Displays as a number, so first time recipients may not recognise you

03

Shared number pool

Suits

Low volume one way alerts with no reply expectation

The limitation

The sending number varies, so threading and replies are unreliable

04

Your existing landline, text enabled

Suits

Businesses whose published number is already well known locally

The limitation

Depends on carrier support and adds a provisioning step

How we work this out during scoping

Australian rules around alphanumeric sender IDs have tightened significantly, driven by scam messaging that impersonated banks and government services. The ACMA has moved the industry toward a register of legitimate sender IDs, with unregistered or impersonating IDs subject to blocking by carriers. The practical implication for you is to plan for registration of any sender ID you intend to use, expect the process to take time, and avoid designing a system that depends on a sender ID you have not secured.

Our usual recommendation is a hybrid: a registered sender ID for one way notifications where the brand name adds trust, and a dedicated number for anything that invites a reply. Both are provisioned under your account with the gateway, not ours.

Two-way SMS into your CRM

One way SMS is easy. The value usually sits in what happens when someone replies. A patient texts back to cancel, a customer asks whether you can come Thursday instead, a candidate says they are running late. If those replies land in a gateway portal that nobody has open, the automation has created a new way to miss things.

Unmatched numbers create a record rather than vanishing

We route inbound messages into the system where the work already happens. Keyword replies such as a confirmation or a cancellation are matched to the appointment or order and actioned automatically, updating the record and freeing the slot. Anything that is not a keyword is treated as a real message: matched to the contact, written to their timeline, and assigned to a person or queue with a response expectation. Unmatched numbers create a record rather than vanishing.

That routing is the part that fails most often in systems we are asked to repair, usually because the SMS tool was bought separately from the CRM and connected by nobody. We treat the gateway as plumbing and the CRM as the source of truth, which is the same principle behind our CRM automation work. Where scheduling drives the messages, the trigger points come out of your booking system rather than being maintained twice.

When SMS is the wrong channel

If your message is longer than a couple of sentences, needs a considered response, or contains anything a person might want to keep and refer back to, it belongs in email. Splitting a long message across several parts is a poor experience and costs more per send anyway.

The channel suits ongoing service relationships far better than one-off transactions

If your customer relationship is infrequent and low value, texting is likely to feel like an overreach. A retailer who someone bought from once two years ago is not owed the intimacy of a text message, and the opt out rate will confirm it. The channel suits ongoing service relationships far better than one-off transactions.

Be careful with sensitive content. Messages appear on lock screens where other people can see them, so anything about a health condition, a debt, a legal matter or an outcome should reference the appointment or the account without describing the substance. Providers delivering services under the NDIS and clinics under AHPRA advertising rules both need this discipline, and we design the templates accordingly rather than leaving it to whoever writes the copy. If you are unsure whether the whole channel is right, start with reminders only and measure the change in no shows before extending. Broader lifecycle messaging belongs in marketing automation, and providers should read our NDIS notes before automating participant communication.

How we scope it

Four ways to scope your SMS Automation project

We do not publish package prices, because the same brief can be a short build or a long one. These are the shapes the work usually takes. Tell us which one sounds like you and you will get a fixed written quote that spells out exactly what it covers.

First workflows

The two or three processes costing the most time now

Fixed written quote, agreed before work starts

  • Message inventory mapped across the customer journey
  • Gateway account and numbers provisioned in your name
  • Sender ID registration prepared and submitted
Request a quote
Most common

Connected stack

The systems you already pay for, talking to each other

Fixed written quote, agreed before work starts

  • Everything in First workflows
  • Consent capture and opt out keyword handling
  • Suppression list shared across SMS and email
  • Triggers integrated with your CRM or booking system
Request a quote

Operations platform

Operations running on automation you can see and audit

Fixed written quote, agreed before work starts

  • Everything in Connected stack
  • Reply routing to records, queues and owners
  • Quiet hours and public holiday logic
  • Carrier test results and a delivery reporting dashboard
Request a quote

Automation care

Watching, fixing and extending as the processes change

Rolling monthly, quoted in writing

  • Every workflow monitored, with alerts that reach a person
  • Fixes when an upstream system changes its behaviour
  • New workflows added from your backlog each month
  • Rolling, cancel with 30 days notice
Request a quote

These are shapes, not menus. Most quotes end up somewhere between two of them, and we will say so when the honest answer is the smallest one. Describe the problem and we will tell you which it is.

Questions buyers usually ask

Frequently asked questions

How long does it take to get automated SMS running?

Two to five weeks for most builds. The integration and testing take the bulk of it. The variable that most often extends a project is sender ID registration, which involves a third party process outside our control, so we start it in week one. If you use a dedicated number instead, provisioning is quicker and we can usually test within days.

What does SMS automation cost to set up and run?

Setup depends on how many message types you need, how many systems trigger them, and whether two-way reply handling is in scope. Ongoing, you pay your gateway per message directly, so volume is a running cost you control rather than something we mark up. We provide a fixed written quote for the build and help you model the send volume before you commit.

Who owns the gateway account and the message history?

You do. The gateway account is opened under your business, numbers and sender IDs are registered to you, and the message history is exportable. We work inside your account as a user you can remove. If you switch providers later, your numbers and your data are yours to move, subject to the gateway's porting process.

Reminders about a service someone has booked are generally treated as transactional rather than marketing, so the position differs from promotional messaging. That said, we still record consent and provide an opt out, because customers do not read legislation and a person who asks to stop receiving texts should stop receiving them. Where a reminder also promotes something, it becomes a commercial message and the Spam Act rules apply fully.

Can replies go to the person who actually needs to see them?

Yes, and this is the part worth getting right. Keyword replies such as confirmations and cancellations are actioned automatically against the booking. Free text replies are matched to the contact, written to their record and assigned to an owner or a queue with a response expectation. Nothing is left sitting in a portal that no one opens.

How do you stop customers being over messaged?

By mapping every message one customer can receive across their journey and enforcing a frequency cap in the sending layer, not just in each individual workflow. Quiet hours, state public holidays and a global suppression list apply across every source. We also review the message set after 30 days of real sending, and usually recommend removing at least one message.

Work out whether SMS is worth it for you

Tell us what you would send and how often. We will give you a straight answer within one business day, and a fixed written quote if it is worth building.