AI Receptionist

Call Recording and Consent Laws Across States: A Guide for Franchise Networks

October 3, 2026 AI Receptionist
Call Recording and Consent Laws Across States: A Guide for Franchise Networks

If your franchise records calls, and most AI receptionist systems do, you are operating under a patchwork of state laws that do not agree with each other. Some states require only one party to consent to recording. Others require everyone on the call to consent. Get this wrong across a 20-state network and the liability adds up fast. This guide covers the practical side. It is not legal advice, and for a network your size, a real attorney should review your policy.

One-party vs. all-party consent

The basic split is simple. In one-party consent states, recording is allowed as long as one person on the call knows about it, which can be your own system. In all-party consent states, sometimes called two-party consent states, everyone on the call must consent to being recorded. About a dozen states, including California, Florida, and Illinois, fall in the stricter camp. The exact list changes, so verify against current law rather than a blog post, including this one.

Which law applies when states differ

This is the part that trips up franchise networks. If your AI system is hosted in a one-party state, the franchisee is in an all-party state, and the caller is somewhere else entirely, which rule governs? Courts have answered this differently in different cases. The safe approach most networks take: follow the strictest rule among the states involved. If any party is in an all-party consent state, get consent from everyone. It is simpler to run one policy network-wide than to maintain fifty state-specific recording rules.

The announcement that solves most of it

In practice, consent is usually handled with a short disclosure at the start of the call: “This call may be recorded for quality and training purposes.” When the caller stays on the line after hearing that, most states treat it as consent. Build this announcement into the AI’s greeting for every location. It costs you nothing and it covers the majority of the risk. Keep a written record of the exact wording and the date it went live.

What to do with the recordings

Recording the calls is only half the question. The other half is storage and access. Decide who can listen to recordings: the franchisee for their own location, corporate for quality audits, and nobody else without a reason. Set a retention period and actually delete old recordings when it passes. A five-year archive of customer calls is a liability, not an asset. If your vendor stores recordings, check where the data lives and what their deletion policy is.

Transcripts count too

AI receptionists generate transcripts and summaries of every call. Treat those the same as recordings for policy purposes. They contain the same customer information and in some states the same consent questions apply. Your data policy should cover recordings, transcripts, and summaries together, not just the audio.

Put it in the franchise agreement

Call recording policy should not live in an email from 2024 that half the franchisees never saw. Write it into the operations manual or the franchise agreement: the disclosure wording, the retention period, who can access recordings, and the franchisee’s responsibility to keep their location’s escalation and contact details current. When every unit follows the same written policy, corporate has a defensible position if anything is ever questioned.

Review it once a year

State laws change. Your network grows into new states. Set an annual review with your attorney: confirm the state list is current, confirm the disclosure wording still holds, confirm the retention and access rules still make sense. An hour a year is cheap insurance for a network recording thousands of calls a month.

For choosing a platform with the recording and reporting controls a network needs, our buyer’s feature checklist covers what to ask vendors, and the franchise and multi-location guide has the broader phone setup picture.

Saqib Ahmed, Founder & AI Engineer

Written by

Saqib Ahmed

Founder & AI Engineer, Peak AI Agency

I write the agents that run on clinic phone lines and inboxes: the conversation engine and the booking logic behind them, plus the integrations with Pabau, Fresha and Phorest. Everything here comes out of systems we have actually shipped, not a content plan.

Email me a question

Next step

Hear it answer your phone before you pay a penny

Book a 20 minute call. We will play you the AI receptionist taking a real booking, then tell you honestly whether it makes sense for your clinic.

No contracts on the call. No pressure. If AI is wrong for your clinic we will say so.

Book a demo WhatsApp