Recording business calls in Australia, done properly.

What the law actually says (the careful bit)

Australia does not have one single call recording law. The rules are layered: federal law deals with intercepting communications while they travel over the network, and each state and territory has its own surveillance devices legislation covering the recording of private conversations. Those state laws are not identical, and the differences matter.

For a small business, running a different recording policy for every state your callers might be in is a losing game. The posture that is compliant everywhere is informed consent: tell people, clearly and before recording starts, that the call may be recorded, and give them a way to object. That is the entire reason the "this call may be recorded" announcement exists. Every big company plays it not because it sounds professional, but because it works in every state.

One thing before we go on: this page is general information, not legal advice. State rules differ, some industries carry extra obligations, and your situation is yours. Confirm your obligations for your state with your lawyer before you switch recording on. It is a short conversation and it is worth having.

Why businesses record calls

Four reasons come up over and over with small businesses:

• Disputes. "We were quoted X" versus "you agreed to Y" arguments end quickly when there is a recording. For quotes, orders and verbal instructions, it is the cleanest evidence you can hold.
• Training. Real calls are the best training material there is. New staff hear how your best people handle the hard questions, and call reviews stop being guesswork.
• Compliance. Some industries are expected to keep an accurate record of advice or instructions given over the phone. A recording beats a hand-typed note every time.
• Abusive callers. The announcement alone changes behaviour. People are more civil when they know they are on record, and if a call does go bad, your staff member has proof instead of a bad memory of a worse afternoon.

Where the recording actually happens

There are three places call recording can live, and they are not equal.

On the phone platform. Modern hosted PBX and VoIP systems record at the platform level. It is a feature you switch on, per user, per queue or across the whole system, and the announcement, storage and access controls live in the same place. This is honestly one of the better reasons to move off old analog lines: on a hosted business phone system, recording is a checkbox, not a project.

On the handset. Recording apps on individual mobiles work, but they scale badly. Every device is its own silo, files end up scattered across personal phones, someone forgets to press record, and there is no central retention or access control. Fine for a sole trader, poor for a team.

In the middle. The old way: recording hardware or software wedged between a legacy PBX and the line. It still works, and it costs more to buy and maintain than either option above. If your gear is old enough to need it, the better spend is usually replacing the system, not bolting onto it.

Storage and retention, done sensibly

A call recording is personal information. Treat it with the same care as any customer record, because that is what it is. The habits that keep you out of trouble:

• Limit who can listen. Named people with a reason to listen, not everyone with a login. Good platforms let you set that per role.
• Set a retention period. Keep recordings as long as they serve the purpose you recorded them for, then let them go. Hoarding years of audio you will never use is risk, not value.
• Automate deletion. A delete policy the platform enforces beats a manual cleanup that never happens.
• Keep them out of shared drives. Recordings belong in the platform or in controlled storage, not in a folder the whole office can browse.
• Think about payments. A recording of a customer reading out their card number is a liability sitting in your storage. Pause recording for payment details, or keep card handling off the phone entirely.

Setting up the announcement

The announcement does the legal heavy lifting, so set it up once, properly, at the platform level:

• Play it before a human answers. On every inbound line, including queues, after-hours and overflow. Something plain works: "Calls may be recorded for training, quality and dispute resolution. Let us know if you would prefer not to be recorded."
• Give people a real way out. Staff should know exactly what to do when a caller objects: pause or stop the recording, or offer to handle the matter by email. On decent systems, pausing a recording mid-call is one button.
• Cover outbound calls too. The greeting only plays on inbound. For outbound, staff mention the recording at the start of the call. Make it part of the script.

What not to do

Secret recording as a business is asking for trouble. Covert recording of private conversations is precisely what the state surveillance device laws are aimed at, penalties can be serious, and a recording you cannot lawfully use is worse than no recording at all. If your plan depends on the other party not knowing, that is your signal to stop and rethink. Announce it or do not record.

The quieter mistakes are worth avoiding too: switching recording on and never securing the files, keeping everything forever "just in case", or letting staff record ad hoc on personal phones with no policy behind it. Each one turns a useful tool into a liability.