AI Receptionist Legal Guide: Call Recording, Disclosure and TCPA Rules for US Service Businesses

Important: What This Guide Is and Isn't

We are a marketing and automation company, not a law firm. This guide summarises widely published legal commentary and primary-source facts so you can ask better questions. Laws vary by state, change often, and depend on your facts. Have a lawyer review your own setup, especially if you handle regulated information (for example law firms, medical or financial services).

Part 1: Call Recording and Consent

Federal law allows recording when at least one party to the call consents. Many states follow that 'one-party' rule. A group of states, however, require every party to the conversation to consent. Commonly cited all-party states include California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania and Washington. Some lists also include Connecticut and Oregon, and Michigan appears on some. The lists genuinely differ between sources, and some states distinguish criminal from civil liability, so check the current statute for each state you serve.

When a call crosses state lines, legal commentary generally advises following the stricter state's standard. For a service business with customers in several states, or a business that can't be sure where a mobile caller is located, the safe operational answer is simple: treat every call as if the strictest rule applies.

• Play a short disclosure at the very start: for example, 'This call may be recorded and answered by an automated assistant to help us serve you.'
• Make the disclosure unskippable and before any personal details are collected.
• Record the fact of consent (the disclosure played) alongside the recording.
• Set a retention period and delete recordings you no longer need.
• Do not record, or pause recording, when callers share payment card details.

Part 2: Should You Tell Callers It's an AI?

No single US federal statute currently requires every business to announce that a voice is AI when answering an inbound call, but the direction of regulation is toward transparency, several states have chatbot and AI-disclosure laws or proposals, and some contexts (such as outbound calling, discussed below) are far stricter. Check the status of your state's rules when you deploy.

Beyond the law, disclosure is also good business. Callers who feel tricked are angrier when the AI reaches its limits. Callers who are told upfront and offered an easy route to a person usually just state what they need. We recommend a short, plain disclosure and a clearly signposted handoff: 'If you'd prefer a person, just say so and I'll connect you.'

Part 3: The FCC's 2024 AI Voice Ruling

On 8 February 2024 the Federal Communications Commission adopted a unanimous declaratory ruling (CG Docket No. 23-362, FCC 24-17) confirming that AI-generated voices are 'artificial' voices under the Telephone Consumer Protection Act (TCPA). The ruling followed AI-generated robocalls that imitated a presidential voice and urged voters in a state primary to stay home.

Because the ruling clarified existing law rather than creating a new rule, it took effect immediately. In practice, calls that use an artificial or prerecorded voice generally require the called party's prior express consent (and, for telemarketing, prior express written consent), unless an exemption applies. Legal commentary on the ruling also notes that it reaches AI tools that choose between prerecorded messages during a call and that there's no carve-out for technology that merely 'purports to provide the equivalent of a live agent'.

Here is the part that matters most for an AI receptionist, offered as our reading of the commentary and not legal advice. The TCPA's artificial-voice restrictions concern calls a business makes. A customer who dials your number and reaches an AI assistant is a different situation from you using an AI voice to dial a customer. If your system also calls people back, runs outbound campaigns, or follows up with leads using an AI voice, the ruling applies directly, and you need documented consent before you start.

Part 4: Texts, Quiet Hours and Opt-Outs

Missed-call text-back, review requests and appointment reminders all involve text messages, which the TCPA also governs. Three principles recur in the commentary:

• Consent: marketing messages generally need documented consent, and the standard is higher for promotional texts than for purely transactional ones (for example a confirmation of an appointment the customer just booked). Keep records of when and how consent was given.
• Quiet hours: federal telemarketing rules restrict calls and texts to between 8 a.m. and 9 p.m. in the recipient's local time, and some states set narrower windows. Whether prior consent exempts a message from quiet hours is an open question in the courts and before the FCC, with at least one federal court dismissing such a claim. Don't rely on that; schedule marketing messages inside the window.
• Opt-outs: honour 'STOP' and equivalent words immediately and stop all related messages. The FCC has adopted rules broadening how revocation of consent works, but implementation dates for parts of them have been postponed repeatedly (a January 2026 order reportedly extended one to January 2027). Build your system to honour opt-outs in any reasonable form regardless.

Part 5: Data, Security and Vendors

Call audio and transcripts are personal data. Ask your provider where recordings are stored, who can access them, how long they are kept, whether they are used to train models, and how to delete them on request. If you serve customers in states with comprehensive privacy laws, deletion and access requests may apply to your recordings. If you handle health information, ask specifically whether the vendor will sign a HIPAA business associate agreement; many general AI products will not.

Ten Questions to Ask Any AI Receptionist Provider

• 1. What is the default disclosure script, and can I edit it?
• 2. Does it support all-party-consent recording rules by default?
• 3. Can callers reach a human on request, and how fast?
• 4. Does the product make outbound calls or texts, and how is consent captured and stored?
• 5. How are STOP and other opt-outs handled across all channels?
• 6. Are texts scheduled around quiet hours by recipient time zone?
• 7. Where are recordings stored, and for how long?
• 8. Is my customers' audio used to train models?
• 9. Can I export or delete all data if I leave?
• 10. Will you put your compliance commitments in the contract?

Sources

FCC, Declaratory Ruling, 'Implications of Artificial Intelligence Technologies on Protecting Consumers from Unwanted Robocalls and Robotexts', CG Docket No. 23-362, FCC 24-17 (8 February 2024). Law-firm summaries consulted include Cooley, Akin Gump, Mayer Brown and TransNexus.

Wiretap and recording-consent summaries: King & Spalding's 'Wiretap Laws in the United States' (2024) and vendor reference pages. Lists vary; verify against current statutes.

TCPA quiet-hours and revocation-rule status: law-firm commentary (JD Supra, Troutman Privacy); not independently verified against FCC orders.