TCPA Compliance for Realtor Texting: A Plain-English Guide

By Colton, Founder of Diviine · Published 2026-07-08 · Category: Real Estate · 6 min read

What you can text, what you cannot, and how to keep automated real estate SMS on the right side of the rules.

The short answer

You may text a person who contacted you first about a specific inquiry. You may not text purchased lists or cold numbers without prior express written consent. Every automated conversation needs identification and a working opt-out, and that applies whether a human or a system sends the message.

The three things that keep you safe

• Basis to contact. Portal inquiry, your website form, your open-house sign-in sheet, or documented, signed consent. Keep the record of where the contact came from and when, because that record is your protection if a complaint ever surfaces.
• Identification. The first message of a new conversation states who you are and what business you represent. Vague or unsigned first messages create ambiguity that works against you later.
• Opt-out. STOP, UNSUBSCRIBE, CANCEL, END, and QUIT must suppress the contact immediately and permanently until they opt back in on their own. This has to work every time, not most of the time.

Things that create real exposure

• Buying a list and texting it cold, even once, even to "just a few" numbers.
• Continuing to message after an opt-out because a teammate re-imported the same contact from a spreadsheet.
• Automated messages that claim to be a human when directly asked whether they are a bot.
• Messaging outside of reasonable local hours, particularly early morning or late night texts to numbers you have no ongoing relationship with.
• Sharing a phone number across multiple agents or teams without tracking which basis-to-contact applies to which agent.

A realistic scenario

An agent's assistant exports last year's open-house sign-in sheets into a new nurture campaign without checking for opt-outs recorded since. Two contacts who unsubscribed six months earlier get texted again. Individually this looks like an oversight; at scale, and in front of a regulator or a plaintiff's attorney, it looks like a pattern. The fix is not more caution, it's a system where opt-out status travels with the contact record no matter how many times it gets imported.

Practical operating rules

Store consent source on every contact record at the moment of creation, not after the fact. Sync opt-out state to your CRM so it survives spreadsheet imports and lead-source merges. Log every message with a timestamp so you can reconstruct the conversation history if asked. If a contact asks whether they are talking to a person, answer honestly and offer to connect them with the actual agent.

FAQ-style wrap

None of this requires avoiding automation. It requires the automation to behave exactly like a well-trained human would: identify itself, respect a stop request instantly, and never text someone who never gave a basis to be contacted in the first place.

This is operational guidance, not legal advice. Have counsel review your specific setup, particularly if you operate across multiple states with different requirements layered on top of federal rules.

Plug it in

Diviine builds consent tracking and opt-out handling into every conversation by default so this does not depend on someone remembering to do it manually. Read the Diviine trust and compliance posture.

How this applies specifically to automated systems

When a system, rather than a person, sends the first message, the same rules apply with one added layer of scrutiny: regulators and courts look closely at whether the basis-to-contact was properly established before any message went out, automated or not. A well-built system checks the lead source at the point of intake and only initiates a conversation when a valid basis exists, such as a direct inquiry on a specific listing. This removes the risk of a human accidentally texting a purchased list or a stale contact that never should have been messaged in the first place.

Multi-state considerations

Some states layer additional consent or timing requirements on top of federal TCPA rules, particularly around calling and texting hours or additional disclosure requirements for automated messages. If your team operates across state lines, this is worth a specific conversation with counsel rather than assuming one national policy covers every market you work in. A cautious default, identify clearly, message during reasonable hours, and honor opt-outs instantly, tends to satisfy most state-level variations even without memorizing every individual statute.

Building this into team culture

Compliance breaks down most often not through malice but through convenience: someone re-imports an old list without checking it, or a new team member does not know the opt-out rules and texts a number that should have been suppressed. The fix is procedural, not just educational. Make opt-out status a field that travels with the contact record everywhere it goes, and make it technically difficult to bypass rather than relying on everyone remembering the policy correctly every time.

FAQ wrap continued

"What should I do if I'm not sure whether a contact gave proper consent?" Do not text them. The downside of a missed opportunity is far smaller than the downside of a documented TCPA complaint, and when in doubt, a phone call or a mailer is a safer channel until consent is clearly established.