SkynetLabs

AI Receptionist Call Recording Consent: AU and US

Published 10 November 20267 min read

An AI receptionist usually records or transcribes the calls it takes. That is part of the value: you can read what the customer said, check how the assistant handled it, and fix mistakes. It is also where the law starts to matter.

This guide covers Australia and the US, because those are the markets we work in. It is written for owners of plumbing, electrical and HVAC businesses, not lawyers.

This is general information, not legal advice. Recording and consent laws differ by place, change over time, and depend on facts. We are a consultancy, not a law firm. Check your setup with a lawyer in the state or states where your callers are before you switch recording on.

The short version

  • Tell every caller, at the start of the call, that it may be recorded and that they are speaking to an AI assistant. That one habit keeps you on the safe side in almost every jurisdiction below.
  • In Australia, each state and territory has its own law, and most of what we read treats consent as the safe default.
  • In the US, about a dozen states require everyone on the call to consent, and California's rule is the one trade businesses meet most often.
  • A separate federal ruling says AI-generated voices count as "artificial" under the TCPA. That matters mostly if your AI ever calls people, not when it only answers.

Why the rule depends on the caller's location

You might assume the law of your own state applies. It is not that simple. A source we read on US call-recording law says that when a call crosses state lines, the stricter state's rule generally applies, and cites a 2006 case for the point. An Australian source gives a different example: a NSW caller recording a WA caller, where it says the NSW Act would generally apply. Those two sources do not describe the same test, which is a good sign that you should not guess.

The practical conclusion is the same either way. If you take calls from more than one state, set your disclosure to the strictest rule you are likely to meet.

Australia

Australia has no single national rule for a business recording its own phone calls. Each state and territory has a surveillance-devices or listening-devices Act, and a federal telecommunications law sits alongside them. The Acts named in the IPC Solutions summary are:

  • ACT: Listening Devices Act 1992
  • NSW: Surveillance Devices Act 2007
  • Victoria: Surveillance Devices Act 1999
  • South Australia: Surveillance Devices Act 2016
  • Northern Territory: Surveillance Devices Act 2007
  • Tasmania: Listening Devices Act 1991
  • Western Australia: Surveillance Devices Act 1998
  • Queensland: Invasion of Privacy Act 1971

That summary says consent is required to record a private conversation in every jurisdiction except Queensland, where it says consent is not required if you are a party to the conversation. Sprintlaw describes Queensland as "often described as more flexible" where a participant records, but still warns against secret recording and notes that using or sharing a recording later can raise separate problems. It tells NSW businesses to be particularly careful about recording private conversations without consent.

Here is where we are unsure. The summaries are not fully consistent with each other. The IPC article, for instance, says "one or both parties" in one place and says clients must be told and must consent in another. We also found conflicting commentary on South Australia while researching this piece. We are not going to pretend we have resolved that. If you serve South Australian or Queensland customers, ask an Australian lawyer.

What both Australian sources agree on is the practical approach:

  • Tell the caller before recording starts. Sprintlaw suggests a notice and treating continuing the call as consent.
  • Offer an alternative. Both recommend giving the person the option of not being recorded rather than forcing them to hang up.
  • Let people pause or stop recording while they give sensitive details, such as card numbers.
  • Store recordings securely and limit who can access them. Australia's Privacy Act also applies to businesses and is a separate topic from consent to record.

An example wording from the Sprintlaw article is "This call is being recorded for training, quality and record-keeping." For an AI receptionist, add the AI disclosure as well.

The US

The federal baseline is that you can record a call you are part of. Many states add a stricter rule. A Nextphone summary lists 12 all-party consent states: California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania and Washington.

The same article lists plenty of caveats. Connecticut and Nevada apply their rule to phone calls but treat in-person conversations differently. Illinois applies it to private, non-law-enforcement conversations. Massachusetts bans secret recording rather than requiring each party's explicit consent. A few other states, such as Oregon, differ between phone and in-person recordings. It is a vendor blog, not a statute, so treat the list as a map of where to look, and check any state you serve.

If you work across state lines, say you are an HVAC contractor near a border, the sensible approach is to disclose on every call, not only for callers you think are in a strict state. You usually cannot tell where a mobile caller is.

California Penal Code 632

California is the one to know. The statute makes it an offence to intentionally record a confidential communication using a recording device without the consent of all parties. The text defines a confidential communication as one made in circumstances that reasonably indicate a party wants it kept among the parties, and excludes cases where parties may reasonably expect to be overheard or recorded.

The statute lists a fine of up to $2,500 per violation, or up to one year in county jail or state prison, or both, with higher fines for repeat violations. It also says evidence obtained in violation is generally not admissible in other proceedings. That is what the statute says on its face. How courts treat a clear "this call is recorded" notice is a question for a California lawyer.

The practical point is easy: tell people at the start. A caller who hears the notice and continues has been informed. The Nextphone article describes staying on the line after a notice as implied consent, and recommends notifying on every call.

The AI-voice rule: FCC 24-17

In February 2024 the FCC adopted a Declaratory Ruling, FCC 24-17, holding that calls made with AI-generated voices are "artificial" voices under the Telephone Consumer Protection Act. Mayer Brown's summary says this means that before placing a call with an AI-generated or AI-simulated voice, the caller must obtain prior express consent from the person called, and that the ruling creates no new rules but applies the existing ones.

Two points for a trade business:

  1. It is aimed at outbound calls. An AI that answers your inbound line is in a different position from an AI that phones people. If you are thinking about AI calling back leads, quote follow-ups or past customers, get legal advice on consent first.
  2. It is not a recording rule. It does not replace the state laws above. You can comply with one and still break the other.

We are also cautious about automatic missed-call text messages, for the same reason: automated messaging rules in the US are strict and the exposure is yours. We do not offer that as a feature.

A disclosure script that works almost everywhere

Keep it short and put it first:

"Thanks for calling [business name]. You're speaking with an AI assistant, and this call may be recorded so we can pass your details to the team. Stay on the line to continue, or say 'person' and I'll connect you."

A few notes on that:

  • It names the AI, so nobody is left guessing who they are talking to.
  • It says why you record, in plain words.
  • It offers a human option. In Australia that matches the "offer an alternative" advice.
  • It does not promise anything you cannot deliver. If there is no one to connect to after hours, say "I'll pass this to a person to ring you back" instead.

A short compliance checklist

  • Disclose AI and recording at the start of every call.
  • Offer a way to opt out of recording or reach a human.
  • Decide where recordings live, who can see them and how long you keep them.
  • Let people skip recording while sharing payment details, or avoid taking card details by phone.
  • Do not run automatic outbound AI calls or texts without legal advice.
  • Ask a lawyer in your state, and in each Australian state you serve, to review your wording once.

Where this leaves you

Recording your calls with an AI receptionist is common and usually manageable. It stops being manageable when it is hidden. The safest setup is boring: a clear notice at the start, an easy way out, and tight control of the recordings. If you want to see how that fits into your phone flow, our AI audit covers it, and our guide to AI receptionist versus answering service shows how recording differs between the two.

Sources

  1. FindLaw (statute text, shown as current at 1 January 2026), California Penal Code section 632, 2026-01-01. Accessed 2026-11-10. Verify against the California legislature's site before relying on it.
  2. Nextphone (vendor blog), Call recording laws by state, undated blog post. Accessed 2026-11-10. Source of the list of all-party consent states and the caveats. A vendor summary, not the statutes.
  3. Sprintlaw (Australian law firm blog), Business call recording laws in Australia, 2026. Accessed 2026-11-10. General information, not legal advice.
  4. IPC Solutions (telephony vendor blog), Legal requirements for call recording in Australia, undated blog post. Accessed 2026-11-10. Lists the state and territory Acts. The article has internal inconsistencies, noted in the text.
  5. Mayer Brown (law-firm summary of FCC 24-17), FCC declares authority and intent to regulate AI-generated calls under the TCPA, 2024-02-27. Accessed 2026-11-10. Ruling adopted and released 8 February 2024.

See the AI audit