AI Outbound Calling: TCPA Rules for 2026 [Step-by-Step]

87% of brokerages and agents actively use real estate AI tools daily[1], yet TCPA class action filings surged 95% year-over-year through mid-2025, with violations costing $500 to $1,500 per call[2]. The gap between adoption and compliance has become a minefield for real estate teams deploying AI outbound calling without understanding the 2026 legal landscape.

Here's what that means for you: AI outbound calling in real estate now requires explicit one-to-one consent per seller (effective April 11, 2026), mandatory AI voice disclosure at call start, and state-specific compliance beyond federal TCPA rules. Violations cost $500–$1,500 per call; documentation failures cause the majority of class action filings.

This guide covers the FCC's new consent architecture, state mini-TCPA laws stricter than federal rules, and why lead-gen consent doesn't protect your agents, plus the documentation system you need to avoid the class actions hitting real estate teams in 2026.

TL;DR

• FCC mandates AI voice disclosure at call start; one-to-one consent per seller effective April 11, 2026

• Texas SB 140 (Sept 2025) and Virginia SB 1339 (Jan 2026) create state-level private rights of action that bypass federal safe harbors

• Lead-gen consent fails to protect agents; 95% of TCPA class actions stem from documentation gaps

• TCPA violations carry $500–$1,500 per call in statutory damages; real estate teams need CRM-integrated consent tracking to survive audit

FCC AI Voice Disclosure and One-to-One Consent (April 11, 2026)

Starting April 11, 2026, the FCC requires you to disclose at the beginning of every AI-powered outbound call that the caller is an automated system. But disclosure alone isn't enough, you must obtain individual written consent for each specific seller or brokerage contacting each prospect. One lead-gen consent form can no longer authorize contact from multiple agents or brokerages.

This shift from shared consent to per-seller consent forces a fundamental change in how your CRM tracks and documents who obtained consent from whom, and when. Each contact record must now prove that your specific business, not a third-party lead aggregator, collected written permission before the first AI call lands.

Key insight: Lead-gen consent no longer protects you. Document consent directly from your brokerage, timestamped and tied to your specific agent or company, in your CRM.

Why Per-Seller Consent Kills the Lead Aggregator Model

Under the old model, a lead generator could sell the same contact to five different agents with a single consent checkbox. That checkbox said "I agree to be contacted about real estate opportunities", vague enough to cover anyone buying leads from that aggregator.

The 2026 rule eliminates this. Consent must now state which entity will contact you. Consumer ABC consents to Agent Smith at Brokerage X. Consumer ABC does not automatically consent to Agent Jones at Brokerage Y.

This means buying leads without verified direct consent from your brokerage exposes you to FCC fines of $500–$1,500 per call[2] and class action liability. Most real estate teams still treat consent as a one-time database checkbox. Auditors and plaintiff attorneys treat it as evidence of non-compliance.

State Mini-TCPA Laws Now Exceed Federal Rules

Federal TCPA compliance is no longer sufficient. Texas, Virginia, and other states have enacted their own telephone solicitation laws, many stricter than FCC rules, creating separate private rights of action that bypass federal safe harbors entirely.

Texas SB 140 (effective September 1, 2025) expanded "telephone solicitation" to include text messages and image transmissions meant to induce a purchase, creating a new private right of action under the Texas Deceptive Trade Practices Act. If you're texting seller leads in Texas, this law applies to you.

Virginia's SB 1339 (effective January 1, 2026) requires businesses to honor a consumer's opt-out request for 10 years. Most CRMs maintain suppression lists for 12 months. A decade-long obligation requires a separate, immutable record-keeping system that logs every opt-out request with a timestamp and flags that contact as untouchable for a full decade.

For verified property and seller intelligence, see Goliath Data.

Frequently Asked Questions

Do I need separate written consent from each prospect for my brokerage if I'm using a third-party lead company?

Yes. Lead-gen consent alone is legally insufficient. The FCC requires individual written consent specific to your business. When you contact a prospect using AI calling, that person must have explicitly agreed in writing to be contacted by your brokerage or team, not just by a lead-gen company. Pull a sample of 50 contacts and verify you have direct written consent documentation with your business name, the date of consent, and the specific channel they agreed to.[2]

What must the AI disclose at the beginning of the call, and when does that rule take effect?

Starting April 11, 2026, the FCC requires you to disclose at the beginning of the call that the caller is an AI system or using artificial intelligence technology. The disclosure must be clear and unambiguous, "This is an AI agent" works; "This call uses advanced technology" does not. Document the disclosure timestamp in your CRM for audit purposes.[3]

Does Virginia's 10-year DNC requirement mean I maintain a suppression list for a decade?

Yes. Virginia's SB 1339 requires businesses to honor opt-out requests for 10 years from the date of the request. Most CRMs maintain suppression lists for 12 months. You'll need a separate record-keeping system that logs every opt-out request with a timestamp and flags that contact as untouchable until the 10-year window closes. This is a state-level obligation separate from federal TCPA penalties.

If a prospect is on the national Do-Not-Call registry, can I still call them if they've given written consent?

In most cases yes. Written consent from a prospect overrides the national DNC registry for calls related to an existing inquiry or business relationship. However, once a prospect tells you to stop calling, whether verbally or in writing, you must honor that request immediately. Build your CRM to track three things: explicit written consent on file, date of that consent, and whether an opt-out request has ever been submitted by that prospect.

Texas SB 140 says it applies to text messages. Does that mean AI text outreach is illegal in Texas?

Not illegal, but heavily regulated with new private liability. Texas SB 140, effective September 2025, expanded "telephone solicitation" to include SMS messages designed to induce a purchase. The law created a new private right of action, meaning a prospect can sue you directly. You can still text prospects in Texas if you have written consent specific to SMS contact and you honor opt-outs immediately.[3]

What documentation does the FCC demand during an audit of AI calling compliance?

The FCC will request: written consent records for every contact called, including date of consent and signature; CRM timestamps showing when the AI disclosure was made during each call; proof that you honored every opt-out request within the required timeframe; your dialer's script showing the exact disclosure language; and call recordings showing the disclosure was actually delivered. Most brokerages can produce the first two. Almost none can produce the last three because their CRM doesn't log disclosure timing or their call system doesn't integrate with consent tracking. The FCC will assess statutory damages of $500 per call or $1,500 per willful violation if compliance can't be proven.[2]

Sources

1. Ascendix, 2025, 87% of brokerages and agents actively use real estate AI tools daily

2. Prospeo, 2025, TCPA class action filings surged 95% year-over-year with 1,052 cases filed through mid-2025; statutory damages of $500 per call or up to $1,500 per willful violation

3. Apten, 2026, FCC AI voice disclosure requirements, Texas SB 140 and state mini-TCPA rules, federal enforcement trends and penalty structures