Compliance
Is AI Calling TCPA Compliant? What US Businesses Must Know (2026)
AI-assisted content · Editorially reviewed
June 14, 2026 · 9 min
AI voice agents are now squarely covered by the TCPA after the FCC's 2024 ruling. Here is what inbound and outbound AI calling actually requires — consent, disclosure, state laws — explained for US small businesses.
The short answer: legal to use, regulated in how you use it
AI voice agents are legal for US businesses. The questions that actually matter are narrower: are you calling out or only answering inbound, do you have consent for the numbers you dial, and are you disclosing that the caller is an AI where state law expects it.
Most small businesses adopt voice AI as an inbound receptionist — the customer calls the shop, the AI answers, qualifies, books, or routes. That posture sidesteps the heaviest part of the rules, because the consent obligations in the Telephone Consumer Protection Act (TCPA) are written around calls a business places to a consumer, not calls a consumer places to the business.
The compliance work concentrates in three places: outbound consent, AI disclosure, and call recording. The rest of this guide walks each one.
The TCPA in one paragraph
The TCPA, passed in 1991 and enforced by the FCC, restricts non-emergency calls and texts made with an autodialer or an artificial or prerecorded voice to wireless numbers and residential lines without the proper level of prior consent. For informational calls the bar is prior express consent. For marketing or telemarketing calls the bar is higher: prior express written consent. Violations carry statutory damages of $500 to $1,500 per call, which is why TCPA class actions are a real business risk, not a theoretical one.
What the FCC's February 2024 ruling actually said
On February 8, 2024, the FCC issued a Declaratory Ruling stating that calls using AI-generated or cloned human voices qualify as "artificial voice" calls under the TCPA. The practical effect is simple: an outbound call placed by an AI voice agent is treated exactly like a prerecorded-voice robocall for consent purposes.
That ruling did not ban AI calling. It closed an ambiguity. Before it, some vendors argued a real-time generative voice was not "prerecorded." After it, the safe assumption is that any outbound AI voice call to a cell phone needs prior express consent — written consent if the call is promotional.
Inbound vs outbound: the line that decides most of your obligations
This is the single most useful distinction for a small business.
| Scenario | Who initiates | TCPA consent for the call | Typical posture |
|---|---|---|---|
| Customer calls your business; AI answers | The consumer | Not triggered — the outbound-consent rules govern calls you place | Default, lowest-risk |
| AI calls a customer who asked for a callback | The consumer requested it | Strong consent basis; document the request | Low-risk, common |
| AI calls existing customers with reminders | The business | Needs prior express consent for the number | Manageable with consent capture |
| AI cold-calls prospects to sell | The business | Needs prior express written consent | High-risk; avoid without counsel |
A receptionist that only answers and only calls back people who asked to be called back operates in the two top rows — where the heaviest rules do not apply.
AI disclosure: the state-law layer
Even when the TCPA does not force it, a patchwork of state laws pushes toward telling people they are talking to an AI.
- California — B.O.T. Act (SB-1001): prohibits using a bot to mislead people about its artificial identity in order to influence a commercial transaction. Disclose the bot and you are inside the safe harbor.
- Utah — AI Policy Act (2024): requires a clear disclosure that a person is interacting with AI when asked, and proactively for regulated occupations.
- Colorado — AI Act (SB 205): consumer-protection framework with disclosure and documentation duties for consequential AI uses, phasing in through 2026.
These statutes differ in scope and triggers, but they point the same direction. The clean operating rule that satisfies all of them is to identify the agent as AI at the very start of every call — one sentence, before the conversation gets going.
Call recording is a separate body of law
Recording is governed by state wiretap statutes, not the TCPA. The US splits into one-party consent states (one participant's consent is enough) and all-party consent states such as California and Florida (everyone on the call must consent). If you record AI calls, announce the recording at the start and configure consent to the strictest standard among the states you serve.
A compliant default configuration
For a typical US service business, the following setup keeps you on the conservative side of every rule above:
- Inbound-only by default. The customer initiates; outbound is limited to callbacks the customer requested.
- AI self-identification at call start. A short, plain statement that the caller is an automated assistant.
- Consent capture for any outbound. Log the time, source, and scope of consent for every number you place a call to.
- Honor opt-outs and the DNC registry. Process "stop calling" immediately and scrub against Do-Not-Call lists for any outbound program.
- Recording disclosure to all-party standard. Announce recording; store consent.
- Written policies, published. Keep your practices documented — see our TCPA Policy and CCPA Notice for the shape of that documentation.
Where the data layer fits (CCPA and friends)
The TCPA governs the call; consumer-privacy laws govern the data. If you operate in California, the CCPA/CPRA gives callers rights over the personal information your AI captures — access, deletion, and opt-out of sale or sharing. Practically, that means a defined retention window, a way to honor deletion requests, and not quietly selling call data. Other states (Virginia, Colorado, Texas, and a growing list) have their own comprehensive privacy laws with similar contours.
The bottom line
An AI receptionist that answers inbound calls, identifies itself as AI, only calls back people who asked, honors opt-outs, and discloses recording is operating well inside US law. The risk lives almost entirely in unconsented outbound marketing — and that is a choice you control, not an inherent property of the technology.
Want your specific call flows checked against this framework before you launch? Book an AI Voice Opportunity Audit — 60 minutes, free, no commitment. This article is general information, not legal advice.
Frequently asked questions
- Are AI voice agents legal to use for business calls in the US?
- Yes. AI voice agents are legal. What the law regulates is how you use them — specifically consent for outbound calls to wireless numbers and, in several states, disclosure that the caller is AI. A default inbound-only posture, where the customer calls you, avoids most TCPA outbound-consent obligations.
- Does the TCPA apply to inbound calls a customer makes to my business?
- Generally no. The TCPA's prior-express-consent rules govern calls a business places to a consumer. When the consumer initiates the call to you, those outbound-consent requirements do not apply. State AI-disclosure rules can still apply, which is why a clear AI identification at the start of the call is best practice either way.
- Do I have to tell callers they are talking to an AI?
- There is no single federal rule that requires it on every call, but several state laws (notably California's B.O.T. Act / SB-1001) and the spirit of FTC guidance push strongly toward disclosure. The safe, simple practice is to identify the agent as AI at the start of every conversation.
- What changed with the FCC's 2024 ruling?
- On February 8, 2024 the FCC issued a Declaratory Ruling confirming that calls using AI-generated or cloned voices are 'artificial voice' calls under the TCPA. That means outbound AI voice calls to wireless and residential lines need the same prior express consent as any other artificial or prerecorded voice call.
- Can I record AI phone calls?
- Call recording is governed by state wiretap law, not the TCPA. Some states require all-party consent (for example California and Florida), others require only one-party consent. If you record, announce it at the start and configure consent capture per the strictest state you operate in.
- Is this legal advice?
- No. This article is general information to help you ask the right questions. Telephone-consumer rules change and depend on your industry, states, and call patterns. Confirm your specific setup with qualified counsel before launching outbound campaigns.