No. The bot deep-links to your reservation portal with the park and pavilion preselected, but the actual booking happens in your existing reservation system. That keeps payment, conflict checking, and cancellation policy inside the system that already enforces them. If you have a REST endpoint for the reservation system, SleekAI can be configured to call it via tool calls, but the default flow is a clean handoff.

If your park pages or trail entries have an ACF or taxonomy field for trail surface (paved, gravel, dirt) and accessibility, SleekAI reads those fields and filters answers accordingly. Without those fields, the bot can only answer from descriptive text on each park's page. The richer your structured data, the more precise the filtering, which is true for any chatbot built on a content site.

Yes, if your site publishes seasonal hours, closure dates, or trail closure announcements. The bot reads them as part of each park's context and quotes them when relevant. A winter trail closure or a flood-related park closure gets surfaced in chat the same way it would be surfaced on the park page, just on demand instead of buried in a news post.

No. The bot can quote permit categories, fees, and application deadlines from your published policy, but it does not approve, deny, or rule on eligibility for any permit. Special event permits, athletic field rentals, and commercial filming permits all require staff review, and the bot routes those to the appropriate office with the right form linked. That's the only sustainable scope for a permit chatbot.

Yes. SleekAI Multibot lets you run a system-wide bot on the home page and park-specific bots scoped to a single park's URL pattern. The Greenfield Park bot might focus on that park's specific amenities, the dog run hours, and the pavilion list; the Lakeview Park bot has its own scope with the splash pad hours and fishing pier info. Each bot has its own instruction and presets.

Athletic fields are often handled by a separate athletic permits process. The bot can quote field types (baseball, soccer, multi-use), season availability, and permit fees from your published page, then route the request to the athletic permits coordinator. It does not approve rentals, schedule fields, or resolve scheduling conflicts; those stay with staff or your athletic permit system.

The instruction tells the bot to direct any safety emergency to 911, including injuries, lost children, wildfire reports, or aggressive animal encounters. For non-emergency park maintenance issues (broken bench, vandalism, downed tree blocking trail), the bot points to your published park maintenance reporting form or hotline. The bot does not dispatch crews or take reports itself.

In your WordPress database, with model name, token usage, and page URL stored alongside each transcript. For parks departments, this turns into useful demand data: aggregate the questions and you see which trails get the most requests, which pavilions are most asked about, and which seasonal info is most wanted. That feedback often improves trail page descriptions and reservation page UX more quickly than any internal review.