Yes. Any meta field, ACF group, Meta Box field, or custom taxonomy attached to a property is readable by the bot. Whether you've added flood zone, school district, walk score, or rental history, those fields flow into context the same way as the standard ones, with no extra config.

Yes. For sale, sold, pending, off-market, and any custom statuses are all part of context, and the bot only suggests active listings unless asked otherwise. If a buyer asks "is 88 Pine Tower still on the market", the answer reflects whatever the status field currently says — including pending if the listing went under contract recently.

If you store estimated payment or mortgage info on the listing, the bot quotes it. It will not invent rates or estimates. So a listing with a populated estimated_payment field gets that figure surfaced; a listing without it gets a polite "that estimate isn't available for this property, but the listing agent can run real numbers for you."

Yes. When no specific listing is mentioned, the bot can suggest the agent specializing in the requested neighborhood or property type. Agent profile posts typically store specialty meta — neighborhoods, property types, languages spoken — and the bot uses that to route accordingly. So a buyer asking about Spanish-speaking agents in Cypress Park gets matched specifically.

Yes. Agent profiles with their listings are linked, so each conversation routes to the correct person. The agent's name, photo, phone, email, and bio are surfaced when the buyer asks about a specific listing, and the tour request goes to that agent's intake. Brokerage offices don't need a central triage step.

Yes. SleekAI responds in the visitor's language using the same listing data underneath, so a Spanish-speaking buyer can browse a primarily English site in Spanish without losing precision. Listing details — prices, square footage, addresses — stay in their stored format, while the conversation around them adapts to the buyer's language.

Yes. When a registered user is logged in, their saved searches, favorited listings, and past inquiries can flow into context, so the bot picks up where the buyer left off. "Any new listings matching what I saved" returns properties that match the saved-search criteria and were added since their last visit.

By default the bot collects the request and forwards it to the listing agent's intake. If your brokerage uses a tour-scheduling tool with a webhook or API — Calendly, ShowingTime, etc. — that can be wired up through SleekAI's tool calls so the bot writes the booking directly. The default behavior keeps things simple; the upgrade path is straightforward.