Wattle AI
Request access

Blog

13 Oct 2026

SMS Booking Confirmations in Australia: ACMA Setup and Reply Options

Send a short, branded SMS at booking that names the time, booking code and a clear reply action: it lifts attendance measurably. A pooled analysis found text notifications raised attendance to 67% versus 54% without them, and ACMA now governs how sender IDs must be registered. Below are templates, timing rules and a compliance checklist, along with how a platform like Wattle automates the whole sequence.

TL;DR:

  • Use a standard mobile number or shortcode for replies; alphanumeric Sender IDs cannot receive texts and are expected to need registration by July 1, 2026.
  • Send an immediate confirmation, then schedule multiple reminders, including a closer reminder or an appointment day text when travel, parking, or preparation could affect attendance.
  • Each message should name the customer, service, full date and time, location or link, booking reference, brand, and a clear reply or contact instruction.
  • Record when and how each customer consented, provide a working unsubscribe option, and keep promotional offers out of transactional booking messages.
  • Automate incoming cancellation and rescheduling replies to release slots or offer alternatives, alert staff when needed, and send a fresh confirmation after changes.
Wattleheywattle.comKeep Booking Conversations MovingWattle can send SMS follow-ups, manage customer replies in one inbox, and support appointment booking across connected channels.Explore Wattle

Table of Contents

Why SMS booking confirmations work

The case for SMS confirmations is not guesswork. A meta-analysis of electronic notifications found patients receiving them were considerably more likely to show up, with pooled attendance at 67% in the intervention groups compared with 54% in control groups, and no-show rates falling from 21% to 15% (Pubmed). A separate systematic review and meta-analysis published in BMJ Open reached a similar conclusion, reporting a risk ratio of 1.23 for attendance among people who received electronic text notifications, with the same pooled attendance split of 67% versus 54% (BMJ Open).

A pooled analysis of electronic notifications found attendance rose to 67% from a 54% baseline, with no-shows dropping from 21% to 15% (pubmed.ncbi.nlm.nih.gov). That gap matters for any business juggling a booking calendar: fewer no-shows mean fewer empty slots and less time spent chasing people by phone.

Part of the advantage is purely operational. Text messages get read within minutes of arriving, unlike emails that sit in an inbox, and customers can glance back at a text days later to confirm the time without digging through their calendar. The BMJ Open review also found that multiple reminders outperform a single message, a pattern consistent with simple behavioural logic: a second nudge closer to the appointment catches people who forgot the first one, and a reply option gives them an easy way to reschedule instead of simply not turning up.

Why SMS booking confirmations work — overview diagram

What to include in an SMS confirmation

A confirmation message only does its job when it answers every question a customer might have without them needing to call you back. The core fields rarely change across industries:

  • Customer name, so the message feels personal rather than like a mass broadcast.
  • Service or booking type, named plainly (consultation, haircut, table, check-in).
  • Date and time, written in full rather than abbreviated to avoid confusion.
  • Location or link, including a street address or a video call link where relevant.
  • Booking code or reference number, so staff can pull up the record instantly.
  • Confirm or cancel instruction, telling the customer exactly what to reply.
  • Contact method, a phone number or short link for questions.

Beyond the functional fields, a few compliance cues belong in every message. The brand name should appear in the body of the text itself, not just the sender field, so recipients know who is messaging them. A working unsubscribe or opt-out instruction needs to be present or easily accessible, and businesses should keep a record of when and how each customer consented to receive texts, since this is the evidence you would need to produce if a complaint ever surfaced.

One decision shapes everything else: whether the message needs to support replies. If you want customers to text back “YES” to confirm or “RESCHEDULE” to change a booking, you need a standard mobile number or shortcode, because using an alphanumeric Sender ID disables incoming replies entirely (Support). Alphanumeric sender IDs still have a place: they are well suited to one-way notices like order updates or appointment reminders where no reply is expected, and they let you put a recognisable brand name in the “from” field instead of a number. For anything built around a reply, such as confirm/cancel flows, a two-way number is the only option that works.

Ready-to-use templates and examples by business type

Below are starting templates for common booking scenarios. Each is written to fit within a single SMS segment where possible and to make the required reply unmistakable.

  1. Appointment confirmation (two-way): “Hi [Name], your [service] is booked for [date] at [time] with [business]. Booking ref: [code]. Reply YES to confirm or NO to cancel.”
  2. Reservation confirmation: “[Business] confirms your table for [party size] on [date] at [time]. Ref: [code]. Reply CHANGE to adjust your booking.”
  3. Hotel check-in reminder: “Welcome to [business]! Check-in from [time] on [date]. Your booking ref is [code]. Reply if you need an early check-in.”
  4. Tradesperson or home service job: “[Business]: your technician is scheduled for [date] between [time window]. Job ref: [code]. Reply RESCHEDULE if this no longer suits.”
  5. Class or event booking: “You’re registered for [class/event] on [date] at [time], [location]. Ref: [code]. Reply CANCEL if you can’t make it.”

Pro Tip: Keep each message concise where you can; a shortened link for maps or directions can help avoid pushing the text into another chargeable segment.

A few notes make these more reliable in practice. Avoid attaching large files like vCards directly in the SMS body since most carriers do not render them; a link to an add-to-calendar page works better. Keep character limits in mind when adding a business name and a shortened link together, as both use up the available message space quickly. For trade teams juggling multiple jobs a day, a practical set of booking confirmation templates built specifically around service call scheduling can be a useful starting point to adapt.

Timing, cadence and follow-up strategy

Sending one message is not enough on its own. A sensible baseline cadence looks like this:

  • Immediate confirmation the moment the booking is made, while the details are still fresh for the customer.
  • A reminder ahead of the appointment, giving people notice to reschedule if something has come up.
  • A follow-up reminder closer to the appointment, catching anyone who missed or ignored the first text.
  • A day-of reminder, useful for appointments where traffic, parking or preparation time matters.

The BMJ Open review found that multiple notifications improve attendance more than a single reminder (BMJ Open). A small number of well-timed texts can capture the benefit without tipping into the kind of frequency that reads as spam.

Build the reply path into the cadence itself. When a customer texts back “RESCHEDULE” or “CANCEL”, the system should automatically open a new time slot, notify staff, and (where possible) offer alternative times without anyone needing to pick up the phone. That loop is what turns a one-way reminder into a genuine reduction in administrative work.

Setup checklist and Australian compliance requirements

Getting SMS confirmations running properly in Australia means a handful of decisions and checks before the first message goes out.

  • Choose your messaging mode first. A two-way long number supports replies like “YES” or “RESCHEDULE”; an alphanumeric Sender ID is one-way only and cannot receive incoming texts (Support).
  • Register any alphanumeric Sender IDs through a participating telco. Under the Telecommunications (SMS Sender ID Register) Industry Standard, ABN entities can ask their originating telco to initiate registration, and unregistered sender IDs may be labelled or restricted (Telecommunications (SMS Sender ID Register) Industry Standard 2025). Providers typically note this process can take around two weeks (Sender IDs).
  • Capture and store consent records for every customer, noting when and how they agreed to receive texts, consistent with Spam Act 2003 obligations (SMS Marketing Compliance Australia).
  • Build in a working unsubscribe mechanism and confirm that an opt-out request propagates across every system promptly.
  • Test end-to-end before going live: send a real confirmation, check the delivery receipt, confirm the message does not appear as “Unverified” to the recipient, and verify that a suppression-list entry actually blocks future sends.

Pro Tip: Run a test send to your own phone on each carrier you expect customers to use (Telstra, Optus, Vodafone), since labelling and delivery behaviour can differ slightly between networks.

From 1 July 2026, alphanumeric sender IDs sent to Australian numbers are expected to be registered, and unregistered messages risk being labelled “Unverified” or blocked outright (SMS Marketing Compliance Australia). Building the registration step into your setup checklist now avoids a scramble later.

Integrations and automation: connecting booking systems and calendars

Manually typing out confirmation texts does not scale past a handful of bookings a week. The standard automation pattern looks like this: a booking platform fires a webhook the moment an appointment is made, a workflow engine (an automation tool or a dedicated SMS platform) picks up that event, sends the confirmation through an SMS provider’s API, and writes the result back to the calendar.

Two-way workflows add a layer: when a reply comes in, the system needs to parse it, either by matching keywords like “YES” or “CANCEL” or by using more flexible natural language handling, then update the booking record and notify staff if a human needs to step in. Calendar integrations such as Google Calendar or Cal.com make this loop useful in practice, since a confirmed or rescheduled booking should show up on the business’s calendar without anyone re-entering it by hand.

When evaluating an SMS provider or automation tool for this job, check for:

  • Sender ID support for both two-way numbers and registered alphanumeric IDs.
  • Delivery receipts, so you know a message actually reached the handset.
  • Retry logic for failed sends, especially on carrier-side errors.
  • Webhook callbacks that notify your systems the moment a reply arrives.
  • Multi-channel fallback, dropping to email or a phone call if a text fails to deliver.

Troubleshooting and best practices

A few recurring issues account for most confirmation problems:

  • Messages showing as “Unverified” or getting blocked usually trace back to an unregistered Sender ID; check your registration status with your telco first.
  • Opt-outs not propagating across every system promptly is a compliance gap worth testing deliberately, not assuming that it works.
  • Marketing content disguised as a transactional confirmation risks complaints and carrier filtering; keep promotional offers out of booking texts entirely.
  • Skipping brand identification in the message body makes a legitimate confirmation look like spam.
  • Not tracking delivery receipts, response rates and no-show trends means you are flying blind on whether the wording or timing actually works.

Handling cancellations and rescheduling requests

A confirmation message is only half the job if customers have no easy way to change plans. Building a reply path for “CANCEL” or “RESCHEDULE” directly into the original text turns a dead-end notification into a working two-way channel.

When a customer replies “CANCEL”, the booking should be released automatically, the slot freed on the calendar, and a brief acknowledgement sent back so the customer knows the request went through. A reply of “RESCHEDULE” works best when it triggers either an automatic offer of the next available times or a quick handoff to staff, depending on how much flexibility the business can support without a person getting involved.

The details matter here. A cancellation confirmation should restate the booking reference so there is no ambiguity about which appointment was cancelled, and a reschedule flow should close the loop with a fresh confirmation text once a new time is locked in, repeating the same core fields (date, time, location, reference) as the original message. Leaving a cancellation or reschedule request unacknowledged, even for a few hours, tends to generate a follow-up phone call, which defeats the purpose of automating the exchange in the first place.

Personalisation techniques that improve engagement

A confirmation text addressed to “Hi Sarah” rather than “Dear Customer” reads as considered rather than mass-produced, and that small difference affects how seriously people treat the message. Beyond the name, a few other details lift engagement without adding complexity.

Referencing the specific service booked, rather than a generic “your appointment”, signals that the business tracks details properly: “your colour and cut with Jade” lands differently than “your appointment”. Mentioning a returning customer’s history, such as noting it is their third visit or referencing a preference they have given before, reinforces that the relationship is remembered rather than reset with every booking.

Timing the tone to the context also counts as personalisation. A reminder for a relaxed service like a haircut can carry a slightly warmer tone than one for a time-sensitive medical appointment, where clarity and brevity matter more than friendliness. None of this requires a complex system: most booking and CRM platforms already hold the customer’s name, service history and preferences, and feeding those fields into a message template is usually a configuration step rather than custom development.

Security practices for protecting customer data in SMS

SMS confirmations carry personal details, names, appointment types, locations and sometimes payment references, which makes basic data hygiene worth taking seriously. Store customer phone numbers and booking details in systems with access controls, rather than in shared spreadsheets that anyone on the team can open.

Avoid putting sensitive details, such as full payment card numbers or medical specifics, directly in an SMS body, since text messages are not an encrypted channel in the way a secure web portal is. A booking reference and a link to a secure page is a safer way to let customers view or pay for something than spelling it out in plain text.

Keep an audit trail of consent and message history for each customer, since this record is what demonstrates compliance if a dispute or complaint arises. Limit which staff members can export or download contact lists in bulk, and remove access promptly when someone leaves the team. These are small operational habits, but they are what separates a business that can answer a data question confidently from one that cannot.

Author perspective: quick operational fixes and common mistakes

The mistakes I see most often are unregistered sender IDs, no record of consent, and a single reminder that arrives too early to matter. Three fixes pay off within a week: put the brand name and booking code in every message, add a second reminder closer to the appointment, and test the reply path end to end before trusting it with real customers. Run templates in live traffic and watch the response data, not assumptions.

— Christopher

How Wattle automates confirmations and two-way SMS

Handling customer communications and bookings is exactly the kind of repetitive work we built Wattle to take off a team’s plate. We connect phone, web, WhatsApp and SMS into one inbox, bringing customer communications together rather than making staff check separate channels.

  • We bring customer communications and calendar integrations together in a single workspace.
  • Staff can take over any conversation the moment a customer needs a human, without losing the thread.

Getting started means connecting a calendar, picking a confirmation template and running a test booking end to end. See Starter, Pro and Max plans to find the right fit.

FAQ

Does Booking.com send confirmation emails?

Booking platforms generally send a confirmation by email when a reservation is made, separate from any SMS confirmation a business sends directly. For bookings made through your own calendar or CRM, the SMS confirmation is the one you control and can customise with your own branding and reply instructions.

How do I activate SMS notifications?

Activating SMS notifications typically means connecting your booking or calendar system to an SMS provider or automation platform, then setting up a template that triggers at the moment of booking. If you need two-way replies like “YES” or “RESCHEDULE”, you will need a standard mobile number or shortcode rather than an alphanumeric Sender ID (support.touchsms.com.au).

How do I write a booking confirmation?

A clear booking confirmation names the customer, the service, the exact date and time, the location or link, a booking reference, and a plain instruction for confirming, cancelling or rescheduling. Keeping the brand name in the message body and using concise wording help it read clearly on any handset.

Where is my booking code?

A booking code or reference number is included in the original confirmation text sent at the time of booking, and it typically reappears in any reminder messages that follow. If a customer has lost the message, the business can look up the booking directly using the customer’s name or phone number in their booking system.

Sources

Recommended

Ready when the phone rings

Give every caller a good first answer.

Request access