LEARN
TCPA & AI Calling for Real Estate: The 2026 Compliance Guide
Last updated: July 2026
This guide is educational, not legal advice. TCPA litigation is a real industry, the rules keep moving, and your facts matter — consult your own counsel before building a calling program.
If software calls your leads with a synthetic voice, federal law has something to say about it. Here’s what the rules actually are, what they cost to get wrong, and a practical checklist — including exactly which parts a vendor can handle for you and which parts stay yours no matter what.
February 2024: the FCC says AI voices are “artificial”
In a declaratory ruling adopted February 8, 2024, the FCC confirmed that AI technologies that generate human-sounding voices are “artificial” voices under the TCPA. This wasn’t a new law — it was the FCC closing the “but it’s AI, not a recording” loophole. Every rule that already applied to artificial and prerecorded voice calls applies to AI voice calls. If an AI ISA calls your leads, you are running an artificial-voice calling program in the eyes of the law.
What the TCPA requires for AI voice calls
- Prior express written consentfor marketing calls made with an artificial voice to cell phones. “Written” can be electronic (a web form qualifies), but it must clearly disclose that the person agrees to receive calls made with an automated or artificial voice from your named business, and it cannot be a condition of purchase. A phone number typed into a form with no disclosure is not consent.
- Identification. The call must identify the business responsible for it and provide contact information.
- Opt-outs must be honored — immediately and across channels. Artificial-voice telemarketing calls must also offer an automated opt-out mechanism during the call itself.
- Quiet hours: 8 a.m.–9 p.m. in the called party’s local time. That’s the federal floor — and it’s the lead’s timezone, not yours. Some states are stricter: Florida, for example, cuts off at 8 p.m. and caps call attempts.
One 2025 development worth knowing: the FCC’s separate “one-to-one consent” rule (which would have required consent to name each individual seller) was vacated by the Eleventh Circuit in January 2025. The underlying prior-express-written-consent requirement was never in question and still stands.
What getting it wrong costs
The TCPA carries statutory damages of $500 per violating call, up to $1,500 per call for willful or knowing violations— and a private right of action, which is why a plaintiffs’ bar exists specifically to find non-compliant callers. Per-call math compounds fast: a misconfigured campaign that makes 200 bad calls is a $100,000–300,000 statutory exposure before legal fees. Several states (Florida, Oklahoma, Washington) layer their own “mini-TCPA” statutes on top with separate damages.
The practical checklist for agents
| # | Do this | Why |
|---|---|---|
| 1 | Put consent language on every lead form: calls and texts, including automated technology and artificial/AI voice, from your named business, not a condition of purchase. | This is what makes the AI callback lawful in the first place. |
| 2 | Keep proof of every consent: which version of the form text they saw, when, and from what IP. | In a dispute, the burden of showing consent is on you. |
| 3 | Maintain an internal do-not-call list and honor every opt-out instantly, in every channel. | Calls after an opt-out are the classic willful violation — the $1,500 tier. |
| 4 | Call only 8 a.m.–9 p.m. in the lead’s local time — and tighter where state law says so. | An out-of-state lead in another timezone is the easiest violation to commit by accident. |
| 5 | Make sure the call identifies your business by name with contact info. | Required on artificial-voice calls. |
| 6 | Keep call logs and opt-out records. | Recordkeeping is your defense; memory isn’t. |
| 7 | Vet lead sources. Purchased or scraped lists rarely carry valid consent to be called by your business with an AI voice. | Liability lands on the caller, not the list broker. |
How Cadence implements each rail
Cadence was built assuming the FCC ruling, not hoping around it. What ships in the product:
- Consent capture with evidence: hosted lead forms record the consent copy version, timestamp, and IP address for every submission — the proof items in checklist rows 1–2.
- Lead-local calling windows: calls are scheduled inside quiet hours in the lead’stimezone, not the office’s.
- Instant opt-out honoring: a lead who says stop is stopped — the request takes effect immediately.
- Per-organization do-not-call list: opted-out and manually flagged numbers are blocked from all future calling for your org.
And the honest caveat: no vendor can make you compliant, and Cadence does not guarantee compliance. The rails handle the mechanical requirements, but the consent language you use, where your leads come from, and how you run your business remain your responsibility. If a vendor tells you their tool makes TCPA a solved problem, that tells you something about the vendor.
Reminder: this is general educational information, not legal advice, and it may not reflect the very latest rulings. Consult a telecom-compliance attorney before launching any outbound calling program.
Related: The best AI ISA tools, honestly ranked · What is an ISA? · The verified speed-to-lead statistics
Don’t take our word for it — call the AI yourself.
This number rings straight to Cadence playing a fictional brokerage’s agent. Grill her like a real lead would.