No. The system instruction explicitly forbids legal interpretation, ruling on disputes, or telling a resident whether a specific action is allowed under the city code. The bot quotes published pages and points to the correct department for any question that requires staff judgment. This is enforced in the instruction itself and reinforced by SleekAI's guideline filter, which catches off-topic or out-of-scope requests before they reach the model.

Yes, if your city publishes a closures page or maintains a holiday list in WordPress. SleekAI reads those entries the same way it reads regular hours, so a resident asking "are you open on Memorial Day" gets the published closure date and the next open business day. If your site does not publish holiday closures, the bot will say so and direct the resident to call ahead rather than guess.

Yes. Because SleekAI uses general-purpose LLMs from OpenAI, Anthropic, Google, or OpenRouter via your own API key, the bot answers in whatever language the resident writes in. For a city with significant Spanish, Mandarin, or Polish speaking populations, this is the difference between a useful front door and one that only serves English speakers, with no per-language translation infrastructure to maintain on your side.

SleekAI indexes the WordPress media library and any pages that link out to PDFs, then matches a resident question to the form title, the department that owns it, and any descriptive content nearby. If your forms library uses ACF fields for department, category, and fee, those map directly into the bot's context so the answer can include the fee and submission method alongside the link.

Yes. SleekAI Multibot lets you run a city-wide bot on the home page and a scoped bot on the Building Department, Police, or Public Works page that only answers within that department's scope. Display conditions tie each bot to a post type, taxonomy, or URL pattern so the experience is focused without splitting your site into separate installs.

Into the WordPress conversation log, with model name, token usage, and the page URL where the chat happened. This is useful for FOIA-style transparency reviews and for spotting common questions that should be turned into a clearer FAQ page. Logs stay in your database under your control, not on a third-party dashboard, which matters for public-sector privacy expectations.

The instruction tells the bot to direct any safety emergency to 911 and any non-emergency police matter to the city's published non-emergency line. The bot will not try to dispatch services itself or take an emergency report. For utilities or after-hours issues, the bot quotes whatever public hotline your site documents (water emergency line, animal control after-hours, and so on) without inventing numbers.

SleekAI runs on your WordPress install and uses the API key you provide, so requests go from your site to the model provider you have a contract with (OpenAI, Anthropic, Google, OpenRouter). No data routes through any Sleek-hosted service. Conversation logs are stored in your database; you control retention, exports, and deletion. The bot does not collect SSNs, license numbers, or other regulated PII, and the guideline filter prevents prompting visitors for them.