When a large company buys an AI tool, procurement and counsel run diligence before a contract is drafted: what data the tool touches, what the model is built on, who the subcontractors are, what happens when versions change. Regulators are moving the same direction; Colorado's new automated-decision law requires developers of covered AI to document intended use, limitations, and monitoring. And as William Galkin, an attorney focused on AI agreements, puts it: with AI tools, "the most important work often begins before the first draft is exchanged."
A solo agent doesn't have a procurement department. But when the AI in question answers your phone, in your name, to your clients, you are the procurement department. This guide compresses that diligence into eight questions you can ask any AI voice vendor in one email, plus what a good answer looks like.
The eight questions
1. Does it declare itself as an AI?
Not every state requires this yet, but the direction is set: Utah's AI Policy Act (SB 226, 2025) already requires disclosing generative AI when a person clearly asks, and requires regulated-occupation providers to disclose it proactively in higher-risk interactions. Beyond the law, there is the trust math: callers are primed for phone suspicion for good reason. The FBI's Internet Crime Complaint Center logged $275 million in real-estate-related fraud losses in 2025 (fraud generally, not AI voice specifically), and voice phishing accounted for over 60% of the phishing-related incident-response engagements Cisco Talos worked in Q1 2025. An AI that opens by saying what it is removes the question. A vendor whose assistant cannot be configured to disclose has made a choice about whose risk that is.
2. What data does it take, and what happens to it?
Be specific about what the vendor receives. For a voice assistant that means: are calls recorded? Transcribed? Retained how long? Used to train models? Treated as the vendor's asset or yours? Policies vary widely, and some say nothing at all about recording or retention. Silence in a privacy policy is an answer.
The industry itself is drawing this line now. MLS rulebooks are adding AI-specific rules market by market, and the strictest of them already prohibit members from uploading listing data into any AI tool that lacks a written zero-training guarantee, free consumer chatbot tiers included. Notice who carries that kind of rule: the member, meaning the agent.
The details tend to be narrower than the headlines suggest, and the shape is consistent from market to market: the restrictions bite hardest on sharing another broker's listing content, and the right to use listing content freely generally belongs to the listing brokerage rather than to the individual agent. So the practical line worth remembering has two parts. A listing you have the authority to share, meaning your own with your brokerage behind it, or someone else's with written permission, going into a tool that does not train on it: that is the safe path. A listing beyond your authority, going into any AI tool: that is the one that needs permission first.
Rules like this are arriving MLS by MLS rather than all at once, so read your own before you assume it matches. Either way you will want your AI vendor's zero-training guarantee in writing, covering both what your callers say and what you upload. Ask for it now; a vendor who already operates that way will hand it over without a meeting.
3. Does the vendor's policy allow matching, sharing, or training on your contacts?
The quiet clause lives in the CRM stack as often as the AI stack. When Zillow-owned Follow Up Boss updated its privacy notice in November 2025, contacts in an agent's CRM who also hold a Zillow account became "Mutual Customers," and their data became subject to Zillow's own privacy notice as well, shareable with Zillow affiliates. You don't choose which of your contacts that covers; a Zillow account on the other end of the deal is enough. Whatever you think of any one vendor, the mechanic is the thing to vet: another company's business model deciding what happens to a book you built call by call. So ask every system that holds your contacts, in writing: does your policy allow my contacts to be matched to another company's records, shared with affiliates or partners, or used to train models? A no should be easy to give. An answer that needs a diagram is a no with extra steps.
4. How long does it keep your clients' data, and who benefits from the keeping?
"We don't train on your data" is a vendor's first answer, not a clean bill. A vendor that never trains can still hold your clients' conversations indefinitely, so ask the follow-up: how long do you keep it, and why? A good answer has three parts: a purpose, a clock, and an owner. Retention that exists to serve you and your clients, with a stated window and an automatic end, passes the test; the law requires some of it, and that kind of keeping protects everyone. Retention with no clock, justified by the vendor's own analytics, partners, or future products, fails it. And silence about retention, like silence about recording, is an answer.
5. Who reviews what the AI says for fair-housing compliance?
The question that is unique to real estate, and the one most vendors hope you skip. Read any vendor's AI-disclosure page with one question in mind: who does it say is responsible for reviewing the AI's output? Ask directly, get the answer in writing, and read the full treatment in our companion guide, The Practitioner's Guide to AI and Fair Housing Compliance.
6. Does it use your cloned voice or a distinct assistant voice?
Cloning your voice and likeness is now pitched to real estate as a routine feature. Avatar-video platforms court agents on conference stages with tools that turn a short recording of you into endless content, and voice platforms market cloned-voice phone agents directly to real estate agents. The word "clone" rarely appears on the pricing page; the capability is the product. Two separate risks follow. Legally: the FCC ruled in February 2024 that AI-generated voices fall under the TCPA's artificial-voice rules for calls the AI initiates, so if your assistant ever places outbound calls, such as callbacks or reminders, consent and identification requirements can apply, and a voice presenting as you personally raises the stakes of getting that wrong. Practically: a caller who later learns "you" were software feels deceived in a way no fine print repairs. A distinct, disclosed persona avoids the impersonation question entirely. It is a design answer, not a legal cure-all.
7. Who else is in the pipeline?
Voice AI runs on a supply chain: a telephony carrier, a model provider, hosting, sometimes annotation or QA vendors. Third-party and supply-chain risk is a standing concern of security diligence, called out in NIST's AI Risk Management Framework, and every link in the chain is a place your callers' words may be processed or retained, depending on architecture and contract. So ask for the chain, and ask for it in a form you can hold them to. A list on a marketing page tells you who, not what they may do, and it can change the week after you read it. What protects you is the written agreement: which providers touch the data, what each one is permitted to do with it, and how you're told when that changes. Ask to see it before you commit, not after. A vendor who will put it in the contract is offering you something a web page cannot, and a vendor who won't put it in writing at all has answered you.
8. Does it screen its own generated copy for fair-housing language?
If the tool writes anything in your name, listing descriptions, ads, or follow-up texts, either it screens its own output for fair-housing language or that screening lands on your desk at 11pm. Agents in real-estate tech communities have flagged AI-drafted listing copy slipping in language a compliance review would catch. Ask where the screen lives.
Turning answers into terms
Diligence only matters if it changes the deal; that is the heart of Galkin's pre-contract framework, and it applies at every scale. For an agent, the vendor's written answers are your evidence, so keep the thread: no recordings, no training, disclosed AI, a named subcontractor chain. Then get the ones that matter into the actual paperwork, whether that is the order form, the terms, or a data-processing addendum, because a contract's fine print can override a helpful email. A vendor who answers cheerfully by email but won't reflect it in the document is telling you which one they intend to honor. And a refusal to answer in writing at all is a risk signal you are allowed to act on.
The regulatory direction backs you up. Colorado's SB 26-189 (effective January 2027, explicitly covering residential real estate) requires developers of covered AI to document intended use, limitations, training-data categories, and monitoring, and to notify deployers of material updates. A vendor who cannot answer your eight questions today will struggle to answer a regulator's tomorrow.
Which raises the version question: AI products change under the hood, and an assistant that handled fair-housing questions carefully in the demo may behave differently after a model update. Ask how the vendor tests updates against their compliance constraints before rollout, and whether you get notified when behavior materially changes.
How we answer our own questions
Rocalyn Edge publishes its answers: AI disclosure on every call, no recordings, no training on your conversations, a distinct configured persona rather than voice cloning, and fair-housing constraints in the product with compliance grading behind it. The details live on the trust page, and the live demo will disclose itself in the first breath. Hold us to the same eight questions; hold everyone to them.