Wattle AI
Request access

Blog

22 Oct 2026

SMS Fallback for WhatsApp: Setting It Up in Australia

SMS fallback for WhatsApp means that when a WhatsApp message fails to reach a customer, your system automatically sends a text to the same mobile number instead. It is not switched on by default. You have to build it into your messaging workflow, decide which messages deserve it, and, in Australia, make sure the SMS side is compliant with the new Sender ID Register.

This guide covers how fallback works, how to configure it without paying twice or annoying customers, and where Australian rules change the picture.

WattleKeep Customer Messages MovingWattle brings WhatsApp conversations, SMS, calls, and website chats into one inbox, so your team can manage customer interactions across channels.Explore Wattle

TL;DR

  • SMS fallback is a failover: if WhatsApp delivery fails or goes unread, the same phone number gets an SMS. It has to be specifically built into your workflow, it is not a universal default.
  • Set the fallback timer to match your WhatsApp template’s time-to-live, or you risk double billing and duplicate messages.
  • Since 1 July 2026, branded SMS sender names in Australia must be registered on the ACMA SMS Sender ID Register, or carriers can replace them with “Unverified”.
  • Use fallback for time-sensitive, must-read messages such as booking confirmations and reminders. Do not use it to push marketing to people who only agreed to WhatsApp.

Table of Contents

What SMS fallback actually does

WhatsApp runs over the internet and needs the customer to have the app installed, a registered number and a working connection. SMS runs over the mobile network and reaches almost any handset. Fallback joins the two: WhatsApp is the first attempt, SMS is the safety net.

Per Alibaba Cloud’s documentation, the SMS is triggered when the first message cannot be delivered under conditions you specify, within a time you set. Typical triggers are an undelivered, unread or send-failed status report. Supported fallback windows usually run from 60 seconds to 43,200 seconds (12 hours), depending on the provider.

A few situations where it earns its keep:

  • The customer does not have WhatsApp, or uninstalled it.
  • The phone is off, in flight mode or has no data.
  • The number is not registered on WhatsApp at all, which you often only discover when you try to send.
  • A time-critical message has gone unread past the point where it is still useful, such as a same-day appointment change.

The unread trigger deserves caution. A message that is delivered but unread is not a failure. Treating it as one means you will text people who simply have not looked at their phone yet. We come back to this below.

Why Australia has its own wrinkles

The SMS Sender ID Register

The SMS half of your fallback has to work properly, and that is where Australia has changed. From 1 July 2026, telcos can only carry texts with alphanumeric sender IDs if they participate in the ACMA SMS Sender ID Register. If your business name is not registered through an approved provider, carriers can replace it with the label “Unverified” on the customer’s phone.

For a fallback message this is a real problem. The customer is already someone you could not reach on WhatsApp. If the text then arrives from “Unverified” rather than your business name, it looks like a scam and may be ignored. The onus for compliance sits with the business, so ask your SMS provider whether your sender ID is registered before you build anything on top of it.

If you want a closer look at how Australian confirmation texts work, including reply options, we cover it in our guide to SMS booking confirmations in Australia.

The SMS Sender ID Register — overview diagram

Consent for both channels

WhatsApp business messaging expects the customer to have opted in to hear from you on WhatsApp. An SMS fallback is a different channel with its own consent expectations. A customer who gave you their number to book a haircut has a clear reason to receive a booking reminder either way. A customer who agreed to WhatsApp updates about one order has not necessarily agreed to marketing texts.

Keep your records tight. We list what to keep in 7 records for audit-proof WhatsApp opt-in, and the same discipline applies to SMS consent. For the wider Australian picture, see WhatsApp customer support in Australia and ACMA opt-in gaps.

How to set up SMS fallback step by step

The exact settings depend on your messaging provider, but the logic is the same everywhere.

  1. Capture the mobile number as the primary identifier. Fallback needs a valid phone number to send to, even when the conversation began on WhatsApp. If your system identifies customers only by a WhatsApp profile or an email, there is nothing to fall back to. The 8x8 developer guide is explicit about this.
  2. Sort your messages into tiers. Decide which messages are must-read (confirmations, changes, access codes, payment problems) and which are nice-to-have (feedback requests, news). Only the first group gets fallback.
  3. Choose the trigger. Start with failed and undelivered statuses. Add unread only for messages that become useless if the customer misses them.
  4. Set the timer. A common recommendation is a fallback timeout of 10 to 60 seconds for urgent items, and it should align with or exceed the WhatsApp template’s time-to-live, per Alibaba Cloud. A timer shorter than the TTL means you can send an SMS and then have the WhatsApp message arrive afterwards.
  5. Write the SMS as its own message. It cannot rely on buttons, images or quick replies. Say who you are, what is happening, and what to do, in plain text. Include a reply keyword or a short link if you need a response.
  6. Register and test the sender ID. Confirm your registration, then send test messages to numbers on different Australian networks.
  7. Log both attempts against one conversation. Staff should see that a WhatsApp message failed and an SMS followed, in a single thread, so nobody chases the customer a third time.

Avoiding double billing and double messages

Misconfigured fallback is how businesses end up paying for a failed WhatsApp message and the SMS that replaced it, as Alibaba Cloud notes. Some of that cost is unavoidable, but a lot of it is design.

On the WhatsApp side, Meta says it does not charge for service messages, or for utility messages sent in response to the customer. Charges are based on the message category and the recipient’s country, so check the current rate card with your provider before you model costs. Reply-driven flows, where the customer messages first, are cheaper than business-initiated templates, and they need fallback less often because the customer is demonstrably on WhatsApp.

Practical rules:

  • Fall back once. One SMS per failed message, never a loop.
  • Suppress the SMS if WhatsApp delivery is confirmed before the timer runs out.
  • Do not fall back on marketing broadcasts. If WhatsApp could not deliver a promotion, that is rarely a reason to text it.
  • Cap by customer. If a number has failed on WhatsApp several times, mark it as SMS-first rather than trying WhatsApp each time.

If you are choosing between broadcast and personal messaging on WhatsApp in the first place, our comparison of WhatsApp broadcast vs one-to-one covers the trade-offs.

Which messages deserve a fallback

The industry pattern among businesses that handle this well is a tiered approach: rich messaging for dialogue, reliable text for must-read notifications. Fallback protects the customer experience at time-sensitive moments. It is not a way to save money.

Message type WhatsApp first? SMS fallback? Why Booking confirmation Yes Yes The customer needs proof the booking exists Same-day reminder Yes Yes Useless if it arrives late, so use a short timer Reschedule or cancellation by you Yes Yes A missed notice costs the customer time Payment failed or invoice due Yes Yes, if consent covers it Time-sensitive and financial Quote follow-up Yes Optional Useful but not urgent Review request Yes No Low value, not worth a second message Promotions Yes No Fallback invites consent problems

For appointment-based businesses, reminders are the clearest win. A guide to compliance-ready WhatsApp appointment reminders walks through how small businesses use WhatsApp for rich conversations and keep SMS for the notifications that must land.

WhatsApp versus SMS: what each is good at

SMS is simple and near universal. WhatsApp is richer but more demanding. Sending marketing at scale through WhatsApp requires access to the WhatsApp Business API and users who have opted in to WhatsApp specifically, which Notifyre describes as more complex and less universal than SMS.

That is why the two work well together. WhatsApp handles the back-and-forth: questions, photos, quick replies, booking changes. SMS handles reach. If you are building the WhatsApp side, our guides on launching compliant WhatsApp business automation and WhatsApp quick replies will save you time, and a click-to-chat link gives customers an easy way to start the conversation themselves, which is the cheapest and most reliable entry point.

Keep a record, whichever channel delivers

Fallback creates two messages for one event, and both may matter later. The NSW Government’s guidance says that text and instant messages, including WhatsApp, can be business records and should be captured into a proper recordkeeping system rather than left in a messaging app. That guidance is written for the NSW public sector, so it is not a rule for private businesses. It is still a sensible standard: keep confirmations, changes and payment notices somewhere you control.

In practice, log the delivery status, the channel used, the timestamp and the message text against the customer’s record. If a customer says they never got a reminder, you can show exactly what was sent and how.

Four fields logged for a customer message

Our view on fallback

We talk to a lot of service businesses, and the same pattern keeps appearing: the missed message is rarely a technology failure. It is a handover failure. The WhatsApp message went nowhere, the SMS was never set up, and nobody on the team knew until the customer turned up at the wrong time or did not turn up at all.

So our advice is to start with the customer’s outcome and work backwards. What must they know, by when? Then pick the channel that gets them that, and the one that backs it up. Most of the value comes from three things:

  • One inbox, so staff see the WhatsApp attempt, the SMS and the customer’s reply in one thread.
  • Clear rules for when a conversation goes to a person instead of being retried automatically.
  • Honest consent records, because a clever fallback built on shaky consent is a liability.

We would rather a business send fewer messages that land than more messages that annoy. If you only get one thing right, make the must-read tier reliable and leave everything else on the lighter channel.

— Christopher

Where Wattle fits

Wattle is an AI front desk for service businesses. It answers calls, website chat, WhatsApp and SMS, books appointments into your calendar, and hands sensitive or complex conversations to your staff. Everything lands in one workspace, so you are not stitching WhatsApp and SMS history together by hand. Plans start at A$99 per month for Starter, with Pro at A$499 per month and Max at A$999 per month. Australian mobile numbers, outbound calling and transfers are listed separately on the pricing page, and you can see what each plan includes on our features page.

If your customers book by text, our guide to two-way SMS for bookings, support and payments shows what that looks like day to day.

Common mistakes

  • Treating unread as failed. Give people a reasonable window before texting, unless the message really is urgent.
  • Forgetting the sender ID. A fallback from “Unverified” can do more harm than no fallback.
  • Sending the same wording on both channels. WhatsApp copy often leans on buttons and emoji. The SMS needs to stand alone.
  • No stop rule. After a failed WhatsApp and a sent SMS, the system should not keep trying. Escalate to a person instead.
  • Ignoring numbers that never had WhatsApp. Learn from the first failure and route that customer to SMS from then on.
  • Relying on the app as the archive. Capture the record elsewhere.

If your wider goal is to bring leads into a single coordinated flow across channels, this overview of omnichannel marketing for service businesses is a useful read on joining the channels up.

FAQ

Is SMS fallback for WhatsApp automatic?

No. It has to be configured in your messaging platform or built into your workflow, and it depends on you holding the customer’s mobile number. Check whether your provider supports it and which triggers and timers it offers.

How long should I wait before the SMS is sent?

For urgent items such as same-day changes, providers commonly suggest timers of 10 to 60 seconds, but the timer should not be shorter than the template’s time-to-live. For less urgent messages, wait longer, since supported windows run up to 12 hours with some providers.

Will I be charged for both the WhatsApp message and the SMS?

Potentially, yes. A failed WhatsApp message can still be billed in some setups, and the SMS is billed on top. Misaligned timers cause the worst of it, so suppress the SMS when delivery is confirmed and check your provider’s rate card.

Do I need to register my SMS sender name in Australia?

If you send texts under a branded sender ID, yes. Since 1 July 2026 the ACMA SMS Sender ID Register applies, and unregistered names can be replaced with “Unverified”. Ask your SMS provider to confirm your registration status.

Can I use fallback for marketing messages?

It is better not to. A customer who opted in to WhatsApp has not necessarily agreed to marketing texts, and a failed promotion is rarely worth a second send. Keep fallback for confirmations, reminders and other must-read notices.

Sources

Recommended

Ready when the phone rings

Give every caller a good first answer.

Request access