No. The bot can locate the request form, quote the fee, list the required ID, and explain in-person and mail-in paths, but it cannot issue or certify any record. Certified copies require a clerk's signature and seal, which is enforced at the legal level, not the chatbot level. The bot handoff is clean: it gives the resident what they need to complete the request, then directs them to the office or the mailbox.

No. Voter eligibility, residency questions, and election rule interpretation are explicitly out of scope in the instruction. The bot quotes published deadlines, polling locations, and absentee ballot links from your election page, then refers any judgment call to the clerk's office or the state Board of Elections. This keeps the bot useful without ever wading into territory that requires a legal opinion.

If your site publishes archive indexes (historical meeting minutes, older vital records availability windows), SleekAI reads them and answers accordingly. For records that may be offsite or microfilmed, the bot says so honestly and refers the request to the clerk's staff for confirmation, rather than guessing whether a 1942 record is available. That honesty is what keeps the bot from generating callbacks.

Yes. SleekAI uses general-purpose LLMs (via your own API key from OpenAI, Anthropic, Google, or OpenRouter), so it responds in whatever language the resident writes in. For a town with a meaningful French, Spanish, or Portuguese speaking population, this turns the clerk's chatbot into a multilingual front door with no per-language translation work on your side.

Each conversation is stored in WordPress with the model name, token usage, page URL, and full transcript. This is useful for FOIA review, for spotting which questions are most common (often a sign your fee schedule page needs work), and for verifying that the bot stays in its declared scope. Logs are on your database, under your retention policy, not on a third-party dashboard.

Yes. SleekAI Multibot lets you run separate bots scoped to specific URL patterns or post types. A clerk's bot on the clerk's pages stays focused on records, licenses, and meetings. A tax collector's bot on tax pages handles payment due dates and exemption forms. Each has its own instruction, presets, and display conditions, so the conversations stay focused and accurate.

No. Conversation logs are stored in your WordPress database under your retention policy. The guideline filter and instruction discourage the bot from asking for SSNs, driver's license numbers, or other regulated PII. If a resident pastes such data anyway, your normal IT and records retention policies apply, just as they would for any form submission. The bot does not transmit anything to Sleek; data goes from your site to the model provider you contract with.

If your clerk's office offers notary services and publishes the hours and fees, SleekAI quotes them and explains what to bring (photo ID, unsigned document, witnesses if needed). Appointment scheduling, if your site uses a booking plugin or calendar, can be deep-linked into chat. The bot does not act as a notary itself; it just helps the resident understand what's needed and when to come in.