A listing video can be beautifully edited and still show the wrong appliance. A buyer consultation can sound polished and still leave someone confused about what they're signing. An agent needs tools whose work can be checked against the property and the actual file.
a16z's seventh Top 100 Gen AI Consumer Apps report gives specialist creative tools their own place alongside the chatbots. Its spending list includes Descript and Otter; Gemini Notebook appears in its web and mobile lists. That makes a useful starting set for an agent: edited footage, recorded notes and questions tied to source documents.
The series hub explains the rankings and control choices, while the integration companion covers general app handoffs. Here, the question is what an agent could do with these tools around a listing, a buyer and a transaction. These are proposed workflows, not tested account integrations or customer results.
The rules come before the listing draft
Describe the property, not preferred residents. 42 U.S.C. 3604(c) prohibits dwelling sale or rental advertising indicating preferences, limitations or discrimination based on race, color, religion, sex, handicap, familial status or national origin. My working rule for AI drafts is to stick to verified property features. Review neighborhood descriptions for steering language too. Don't ask a model to describe the kind of people who would belong there.
Keep the original beside altered photographs. California's Business and Professions Code 10140.8, added by AB 723 and effective January 1, 2026, requires a reasonably conspicuous disclosure that the image has been altered, on or adjacent to the image, in covered for-sale advertising. The disclosure must explain that the originals are accessible through a public website link, URL or QR code, where the original is clearly identified. On a website the advertiser controls, the posting must also include the original or a public link clearly identifying it.
That section includes changes to furniture, fixtures, landscaping and views through windows. Ordinary lighting, sharpening, cropping and similar corrections are excluded only when they don't change the property's representation. A staging label doesn't make hiding a defect acceptable. Check your own MLS's published image rules before uploading; this article doesn't claim one nationwide MLS standard.
A generated voice doesn't remove calling restrictions. The FCC's February 2024 declaratory ruling places AI-generated human voices under the TCPA's artificial or prerecorded voice restrictions. Covered calls require prior express consent absent an emergency purpose or exemption; advertising or telemarketing calls require prior express written consent. This isn't a blanket ban on every AI voice use. It is a reason to keep an outbound prospecting bot out of this starter setup.
Ask before recording. State requirements vary. California Penal Code 632 requires all parties' consent to record a confidential communication within its scope. Otter's recording guidance discusses permission, notices and jurisdiction-specific review. A bot joining a meeting doesn't establish consent. Ask your broker or attorney what applies to your state and situation before recording a consultation or showing conversation.
Explain the buyer agreement before the tour. NAR's facts page says an MLS Participant working with a buyer must enter a written buyer agreement before touring, including in-person and live virtual tours, under the practice changes effective August 17, 2024. A consultation deck can explain the brokerage-approved form; it shouldn't invent contract language. The NAR ledger article already covers the settlement and commission background.
A familiar voice isn't payment verification. An IC3 advisory on AI-assisted fraud describes cloned audio used to obtain payments and recommends hanging up and independently contacting the organization. Applied to closing: verify wiring instructions through a previously verified number. Don't trust a changed number supplied in the same message or call.
A solo agent's week, with the files accounted for
Capture a narrow conversation
At a listing appointment, an agent could ask permission to record a short fixture walk-through in Otter: which refrigerator stays, which light fitting goes, which item needs confirmation. Keep seller motivation and negotiation talk outside that recording. If the conversation moves there, stop recording and make private notes in the brokerage's existing records.
Otter's export guide documents TXT exports on Basic and additional formats on paid plans. The agent manually downloads the text, compares it with their own observations and files the checked inclusion list in brokerage-controlled storage. The recording and transcript have already reached Otter. Downloading them doesn't undo that disclosure or delete the service copy.
After a buyer showing, the same narrow approach could capture questions about the home with permission. The useful output is an unresolved-question list, not an AI verdict about whether the buyer should offer. Pre-approval letters, account details, offer terms and private seller notes stay out.
Draft from approved facts
For a listing description, the agent could manually upload a deliberately prepared property fact sheet to Gemini Notebook. Google's source guide documents PDF, text and other source types. Its chat guide explains source citations that open the relevant passage. Ask it to assemble supported facts and flag missing support, then write and review the public description against those sources.
The uploaded sheet should contain only approved marketing facts. It isn't the full seller file. Confirm measurements, inclusions and dates in the authoritative records; a citation to a mistaken sheet repeats the mistake. The source copy reaches Google's service, and this workflow doesn't claim a connection to an MLS.
For a buyer consultation deck, the agent could use a notebook containing the brokerage's approved public explanation of its buyer agreement. Ask for questions a buyer might still have, verify each answer, then manually place the approved wording into the existing slide editor. The signed agreement stays in the transaction platform.
For a market update, use a dated report the brokerage has permission to reuse. Ask for a factual summary with source references, then check the reporting period and geography before publishing. Don't let the model turn a backward-looking report into a price forecast or neighborhood recommendation.
Publish the actual home
The agent could upload their own approved walk-through footage and narration to Descript, edit it and review captions against the spoken words. Descript documents local MP4 exports and separate SRT or VTT subtitle exports. Save the accepted video and captions beside the source footage. Manually upload the checked files to the existing publisher, checking which caption format it accepts.
Descript holds the uploaded footage and working project. Use an empty-home recording without clients, personal papers, security codes or private conversations. For photographs, keep the original set and any altered versions together through the brokerage's normal media review. Don't turn still images into invented rooms or erase a utility pole to make a tour more attractive.
A social clip should use the same approved facts as the listing. Check the final cropped view for lost disclosures and caption errors. The export is the handoff; no direct connection to every social platform, MLS or brokerage website is assumed.
Follow up from the CRM record
Follow Up Boss documents webhooks, including a newly created contact event, and a People API. An account owner could configure a webhook to an n8n receiver, then have n8n retrieve the allowed contact fields through an authenticated HTTP request. That HTTP request is the bridge; no native Follow Up Boss node is assumed.
Start with an internal review queue for the assigned agent. After the agent selects the right recipient and approved question, n8n's Gmail draft operation can prepare a message. The agent checks and sends it. No lead's free-text message becomes an instruction to a model or permission to send a reply.
For showing feedback, the agent could select a reviewed question list from the showing notes and manually start that draft step. For past-client touchpoints, the agent selects eligible contacts in the CRM and checks their communication preferences before preparing a home-anniversary draft. The CRM holds contact details, n8n processes selected fields, and Gmail receives the draft. No cloud model needs the buyer's budget or the seller's reason for moving.
Close with questions, not automatic decisions
An agent could upload an authorized, nonconfidential HOA rules document to a separate Gemini Notebook and ask where it discusses exterior changes. Open the cited passage and check the current original before passing a question to the appropriate professional. Don't upload the entire resale package merely because one public rule is relevant. Meeting minutes, owner details and financial attachments need a separate privacy decision.
Keep the transaction checklist in the brokerage's existing system. The agent manually records a checked question or confirmed milestone there; the notebook doesn't change a deadline, interpret title coverage or confirm that a contingency has been met. The condo article covers the ownership questions behind HOA documents without needing another investment discussion here.
Five agent setups worth separating
The listing-focused agent
Start with approved footage, manually upload it to Descript, correct the transcript and export an MP4 plus captions. The agent reviews the home shown in every cut, then manually publishes through the existing website or social editor. Keep a brokerage copy of originals and accepted outputs; Descript holds the editing copy.
Set up first: one actual walk-through to one checked captioned export. Add a property fact notebook only after the fixture list and public description agree. This makes the less glamorous inclusion check part of the media job.
The buyer's agent
Start with the brokerage's approved buyer-agreement explainer, manually add it as a Gemini Notebook source and ask for a list of questions the explanation leaves unanswered. Check the references, then manually paste accepted wording into the consultation deck. Review the actual agreement with the buyer before the covered tour. Nothing here signs or changes the agreement.
Set up first: the public explainer to a checked consultation question sheet. Keep purchasing capacity, negotiation strategy and signed forms in the existing buyer file. Useful assistance can begin before any client document leaves the brokerage.
The bilingual-market agent
Start with an approved public listing clip in Descript, generate translated captions, ask a fluent reviewer to check property terms and export the accepted subtitles. Descript's translation page documents the feature and subtitle exports; its plan comparison distinguishes translation and proofreading features. Check the chosen account's entitlement before building around it. No language-count or unlimited-use promise is needed.
Set up first: one reviewed clip to one checked second-language caption file. Manually publish it with the matching video. Preserve the original wording and the reviewer's corrections in brokerage storage. Keep contract translation and legal explanation with qualified people; a translated caption isn't a translated agreement.
The new-construction or land agent
Start with a builder-approved specification sheet or a public permit document you're entitled to use. Manually add it to Gemini Notebook, ask which statements support the proposed marketing claims, then inspect the cited passages. Copy unresolved questions into the brokerage's existing checklist by hand. Ask the builder or relevant authority to resolve them before publication.
Set up first: one approved specification sheet to a list of supported claims and open questions. Don't let a rendered picture establish what will be built, or let a permit summary establish buildability, utilities or legal access. Private pricing negotiations and buyer finances stay in the transaction records.
The small independent brokerage
Start with an owner-authorized Follow Up Boss event, verify its signature, receive it in n8n and retrieve only the needed fields. Put the resulting contact ID and assigned agent into an internal review queue. When that agent approves a factual note, n8n can use the documented Add a note API to file it against the selected contact.
Set up first: event to internal queue, with no customer message. The brokerage should hold the vendor accounts, integration credentials and approved source templates. Its approved-tool list should say who may upload recordings, who approves media and where accepted files live. n8n's host also holds processed data and execution records; restrict access and retained fields there.
The CRM and transaction layer needs its own boundary
Follow Up Boss says only the account owner can create, update or delete webhooks. Its authentication guide says API keys carry the user's privileges. An agent's credential isn't interchangeable with the broker's. Use the narrowest authorized access and keep keys out of prompts, exported notes and shared templates.
For the configured bridge, n8n documents a Webhook receiver and HTTP Request node. The receiving workflow must implement Follow Up Boss's documented signature verification before acting. Treat repeated event IDs as the same event and validate the selected contact before writing a note. A failed retry shouldn't attach showing feedback to another buyer.
The first transaction handoff can stay manual: the coordinator checks the signed document in the brokerage's transaction platform and updates the checklist there. This article doesn't assert a dotloop, SkySlope or DocuSign connector, and it assumes no MLS feed or IDX redistribution rights. The existing industry MCP guide covers connection choices and data-access limits.
Earlier posts cover agent inboxes and persistent assistant memory. Use those for the general setup. The addition here is a checked connection to the property file, with private transaction facts kept out of the creative tools.
Start with a file you can inspect
In week one, take an empty-home clip through editing, caption review and a local export. Keep the original and accepted version together. Don't publish until the factual wording, image treatment and disclosures pass the brokerage's review.
In month one, try the CRM event-to-review-queue chain with a test contact. Check the assigned agent, signature handling and repeated-event behavior before allowing it to write approved notes. Confirm someone at the brokerage can recover the files and disable the integration without an individual agent's personal account.
Don't record first and ask later. Don't let a caption invent an included appliance. Don't publish a staged photograph without checking the law and your MLS rules. Don't make a buyer agreement, a wire instruction or a contract deadline depend on an unchecked model answer.
Related reading
- The a16z series hub and control choices.
- General app connections for solo owners and small businesses.
- NAR's finances and the commission background.
- The other trade companions: mortgage brokers, insurance agents and financial planners.
Fact-check notes and sources
Reviewed October 16, 2026. Features below are documented capabilities, not measured business outcomes. No prices, savings estimates or automatic legal judgments are claimed.
- Starting list: a16z seventh edition. The selected applications appear in its lists; the workflows are my proposals.
- Advertising and recordings: 42 U.S.C. 3604(c), California image-alteration law, California confidential communications statute and FCC AI-voice ruling. No HUD guidance or specific MLS image rule is relied on.
- Buyer agreements and fraud: NAR's written agreement facts, its settlement FAQ page, IC3 on AI-assisted fraud and IC3 on business email compromise.
- Otter: recording permissions and exports and plan restrictions.
- Gemini Notebook: supported sources and copies and source citations in chat. Google's current help uses Gemini Notebook; some report text also uses the earlier NotebookLM name.
- Descript: local video exports, subtitle exports, translation and plan comparison. Export quality and translation access need checking for the account used.
- CRM: Follow Up Boss webhooks and signature verification, contact retrieval, adding notes and authentication and privileges.
- Additional transaction review: Docusign Connect documentation was reviewed; the proposed transaction-platform handoff here stays manual.
- Workflow bridge: n8n Webhook, HTTP Request and Gmail draft operations.
This post is informational, not legal or investment advice. Ask your broker or attorney about your state and transaction. Product names identify the tools discussed; no affiliation is implied.
