California AI Meeting Notes Consent: A Brokerage Workflow
A California brokerage workflow for AI meeting notes consent: check capture settings, document agreement, and control transcript sharing and retention.
A clearer view of housing.
Real estate AI callback consent depends on purpose and provable permission. Check lead forms, vendor handoffs, opt-outs, and recording requirements.
Submitting a telephone number or requesting property details does not automatically authorize an AI marketing call. Real estate AI callback consent depends on what the consumer agreed to and what the brokerage plans to say. A lead form can establish permission, but its contents matter.
The FCC’s published rules generally require prior express written consent for artificial-voice marketing calls to cellphones and residential lines. Court decisions qualify that framework, as explained below. For a national brokerage adopting AI and automation, documented written permission is a prudent operating standard for outbound marketing calls. 47 CFR § 64.1200
The FCC’s AI-voice ruling, released and effective February 8, 2024, confirms that AI-generated human voices fall within the Telephone Consumer Protection Act’s artificial-voice restrictions. A conversation generated in real time can qualify; it need not play a prerecorded script. Artificial voice is an independent trigger, so a vendor’s assurance that its system does not use an autodialer does not resolve the consent question. FCC 24-17
An inbound AI receptionist answers a call the consumer initiated. A later callback is a new outbound call requiring its own assessment. For nonmarketing artificial-voice calls to cellphones, the FCC framework generally requires prior express consent, which need not be written. Residential nonmarketing exemptions have separate conditions, including call limits and opt-out duties. FCC delivery restrictions
Classify the proposed conversation by its purpose and permitted content. As a hypothetical distinction, confirming an already arranged appointment without promotion presents a different question from a bot recommending listings and pitching representation. Calling the latter a “courtesy callback” does not change its purpose.
For an informational workflow, define what the AI may say and when it must stop or transfer the conversation. If its instructions include selling brokerage services, evaluate it as marketing before launch.
Under the FCC’s written-consent framework, the agreement must contain a clear disclosure, the consumer’s signature, authorization for the relevant marketing calls and technology, and the designated telephone number. It must also disclose that signing is not a condition of purchasing property, goods, or services. Electronic signatures can qualify under applicable law. FCC consent requirements, paragraphs 32–34
Review the complete submission experience. A checkbox labeled “Contact me” does not establish those elements on its own. Neither does a CRM field saying “TCPA consent: yes.” Identify the business whose calls the consumer authorized and determine whether that authorization covers the brokerage’s proposed campaign.
Apply the same review to a third-party form. Request the disclosure and business identification displayed when this particular consumer submitted it. A vendor’s current demonstration form cannot establish what an earlier lead saw.
On January 24, 2025, the Eleventh Circuit vacated the FCC’s added requirements for consent to one seller at a time and for calls to be logically and topically associated with the interaction prompting consent. The court expressly said the older, 2012 written-consent rule was not before it. The decision did not approve every purchased lead. Insurance Marketing Coalition v. FCC
A separate decision qualifies the framework in 2026. In Bradford v. Sovereign Pest Control, decided February 25, 2026, the Fifth Circuit held that express consent could be oral or written for the prerecorded calls at issue, whether informational or telemarketing. Its finding of consent involved an existing service agreement, the customer’s statements, and subsequent dealings. Bradford opinion
The Fifth Circuit covers federal district courts in Louisiana, Mississippi, and Texas. Its decision should not be treated as nationwide approval to call any submitted number. Before launch, have qualified counsel review campaign jurisdiction, consent language, applicable FTC and state requirements, and recording practices.
The FCC’s consent order places the burden of demonstrating disclosure and unambiguous consent on the seller. FCC 12-21, paragraph 33 The handoff from lead source to CRM to calling vendor should therefore preserve retrievable evidence for each number.
The table below is a recommended operating record. It includes evidence of the agreement’s required contents and supporting audit information; the FCC consent definition does not prescribe this database design.
| Record to retrieve | What it establishes or helps verify |
|---|---|
| Exact disclosure and form version | The permission requested, covered technology, and purchase-condition disclosure |
| Authorized business identity | Whether the brokerage’s campaign falls within the permission given |
| Consumer’s signature or electronic signing event | The act of agreement tied to the disclosure presented |
| Telephone number in the agreement | The number the consumer authorized |
| Timestamp, time zone, source URL, and submission identifier | When and where the event occurred, and which records belong together |
| Original inquiry and campaign instructions | Whether the proposed conversation fits the permission’s scope |
| Revocations, do-not-call status, and delivery acknowledgments | Whether later instructions reached every system acting for the brokerage |
Timestamps, preserved page captures, and submission identifiers support the record; they cannot substitute for valid consent. A lead supplier’s certificate should let staff retrieve the underlying evidence rather than merely repeat a compliance label.
Test the handoff with one sample lead. Operations should be able to retrieve its agreement from the source, match it to the CRM record, and identify the campaign the calling vendor would run. Include those artifacts in the brokerage’s CRM export requirements, so changing vendors does not strand the evidence.
For old leads, review the original authorization, any later withdrawal, and whether the number still belongs to the intended recipient. Importing an old contact into a new system supplies no new evidence of permission.
Consent is only one launch requirement. Resolve do-not-call status and calling hours, and test the required caller identification and opt-out functions. For artificial-voice marketing messages, the rules require an automated voice or keypress opt-out mechanism. Using it must record the number on the do-not-call list and terminate the call immediately. Voicemail delivery has additional callback opt-out requirements. Artificial-voice message requirements
The FCC’s 2024 revocation rules recognize reasonable methods of withdrawing consent and generally require requests to be honored within a reasonable time, no longer than ten business days. That outer limit is not a reason to keep a campaign running after a clear stop request. Revocation rule
The relevant revocation provisions generally became effective April 11, 2025. A later waiver postponed the specific requirement extending an opt-out from one informational category to unrelated matters. Under an FCC order effective November 25, 2026, callers may limit that opt-out to its own category. Neither change narrows the reach of a marketing stop request, which still covers all of the caller’s marketing calls and texts. Effective-date notice, DA 26-12, FCC 26-67
As an operating practice, record the request immediately and suppress pending marketing activity across the CRM, AI calling vendor, texting platform, retry queues, and agent tasks acting for the same brokerage. Preserve the request’s wording and receipt time. Require acknowledgment from connected systems, and prevent a later lead import from silently restoring campaign eligibility.
Test a withdrawal while a callback is queued. The test succeeds when the queued call is canceled, the request remains retrievable, and another import cannot restart it.
The FCC proposed additional AI disclosures in FCC 24-84, released August 8, 2024, and published in the Federal Register September 10. The proposals would address disclosure when obtaining consent and at the start of an AI-generated call. They should not be described as final requirements: the FCC’s 2026 regulatory agenda lists the proceeding as a long-term action with its next action undetermined. Published proposal, FCC regulatory agenda
Plainly identifying the AI remains a sensible transparency practice. It cannot repair missing permission for an outbound marketing call, and the status of the federal proposal does not settle state disclosure obligations.
Permission to receive a call does not establish permission to record it. California illustrates the distinction: its Supreme Court held that Penal Code section 632.7’s consent requirement for recording covered cellular or cordless telephone communications applies to participants as well as outsiders. Smith v. LoanMe
Ask the vendor whether it stores audio, produces transcripts, sends speech to another processor, or retains material for model training. Evaluate those functions separately, including when processing begins and what happens if a participant declines. The California recording and transcription workflow develops that distinct review.
Before launch, the team responsible for brokerage operations should be able to retrieve the authorization for a selected number, explain why it covers the proposed conversation, and demonstrate that a withdrawal stops the queued call. If any check fails, keep that lead out of the AI marketing campaign until the gap is resolved.
Possibly, but the form submission alone does not establish permission for an AI marketing call. Examine the disclosure, agreement, authorized business, telephone number, and intended conversation under the applicable rules and court decisions.
A callback is an outbound call even if the consumer first contacted an inbound receptionist. Evaluate its purpose and authorization separately; an informational callback and a marketing campaign can require different consent.
Do not enroll old contacts solely because they remain in the CRM. Retrieve the original authorization, check its scope and any withdrawal, and verify that the intended recipient still uses the number.
The Eleventh Circuit’s 2025 decision did not decide the older written-consent rule. The Fifth Circuit’s 2026 Bradford decision accepted oral or written express consent for the prerecorded calls before it. That is a jurisdictional qualification, not nationwide permission to call any lead.
Do not assume it does. Recording, transcription, and third-party processing need a separate review of the applicable law and the vendor’s actual handling of the conversation.
Written by
The Housing Current Editorial Team
Editorial Team
Reporting, analysis, and practical explainers across housing markets, mortgage finance, real estate business, investing, policy, and homebuilding.
A California brokerage workflow for AI meeting notes consent: check capture settings, document agreement, and control transcript sharing and retention.
Use real estate AI regression testing to compare transaction summaries and deadlines, score errors, and decide when to pause or roll back an update.
Real estate AI prompt injection can trigger unwanted actions. Check assistant permissions, approval controls, audit logs and vendor testing evidence.