Call Recording Laws in Australia: What Businesses (and AI Voice Agents) Must Tell Callers
Can your business record phone calls in Australia? Often yes, but only if you handle consent and disclosure correctly, and the rules differ by state, which is exactly where businesses get caught. With call recording now built into hosted phone systems and AI voice agents, getting it right matters more than ever, because an AI agent quietly transcribing a call is treated much like recording it. Byteway sets up compliant phone systems and AI voice agents for Australian businesses, so this guide explains the law in plain English: the state differences, the safe disclosure practice, the wording to use, and what applies specifically to hosted PBX and AI voice agents. (This is general information, not legal advice, and the calendar flags mandatory legal review before publishing.) Is it legal for a business to record phone calls? It can be, but call recording sits across two layers of law. Federally, the Telecommunications (Interception and Access) Act 1979 governs intercepting communications passing over a telecommunications system. On top of that, each state and territory has its own surveillance-devices or listening-devices legislation governing the recording of private conversations, and these differ in whether a party to the conversation may record it. Then, once a call is recorded, the recording is personal information, so the federal Privacy Act and the Australian Privacy Principles govern how you store, use and disclose it. So “can I record calls” is really three questions: may I record it, did I give proper notice, and am I handling the recording lawfully. The state differences (and why disclosure solves them) The key difference between states is whether a party to a private conversation can record it. Broadly, some states are more permissive, allowing a party to the conversation to record it, while others are more restrictive, effectively requiring the consent of all parties. As a general guide: (Legal-review note: present this as a general guide only and confirm current provisions per jurisdiction before publishing. This is a calendar-required proof asset.) Here is why this complexity matters less in practice than it looks: if your business tells every caller, up front, that the call may be recorded and gives them the chance to object, you have obtained consent, which satisfies the strictest all-party-consent states and is good practice everywhere. The safe, simple, nationally-compliant approach is therefore to disclose and seek consent on every call, rather than trying to operate different rules in different states. Disclosure is the rule that works across the whole country. The disclosure wording to use Compliant disclosure is clear, upfront and gives the caller a choice. A simple, effective form of words, played or stated at the very start of the call: “This call may be recorded for quality and training purposes. If you’d prefer not to be recorded, please let us know.” Or, for an outbound call: “Before we start, I should let you know this call may be recorded. Is that okay?” The principles that make disclosure sound: it comes at the beginning, before anything substantive is said; it is clear that recording may occur; and it gives the caller a genuine opportunity to object or discontinue. Burying it, or disclosing after the conversation, defeats the purpose. Keep it simple and at the start. What this means for hosted PBX and AI voice agents? Modern phone technology makes this both easier and more important to get right. Hosted PBX / cloud phone systems can play an automatic recording disclosure at the start of every call, which is the cleanest way to ensure consistent, compliant disclosure, no reliance on staff remembering to say it. If you record calls through your hosted phone system, set up an automatic disclosure message, and make sure recordings are stored securely with appropriate access and retention. AI voice agents raise the stakes, because they typically transcribe calls, and a transcript is generally treated like a recording for these purposes. So an AI voice agent that records or transcribes calls must disclose this to callers at the start, just as a human-recorded call would, and handle the resulting data under the Privacy Act. This is one of the most common compliance gaps in AI receptionist deployments, the agent quietly transcribing without proper disclosure, and it is exactly why an AI voice agent should be deployed with the consent flow built in, not bolted on. A checklist for both: Disclose at the start of every call, automatically where possible. Obtain consent (the caller can object or discontinue). Store recordings and transcripts securely, with access limited to those who need them. Use them only for the stated purpose (quality, training, records). Set a sensible retention period and dispose of recordings securely after it. And document your approach, so you can show it if asked. Do these and your call recording, human or AI, stands on solid ground. Byteway Expert Insight The call-recording mistake we see most, especially with AI voice agents, is silent recording or transcription with no disclosure, which can turn a useful tool into a legal exposure, and the business often does not realise it is happening because the AI does it automatically. The fix is not to avoid recording, which has genuine value for quality and records, it is to build disclosure and consent into the call flow so it happens on every call without anyone having to remember. For a hosted phone system or an AI voice agent, that is a setup decision: an automatic disclosure message at the start, secure storage, and a retention policy. Done that way, recording is compliant everywhere in the country and the business gets the benefit without the risk. Done silently, it is a problem waiting to be noticed. How Byteway helps? We set up hosted phone systems and AI voice agents with compliant call recording built in: automatic disclosure at the start of every call, secure storage, access control and a sensible retention policy, handled under the Privacy Act. For the related rules on video surveillance, see our guide to CCTV privacy
