Back to insights
Checking Compliance Practices

Are AI calls considered robocalls?

Yes—AI voice calls are legally robocalls under the TCPA. Learn the FCC's 2024 ruling, consent and disclosure rules, and how compliant AI follow-up books...

Are AI calls considered robocalls?

Are AI calls considered robocalls?

Key Facts

AI Voice Calls Are Legally Robocalls Under TCPA

If your AI voice agent sounds convincingly human, the FCC doesn't care — legally, it's still a robocall. That's the core message of the FCC's February 8, 2024 Declaratory Ruling, which explicitly classifies AI-generated voices as "artificial" under the Telephone Consumer Protection Act (TCPA).

The ruling closed what could have been a major loophole. Voice cloning technologies don't get special treatment just because they approximate a live person, as the FCC's official ruling makes clear. The legal standard is simple: if technology generates the words you hear rather than a live person speaking in real time, the call falls under robocall rules, according to TCPA legal analysis.

Some providers hoped that having a live agent join mid-call would change the classification. It doesn't. The FCC stated that "the statute does not allow for any carve out of technologies that purport to provide the equivalent of a live agent," a point reinforced in compliance guidance for voice AI. Even hybrid calls — where AI opens the conversation and a human takes over — remain subject to TCPA restrictions.

That means AI calls must follow the same rules that have governed robocalls for decades:

  • Prior express written consent for marketing calls to cell phones in 47 states
  • Calling hours restricted to 8 a.m. to 9 p.m. in the customer's local time
  • Do-not-call list scrubbing at least every 31 days
  • Record retention of at least 4 years, with 7 years recommended

Enforcement is accelerating. TCPA filings increased 95% year-over-year in 2025-2026, with aggregate verdicts exceeding $925 million, according to recent litigation tracking. Statutory damages run $500 to $1,500 per violation with no aggregate cap, and class-action settlements have ranged from $4.75 million to $19 million, per telecom compliance reporting.

Crucially, outsourcing doesn't transfer risk. The Lamb v. Mortgage One Funding case alleges liability for "vendors, lead generators, or agents" placing AI calls on a company's behalf — meaning the hiring business is on the hook, not just the vendor. As one compliance analysis puts it: "AI may automate the interaction. It does not automate away accountability."

If you're evaluating AI calling services — whether for lead qualification, database reactivation, or after-hours response — compliance practices should be a top screening question. Ask how consent is captured and verified, whether AI disclosure happens at the start of every call, and how opt-outs are honored across channels.

At Worqd, our AI SDR and voice agent work is built around these requirements: explicit consent captured upfront, clear AI disclosure on calls, and calls that hand off to a real person with full context. Fast follow-up only counts if it's follow-up you can legally stand behind. The FCC has also proposed additional AI-disclosure rules that would require clear disclosure at the start of every AI call or text — one more reason to work with a partner who tracks the rules as closely as the results.

Compliance Requirements for AI-Powered Sales Calls

The FCC's February 2024 Declaratory Ruling settled the debate: AI-generated voices are legally "artificial" under the TCPA, placing them squarely in robocall territory regardless of how human they sound. That classification triggers the same consent framework that governs traditional autodialed calls — and the stakes are steep. Statutory damages run $500 to $1,500 per violation with no aggregate cap, and class-action settlements in 2025–2026 ranged from $4.75 million to $19 million for telecom-style defendants.

For any service placing marketing calls to cell phones, prior express written consent (PEWC) is non-negotiable in 47 states. That consent must name the business, sit on its own unchecked checkbox, and make clear that agreeing isn't a condition of purchase. Texas, Louisiana, and Mississippi follow a different standard after the Fifth Circuit's Bradford v. Sovereign Pest ruling — oral consent may suffice there — but written consent remains the safer baseline given the jurisdictional split. Informational or transactional calls need only prior express consent, but the moment a marketing purpose enters the picture, PEWC applies.

Disclosure requirements are layering on top of consent. Texas now mandates AI disclosure within the first 30 seconds of a call under SB 140, while California requires bot disclosure in commercial contexts. The FCC has proposed federal rules that would make AI disclosure mandatory at call onset nationwide. A single script can satisfy multiple regimes: "This is an AI assistant calling from [Company] on a recorded line. Is this a good time to talk?"

  • Obtain and document PEWC with dual checkboxes — one for transactional follow-up, one for marketing including AI voice
  • Deliver AI disclosure at the start of every outbound call using a jurisdiction-spanning script
  • Verify consent independently — don't rely on a "consent=true" field passed from a lead source
  • Retain consent records for 4–7 years and honor opt-outs within 10 business days across all channels
  • Restrict calling to 8 a.m.–9 p.m. in the recipient's local time and scrub DNC lists in real time

Worqd builds these requirements into every AI SDR and voice agent deployment — consent architecture, disclosure scripts, real-time DNC checks, and audit-ready record retention — so the follow-up that books calls stays on the right side of the law.

How Worqd Ensures TCPA-Compliant AI Calling

The FCC made one thing unmistakably clear in its February 2024 ruling: an AI voice counts as an "artificial voice" under the TCPA, no matter how human it sounds. That means anyone using AI SDRs or voice agents carries real legal exposure — and TCPA violations run $500 to $1,500 per call, with no aggregate cap and trebled damages for willful violations (legal analyses).

Worse, outsourcing doesn't shield you. The Lamb v. Mortgage One Funding case, filed in February 2026, alleges liability for "vendors, lead generators, or agents" placing AI calls on a company's behalf — so hiring an outside partner transfers zero risk (TCPA litigation reporting). TCPA filings also jumped 95% year-over-year, with aggregate verdicts exceeding $925M.

This is why Worqd builds compliance into its AI SDR and voice agent services from the start, rather than treating it as an afterthought. The approach rests on the same architecture TCPA attorneys recommend.

Consent that holds up under scrutiny

Every form uses dual consent checkboxes — one for transactional follow-up, one separate, unchecked-by-default box for ongoing marketing communications including AI voice. This matters because regulators draw a hard line between "valid consumer data" and "valid consumer consent," and AI-powered bots increasingly submit lead forms with real consumer information but no actual consent (compliance experts). Consent records are retained well beyond the TCPA's four-year minimum.

Disclosure and calling discipline

Every outbound call opens with an AI disclosure that satisfies multiple jurisdictions at once — covering Texas's 30-second disclosure rule, California's bot disclosure mandate, and the FCC's proposed federal requirement (TCPA compliance guidance). Calling windows respect the TCPA's legal hours of 8 a.m. to 9 p.m. in the customer's local time (telecom compliance requirements).

The operational guardrails include:

  • Real-time DNC scrubbing — checking numbers against do-not-call lists continuously, well beyond the minimum 31-day scrubbing cycle
  • Opt-out requests honored within 10 business days across every channel
  • Consent verification that independently documents proof, never relying on a bare "consent=true" field
  • Record retention of 4–7 years, aligned with the TCPA statute of limitations

The FCC removed 185 providers from the Robocall Mitigation Database in August 2025 alone, and false filings now carry a $10,000 base forfeiture per violation (regulatory enforcement data). Enforcement is active and accelerating, not theoretical.

For businesses evaluating any AI calling provider, the question isn't whether the technology works — it's whether the vendor's consent, disclosure, and record-keeping practices would survive a plaintiff's attorney. If a provider can't clearly explain its consent architecture, that gap becomes your liability the moment its AI voice dials your leads.

Want AI follow-up that books calls without legal risk? Book a Growth Call and see how fast, compliant follow-up fits your funnel.

Frequently Asked Questions

Are AI voice calls legally considered robocalls?
Yes. The FCC's February 8, 2024 Declaratory Ruling explicitly classifies AI-generated voices as "artificial" under the TCPA, so they fall under robocall rules no matter how human they sound. The legal standard is simple: if technology generates the words rather than a live person speaking in real time, it's a robocall. See the FCC's official ruling.
If a live agent joins the call partway through, does that make it legal?
No. The FCC stated that "the statute does not allow for any carve out of technologies that purport to provide the equivalent of a live agent." Even hybrid calls — where AI opens the conversation and a human takes over — remain subject to TCPA restrictions, per compliance guidance for voice AI.
What are the penalties for violating TCPA rules with AI calls?
Statutory damages run $500 to $1,500 per violation with no aggregate cap, and willful violations can be trebled. TCPA filings increased 95% year-over-year in 2025-2026 with aggregate verdicts exceeding $925 million, and telecom compliance reporting shows class-action settlements ranging from $4.75 million to $19 million.
Can I outsource AI calling to a vendor and shift the legal risk to them?
No — outsourcing doesn't transfer risk. The Lamb v. Mortgage One Funding case alleges liability for "vendors, lead generators, or agents" placing AI calls on a company's behalf, meaning the hiring business is on the hook. As one compliance analysis puts it: "AI may automate the interaction. It does not automate away accountability."
What consent do I need before making AI marketing calls?
Prior express written consent (PEWC) is required for marketing calls to cell phones in 47 states — it must name the business, sit on its own unchecked checkbox, and not be a condition of purchase. Texas, Louisiana, and Mississippi follow a different standard after the Fifth Circuit's Bradford v. Sovereign Pest ruling, where oral consent may suffice, but TCPA legal analysis recommends written consent as the safer baseline everywhere.
Do I have to tell people they're talking to an AI?
Increasingly, yes. Texas requires AI disclosure within the first 30 seconds of a call under SB 140, California requires bot disclosure in commercial contexts, and the FCC has proposed federal rules that would mandate AI disclosure at the start of every AI call or text. A single script like "This is an AI assistant calling from [Company] on a recorded line" can satisfy multiple jurisdictions at once.
What should I ask an AI calling provider before hiring them?
Ask how consent is captured and verified (never a bare "consent=true" field from a lead source), whether AI disclosure happens at the start of every call, and how opt-outs are honored across channels. Also confirm they scrub DNC lists at least every 31 days, restrict calls to 8 a.m.–9 p.m. local time, and retain records for 4–7 years — the TCPA consent rules leave no room for shortcuts. Worqd builds all of these into every AI SDR and voice agent deployment.

The Bottom Line: Fast Follow-Up Only Counts If It's Legal

So, are AI calls robocalls? Legally, yes — the FCC's February 2024 ruling made that unmistakably clear, no matter how human your voice agent sounds. That means the same rules apply: written consent for marketing calls, AI disclosure at the start of every call, calling-hour limits, DNC scrubbing, and records you can actually produce. The stakes are real — TCPA filings jumped 95% year-over-year, with aggregate verdicts exceeding $925 million according to recent litigation tracking. And outsourcing doesn't pass the risk along; if a vendor's AI dials your leads, the liability lands on you. Before you sign with any AI calling provider, ask how consent is captured and verified, how opt-outs are honored, and whether their records would survive a plaintiff's attorney. That's exactly the standard Worqd holds its AI SDR and voice agent work to — compliance built in from the first dial, so the follow-up that books calls is follow-up you can stand behind. Want compliant AI follow-up for your funnel? Book a Growth Call and see how it fits.

Want help putting this into action?

Book a Growth Call
TopicsAI calls robocalls TCPAAI voice agent complianceTCPA consent rules AI callsFCC AI generated voices rulingTCPA compliant AI callingAI SDR legal requirementsAI robocall disclosure rules

Stay in the Loop