The code took a day. The trust layer was the work.
Sending a text is the easy half. Getting your business name on it, in a way customers can trust, is the real work, and it is what Australia's SMS Sender ID Register is built to protect.
The ask
The client wanted their business name at the top of the SMS. Not a coding problem, a trust problem.
The mechanism
A verified layer around branded sender IDs, so a brand name is harder to fake and means something.
The work
The SMS code was a day. Lining one business identity up across four parties was the rest.
The takeaway
A business name in an inbox should mean something. Branded SMS is worth doing, scoped honestly.
The SMS feature worked on day one. The client could type a message, hit send, and it landed on a test phone.
But sending a text was only half the job.
What the client actually wanted was their business name across the top, the way a message comes from 'AusPost' or 'myGov' rather than an unknown mobile number. That part was not a coding problem. It was a trust problem.
A normal SMS can be sent quickly. A branded SMS sender ID has to prove it belongs to the business using it. That difference matters, because the same thing that makes branded SMS useful for legitimate businesses also makes it valuable to scammers.
A familiar name at the top of a message changes how people read it.
That is why Australia's SMS Sender ID Register exists.
Why branded SMS needs a trust layer.
Branded SMS is powerful because it removes ambiguity.
A customer who receives a reminder from their accountant, clinic, courier, school or utility does not have to guess whether the message is legitimate. The name at the top gives them context before they even read the first line.
But that only works if the name means something.
If anyone can send a message under any brand name, the sender ID becomes a costume. 'AusPost' can be copied. 'myGov' can be copied. A bank, insurer, telco, energy provider or local business can be impersonated by someone who has no relationship with that organisation at all.
That is the problem the register is designed to solve.
It does not make SMS perfect. It does not stop every scam. It does not replace customer education, fraud detection or common sense. But it does create a verified layer around branded sender IDs, so a business name in an SMS is harder to fake and more useful as a trust signal.
That is a good thing.
One identity, four parties.
You do not just write a line of code and claim a business name in the SMS inbox.
In our case, the provider was Sinch ClickSend. The process involved lining up one business identity across several parties:
- The Australian Business Register, where the ABN and authorised contact details need to be current.
- myID, where the representative proves they are a real person.
- ACMA Assist, where the sender ID is checked against the business name, trade mark or domain.
- The SMS provider, which lodges the registration and connects the business to the messaging network.
The government review itself was not the painful part. The time went into getting the identity details correct across the systems that all had to agree with each other.
That is an important distinction.
This is not a process that should always take two weeks. If the business has its ABN details, authorised contact, email address, domain and representative access ready, the path should be much smoother. In our case, there was back and forth over the fortnight to get everything lined up correctly.
The code was still the easy part.
Code was never the bottleneck.
When a feature touches money, identity or government, the timeline is often set by the systems around the software.
Payments onboarding has this shape. Bank API access has this shape. Government integrations have this shape. Branded SMS now has this shape too.
The engineering can be quick, but the delivery depends on proving that the right organisation is asking for the right access to the right system.
That is not bureaucracy for its own sake. It is the work that turns a feature from 'technically possible' into 'safe enough to trust'.
The friction is the feature.
From the customer's side, that friction is the feature.
The registration process can feel like friction if you are only looking at it from the build side.
But from the customer's side, that friction is the feature.
The point is not just to make businesses fill in forms. The point is to create a messaging environment where a sender ID has a verifiable relationship to the organisation using it.
That matters because trust has become scarce in the inbox.
People are being trained to distrust links, ignore unexpected messages and treat even familiar brands with suspicion. That suspicion is rational. The scam environment has made it rational.
A verified branded sender ID gives legitimate businesses a way to stand apart from that noise. It says: this message is not just technically delivered, it is coming through a channel where the sender name has been checked.
That is valuable for the customer. It is also valuable for the business.
Why businesses should use branded SMS.
For many businesses, SMS is still one of the most direct customer channels they have.
Appointment reminders. Delivery updates. Payment notices. One-time codes. Service alerts. Account notifications. Customer follow-ups.
These messages are often useful, time-sensitive and expected. But if they arrive from a random number, the customer has to do the trust work themselves.
A branded sender ID reduces that ambiguity.
It does not mean every customer will trust every message. It does not mean every SMS should contain links. It does not remove the need for careful wording and good security practice.
But it gives the message a cleaner starting point.
In an age of spam, that is not cosmetic. It is part of the customer experience.
The honest caveats.
The register only covers branded sender IDs. Plain mobile numbers are unaffected. Scammers will keep adapting.
That is why this should be understood as trust infrastructure, not a silver bullet.
It raises the cost of impersonation. It makes spoofed brand names harder to use. It gives legitimate organisations a clearer way to identify themselves. It gives customers one more signal when deciding whether a message deserves their attention.
That is the right kind of regulation: narrow, practical and aimed at restoring meaning to a channel people still rely on.
What I'd tell anyone commissioning this.
Do it, but scope it honestly.
The SMS code is the visible part. It is also the easy part.
The real work is making sure the business identity, domain, authorised representative, ABN details and provider setup all line up before you need them. If those pieces are ready, the process should be straightforward. If they are not, the back and forth can easily become the project.
That is not a reason to avoid branded SMS. It is the reason to treat it properly.
A business name in an inbox should mean something. Australia's Sender ID Register helps make that true.
The code took a day. The trust layer was the work, and the trust layer is the point.
Want your business name on your texts, in a way customers trust?
I build the SMS feature and walk the registration across the ABR, ACMA and an approved provider with you, so your brand name actually means something in the inbox.
Background: Australia's SMS Sender ID Register is administered by the Australian Communications and Media Authority (ACMA). Businesses register a branded sender ID through an approved telco or messaging provider, in this case Sinch ClickSend, with identity checked across the Australian Business Register and the government's myID Digital ID.