Yes. Each pad records its max length, slide clearance, and pull-through vs back-in classification. A 41-foot Class A with two slides asking for a pull-through gets the four or five pads that genuinely accommodate the rig, not every pad in the park. The clearance numbers are read on every query, so when you re-measure a pad after a tree trim the answer updates the same day.

Yes. The rate-table post stores nightly, weekly, monthly, and seasonal rates per pad type. The bot picks the right tier for the requested duration, so a 38-night stay gets the monthly rate not 38 nightly rates summed up. Holiday and event premiums layer in correctly when they're stored as date-based overrides on the rate row.

Yes. Electric billing rules (metered, included, capped) and the per-kWh rate are stored as park-level fields and surfaced on monthly stays. The bot notes that electric is billed separately, gives a realistic monthly range based on typical AC and heat use, and references the meter-read date if you publish one. Some parks include electric in winter months, and the seasonal version of the field is what the bot quotes.

Yes. Monthly and seasonal stays usually require an application with deposit, references, and proof of insurance. The bot captures rig details, dates, and intent in chat, then routes the conversation to the long-term form or a dedicated email. The handoff includes the captured fields so the office isn't re-asking for length and amp service.

Yes. Pool hours, clubhouse hours, laundry hours, dog wash hours, and propane fill schedule are all park-level fields the bot references. Seasonal closures (pool closed November to March) read from the same fields so the answer matches the time of year. Updates flow through the moment you edit the field.

Yes. If you record Wi-Fi performance per pad (signal strength, last speed test, repeater proximity) the bot quotes those numbers. Remote workers shopping for a winter base usually ask before booking, and a real number like "30 to 50 Mbps down on Sites 7 to 15, weaker in Loop B" wins those bookings over a vague "yes we have Wi-Fi."

Yes. SleekAI doesn't replace your reservation software, it reads from the same WordPress data the booking pages use. Campground Manager, ResNexus integrations that publish to WordPress, and any custom booking plugin all work as long as the inventory and bookings are queryable. For external SaaS systems, a webhook or scheduled sync into a WP table keeps the bot current.

Yours. SleekAI is BYO API key, so you bring an OpenAI, Anthropic, Google, or OpenRouter key and the model bills you directly. There's no per-message markup. A single-location park typically spends $5 to $30 a month in actual API usage. GPT-4o-mini is the standard pick; some parks step up to GPT-4o or Claude Sonnet for the long-term application intake which benefits from stronger reasoning.