11 Aug Building the Right Sender ID Strategy for a Multi-User Organisation
Now that the ACMA’s Sender ID Register is in force, “which Sender ID should we use?” is no longer just a branding question – it’s a compliance and operational one. Here’s how medium-sized organisations should structure their SMS sending.
For a sole trader, choosing a Sender ID is a single decision. For an organisation with multiple departments, dozens of staff sending SMS, and a mix of transactional, operational and marketing messages, it’s an architecture question, and one worth revisiting now that the ACMA SMS Sender ID Register is fully operational.
First, the fundamentals
Every SMS your organisation sends uses one of two mutually exclusive sending methods:
Alpha Sender ID – an alphanumeric brand name (maximum 11 characters, no spaces or symbols) displayed in place of a number. It delivers instant recognition, but it is strictly one-way: recipients cannot reply, so opt-outs must be handled via alternative methods such as opt-out links. Since 1 July 2026, every Alpha Sender ID used to message Australian numbers must be registered with the ACMA – unregistered IDs are over-stamped “Unverified” on delivery.
Virtual Number – a dedicated Australian number exclusive to your organisation. Messages sent and received from the same number, enabling two-way workflows: reply-based confirmations, automatic STOP opt-out processing, keywords, and inbound campaigns. Virtual Numbers sit entirely outside the ACMA register – no registration required, ever.
A common misconception during the register rollout was that registering an Alpha Sender ID would attach the brand name to Virtual Number messages. It does not – the two methods never combine on a single message. The strategic question is therefore not “which one?” but “which one, for which message type?”
A message-type framework
We recommend organisations map every SMS use case against one question: does this message require, or benefit from, a reply?
| Message type | Reply needed? | Recommended sender |
|---|---|---|
| 2FA / authentication codes | No | Registered Alpha Sender ID |
| Payment & arrears notifications | No | Registered Alpha Sender ID |
| Outage / incident alerts to staff or clients | No | Registered Alpha Sender ID |
| Appointment & inspection reminders | Yes – confirm/reschedule | Virtual Number |
| Marketing campaigns | Yes – STOP opt-outs | Virtual Number |
| Customer surveys & feedback | Yes | Virtual Number |
| Text-in lead generation & keywords | Yes | Virtual Number |
The pattern most of our clients land on: registered Alpha IDs for high-trust, one-way notifications where brand recognition is critical, and Virtual Numbers for everything conversational. Both run side by side from the same MessagePort account.
Structuring this across teams
Where multi-user organisations get into trouble is inconsistency – one department sending reminders from an Alpha ID (and losing the replies), another sending marketing from a shared number the customer doesn’t recognise. MessagePort provides the controls to standardise this centrally:
- One registration, whole account. Once your Alpha Sender ID is approved via the ACMA register, it’s available to every user on your account – no per-user registration. Administrators can review the Sender ID list under Settings > Profile & Settings > SMS Settings.
- User management and permissions. Multiple administrators can oversee reporting and manage user lists, ensuring staff send from the approved Sender IDs for their function.
- Cost centres. Group users by department or division for reporting, so you can see exactly which teams are sending what – and from which Sender ID.
- Automated compliance. Opt-outs to your Virtual Number are processed automatically, keeping your database aligned with Spam Act unsubscribe requirements without manual handling.
Don’t forget the housekeeping
Two administrative points that caught many organisations out during the rollout:
- ABR currency. The ACMA verifies Sender ID registrations through the authorised contact recorded on the Australian Business Register. If your listed contact has left the business or the email address has lapsed, registration approval will stall until it’s corrected.
- Audit your integrations. Alpha Sender IDs configured in API workflows, Email SMS or third-party integrations count just the same as those used in the platform. An unregistered ID buried in an old integration is quietly delivering “Unverified” messages to your customers today.
Where to from here
If your organisation hasn’t reviewed its sender strategy since the register went live, now is the time. Our team can audit your account’s Sender IDs, complete any outstanding ACMA registrations on your behalf, and help you assign Virtual Numbers where two-way capability will lift response rates.
A well-structured Sender ID strategy isn’t just about avoiding an “Unverified” label – it’s about making sure every message your organisation sends arrives with the right identity, the right reply path, and full compliance built in.