SleekAI reads each department's pages as separate context entries, with department names, descriptions, and topics indexed. When a resident asks a question, the bot identifies the relevant department by topic match and pulls the answer from that department's content. For ambiguous questions, the bot lists the candidates and asks the resident to clarify, instead of guessing wrong and sending them to the wrong window.

No. The instruction explicitly forbids tax interpretation, eligibility rulings on exemptions, or advice on whether to appeal. The bot quotes published deadlines, fee schedules, and links to forms, then refers any judgment call to the Assessor, Treasurer, or a qualified tax professional. This keeps the bot useful for the 80% of questions that are pure wayfinding without ever drifting into advice territory.

Yes. SleekAI uses general-purpose LLMs via your own API key (OpenAI, Anthropic, Google, OpenRouter), so it answers in whatever language the resident writes in. For counties with significant Spanish, Vietnamese, or Tagalog speaking populations, this turns a single English website into a multi-language front door with no translation infrastructure on your side. Forms are still returned in whatever languages your site publishes them.

Each office's pages are indexed separately, with the boundary between assessment and tax collection respected. A question about assessed value goes to the Assessor; a question about paying the resulting tax goes to the Treasurer. The bot can explain the relationship between the two without conflating them, which is a common source of confusion for residents and a common source of misrouting in generic chatbots.

Yes. SleekAI Multibot lets you run a county-wide bot and department-specific bots scoped to URL patterns or post types. The Sheriff's bot can have a different tone and a stricter scope. The Public Health bot can include clinic hours and immunization schedules without polluting the Treasurer's chat. Each bot has its own instruction, presets, and display conditions.

The bot can locate your FOIA request form, explain the submission path, and quote any published fees or response timeframes from your records page. It does not promise specific records will be released, it does not interpret exemptions, and it does not act as a records officer. The handoff is clean: form, fee, contact, and any published response window, with the actual review handled by staff.

The instruction tells the bot to direct any safety emergency to 911 and any non-emergency law enforcement matter to your published non-emergency line. The bot does not take reports, does not dispatch deputies, and does not provide live incident info. For public health emergencies, it points to your health department's published hotline rather than inventing a number, which keeps the bot honest in moments that matter most.

Everything stays on your WordPress install. SleekAI uses your own API key, so requests go from your site to whichever model provider you contract with (OpenAI, Anthropic, Google, OpenRouter), not through any Sleek-hosted service. Conversation logs live in your database with the page URL, model name, and token usage stored alongside the transcript. Retention is whatever your records policy dictates.