Call recording laws in Australia: what AI phone agents must tell callers

If your AI phone agent records calls, and most do, because the recording and transcript are how you check its work, you need every party to know the call is being recorded. That single habit addresses the federal interception rule, gives you the best footing under the stricter state laws, and costs you one sentence per call.

This article explains why, jurisdiction by jurisdiction, and gives you a disclosure script built for AI calls. For the wider set of rules on calling hours, the Do Not Call Register and SMS, see our guide to AI voice agents in Australia.

The federal layer: interception means recording without knowledge

Phone calls travel over a telecommunications system, which brings in the Telecommunications (Interception and Access) Act 1979. Section 7 says a person must not intercept a communication passing over a telecommunications system. Section 6 defines interception as "listening to or recording, by any means, such a communication in its passage over that telecommunications system without the knowledge of the person making the communication".

The key word is knowledge. If the person speaking knows the call is being recorded, recording it is not interception under that definition. That is why the "this call may be recorded" message you hear on every bank and telco line exists. The Australian Law Reform Commission has noted that the interception offence has no participant-monitoring exception, so being a party to the call doesn't on its own make recording without knowledge safe under the federal Act.

There is legal debate about exactly when recording equipment at one end of a call is recording "in its passage over" the system. You don't need to win that argument if everyone on the call has been told.

The state and territory layer: who has to consent

Each state and territory also has a listening devices or surveillance devices law covering the recording of private conversations, and they don't agree. The ALRC's 2014 report grouped them in two camps: Queensland, Victoria and the Northern Territory have participant-monitoring exceptions that let a party to a conversation record it, while the other jurisdictions don't, and instead rely on consent of the principal parties or narrow exceptions such as protecting a party's lawful interests.

The South Australian position comes from the 2016 Act, which replaced the 1972 Act the ALRC reviewed; the SA Law Handbook summarises it as prohibiting recording a private conversation without the consent of all principal parties, subject to exceptions. Even in the "one party may record" places, sharing or publishing a recording is restricted, so a transcript that ends up in a public review response is a different question from a recording kept for quality checks.

Why the strictest rule is the one to design for

Your AI agent can't reliably know where the other person is. A Melbourne business can call a mobile that's sitting in Sydney, and an inbound caller with a Brisbane number may be in Hobart. Interstate calls can engage more than one state's law. Designing around the all-party standard, by telling everyone and recording only when they stay on the line, is simpler than mapping caller locations and safer than guessing.

AI calls add two extra questions

AI voice agents record by default in a way human receptionists don't: the agent's own listening is a transcription of the caller's words, and most platforms keep audio and transcript for quality review. That raises two practical points beyond classic recording law.

• Disclose the AI as well as the recording. No Australian statute we're aware of requires an AI disclosure on every call, but a caller who thinks they're speaking to a person and later learns otherwise has a fair complaint. Say it up front.
• Recordings and transcripts are personal information. If the Privacy Act applies to your business, the Australian Privacy Principles govern collection notices, use and security. Since 10 June 2025, there's also a statutory tort for serious invasions of privacy in the Privacy Act. Our explainer on the Privacy Act and AI goes further.

A disclosure script for inbound and outbound AI calls

Put the disclosure in the first breath of the call, before any personal details are collected. Keep it short; long legal preambles cause hang-ups.

Inbound

Outbound

If the caller objects

Decide in advance what happens when someone says "I don't want to be recorded". Three options, from best to worst:

1. Stop recording for the rest of the call, if your platform can, and say so: "No problem, I've stopped the recording." Note in the CRM that the call wasn't recorded.
2. Offer a person: "I'll get one of the team to call you back on this number." Then create the call-back task.
3. Offer another channel: "I can text you a booking link instead."

What you shouldn't do is carry on recording after an objection. Continuing after someone has said no defeats the knowledge-and-consent footing you just built.

Retention, access and the paper trail

Recording is only half of it. Decide, in writing, how long you keep audio and transcripts, who can listen, and when they're deleted. Our defaults for a small business:

• Keep the call summary and outcome in the CRM as the long-term record; keep raw audio for a short, fixed period that suits your review cycle and any industry obligations.
• Limit audio access to the people who review call quality.
• Log the disclosure itself, so each call record shows the recording notice was played.
• Update your privacy policy to say calls may be answered or made by an AI assistant and recorded, and how to ask for a person.
• Don't publish or share recordings outside the business without checking the publication rules in your state.

Fulcrum Lyre is designed around all-party recording consent, with the disclosure at the start of each call and outcomes logged to the CRM. If data location matters to you, read about the privacy and data handling and our view on sovereign AI for Australian operators.

Putting recording rules alongside the calling rules

Recording is one item on a longer list. Outbound calls also need to follow ACMA's calling hours, identification and Do Not Call rules, which we cover in ACMA rules for AI outbound calls. Inbound agents need a clear path to a person, covered in after-hours AI answering. If you get those right and say "this call is recorded" every time, you've dealt with most of the risk.