TCPA and FTC AI Disclosure Rules: What AI and SaaS Companies Deploying Automated Calls, Texts, and Chatbots Need to Know
If your platform places automated calls, sends automated texts, or puts an AI chatbot or voice assistant in front of customers, you’re now sitting at the intersection of two overlapping compliance regimes: the Telephone Consumer Protection Act (TCPA) and a rapidly expanding body of FTC guidance on AI disclosure. Neither is new in concept, but 2026 has brought real changes to how aggressively — and how specifically — regulators expect businesses to comply.
TCPA Obligations Didn’t Go Away Just Because the Calls Are Automated by AI
The TCPA has always regulated autodialed calls and texts, requiring prior express consent, honoring do-not-call requests, and following specific disclosure and recordkeeping rules. What’s changed is the FCC’s clarification that AI-generated voices used in robocalls fall squarely within the TCPA’s scope. That means:
- Prior express consent is required before placing calls or texts that use an AI-generated or AI-assisted voice — the same baseline standard that applies to traditional autodialed calls.
- Failure to disclose that a call or text is AI-generated can create additional liability layered on top of ordinary TCPA exposure, not a substitute for it.
- Consent language, opt-out mechanics, and call/text scripts built for a “traditional” autodialer often need to be revisited when an AI voice or AI-drafted text is introduced into the same channel.
For AI-powered service desks, appointment reminder systems, review-request platforms, and customer outreach tools, this means the underlying TCPA compliance work doesn’t change — but the disclosure layer sitting on top of it does.
The FTC’s AI Disclosure Guidance Adds a Second Compliance Layer
Separately from telecom-specific rules, the FTC has been building out — through enforcement actions, updated Endorsement Guides, and a comprehensive AI policy statement — a consistent position under Section 5 of the FTC Act: if a consumer could reasonably believe they’re interacting with a human, and the business knows otherwise, failing to say so is a deceptive practice.
In practical terms, the FTC’s current guidance points toward a few consistent requirements for customer-facing AI:
- Clear, conspicuous, and timely disclosure. Disclosure has to happen before or at the point of interaction — not buried in a terms of service page or a footer link the customer never sees.
- No impersonation of humans. Chatbots, voice assistants, and automated texting tools that could be mistaken for a live person need an affirmative “this is AI” disclosure, not just the absence of a denial.
- Truthful, substantiated claims. AI-generated responses, recommendations, or content are held to the same truthfulness standard as anything a human employee would say — using AI to generate the message doesn’t lower the bar.
- Endorsement and review integrity. AI-generated or AI-assisted testimonials, reviews, and endorsement-style content must be disclosed as such when presented as genuine consumer experiences.
The FTC has also signaled it’s not finished. A newer proposed policy statement addresses “suppression of accuracy” in AI systems, focusing on whether AI outputs are steered in ways that depart from what users would reasonably expect, and whether that steering is adequately disclosed. That proposal is still in a public comment period, but it’s a strong signal of where enforcement priorities are heading.
Why This Matters More for AI SaaS and AI-Powered Service Businesses
If your product is an AI receptionist, an AI-driven customer service desk, an omnichannel support platform, or any tool that automates outbound calls, texts, chat, or reviews on behalf of your clients, you’re carrying compliance risk on two fronts simultaneously:
- TCPA exposure tied to the automated call/text itself — consent, opt-out, calling hours, recordkeeping.
- FTC deception exposure tied to whether the AI nature of the interaction was properly disclosed to the end consumer.
A platform can be fully TCPA-compliant on the telecom side and still create FTC exposure if the AI disclosure isn’t clear, conspicuous, and timely. The two frameworks need to be addressed together — in your Terms of Use, your Privacy Policy, your subscriber agreements, and the actual scripts and UI your product uses to interact with end users.
Practical Steps Worth Taking Now
Keep documentation of your AI systems, what they’re used for, and where disclosures live — the FTC’s current posture rewards businesses that can show their compliance work, not just claim it.
Audit every channel where your platform (or your client’s platform) places automated calls or texts, and confirm consent and disclosure language accounts for AI-generated voice or content.
Review chatbot and voice assistant scripts for an affirmative, early AI disclosure — not just a passive absence of misrepresentation.
Update subscriber/vendor agreements so that disclosure obligations are clearly allocated between platform provider and end-client.
Get Help Getting This Right
This is exactly the kind of overlapping regulatory work I handle for AI and SaaS clients on a flat-fee basis — reviewing or drafting the Terms of Use, Privacy Policy, MSA, and disclosure language your platform needs to address both TCPA and FTC AI disclosure requirements together, rather than patching them in separately after the fact.
Andrew S. Bosin, Esq.
Andrew S. Bosin LLC
36 Highland Road, Glen Rock, NJ
www.njbusiness-attorney.com | 201-446-9643
Email: andrewbosin@gmail.com.
This post is provided for general informational purposes and does not constitute legal advice. Contact our office to discuss how these requirements apply to your specific platform and use case.
#TCPACompliance #FTCCompliance #AILaw #AICompliance #SaaSLaw #AISaaS #TechLaw #StartupLaw #NJAttorney #AIRegulation #ConsumerProtection #LegalTech