SleekAI reads whatever your WordPress site exposes. If your PMS pushes calendar availability, rates, and listing detail into WordPress (via plugin sync, iCal feed mirrored to post meta, or a custom integration), the bot reads those fields and quotes them. For live calendar checks, the bot can deep-link to the property's PMS-powered booking widget so the actual availability lookup happens server-side, with the result rendered to the guest in-conversation.

Yes, if your seasonal rates are published. Most STR sites store base nightly rate and seasonal multipliers as named fields or in a rate-by-month repeater. The bot reads the rate for the dates the guest mentions and quotes the stay total accordingly. For dynamic-pricing systems (PriceLabs, Beyond, Wheelhouse) that push daily rates into WordPress, the bot reads the same fields the PMS reads, so the guest gets the actual asking rate at the time of conversation.

The bot surfaces house rules in the pre-booking conversation rather than enforcing them at booking time. A guest asking about hosting a wedding party at a no-events cabin gets a clear no, plus a list of properties that do allow small events. A guest with two large dogs asking about a one-small-dog property gets routed to the dog-friendly options instead. Reducing house-rule violations starts with surfacing the rules clearly upfront.

Yes. Multibot lets you run a separate chatbot per destination (Smokies cabins, Gulf Coast beach houses, Mountain ski rentals). Each chatbot can have its own greeting, property scope, and local recommendations. Display conditions tied to the property's destination taxonomy ensure the right bot loads on the right listing pages. For multi-region brands, this prevents the bot from suggesting a beach house when the guest is looking at mountain cabins.

The bot's purpose is to keep guests on your direct-booking funnel where you avoid Airbnb's 14 to 16 percent service fee. It quotes your direct-booking nightly rate, fees, and total, links to your own booking widget, and frames direct booking as the price-advantaged option. The bot does not link to your Airbnb listing unless you explicitly add that route, since the goal is to capture the booking on your platform.

Yes. If a guest writes in French, German, Spanish, or any other language the model supports, the bot replies in that language. This matters for European, Latin American, and Asian guests booking US or coastal properties. Property names, amenity names, and policy text stay in their published language so guests can match the spoken or chatted answer to the listing page they are looking at.

Damage hold amount, refund timing, and security deposit policy read from listing fields and the bot quotes them when guests ask. For properties that use a damage-waiver fee instead of a refundable hold (typical for cabin rentals through SuperHog, Safely, or Waivo), the bot quotes the waiver fee and explains the trade-off clearly so guests know what they are agreeing to at checkout.

Yes. SleekAI uses your own API key with OpenAI, Anthropic, Google, or OpenRouter, and standard API terms exclude conversation data from model training. For property managers handling guest details, special requests, and accessibility needs, this keeps guest information inside your WordPress install. Conversation logs stay in your database, viewable in WP admin with model name, token use, and page URL, useful for training new front-desk staff on common questions.