TCPA Compliance for Real Estate Texting: What Teams Need to Know

Texting real estate leads is legal under the TCPA, but only with the right kind of consent before you send. The rules differ for a marketing text to a cold lead versus a scheduling update to a past client. Getting that distinction wrong is where most teams get exposed.

This guide covers what the law requires today. That includes the FCC rule change that reshaped lead-gen texting in 2025, quiet hours, opt-out handling, and what to check in your texting platform.

This is general education, not legal advice. Confirm how these rules apply to your team, your state, and your specific lead sources with a licensed attorney before you finalize a texting policy.

What the TCPA Actually Covers

The Telephone Consumer Protection Act, 47 U.S.C. § 227, treats a marketing text the same way it treats a robocall. The FCC's implementing rules sit at 47 CFR § 64.1200. They apply whether a message goes out from a person's phone or through an automated platform.

A text sent to a lead who never agreed to receive it can violate the law. That holds even if a human typed it instead of a machine.

Why Texting Leads Falls Under the Same Law as Robocalls

The FCC has treated SMS as a "call" under the TCPA for two decades, and courts have upheld that reading consistently. This means the consent rules that apply to an automated phone call also apply to a text sent through a CRM's mass-texting feature. One unsolicited marketing text can trigger the same liability as an unwanted robocall.

Who This Applies To: Agents, Teams, and Brokerages

The law does not stop at the agent who hit send. A team lead who authorized a mass-text campaign can carry vicarious liability for that agent's texts. So can a brokerage that supplied the platform an agent used.

A team lead who instructs six agents to text a purchased list without checking for consent has exposed the whole team. Not just the agent who sent it.

Consent, Explained: Written vs. Express

Real estate texting runs into two different consent standards, and mixing them up is the most common team-wide mistake.

Prior Express Written Consent

Any automated marketing text needs Prior Express Written Consent. That means a signed or electronically confirmed agreement naming the phone number and the sender. It must also state that agreeing to texts is not a condition of any purchase. A lead who fills out a generic "contact me" form on a listing site has not automatically given this.

Prior Express Consent

Prior Express Consent is the lower bar. It covers relationship or transactional texts, like confirming a showing time with someone already working with the agent. It does not require a signed form, but it does require that the lead gave their number expecting contact of that kind.

A Real Estate Example of Each

• Marketing text, needs written consent: A team buys a list of aggregator-sourced leads and wants a recurring "new listings this week" text blast.
• Transactional text, covered by the lower standard: A past client texts an agent's cell to ask about a showing. The agent replies with a time.

The first requires documented, specific consent before a single message goes out. The second is covered by the existing relationship. NAR's compliance guidance draws this same line for members.

The FCC One-to-One Consent Rule: What Changed and What Didn't

Teams that lean on multi-party lead forms, the kind where one form submission gets sold to several agents, should know exactly where this rule stands. A lot of older content still describes it as pending.

What the December 2023 Rule Would Have Required

In December 2023, the FCC adopted a "one-to-one consent" rule meant to close a long-standing loophole. Under the old reading, a single consent checkbox on an aggregator's form could authorize dozens of unrelated sellers and agents to contact the same lead. The new rule would have required a separate, specific consent for each individual seller or agent before contact.

Vacated by the 11th Circuit, January 2025

The rule never took effect. In late January 2025, the 11th Circuit Court of Appeals vacated the one-to-one consent rule in Insurance Marketing Coalition v. FCC, ruling the FCC had exceeded its authority under the statute. The FCC declined to appeal the decision.

What This Means in Practice Today

Multi-party lead forms and aggregator-sourced leads remain usable under the consent standard that existed before the 2023 rule. That does not remove the underlying requirement. The consent disclosure on the form still has to be clear and conspicuous about which parties may contact the lead, real estate agents included. A form that buries "and up to 50 partners may contact you" in fine print is still a compliance risk, rule or no rule.

The Do Not Call Registry and the Established Business Relationship Exception

Marketing texts count as calls for Do Not Call Registry purposes. A number on the national registry cannot receive unsolicited marketing texts from an agent it has no relationship with.

How the EBR Exception Works

The Established Business Relationship exception lets an agent contact a number on the registry if there is a recent transaction or inquiry. The window is 18 months after a completed transaction, or 3 months after an inquiry with no transaction. A buyer who toured homes with an agent two months ago and never signed anything still falls inside that 3-month window.

Why Teams Still Need an Internal DNC List Even With the EBR Exception

The EBR exception does not erase a direct opt-out request. If a lead tells an agent to stop contacting them, that request overrides the exception immediately, regardless of how recent the relationship is. A team of six agents sharing a contact database needs one internal do-not-contact list, not six separate memories of who asked to be left alone.

Quiet Hours and Opt-Out Handling

Federal rules only allow calls and texts between 8 a.m. and 9 p.m. in the recipient's local time zone, and several states set a narrower window.

Federal Quiet Hours and Stricter State Mini-TCPAs

A handful of states have passed their own "mini-TCPA" laws with tighter restrictions than the federal window. Some cut the evening cutoff earlier than 9 p.m. A team working leads across state lines needs to check the specific rule for each lead's location, not just apply the federal default everywhere.

Honoring STOP Requests

A lead can revoke consent through any reasonable method: replying STOP, QUIT, or CANCEL, or simply telling the agent directly to stop texting. FCC guidance is clear that the request does not need to use a specific keyword to count.

The honoring has to be immediate. It has to hold across every agent on a team, not just the one who received the original request. Proplo's texting logs a STOP reply immediately and stops further outreach to that number. That closes the gap where one team member might accidentally recontact a lead who already opted out with someone else on the team.

A2P 10DLC: Why Your Texting Platform's Carrier Registration Matters

Even a fully compliant, consented text can get blocked or filtered by carriers if the platform sending it is not properly registered.

What A2P 10DLC Registration Is

Application-to-Person 10-digit long code (A2P 10DLC) registration is how carriers verify that a business texting from a standard number is a legitimate sender. It confirms the sender is not a spam operation. Any CRM or texting platform, from Follow Up Boss to kvCORE to Proplo, has to register the business and the campaign type. That registration goes through The Campaign Registry, or messages risk carrier filtering.

What to Check Before You or Your Team Texts Through Any CRM or Dialer

Ask the platform directly whether the business and campaign are registered, not just whether texting is a listed feature. An unregistered sender can see message deliverability drop sharply, sometimes with no error message, just silence. A team that assumes messages are landing because the software shows "sent" can miss this for months.

What Happens If a Team Gets This Wrong

TCPA violations carry statutory damages that add up fast across a text blast. The exposure applies to the team, not just the individual agent who hit send.

Penalties: $500 to $1,500 per Violation

Under 47 U.S.C. § 227(b)(3), each violation carries a statutory penalty of $500, and courts can raise that to $1,500 per violation for conduct found willful or knowing. A single unconsented text blast to 200 numbers is not one violation. It is potentially 200.

Vicarious Liability for Team Leads and Brokerages

A team lead or brokerage that authorized, directed, or knowingly benefited from a contractor-agent's non-compliant texting can be held liable alongside the agent. This is the specific risk that makes a written, team-wide texting policy worth the time. It protects the team, not just the agent who sends the message.

Building a Team Texting Policy

A written policy turns these rules into something a team can actually follow day to day, instead of relying on each agent's individual judgment.

A 6-Point Checklist for Setting Team-Wide Texting Rules

1. Separate marketing from transactional texts. Require written consent documentation before any recurring marketing text goes out, and reserve the lower consent standard for existing-client updates.
2. Maintain one shared opt-out list. Every agent should check and update the same internal DNC list, not a personal one.
3. Set quiet hours by the lead's time zone, not the agent's, and apply the strictest state rule that could plausibly apply.
4. Confirm carrier registration on whatever platform the team texts through before sending a single campaign.
5. Require STOP handling within the platform, so an opt-out on one channel applies everywhere a lead's number is stored.
6. Review vendor and lead-source consent disclosures before buying or importing any list, especially multi-party aggregator leads.

Each point on this list maps back to a specific rule covered above. A team lead can hand it to every agent without re-explaining the underlying law each time. This matters most for a platform built for team leads managing multiple agents, where consistency across agents is the actual goal.

How Proplo Helps

Proplo's two-way texting with built-in opt-out handling stops outreach to a number the moment it logs a STOP reply. That opt-out applies across the platform, not just the one channel the reply came in on. Every outbound message, including the review-first follow-up sequences and vendor coordination texts, goes through the agent's approval before it sends. That gives a team lead a real checkpoint on what actually goes out.

None of this replaces a written policy or legal review. It gives a team one consistent set of texting behaviors to build that policy around. Six agents no longer interpret the rules six different ways.