TCPA Compliance for Real Estate Transaction…

Quick answer. tcpa compliance for real estate in 2026: By Vikas Malpani, CEO of ReBillion and CAR Certified Transaction Coordinator. This guide covers Direct Answer, What TCPA is (and what it covers), Why TCPA matters now in real estate (2026 update).

By Vikas Malpani, CEO of ReBillion and CAR Certified Transaction Coordinator. Last reviewed June 4, 2026.

Direct Answer

TCPA compliance for real estate transaction coordinators means complying with the Telephone Consumer Protection Act (47 USC 227), the FCC’s implementing rules (47 CFR 64.1200), the FCC’s February 2024 AI voice ruling (FCC 24-17), the FTC Telemarketing Sales Rule (16 CFR 310), and applicable state overlays — every time the TC, the brokerage, or any TC software places an automated outbound call, sends an SMS, or runs a ringless voicemail. ReBillion is the only AI-native transaction coordinator with TCPA compliance baked in at the platform layer: consent capture, do-not-call honor, AI identification on connect, calling-time enforcement, two-party recording disclosure, and 7-year audit trail retention.

A brokerage’s TCPA exposure is almost never the agent making a single bad call. It is the automated SMS blast, the AI voice deployment without identification, or the call to a number on the National Do Not Call Registry placed by a tool the broker did not realize was dialing. The private right of action runs at $500 per violation, treble damages for willful violations, and the plaintiffs’ bar has been organized around TCPA since 2015. This guide is the version of the law a transaction coordinator actually needs to operate.

—

What TCPA is (and what it covers)

The Telephone Consumer Protection Act is a 1991 federal statute, codified at 47 USC 227. Its core prohibition: no automated calls or texts to a U.S. number without the called party’s prior express consent. The FCC implements the statute through 47 CFR 64.1200 and a stream of declaratory rulings. The FTC adds the Telemarketing Sales Rule (16 CFR 310) on top.

The categories TCPA covers in a real estate operations context:

• Automated outbound voice calls to residential and wireless numbers — including any call placed by an autodialer or using an artificial or prerecorded voice. After FCC 24-17 in February 2024, AI-generated voices fall squarely inside the artificial-voice category.
• SMS messages sent by an automatic telephone dialing system. Most modern bulk SMS platforms count. One-to-one texts typed by a human do not.
• Ringless voicemail. Treated as an artificial voice call by most courts.
• Fax broadcasting. Still covered, still actionable, still occasionally relevant in title and lender workflows.

The statute is technology-neutral. New AI voice agents are TCPA subjects because the FCC said so explicitly in 2024.

What TCPA does not regulate:

• Calls placed by a human, manually, one number at a time, to a known counterparty for transactional purposes.
• Calls to business lines that the called business has held out as a contact for the purpose at hand (lender business desks, title office business lines, utility company business desks).

The line between “automated marketing call” and “transactional call to a known business counterparty” is the entire compliance question.

—

Why TCPA matters now in real estate (2026 update)

Five forces made TCPA a 2026 priority for every brokerage operator I talk to.

1. AI voice deployments are real. Before 2024, AI voice in TC operations was theoretical. After FCC 24-17, it is regulated, deployable, and unmistakably high-leverage. Brokerages running AI voice without TCPA hygiene are running uninsured.

2. The plaintiffs’ bar has expanded. TCPA class actions doubled between 2018 and 2024. Defense costs for a single class action that survives a motion to dismiss now routinely cross $1M. Brokerages are not just exposed for their own tools; they are exposed when their vendors mishandle calls placed on the brokerage’s behalf.

3. State overlays got tighter. Florida’s Telephone Solicitation Act, as amended in 2023, materially expanded private right of action and consent requirements for telemarketing to Florida residents. Oklahoma adopted a similar statute. California passed updates in 2023 and 2024 sharpening calling-time and identification rules. Brokerages in or contacting these states cannot rely on federal rules alone.

4. The Robocall Mitigation Database is enforced. Voice providers must be registered. Calls originating from unregistered providers can be blocked by terminating carriers. The compliance burden has moved upstream into the provider stack.

5. AI identification is non-negotiable. FCC 24-17 made the artificial-voice identification requirement explicit for AI voices. A polite “this is an AI assistant calling about your active file” within the first seconds of the call is now the line between compliant operations and a $500-per-violation exposure.

This is no longer a theoretical regulatory regime. Brokerages that ignored TCPA in 2018 because nobody got sued are watching peers get sued in 2025 and 2026.

—

How TCPA applies to a real estate TC workflow

A working TC workflow touches the phone, SMS, and email constantly. Map each touch to a consent basis.

Transactional calls to file counterparties. A call to the lender named on the file, the title officer of record, the utility company associated with the property, or the HOA management company contracted on the deal. Consent basis: the counterparty is named in or contracted under the active real estate transaction. Subject to identification, calling-time, and recording-disclosure rules; not subject to prior-express-written-consent rules.

Calls to buyers, sellers, or agents named on the file. Consent basis: the engagement agreement (the brokerage’s listing agreement, buyer representation agreement, or service agreement with the agent) typically includes consent to receive transactional communications. Confirm in writing that the agreement covers automated and AI-driven communication explicitly.

SMS reminders to buyers, sellers, or agents. Same consent basis as transactional calls. Be careful: SMS sent through any bulk platform that uses automatic telephone dialing system functionality is TCPA-covered. Ad-hoc one-to-one texts typed by a human are not.

Marketing or referral solicitation. Different category entirely. Requires prior express written consent. Most TC software should not be used for marketing calls or SMS; if you are, do it through a tool with full marketing-consent capture.

Cold outreach to potential vendors, lenders, or title companies you do not have a relationship with. Requires prior consent or business-line targeting. The internal rule we apply: do not automate cold outreach.

This map decides everything. If a call does not fall into one of the first three categories, the AI voice agent should not be making it.

—

Implementation and compliance requirements

There is a 2026 version of the TCPA compliance checklist for any TC operation. We use this internally, and it is what brokerage attorneys want to see when they review a vendor.

The TCPA-clean voice agent checklist (10 items)

1. Map every automated call or SMS to a consent basis. Transactional, written consent, established business relationship, or one-to-one human. Anything else does not get sent.
2. AI identification on connect. Per FCC 24-17, AI voice identifies itself within the first seconds of the call. Recorded calls identify the recording.
3. National Do Not Call Registry check at dial. Every dial is checked against the National DNC list. The 31-day grace window for established business relationships is honored.
4. Internal do-not-call list. Every “stop calling” request adds the number to the internal DNC list and suppresses it across the platform.
5. State DNC lists. Many states publish their own DNC registries (FL, TX, IN, MO, OH, PA, TN, WI). Check at dial for any matching state.
6. Calling-time enforcement. No calls before 8 a.m. or after 9 p.m. local to the called number, per 47 CFR 64.1200. Florida’s TCPA-equivalent statute narrows this further; the system enforces the tightest applicable window.
7. Two-party-consent recording disclosure. California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Nevada, Pennsylvania, and Washington require both-party consent. The agent notifies on connect for every call, every state.
8. Caller ID transmission per TRACED Act / STIR/SHAKEN. Accurate caller ID, attestation level, originating provider registered in the Robocall Mitigation Database.
9. Audit-trail retention. Trigger, consent basis, dial timestamp, identification confirmation, transcript, outcome code, opt-out events. Retained 7 years.
10. Quarterly policy review. TCPA case law, state rule updates, FCC guidance. A standing quarterly review catches drift before it becomes exposure.

A brokerage that runs all 10 items can deploy AI voice with confidence. A brokerage that runs 7 or fewer is uninsured.

—

Case study: how a 60-agent brokerage avoided a $312,000 SMS exposure

A 60-agent brokerage in Florida came to us in early 2026 for an AI voice deployment review. Their existing SMS workflow — a bulk platform sending closing reminders and “do you want to refer a friend” messages — had been live for 18 months. They had never done a TCPA audit on it.

The audit found:

• 624 messages sent to numbers on the National DNC list within 31-day windows without an established business relationship.
• 312 messages crossing the marketing line (“refer a friend”) without prior express written consent.
• No documented opt-out path. Recipients replying “STOP” were not being suppressed.

At a $500 statutory minimum per violation, the theoretical exposure on the marketing-line messages alone was $156,000. Treble damages for willful conduct doubled it. Add Florida’s TCPA-equivalent statute layered on top, and the realistic litigation exposure was north of $312,000 before any class certification.

The remediation:

• Bulk platform retired. New SMS workflow runs through a TCPA-aware system with consent capture per recipient.
• Marketing-line messages moved into a separate platform with prior-express-written-consent capture at the lead source.
• Transactional reminders moved into ReBillion, which has consent capture, DNC honor, and opt-out handling at the platform layer.
• A written AI voice and SMS policy was drafted and approved by the brokerage’s outside counsel.
• A quarterly compliance review was scheduled.

No lawsuit has been filed against the brokerage as of the date of this guide. The exposure window remains open under the relevant statutes of limitation, but the brokerage has cleaned its operational surface. The lesson the brokerage learned the hard way: TCPA exposure is rarely about the AI voice agent; it is about the SMS workflow nobody audited.

—

How ReBillion handles TCPA compliance

ReBillion is the only AI-native transaction coordinator with TCPA compliance enforced at the platform layer rather than configured per deployment. The architectural choice matters: when compliance lives at the platform, every brokerage benefits from every fix, and no brokerage can accidentally turn it off.

Specifically:

• Consent basis tagged at file creation. Every counterparty on a file is tagged with its consent basis when added. No call goes out without a basis.
• AI identification enforced at the voice agent. The identification line is part of the model’s system prompt and cannot be disabled by a brokerage user.
• DNC checks at dial. National DNC, state DNC, and internal DNC are checked in the dial pipeline, not in a campaign manager. Skipping is not a setting.
• Calling-time enforcement by destination. The destination zip-code or area-code time zone drives the window. A California brokerage calling a Florida lender at 8:30 a.m. Pacific is calling at 11:30 a.m. Eastern; the system allows it. The same brokerage calling a Pacific Time lender at 6 a.m. Pacific is blocked.
• Recording disclosure on every call. Two-party-consent states get the same disclosure as one-party-consent states. We do not optimize against the strictest rule.
• Audit-log retention for 7 years. Aligned to NAR and state recordkeeping rules, and to Fannie Mae / Freddie Mac document custodian guidelines for files where applicable.
• Robocall Mitigation Database registration. Our voice provider stack is registered. Sub-processor list is on the privacy page.

What ReBillion does not do: pretend that buying our software is a full TCPA compliance program. Brokerages still need a written policy, a marketing-vs-transactional separation, and a quarterly review. We provide the operational surface; the brokerage owns the policy.

—

Tools and vendors compared

Brokerages comparing TCPA-aware tools usually look at four categories. Honest read:

The category split that matters: tools that enforce TCPA at the platform layer versus tools that hand the brokerage a compliance toolkit. ReBillion is the only TC software in 2026 doing the former.

—

Common mistakes to avoid

Assuming transactional means unregulated. Transactional calls are exempt from prior-express-written-consent rules. They are not exempt from identification, calling-time, DNC honor, recording disclosure, or audit-trail requirements.

Treating SMS as a free zone. SMS through any automatic telephone dialing system is TCPA-covered. Plaintiffs’ lawyers love SMS class actions because the per-message damages add up fast.

Letting AI voice “freelance.” A voice agent that drifts off-script into marketing-adjacent topics has crossed a regulatory line. Tight scope, strict identification, fast handoff to humans.

Skipping state overlays. Florida and Oklahoma especially. A federal-only compliance posture is incomplete.

Forgetting the 31-day DNC grace window. Established-business-relationship exemptions have time limits. Track them.

Outsourcing TCPA to a vendor without a written program. “The vendor handles it” is not a defense. Brokerages remain liable for calls placed on their behalf.

No written policy. When the demand letter arrives, the first request is the brokerage’s written TCPA policy. Have one.

—

FAQs

Q: What is TCPA compliance for real estate transaction coordinators?

A: Compliance with the Telephone Consumer Protection Act (47 USC 227), the FCC’s implementing rules (47 CFR 64.1200 and FCC 24-17 for AI voice), the FTC Telemarketing Sales Rule (16 CFR 310), and state overlays — every time a TC, brokerage, or TC software places automated outbound calls or SMS.

Q: Does TCPA apply to AI voice agents?

A: Yes. The FCC’s February 2024 Declaratory Ruling (FCC 24-17) clarified that AI-generated voices fall within the “artificial or prerecorded voice” definition. All TCPA requirements apply.

Q: What is the penalty for a TCPA violation?

A: $500 per violation, with treble damages ($1,500 per violation) for willful or knowing violations. There is a private right of action and a flourishing class-action bar.

Q: Are transactional calls to lenders and title companies TCPA-regulated?

A: They are subject to TCPA’s identification, calling-time, DNC, and recording-disclosure rules. They are typically not subject to prior-express-written-consent rules because the counterparty is a known business contact tied to the active transaction.

Q: What about calls to buyers and sellers on an active file?

A: Permissible based on the engagement agreement consent and the established business relationship — provided the brokerage’s listing or buyer agreement explicitly covers automated and AI-driven transactional communication.

Q: What time of day can a TC software call?

A: Per 47 CFR 64.1200, no calls before 8 a.m. or after 9 p.m. in the called party’s local time. Some states tighten the window. The system enforces the strictest applicable rule.

Q: What is the Robocall Mitigation Database?

A: An FCC-maintained database of voice service providers required to certify their robocall mitigation programs under the TRACED Act and the STIR/SHAKEN framework. Originating voice providers must be registered.

Q: Does Florida have its own TCPA-style law?

A: Yes. The Florida Telephone Solicitation Act, as amended in 2023, expanded private right of action and consent requirements for telemarketing to Florida residents. Brokerages contacting Florida numbers must comply with both federal TCPA and Florida law.

Q: What about California and Oklahoma?

A: California has rolling updates sharpening identification and calling-time rules. Oklahoma’s Telephone Solicitation Act (2022, with subsequent updates) creates an additional consent surface. Both must be layered on top of federal TCPA.

Q: Do I need two-party consent to record a call?

A: In California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Nevada, Pennsylvania, and Washington — yes. ReBillion notifies on connect in every call, every state, to avoid the cost of getting the destination wrong.

Q: How long do I need to retain TCPA audit logs?

A: We retain 7 years aligned to state real estate commission recordkeeping rules and document custodian guidelines. The TCPA statute of limitations is 4 years (federal) and varies by state; 7 years is the safer floor.

Q: Is “stop” enough to opt out?

A: Yes, and any reasonable equivalent (“unsubscribe,” “remove me,” “do not call again”). The system must honor the opt-out within a reasonable time, typically interpreted as immediate suppression.

—

Get Started

If your brokerage is running any automated SMS, voice, or AI-driven outbound communication and you have not done a TCPA audit in the last 12 months, do one now. Book a TCPA review at rebillion.ai and we will walk through your current stack against the 10-item checklist. If you are evaluating an AI voice agent for transaction coordination, the TCPA posture should be the first question on the vendor call, not the last. We built ReBillion to be the only TC software with the answer already wired in.

Related guides on ReBillion

• Brokermint Alternative for Real Estate Brokerages (2026)
• Paperless Pipeline Alternative: AI-Native TC Software

Written by Vikas Malpani

Vikas Malpani is the CEO and Co-Founder of ReBillion and a CAR-Certified Transaction Coordinator. A serial real estate technology entrepreneur with 15+ years across technology and real estate operations, he was named to MIT Technology Review's TR35 list of young innovators. At ReBillion he leads the AI systems that deliver compliant, accurate transaction coordination for brokerages and agents across all 50 US states. Connect with Vikas on LinkedIn: https://www.linkedin.com/in/vikasmalpani/

View Profile