Workshop SMS Reminders in Australia: Spam Act, Consent and Sender IDs

The Spam Act regulates commercial electronic messages with an Australian link. Section 6 looks at the content and presentation of the message and the material available through its links and contact details. If one purpose is to offer, advertise or promote goods, services, a supplier or a business opportunity, the message can be commercial.

That makes internal labels unreliable. A software button named ‘service reminder’ does not automatically make the resulting SMS factual, and a template named ‘customer update’ does not remove a promotional sentence. The actual message received by the customer is the relevant object.

ACMA has specifically warned that a bill, invoice, account or service message can become commercial when it also contains promotional or sales content. A workshop therefore needs to examine the complete rendered message, including a booking link, offer, review request or deferred-work invitation, rather than assuming the operational first sentence controls the classification.

ACMA says messages are generally not spam when they are appointment or payment reminders or notifications of a service or product fault. The Spam Act also defines a designated commercial electronic message that contains no more than factual information, directly related comment and permitted identification details. These factual messages receive a partial exemption from the consent and unsubscribe rules.

The boundary is narrower than many templates imply. ‘Your vehicle ABC123 is booked tomorrow at 8:00 am’ is factual. ‘Your vehicle is booked tomorrow—ask us about our discounted air-conditioning service’ introduces promotion. A payment reminder can similarly cross the line if it also advertises a new product or asks the customer to buy something unrelated to the existing account.

Factual-only status is not a reason to hide the sender. Schedule 1 of the Act says designated factual messages must still comply with section 17, which requires accurate identification of the person or organisation authorising the message and usable contact information. Clear identity also reduces customer hesitation around links and vehicle information.

ACMA describes express and inferred consent. Express consent is the clearer evidence: the person knowingly agrees to receive marketing by completing a form, actively ticking a website choice, agreeing by phone or consenting in person. ACMA recommends keeping who consented, when they consented and how that consent was given.

Inferred consent can exist where the recipient knowingly supplied the address, has a provable ongoing relationship with the business and could reasonably expect directly related marketing. ACMA also makes clear that a one-off purchase does not by itself create inferred consent for future promotions. Workshops should not turn every invoice mobile number into an indefinite campaign list.

An electronic marketing message cannot be used merely to ask for consent because that request is itself a commercial message. Purchased lists do not shift responsibility either. The workshop authorising the messages remains responsible for establishing consent even when the list, automation or delivery platform came from another provider.

Every commercial electronic message must accurately identify the individual or organisation that authorised it and include correct contact information. ACMA says those details must remain correct for at least 30 days after sending. If a software or marketing provider sends on the workshop's behalf, the message still needs to identify the workshop rather than only the technology provider.

Sender identification inside the content is separate from the technical sender shown at the top of the phone. A message sent from an ordinary mobile-capable number can be replied to and does not use an alphanumeric Sender ID. A branded Sender ID is the short business name displayed instead of a number, such as an acronym or trading name.

The two mechanisms should reinforce each other. The body should still make the workshop and contact path understandable, while the configured SMS route should be documented so staff know whether replies, STOP commands and Sender ID registration are supported.

ACMA says every commercial message must make unsubscribe clear and easy. The method cannot charge a fee beyond the ordinary cost of using the address, require extra personal information or force the recipient to create or log in to an account. A typical two-way SMS instruction is ‘Reply STOP’; another working low-cost contact method can be used where replies are unavailable.

The request must generally be honoured within five working days. The unsubscribe facility also needs to remain functional for at least 30 days after the message is sent. That means an expired campaign page or a sender address that cannot receive the stated response can fail even when the template contains the word ‘unsubscribe’.

ACMA has highlighted a common technical error: an alphanumeric Sender ID usually cannot receive replies, so telling the customer to reply STOP to that header does not create a working facility. A workshop using a branded one-way name needs another valid unsubscribe path and a reliable process that updates the sending list.

Australia's SMS Sender ID Register now changes how unregistered branded messages appear. ACMA says that from 1 July 2026 an unregistered Sender ID can be replaced by ‘Unverified’ and grouped with other unverified messages on the recipient's phone. The intention is to make business impersonation harder and give customers a clearer warning signal.

A Sender ID is a branded name at the top of the message, generally between two and eleven characters and subject to content and organisation-linking rules. An organisation with an ABN needs current authorised-contact or service-of-notice information on the Australian Business Register and works through its telco or messaging provider to register the name.

ACMA also states that a business sending from a phone number rather than a branded Sender ID does not need to do anything for this register. Workshop buyers should therefore ask their software provider which route is actually used, whether two-way replies are supported and who owns any Sender ID registration. A logo in an SMS-settings screen is not proof that the technical route has been registered.

The legal rule belongs to the workshop, while the evidence is often distributed across staff and systems. Consent might have been given on a paper form, at the counter, through an online booking or during a call. An unsubscribe might arrive by STOP, email, phone or an in-person request. If those events do not update one usable customer record, the next campaign can repeat the problem.

Useful software preserves the distinction between a mobile number, permission to send a factual job message, permission for commercial marketing and a recorded SMS opt-out. It also records who changed the state, when it changed and which inbound message created it where available.

Recycled mobile numbers make record quality more important. ACMA's current consumer guidance recognises that unwanted messages can be intended for a previous number holder. A customer identity, vehicle and recent outbound context should be unambiguous before an inbound reply changes consent or opens a workshop task.

ACMA is explicit that a business remains responsible when another company sends its marketing messages. That includes outsourced campaign services, bought lists and software automation. A provider can supply technical controls, but it cannot know the purpose of every sentence or establish consent that the workshop never collected.

A credible workshop-software demonstration should therefore show the control plane as well as the send button: master enablement, automatic-event enablement, template wording, consent and opt-out state, queued and delivery results, inbound processing, failure handling and the staff history.

The same evidence protects the customer experience. A message that arrives twice, uses the wrong vehicle, cannot accept STOP or leads to a portal for another customer is not merely a marketing inconvenience. It damages confidence in every later workshop update and link.

The Office of the Australian Information Commissioner explains that commercial email and SMS marketing is governed by the Spam Act, while APP 7 applies to other forms of direct marketing in defined circumstances. Other Australian Privacy Principles can still apply to the collection, use, disclosure, quality and security of the personal information surrounding a message.

Coverage varies. APP entities generally include private-sector organisations above the relevant turnover threshold and some smaller businesses in specified categories. A workshop should confirm its own position rather than assuming that the Spam Act replaces every privacy obligation or that small-business status makes customer communication risk irrelevant.

Operationally, the safer design remains consistent: collect only the contact context required, explain its purpose, restrict staff access, keep details accurate, protect links and retain an understandable history. These controls are useful even where a particular statutory provision does not apply to the workshop.

Workshop HQ's customer-communication workflow is available now. Staff can send individual SMS updates from workshop context, booking confirmations and reminders can be enabled through automatic rules, and owners have separate controls for customer SMS, automatic sending, event activation, timing and template wording.

Where the configured provider supports the events, outbound records retain queued, sent, delivered or failed state. Supported inbound routes capture replies against an unambiguous customer and repair-order context, recognise common opt-out commands including STOP and UNSUBSCRIBE, update SMS opt-out state and create a visible customer-question follow-up for staff. Service reminders, deferred-work follow-ups and review requests are gated by recorded marketing consent.

Workshop HQ does not claim that software automatically makes every workshop message legally compliant. The workshop controls the recipient, purpose and final wording and remains responsible for consent and sender obligations. Branded Sender ID availability and registration depend on the configured provider route and should be verified before use. That boundary is part of the product evidence: useful controls, visible history and an honest statement of who owns the decision.