Yes. Active, pending, and sold statuses are read so the bot only suggests properties currently for sale unless asked otherwise. If a buyer asks "what about the house on Mariposa," the bot will note if it's gone pending or sold rather than continuing to offer it. This avoids the embarrassing case of a chatbot pitching a property that closed last week.

Yes. Neighborhood and city fields are part of context, enabling "show me homes in Cypress Park under $700k" style queries. If your Impress setup uses a neighborhood taxonomy, that works the same way — the bot scopes by term. Some sites also tag school districts or subdivisions, and those are filterable too as long as they're stored on the listing.

Yes. Pool, garage, basement, fireplace, central air, and any custom amenity field on the listing is readable. Boolean flags are interpreted naturally — a buyer asking "does it have a pool" gets a yes or no based on the actual flag value, and the bot doesn't have to guess from description text.

The bot collects the visitor's preferred time and contact info, then forwards the request to the listing agent's standard intake — typically the agent's email or whatever lead capture system you've wired up. It doesn't write directly to a third-party calendar by default, but if you have a tour-scheduling tool with a webhook, that can be connected through SleekAI's tool calls.

Yes. Open house times stored on the listing — usually as a date/time meta field or in a repeater of upcoming open houses — are surfaced when buyers ask about viewings. "When's the next open house at 1284 Mariposa" returns the actual scheduled time rather than a generic "please check our schedule."

Yes. Any meta field you add to the listing is readable, including bespoke fields like school district, flood zone, HOA name, lot premium, or seller financing options. The bot doesn't need to know the field exists in advance — it sees whatever is on the post object at request time.

Yes. When a buyer asks about a specific property and is interested but the price or location doesn't fit, the bot can pull similar listings — same neighborhood, similar price range, similar bed count — from the catalog and present them as alternatives. The matching is structural rather than tag-based, so the comparisons are usually meaningful.

Yes. HOA fee, HOA name, property tax estimate, and tax year are all readable if your Impress configuration stores them on the listing. The bot quotes whatever values are present and avoids inventing estimates if a field is empty. "What's the HOA on Mariposa" returns $42/month if that's the stored value, or "that field isn't filled in for this listing" if it isn't.