Sales Automation
AI Calls and Texts for Real Estate: A Pre-Send Consent and Opt-Out Checklist
A pre-send checklist for AI calls and texts in real estate: verify lead source, consent evidence, Do Not Call status, opt-outs, and the October 2026 FCC update.
By REN AI Editorial Team ·
A saved phone number is not a send-ready lead. Before an AI-assisted call or text, a real estate team should verify how the number was obtained, what communication was authorized, who will send it, what technology is used, and whether the person has opted out. If a material fact is missing, pause outreach and give a named human reviewer the decision.
What should a real estate team check before an AI-assisted call or text?
Match the contact's documented permission to the seller, number, purpose, channel, and calling or texting method. Check applicable Do Not Call restrictions, local-time rules, and every known opt-out before the message enters a queue. Allow only a clearly supported contact path; hold conflicting or incomplete records for human review, and suppress revoked contacts across the tools that can act on them.
Scope and date: Educational operational guidance checked October 4, 2026, not legal advice or a compliance certification. Federal requirements differ by call type, device, purpose, and relationship; state rules, brokerage policy, and provider terms may impose additional limits. A qualified communications or real-estate attorney should review campaign-specific decisions. The currently codified FCC rule and the newly released but future-effective FCC 26-67 order must not be treated as interchangeable.
First, classify the message and the technology
A person asking about a specific property, a past client, a purchased list entry, and an imported portal lead may have very different records and expectations. Label each proposed message by purpose (for example, marketing or a requested response), channel (voice or text), sender, and technical method. Do not assume that adding AI to a script makes every manual call a robocall, or that a manual-looking message escapes applicable rules.
| Proposed contact | Question before release | Conservative team action |
|---|---|---|
| Outbound AI-generated voice marketing call | Does the record support the applicable prior express written consent for this seller, number, and marketing method? | Hold until the proof, approved script, opt-out path, and attorney-reviewed campaign rules are documented. |
| Automated text to a former inquiry | What is the message purpose, how is it sent, what was authorized, and has consent been revoked? | Check the actual consent and applicable texting rules; do not treat an old inquiry as blanket permission. |
| Individually placed human follow-up call | Does a telemarketing or Do Not Call rule, local-hour restriction, opt-out, or brokerage policy still apply? | Keep human ownership and honor applicable restrictions even if no artificial voice is used. |
The FCC's February 2024 AI-voice ruling confirms that AI technology generating a human voice falls within its artificial/prerecorded-voice restrictions. The FCC's current rules separately define prior express written consent for specified telemarketing calls made with an autodialer or artificial/prerecorded voice. These are not blanket definitions of every AI-assisted text, inbound reply, or live human call.
What evidence belongs in a send-ready lead record?
A useful record can show why this contact may receive this specific message now. Preserve the source and time of capture, the seller and exact consent language where needed, the intended number and channel, the selected purpose and technology, prior conversations, opt-outs, and a named decision owner. These are operational evidence fields, not a claim that every field is mandated for every communication.
| Evidence | Review question | If missing or conflicting |
|---|---|---|
| Source and disclosure | Where, when, and on whose form or page was the number collected? What text did the person see? | Hold and locate the original evidence; a source tag alone is insufficient. |
| Permission match | Does the authorization, if required, cover the actual seller, number, message purpose, channel, and method? | Hold for qualified human/legal review, not AI inference. |
| Suppression and timing | Any opt-out, company-specific or National Do Not Call restriction, local-time issue, or provider block? | Stop or hold; update every affected queue and vendor. |
| Decision trail | Who approved the campaign rule and this exception, and what version of the message was used? | Keep the record out of automatic release pending review. |
For the broader problem of source fields, role permissions, and data quality, see the real estate CRM data-governance guide. An outreach eligibility decision should be traceable even if contacts move between a CRM, an AI caller, an SMS provider, and a human ISA.
Does an old CRM entry or purchased lead prove permission?
No. Storage is not consent. A prior property inquiry may establish relevant conversation context, but it does not document an unlimited right to use every future channel or calling method. A purchased lead can be especially difficult to assess if the original form, seller identity, and disclosure are unavailable. Put unsupported records on hold; do not use AI to invent permission. The database reactivation playbook covers segmentation after the permission gate.
Do not repeat a common outdated rule claim: the FCC's former one-to-one lead-generator consent restriction was vacated by the Eleventh Circuit in January 2025 and removed from FCC rules in July 2025. That ruling did not eliminate otherwise applicable prior express written consent, Do Not Call, revocation, state-law, or platform requirements. A missing disclosure remains a reason to review a lead, not a reason to assume the former rule is still in force.
How should opt-outs stop calls and texts across tools?
Treat a clear stop request as a stop signal, not a sentiment score. Pause the affected marketing activity on receipt, record the exact words, number, channel, time, and source, and make the decision visible to each approved caller, text sender, and vendor that can act on that contact. Route ambiguity to a person before any new outbound step. This immediate pause and cross-tool reconciliation are REN AI editorial recommendations, not assertions that REN AI automatically provides a compliance system.
As checked October 4, 47 CFR § 64.1200(a)(10)–(12) permits revocation of the covered consent by any reasonable means. It names standardized text replies such as “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” and “unsubscribe,” and also addresses understandable requests using other words. Covered revocations must be honored within a reasonable time, no later than ten business days. That is an outer limit for that rule, not a recommended wait before pausing a campaign. The FTC's Telemarketing Sales Rule guidance separately explains company-specific and National Do Not Call requirements and limits on covered outbound telemarketing calls; its scope does not automatically extend unchanged to every text or interaction.
What changed in the FCC's September 30, 2026 vote?
Adoption is not the same as effectiveness. In FCC 26-67, adopted September 30 and released October 1, the Commission adopted revised rules allowing properly disclosed designated opt-out methods and permitting a narrower interpretation of some revocations in response to informational messages. A revocation responding to a marketing message still bars future marketing messages from that caller under the adopted text. The order says its amendments become effective 30 days after Federal Register publication; the FCC will announce the specific date. As of this article's October 4 source check, do not treat those amendments as effective merely because the order has been released.
The January 2026 FCC waiver delayed only the broader all-category effect for a request responding to one kind of informational message until January 31, 2027. The newly adopted changes are set to supersede that delayed date when the amendments take effect. FCC 26-67 also asks questions in a Further Notice of Proposed Rulemaking; those questions are proposals, not current rules. Teams should monitor the Federal Register/FCC effective-date notice and obtain campaign-specific legal review before changing opt-out logic. A business may still choose to accept more stop methods as an operational preference.
Use a seven-step go, hold, or stop review
- Name the accountable seller and owner. Identify the brokerage/service on whose behalf the message is sent and the human who will handle exceptions.
- Classify the attempt. Record voice versus text, marketing versus requested service, AI-generated voice versus human voice, and any autodialer or automated send behavior requiring separate review.
- Open the original permission evidence. Compare the actual language, capture date, number, purpose, and sender with the proposed contact. Ask for counsel's interpretation where needed.
- Screen restrictions. Review all recorded opt-outs, applicable Do Not Call requirements, local calling time, state law, brokerage policy, and provider rules before release.
- Choose a disposition. Go only with a supported approved path; hold missing or contradictory evidence; stop an applicable opt-out or other prohibition.
- Test the exit path. Verify a stop request from a message reaches the responsible person and blocks any other approved system's pending sequence before scaling the campaign.
- Retain the decision. Save source evidence, campaign rule and script version, release time, reviewer, and any later revocation or correction without representing a software status as a legal conclusion.
Illustrative example, not a legal determination: A portal inquiry arrived last month, but the original form's disclosure is unavailable. The broker wants a prerecorded AI-voice marketing call followed by automated texts. The correct operational disposition is hold: ask a responsible person to recover and review the original permission, call method, seller identity, and suppression status. The CRM tag “inquired” cannot substitute for that evidence. If the person has since replied “please stop texting,” stop the affected text outreach and escalate the scope of any other outreach for review rather than resuming on a different tool.
Where does REN AI fit—and where does human responsibility remain?
The REN AI operating system describes connected lead, CRM, follow-up, and appointment workflows; REN AI Workforce describes configurable AI callers, texters, and follow-up agents. Use the pre-send gate above as a procurement and campaign-design conversation, not a claim that the platform independently verifies consent, scrubs Do Not Call lists, synchronizes every vendor, provides legal review, or certifies compliance. The AI ISA and human ISA comparison clarifies where an agent should take ownership. For an account-level look at the software and support, start a free REN AI account; review REN AI customer experiences separately from legal suitability.
Frequently asked questions
Does a lead saved in a real estate CRM automatically permit AI calls or texts?
No. A CRM record shows that a contact was stored, not what the person agreed to receive. Check the original source, the actual consent language, seller, number, channel, intended purpose, applicable technology, prior revocations, and other applicable restrictions. Put unresolved records on hold for human review; do not infer permission from lead age or an import tag.
Are AI-generated voice calls subject to the FCC's artificial-voice rules?
Yes. The FCC's February 2024 ruling says AI technologies that generate human voices fall within the TCPA restrictions for artificial or prerecorded voice calls. The required consent depends on the call's purpose and other circumstances; telemarketing with an artificial voice can require prior express written consent. Have counsel review the actual calling method and script before launch.
How quickly should a team stop outreach after an opt-out?
Pause the affected contact and campaign as soon as the request is received, then synchronize the suppression decision to every approved caller, texter, queue, and vendor. Immediate operational pause is a REN AI recommendation, not a claim about the legal deadline. The currently codified FCC rule for covered robocalls and robotexts requires honoring a valid revocation within a reasonable time, no later than ten business days; other rules may be stricter.
Did the FCC's September 2026 revocation changes already take effect?
Not merely because the FCC voted on September 30 and released FCC 26-67 on October 1, 2026. The order says the revised rules take effect 30 days after Federal Register publication, with a further FCC notice identifying the specific date. Check that notice and the current rule before changing legal settings; additional issues in the order are proposals, not adopted requirements.
Sources and methodology
Federal sources were checked October 4, 2026. The decision gate and immediate cross-tool pause are editorial workflow recommendations; legal conditions require a qualified reviewer and may change after this date. The principal sources are the currently codified FCC calling/texting rule, FCC AI-voice declaratory ruling, FCC 26-67 report and order/Further Notice (October 1, 2026), FCC January 2026 limited waiver, FTC Telemarketing Sales Rule business guidance, and the FCC order deleting the vacated one-to-one restriction. None of these sources determines the legality of a specific REN AI user's campaign.