Yes. Each listing is a custom post with postmeta fields for WiFi password, lockbox code, and parking instructions. The bot reads the listing post on every request based on the page URL or the reservation tied to the guest's login. A guest at Pine Hollow gets the cabin's WiFi, Harbor Loft gets the loft's garage code.

The bot reads the reservation post and looks at the next reservation on the same listing. If the cleaning window between current checkout and the next checkin is wider than the cleaner's turnaround, late checkout is offered with a price. If the window is tight, the bot explains the constraint and routes to the assigned manager.

Yes. Each market has a document in an OpenAI Files vector store covering registration requirements, occupancy tax rates, and noise ordinance hours. The bot reads the city tag on the listing to surface the right rule. The output is informational rather than legal advice but covers the common compliance questions an owner or guest has.

Display conditions in SleekAI Multibot scope each bot by URL pattern, post type, and logged in role. The public listing page runs a pre booking bot. The guest guidebook URL runs a reservation aware bot. The /owners/ portal runs a bot for payouts. The internal staff dashboard runs a fourth bot for operational alerts.

Amenities are stored as taxonomy terms or postmeta on each listing. The bot reads pet policy, hot tub instructions, pool hours, and accessibility features per property. When a guest asks whether a cabin allows dogs, the bot quotes the pet fee, the weight limit, and the dog count from that listing rather than a portfolio wide answer.

All conversation logs stay inside your WordPress database. The data path is browser to WordPress to your OpenAI or Anthropic key directly, with no Sleek server in between. For STR managers operating in markets like California, New York, and the European Union, that direct path matters for guest data handling. Retention is configurable in WordPress admin.

Yes. Most after hours messages are WiFi, lockbox, or parking related, and the bot answers those from postmeta without waking anyone. The bot escalates to the on call rotation only when the guest asks about a tripped breaker, a stuck lock, or an emergency. Routing rules are configurable per market and per role.

Most PMS chatbots read your help center, not your listing data. They cannot scope to a specific reservation because they are not authenticated against the same user table that owns your guidebooks. SleekAI installs in WordPress, reads the listing post type natively, and authenticates against your WordPress users so guidebook scoping needs no separate login.