Guides · Compliance · For owners considering an ai phone agent for inbound calls
Is it legal for AI to answer a business phone line? U.S. and EU rules, October 2026
By the Lead Friendly team · Published October 14, 2026 · Updated October 14, 2026
Read these guides often? Add leadfriendly.com as a preferred source in Google.
Short answer: In the U.S. and the EU, we found no law that bans an AI from answering a business's inbound calls. The rules that matter are disclosure (tell callers it is an AI), recording consent, and, for medical offices, HIPAA. The FCC's 2024 ruling that AI voices count as 'artificial' under the TCPA is mostly about calls a business places, not calls it receives. Rules differ by state and are changing, so treat this as a map to check with a lawyer, not as legal advice.
The rules at a glance
This table lists what we opened and read for this guide. 'Status' is how we read the text on the date at the bottom of this page; laws get amended, so check the linked source before relying on it.
| Rule | Who it reaches | What it asks of a business | Status as we read it |
|---|---|---|---|
| FCC Declaratory Ruling 24-17 (TCPA) | Calls using AI-generated voices | Prior express consent of the called party before initiating such a call | Adopted Feb 2, 2024; released Feb 8, 2024 |
| California Bus. & Prof. Code 17940-17941 | Bots communicating online with people in California | Do not hide that it is a bot to push a sale or sway a vote; a clear disclosure avoids liability | Defined around websites and apps |
| Utah Code 13-75-103 and 13-75-104 | Suppliers using generative AI with consumers | Disclose AI if the person clearly asks; stricter, up-front disclosure for regulated occupations | In effect since May 7, 2025 (SB 226 as enrolled) |
| Maine 10 M.R.S. 1500-DD | Chatbots and other computer technology in trade | Clear notice that the consumer is not engaging with a human, if they might think so | Enacted 2025 |
| Colorado SB 26-189 | Automated decision-making in consequential decisions | Notice and review rights for consequential decisions | Obligations listed from Jan 1, 2027 |
| EU AI Act Article 50(1) | Providers of AI systems that talk to people | Design the system so people are told it is an AI, unless obvious | Applies from Aug 2, 2026 as published |
| HIPAA, 45 CFR 164.502(e) | Covered entities sharing patient information with vendors | A written agreement with satisfactory assurances (a BAA) | Federal rule in the eCFR |
Try Lead Friendly free
AI voice agents + CRM + TCPA-gated compliance. Free trial: 7 days or 30 AI voice minutes, whichever comes first. No card required.
Federal: the FCC ruling is mostly about calls you place
In a Declaratory Ruling adopted February 2, 2024, the FCC confirmed that the Telephone Consumer Protection Act's restrictions on an 'artificial or prerecorded voice' cover current AI technologies that generate human voices. Calls that use them need the prior express consent of the called party, absent an emergency purpose or an exemption.
The ruling is written around calls a business initiates to someone else. A customer who dials your number and reaches an AI is not a called party who was rung up. That is how we read it; the ruling does not say so in those words, so a lawyer should confirm for your situation.
The line gets thin the moment the AI places a call: a callback after a missed call, a reminder, a follow-up. Those are outbound calls and the TCPA applies. We cover that side in our guides on whether AI cold calling is legal and the TCPA checklist.
Outbound AI calls, texts and do-not-call rules are covered in separate guides linked under Related. This guide is about inbound calls.
State AI-disclosure laws
$2,500
Maximum administrative fine per violation of Utah's AI disclosure chapter, under 13-75-105
Source: Utah S.B. 226 (2025), Artificial Intelligence Consumer Protection Amendments, enrolled copy
California's bot law (Business and Professions Code 17941) makes it unlawful to use a bot to communicate with a person in California online, with intent to mislead about its artificial identity to incentivize a sale or sway a vote. A person using a bot is not liable if it discloses that it is a bot, clearly and conspicuously. The statute defines 'online' as a public-facing website, web application or digital application. On that wording a phone call is not obviously covered, but we would not build a product around that gap.
Utah's 2025 law (SB 226, Utah Code 13-75-103) requires a supplier using generative AI with a consumer to say it is an AI and not a human if the person asks clearly. People in regulated occupations must prominently disclose high-risk AI interactions, verbally at the start of a spoken one. Section 13-75-104 offers a safe harbor if the AI discloses clearly at the outset and throughout the interaction.
Maine's 10 M.R.S. 1500-DD says a person may not use an AI chatbot, or any other computer technology, in trade with a consumer in a way that may mislead a reasonable consumer into thinking they are talking to a human, unless the consumer is clearly told otherwise. The chatbot definition includes software that simulates conversation through aural communications, which reads on voice agents. A violation is a violation of Maine's Unfair Trade Practices Act.
Colorado's original AI Act was repealed and re-enacted in May 2026 as SB 26-189, which is about automated decision-making technology in consequential decisions, with obligations listed from January 1, 2027. An AI that books appointments or takes messages is not obviously making consequential decisions, but one that screens applicants or decides who gets service could be.
Recording is a separate question
Telling callers they are speaking with an AI does not answer whether you may record the call. Recording consent depends on the states of the people on the call: some require every party to agree, others only one. An AI agent that records and transcribes every call is recording, and the same rules apply as for a human receptionist whose calls are recorded.
Our guide on call-recording consent by state sets out the rule for each state. If your callers come from many states, the cautious approach is to give the notice that satisfies the strictest of them, at the start of the call.
EU: Article 50 of the AI Act
Regulation (EU) 2024/1689, Article 50(1), requires providers to design AI systems that interact directly with people so that those people are informed they are dealing with an AI system, unless that is obvious to a reasonably well-informed, observant and circumspect person given the context. Article 113 says the Regulation applies from 2 August 2026, with listed exceptions for other chapters.
A 2026 'digital omnibus' amendment changed some AI Act dates. The final compromise text we opened (PE-CONS 30/1/26 REV 1, July 2026) adds a transition to 2 December 2026 for providers' content-marking duty under Article 50(2) for systems already on the market before 2 August 2026. We did not find a change to Article 50(1) in it, but we have not confirmed the text as published in the Official Journal, so check there.
The Article 50(1) duty sits with the provider of the AI system, with other duties on deployers. If you are a business using a vendor's phone agent, the practical step is to confirm the vendor discloses on every call and keep that disclosure switched on.
Medical callers and HIPAA
If your callers are patients and the AI hears or stores protected health information, the vendor is likely acting for you in a way HIPAA treats as a business associate. Under 45 CFR 164.502(e) a covered entity may share protected health information with a business associate only if it obtains satisfactory assurances, documented in a written contract.
In practice that means a business associate agreement. Lead Friendly is not HIPAA-eligible and does not sign a BAA, so a medical practice should not route calls containing patient information through it. Other vendors do sign BAAs; ask for the signed agreement before you go live.
A pre-launch checklist
- 1
Turn on the AI disclosure
Every call should open by saying the caller is speaking with an AI. Check the exact words in a test call.
- 2
Map where your callers live
Note the states and countries your callers call from, then check recording consent and any AI disclosure statute for each.
- 3
Decide what is recorded
Add a recording notice at the start of the call if any state you serve requires every party to consent.
- 4
Keep a person reachable
Set rules for transferring to someone on your team, and a message-taking fallback when nobody is available.
- 5
Separate inbound from outbound
Callbacks, reminders and texts are outbound and carry TCPA, do-not-call and quiet-hours duties.
- 6
Ask a lawyer about your trade
Regulated fields such as health, finance, insurance and law have their own rules beyond this guide.
Last reviewed, and what this is not
Last reviewed October 14, 2026. This guide summarises public texts and is not legal advice. Laws and agency positions change, secondary summaries of them often lag the text, and we could not open every official page ourselves; where a page was blocked we used the nearest accessible copy, noted in the sources. Check the linked source and consult a lawyer licensed in your state before relying on any of it.
Frequently asked questions
Does the TCPA apply when an AI answers calls I receive?
The FCC's 2024 ruling is about AI-generated voices in calls a business initiates, which need the called party's prior express consent. Answering a call the customer placed is a different situation, and we read the ruling as not reaching it. Callbacks and follow-up calls the AI places are outbound and are covered. Confirm with a lawyer.
Do I have to tell callers it is an AI?
Several laws point that way: Utah requires disclosure when asked, Maine requires notice where a consumer might think they are talking to a human, and the EU AI Act requires providers to build in disclosure unless it is obvious. Telling every caller at the start is the simplest way to meet all of them. Lead Friendly's agent discloses on every call.
Do I need consent to record an AI-answered call?
Recording consent follows state law, not whether the answerer is human or AI. Some states need every party to agree. See our state-by-state guide and give the strictest notice that applies to your callers.
Can a medical office use an AI receptionist?
Only if the vendor will sign a business associate agreement and protects patient information as HIPAA requires. Lead Friendly is not HIPAA-eligible and signs no BAA, so it is not suited to calls that carry patient information. Other vendors do offer BAAs; ask for the agreement in writing.
Does the EU AI Act apply to a U.S. business?
It can reach providers and deployers outside the EU when the system is used in the EU, but whether it applies to you depends on facts we cannot assess here. If you take calls from people in the EU, ask a lawyer familiar with the Act.
See it on your own calls
Pick your industry, paste your website, and hear your AI agent take a call. Free for 7 days or 30 AI voice minutes, whichever comes first; no credit card.
Start free trialSources
- FCC 24-17, Declaratory Ruling, CG Docket No. 23-362 · accessed 2026-10-14Adopted Feb 2, 2024; released Feb 8, 2024.
- California Business and Professions Code 17941 (bots), with 17940 definitions · accessed 2026-10-14Public mirror of the code; the official leginfo.legislature.ca.gov page blocked our automated access.
- California Business and Professions Code 17940 (definitions) · accessed 2026-10-14Defines 'bot' and 'online'.
- Utah S.B. 226 (2025), Artificial Intelligence Consumer Protection Amendments, enrolled copy · accessed 2026-10-14Enacts Utah Code 13-75-101 to 13-75-106. We read the enrolled bill, not the current codified text.
- Maine Revised Statutes, Title 10, Chapter 241 (section 1500-DD) · accessed 2026-10-14Generated Oct 5, 2026 by the Maine Legislature.
- Colorado General Assembly, SB26-189 bill page and summary · accessed 2026-10-14Signed May 2026; repeals and re-enacts SB 24-205.
- Regulation (EU) 2024/1689 (AI Act), Official Journal text on EUR-Lex, Articles 50 and 113 · accessed 2026-10-14
- Council of the EU, PE-CONS 30/1/26 REV 1 (Digital Omnibus on AI, final compromise text) · accessed 2026-10-14Pre-publication text; not confirmed against the Official Journal.
- 45 CFR 164.502(e), disclosures to business associates (eCFR) · accessed 2026-10-14
This guide is general information, not legal advice. TCPA, FCC, and state rules change and apply differently to each program — consult qualified counsel about your specific use.