CiVQ Knowledge Guide
Modules · Engage tier

AI Assistant

An optional bilingual assistant that answers resident questions from your own indexed documents, escalates to staff when needed, and never blocks any other module.

Resident-facingEngage tierBilingual EN / ES

Residents ask a question in English or Spanish; the assistant answers from a knowledge base your staff curate — ordinances, policies, FAQs — and hands the conversation to a person when it should. It's a layer on top of the platform: helpful where it's enabled, and never required by anything else.

What you can do

Knowledge base

Index your documents

Paste ordinances, policies, or FAQs with a source type and reference; each is chunked and indexed so the assistant answers from your real content, not guesses.

Bilingual

English or Spanish

Documents can be tagged English, Spanish, or bilingual, and conversations carry the resident's language — answers come back in kind.

Conversations

Review transcripts

Browse constituent conversations and open any one to read the full transcript, with each message tagged user / assistant / system.

Escalation

Hand off to staff

A conversation can be escalated to a real ticket; the back-office flags escalated chats so nothing falls through.

Maintenance

Re-index on demand

One button re-indexes the whole knowledge base after content changes, so answers stay current.

Oversight

Usage at a glance

KPI cards show conversations, active and escalated counts, documents indexed, and per-conversation token usage.

A typical workflow

  1. Curate the knowledge base — staff index ordinances, policies, and FAQs with their source references and language.
  2. A resident asks — in English or Spanish, from the public surface where the assistant is offered.
  3. It answers from your content — drawing on the indexed documents, in the resident's language.
  4. It escalates when needed — anything it shouldn't answer becomes a ticket for staff.
  5. Staff review & tune — read transcripts, watch escalations, and re-index after content updates.

A closer look

In practice
The assistant is purely additive. Turn it off and every other module works exactly the same — Permits, 311, Payments, Records and the rest never depend on it. Turn it on, and it answers the routine "what are the office hours / how do I apply" questions from your own documents, freeing staff for the calls that actually need a person.
Where it lives
Staff back-office: /dashboard/aiassistant — the conversation viewer plus the knowledge-base document manager and re-index control.

Works with

Many modules — it assists across the platform from your indexed content (e.g. Permits, 311, Records) but is required by none of them.

CiVQ
Bilingual civic software for local government — own it or rent it.
Product
Products Pricing Why CiVQ Bilingual
Company
About Contact Platform guide API docs
Legal
Privacy Terms Accessibility
© 2026 CiVQ · Pragmatic Business Solutions, LLC — Rio Grande City, TexasKnowledge Guide
×
↑↓ to navigate↵ to openesc to close