It's 9:40 on a Tuesday and the morning huddle on your collections floor has been hijacked by a forwarded email. Your compliance officer has flagged the AI voice vendor you demoed last week - the one that promised to double contact attempts without adding headcount - with a one-line question: "Have they looked at the FCC docket on this?" The vendor's pitch deck had a slide about efficiency. It did not have a slide about the Telephone Consumer Protection Act. This article is the slide they left out.
The rule that already exists
Start with what is settled, because more is settled than most vendor pitches let on. On February 8, 2024, the FCC issued a unanimous declaratory ruling confirming that the TCPA's restrictions on "artificial or prerecorded voice" calls cover current AI technologies that generate human voices - including voice cloning that mimics a real person and fully synthetic voices that never belonged to anyone.
That wasn't a new law. It was the Commission saying the old law already applies. If your outbound campaign uses an AI-generated voice, the TCPA already treats it exactly like a prerecorded robocall: prior express consent before the call, clear identification of who's calling, and a working opt-out. Despite the headlines at the time, the ruling didn't make AI voice calls illegal - it made them regulated, the same way prerecorded calls have been regulated for decades. Legal, but only inside the lines.
For a collection agency, those lines matter more than for almost anyone else, because you're already operating under Regulation F's call-frequency presumptions and, depending on your footprint, stricter local caps on top of them. An AI voice doesn't get you extra attempts. It gets you the same rationed attempts, executed by software - with every consent and disclosure obligation intact.
The disclosure rule still in the pipeline
What's not settled yet is the part worth preparing for. In August 2024, the FCC adopted a notice of proposed rulemaking - the first proposed rules aimed specifically at AI-generated calls and texts. Three proposals in it should have every collections operator's attention. The Commission proposed to define what counts as an "AI-generated call." It proposed to require callers to disclose to the consumer, on the call itself, that they're hearing AI. And it proposed that consent forms explicitly state that calls will be AI-generated - meaning consent to be called and consent to be called by an AI may become two different things.
Comments closed in October 2024, and as of mid-2026 the Commission hasn't issued a final rule. It would be a mistake to read that silence as retreat. The declaratory ruling passed unanimously, several states have been writing their own AI-disclosure laws (California's Bolstering Online Transparency Act has required bots to disclose themselves in certain commercial conversations since 2019), and no commissioner has argued that consumers should hear a synthetic voice without knowing it. The direction of travel is one-way.
Write every script as if the first sentence must say it's AI - because that's precisely what the pending rule proposes, and rewriting one sentence is cheap while re-papering a consent file is not. The consent proposal is the sleeper here. If the final rule requires that consent explicitly name AI, consent language you collected in 2024 that says "calls, including autodialed and prerecorded calls" may not stretch to cover it. Ask your counsel now whether your intake language would survive, and fix the template before you have a million accounts consented under the old one.
Outbound is where the exposure lives
Here's the distinction that should shape your whole strategy: the TCPA's artificial-voice restrictions govern calls you place. When a consumer calls you and an AI answers, you're in a different posture - your FDCPA and Reg F obligations still apply in full, but the robocall consent machinery that generates class actions attaches to outbound dialing, not to answering your own phone.
Run the exposure math on your own portfolio, not a vendor's slide. TCPA statutory damages run $500 per violating call, up to $1,500 if the violation is willful, and there's a private right of action with no cap on class size. Take one outbound AI-voice campaign of 10,000 calls placed against consent language that turns out not to cover AI, and you're staring at a theoretical exposure between $5 million and $15 million - from one campaign, one defect. Nobody expects the worst case, but plaintiffs' firms build practices on exactly this arithmetic.
The cheapest way to shrink TCPA exposure is to move resolution from calls you place to conversations the consumer starts. This is the same logic collections teams have been applying since Reg F rationed their attempts: when outbound is capped and regulated, the letter, the statement, the QR code, and the inbound line carry the strategy. A consumer who dials the number on their letter at 11 PM and reaches an agent that verifies them, explains the balance, and takes a payment has resolved the account with zero outbound consent risk - because you never placed a call.
What to prepare this quarter
None of this requires waiting for the FCC to act. The preparation is the same whether the final rule lands next quarter or next year:
- Inventory where AI voice touches outbound. Every campaign, every vendor, every voicemail drop. If a synthetic voice speaks on a call you initiated, it's on the list.
- Pull your actual consent language. Does it name artificial or prerecorded voice? Would it survive a requirement that AI be named explicitly? Get a written answer from counsel, not a nod.
- Script the disclosure and A/B it. Put "this call uses an AI assistant" in the first sentence of an outbound script and measure completion and payment rates against your current script. Operators who've tested this often find the drop-off smaller than feared - but find out with your numbers.
- Log everything per call. Consent source and date, disclosure played, opt-out honored, transfer offered. If the rule finalizes, this is your audit trail; until then, it's your defense file.
- Ask vendors the docket question. If a voice vendor can't speak fluently about the 2024 declaratory ruling and the pending rulemaking, they're selling you their risk.
Treat disclosure as a product decision you test, not a legal footnote you bolt on at the end. The same discipline applies beyond collections - patient billing calls ride on the very same TCPA rails, and a billing operation that gets consent and disclosure right earns something regulators can't mandate: patients who trust the voice enough to stay on the line.
Start small, measure it
You don't have to re-architect your dialer strategy this month, and you shouldn't bet compliance on guesswork either way. Start where the regulatory risk is lowest and the data is fastest: the inbound line. Put an AI voice agent on the number printed on your letters and statements, let it disclose plainly that it's an AI assistant, and let it verify, explain, and resolve around the clock. No outbound consent question, full disclosure from the first sentence, and every conversation logged.
Then count, the way you'd evaluate anything: how many inbound calls came in after hours, how many resolved without a human, what that did to your cost per resolution and your outbound attempt budget. With published pricing, the comparison takes minutes, and if the numbers don't clear your bar you've lost nothing but a short experiment. If they do, expand from there - inbound first, disclosed outbound second, always ahead of the rule instead of scrambling behind it. One caveat that belongs in print: this article is field notes, not legal advice - take the specifics to your counsel. Then start the experiment, and let your own call log make the argument.