If your WordPress site is the source of truth for listings, the bot reads each post directly. If listings come from LoopNet, Crexi, or CoStar feeds, the bot reads whatever you mirror to WordPress, so freshness depends on your feed sync. Most retail brokerages publish a curated subset of their availabilities to WordPress for marketing, and that subset is what the chatbot answers from. Internal-only deals stored outside WordPress stay private to the brokerage.

SleekAI only reads fields you mark as public on the listing post. Confidential financials, asking-price-on-request deals, and internal commission splits stored in private custom fields stay invisible to the bot. For deals where the broker prefers to hold pricing back until a tenant qualifies, the bot can route the visitor through a qualification flow before disclosing rent ranges, with the threshold configurable per listing.

Yes, as long as the data is published on the listing or market page. If you store ADT or VPD counts, three- and five-mile demographics, daytime population, and household income on each site, the bot reads those fields and ranks sites by tenant-stated thresholds. The bot does not pull from third-party services like Placer.ai or ESRI unless you have already imported and stored that data on the WordPress post.

Yes. Multibot lets you scope each chatbot to a submarket, a broker team, or a specific property type. A retail team in Atlanta can run a chatbot separate from the Charlotte team, each routing to its own broker pool. Display conditions tied to URL or page template let the right bot appear on the right listing pages without manual configuration per page.

If you publish the rent roll, anchor tenants, and exclusive use clauses on the listing page, the bot quotes them. For sensitive details that only specific tenants should see, the bot can be told to hold them back until qualification completes. Use clauses, kick-out provisions, and right-of-first-refusal terms are typical published items the bot answers about confidently.

Yes. Pad sites, hard corners, ground leases, and build-to-suit opportunities all read as listing posts with their own field sets, including pad dimensions, utility status, entitlements, and delivery condition. The bot distinguishes shell, vanilla box, and turnkey delivery and quotes the tenant improvement allowance when it is published on the listing.

Yes. Each listing post has an assigned broker field. When a tour or LOI request reaches that point in conversation, the bot captures the tenant's concept, credit profile, target opening, and contact details, then triggers a webhook or email to the listing broker with the full chat transcript attached. Brokers receive context-rich leads instead of one-line emails.

No. SleekAI uses your own OpenAI, Anthropic, Google, or OpenRouter API key, and standard API terms exclude conversation data from model training. For brokerages handling sensitive lease negotiations, this keeps tenant interest, qualification, and deal flow private to your account. OpenAI's enterprise terms tighten that further if required by a parent firm or franchise group.