A buyer sees your sign rider on 412 Maple, texts the number to ask about square footage, and you reply. Perfect. You've got an inbound text, a real question, a live lead. Three weeks later that same person is getting your Tuesday "5 new listings in Oakwood Estates" blast, your open-house reminders, and a "just reduced!" ping about a house they never asked about.
That last part is where agents get themselves into trouble. The contact consented to talk about one property. They did not consent to your farm-area marketing program. Those are two different things, and carriers and plaintiff's attorneys both treat them as two different things.
Full disclosure: I work for Ready, an SMS platform. We handle opt-out and consent tracking, so I have a horse in this race. But the scope problem I'm describing is real regardless of what tool you use, and I'd rather you understand it than learn it from a demand letter.
Consent has a shape, and that shape is set by the opt-in
The word "consent" makes it sound binary — either you have it or you don't. In practice it's bounded. Express consent covers the purpose the contact agreed to, and nothing wider.
When someone texts you about 412 Maple, the reasonable scope of what they agreed to is: a conversation about 412 Maple. Maybe, generously, about their home search if the exchange makes that clear. It is not:
- Recurring marketing blasts about unrelated inventory
- Automated drips promoting your listings, your team, or your open houses
- A subscription to your neighborhood newsletter
The FCC and TCPA case law draw a hard line between transactional/relationship messaging (answering the question they asked) and marketing (promoting things they didn't ask about). A single inbound inquiry lands you firmly on the first side of that line. Dropping the same lead into a recurring promotional drip crosses to the second — without a new opt-in that actually says so.
I wrote about the mechanics of that split in more detail here: one-to-one follow-up and marketing blasts live under different consent rules. This post is about the scope version of the same mistake — same lead, but you widened the topic instead of the message type.
Why "they contacted me first" doesn't save you
The most common defense I hear is: "They texted me. How can I be in trouble for texting back?"
You're not. Texting back about the thing they asked is fine. The problem is the second program you enrolled them in. Prior express written consent for marketing has to be:
- Clear and conspicuous — the person can see what they're agreeing to.
- Specific to marketing — not buried inside "I'd like info on this house."
- Not required as a condition of getting the answer they wanted.
An inbound inquiry about one listing meets none of those for marketing purposes. It's a warm lead, not a subscriber. The distinction matters because TCPA statutory damages run $500 to $1,500 per text — and a real-estate drip that fires eight to twelve messages over a few weeks turns one annoyed lead into five figures of exposure fast.
If your lead sources include skip-traced or purchased numbers on top of this, the exposure compounds. That's a different (and worse) problem, covered in one cold text to a skip-traced number can cost $500 to $1,500.
The complaint spiral, and why it hits deliverability too
Set aside lawsuits for a second. Scope creep hurts you at the carrier level before any attorney gets involved.
Someone who asked about 412 Maple and starts getting Oakwood Estates promos does one of two things: replies STOP, or reports the message as spam. Both are logged. Carriers watch spam-complaint rates and opt-out rates per campaign, and a 10DLC campaign that spikes on either gets throttled or filtered. Your legitimate texts — including the ones to leads who do want them — start silently not arriving.
So the person you annoyed by over-messaging also degrades delivery for the whole list. Scope discipline isn't just legal hygiene; it protects the channel you paid to register.
How to legitimately broaden the scope
You can absolutely turn a single-listing inquiry into a subscriber. You just have to ask, and record the ask. Here's the clean pattern:
Step 1 — Answer the question. They asked about 412 Maple, you tell them about 412 Maple. This needs no marketing consent.
Step 2 — Offer the upgrade explicitly. Something like:
"Happy to help with Maple. Want me to text you new listings in the Oakwood area as they hit? Reply YES to get 2–4 alerts a week. Msg&data rates may apply, reply STOP anytime."
Step 3 — Only enroll them in the drip if they reply YES. That reply is your new, wider consent — and it's dated, logged, and specific to the marketing program.
This is the same "one-tap upgrade" logic ecommerce brands use to turn an order-status text into a promo subscriber. The mechanics translate directly to real estate: the one-tap upgrade that converts transactional contacts legally walks through it.
Notice what you get for that extra step. The lead who typed YES is genuinely interested in the area. Your open rates go up, your complaint rate goes down, and your consent record is airtight. Double opt-in isn't just a legal nicety — it's a deliverability advantage at the carrier level.
What "logged consent" actually needs to contain
If you ever have to defend a send, "I'm pretty sure they said yes" is worthless. You want a record with:
- The phone number and the exact opt-in language shown
- The timestamp and the contact's affirmative response
- The scope — what program/topic they agreed to (single listing vs. area alerts)
- A trail showing STOP was honored the moment it arrived
This is where the platform earns its keep. Ready records opt-in attestation on bulk and API sends, honors inbound STOP automatically, and propagates that opt-out across campaigns — so a contact who quits your Oakwood alerts can't get accidentally re-added by a different workflow later. Quiet-hours enforcement holds sends outside permitted local hours based on the recipient's area, which matters when your farm spans a timezone line.
None of that makes you lawsuit-proof. Consent is ultimately the sender's responsibility, and no software decides on your behalf whether a given YES actually covered a given message. What the tooling does is make the right behavior the default and give you the audit trail when someone asks.
A quick scope-check before you hit send
Run any real-estate send through this before it goes out:
| Question | If the answer is "no"… |
|---|---|
| Did this contact opt in to this topic, not just contact me once? | Don't send marketing — reply to their original question only. |
| Was the opt-in specific to marketing, not buried in a listing inquiry? | Send an upgrade offer, wait for YES. |
| Is my message about what they agreed to, or wider inventory? | Narrow it, or get broader consent first. |
| Would this arrive during the recipient's quiet hours? | Schedule it; let quiet-hours enforcement hold it. |
| If they reply STOP, does it stop everywhere? | Fix your opt-out handling before you scale sends. |
If every answer is yes, send. If any is no, you've found the gap before a carrier or a lawyer did.
The practical takeaway
One inbound text about one house is exactly that: consent to talk about one house. Your farm-area drip is a separate program that needs its own, explicit, logged opt-in. The good news is the fix costs you a single message — an offer to send area alerts, and the discipline to only enroll people who say yes. You lose a few names off the top of the funnel and gain a list that opens your texts and doesn't report them.
If you want to see how the consent logging, automatic STOP propagation, and quiet-hours pieces fit together, that's most of what Ready's SMS product does — start with the free 2,500 credits and no card required at app.tryready.com/signup. And if you're still drawing the line between one-to-one replies and blasts, read the drip-vs-blast consent breakdown first — it's the foundation this post builds on.