16 Jul The ACMA SMS Sender ID Register: Lessons from the Rollout

The Sender ID Register came into full effect on 1 July 2026. Having guided hundreds of organisations through registration, we’ve identified the misconceptions that caused the most disruption, and what your business should verify now that the rules are live.

The Australian Communications and Media Authority’s SMS Sender ID Register is now fully operational. Established under the Telecommunications (SMS Sender ID Register) Industry Standard 2025 as part of the Federal Government’s Fighting Scams initiative, the register addresses a genuine vulnerability: for years, scammers exploited loosely managed Alpha Sender IDs to impersonate banks, government agencies and major brands – with fraudulent messages landing in the very same thread as legitimate ones.

From 1 July 2026, telcos are required to over-stamp any unregistered Alpha Sender ID with the label “Unverified” on messages delivered to Australian mobile numbers. For organisations sending transactional alerts, 2FA codes, payment notifications or marketing at scale, that label carries real commercial consequences: reduced trust, lower engagement, and customers second-guessing legitimate communications.

The policy objective is sound. The rollout, however, exposed widespread confusion about what the rules actually require. Here are the three misunderstandings we encountered most frequently, and the clarifications every organisation should have on record.

Misconception 1: Registration is mandatory for every SMS sender

The single most common assumption we saw was that all businesses sending SMS were required to register a Sender ID before the deadline.

The register applies exclusively to Alpha Sender IDs – the alphanumeric brand name (e.g. “Edgility”) displayed in place of a phone number. Organisations sending from a Virtual Number or Shared Local Number – a dedicated Australian mobile or long code number assigned exclusively to their account – are entirely outside the scope of the legislation. No registration is required, and no action was ever needed.

If your organisation has never used an Alpha Sender ID, the register imposes no new obligation on you. There is no requirement to adopt one, and for many use cases – particularly anything requiring replies – a Virtual Number remains the stronger operational choice.

Misconception 2: Registering an Alpha Sender ID adds your brand name to Virtual Number messages

Many organisations registered an Alpha Sender ID expecting their business name to then appear alongside, or instead of their Virtual Number on outbound messages. This reflects a fundamental misunderstanding of how SMS Sender IDs work.

Alpha Sender IDs and Virtual Numbers are mutually exclusive sending methods. Each message is dispatched from one or the other:

• Alpha Sender ID: your organisation’s name is displayed; recipients cannot reply. One-way only.
• Virtual Number or Shared Local Number: the message originates from your dedicated number; recipients can reply, and all correspondence threads are consistently under that number.

Registration verifies your organisation’s authority to use a branded name when sending from that name. It does not, and cannot, overlay branding onto number-based sending – the two operate on entirely separate mechanics within the telco network. Organisations wanting both brand presence and two-way capability typically run both methods in parallel: registered Alpha IDs for one-way alerts, Virtual Numbers for anything conversational.

Misconception 3: Virtual Numbers must be registered with the ACMA

A number of organisations attempted to register their Virtual Number as their Sender ID – some were concerned their messages would be flagged “Unverified” without it. To be clear: the legislation applies to alphanumeric Sender IDs only. Numeric senders – Virtual Numbers, long codes and standard mobiles – have always been tightly managed within the carrier network and sit outside the register entirely.

Messages sent from a Virtual Number will never be over-stamped as “Unverified”. There is no registration pathway for numbers because none is required.

What organisations should verify now

With the register live, we recommend a short internal audit:

1. Identify every Alpha Sender ID in use across your organisation. Login navigate to Settings > Sender IDs to review your Sender ID list. Multi-department organisations should check all sending workflows, including API integrations and Email SMS.
2. Confirm registration status. Any unregistered Alpha ID currently in use is being delivered as “Unverified” to your customers right now. Registration remains open – our ACMA Sender ID Registry page outlines the process, which Edgility manages on your behalf.
3. Check your ABR details. The ACMA verifies registrations via the authorised contact listed on the Australian Business Register.
4. One registration covers your whole account. Once your Sender ID is approved, it is shared across all users of your Edgility account – there is no per-user or per-department registration requirement.
5. Review your sending strategy. If the “reply STOP” opt-out, two-way confirmations or inbound workflows matter to your operations, ensure those message types are routed through a Virtual Number rather than an Alpha ID.

The upside worth remembering

Compliance obligations aside, the register genuinely strengthens the channel your business relies on. Verified Sender IDs mean your customers can trust that a message displaying your name is from you, and that scam messages impersonating your brand are flagged before they do damage. For organisations that have invested years building customer trust over SMS, that protection is significant.

If you’re uncertain about your organisation’s registration status or sender strategy, contact our team – we’ll review your account configuration and confirm exactly where you stand.