ZECH
Solution · Knowledge work

Give staff answers they can check, drawn only from documents they are allowed to see.

Questions are answered from your wikis, policies, tickets and shared drives, with a link to the passage behind every answer. Permissions follow the source systems, and questions the assistant cannot answer go to the people who can.

The workflow
  1. 01Connect and index sources
  2. 02Ask a question
  3. 03Retrieve permitted passages
  4. 04Draft a cited answer
  5. 05Escalate and improve
Who uses it

The workflow

Employees in operations, support, HR, finance and engineering who spend part of every day looking for the current version of an answer, and the subject experts they keep asking.

Today
  • The same questions go to the same few experts in chat every week.
  • Search returns ten versions of a policy and no sign of which is current.
  • New starters take weeks to learn where things are kept.
  • Answers given from memory drift from the documented procedure.
  1. Connect and index sources

    System

    Documents are pulled from the agreed systems on a schedule, split into passages and indexed together with their access permissions and last-updated dates.

  2. Ask a question

    Person

    A staff member asks in plain language from chat, the intranet or inside the tool they already use.

  3. Retrieve permitted passages

    System

    The search step finds relevant passages, filtered to what that person is allowed to read in the source system.

  4. Draft a cited answer

    AI

    The model writes a short answer using only the retrieved passages and links each statement to its source. If the sources do not cover the question, it says so.

  5. Escalate and improve

    Person

    Unanswered or flagged questions go to a named owner, whose reply is added to the knowledge base or used to fix the source document.

What to measure

Where people stay in control

Every answer shows its sources so the reader can check them. Users can flag a wrong or outdated answer in one click, and flagged answers go to the content owner for that area. Owners review the most-asked unanswered questions each week and decide which documents to write or correct.

  • Share of questions answered with a cited source
  • Time to find an answer, compared with the pre-launch baseline
  • Rate of answers flagged as wrong or outdated
  • Repeat questions reaching subject experts directly

Data and integrations

  • Read access to the document systems in scope, such as SharePoint, Confluence, Google Drive or a ticketing tool
  • Identity provider and group mappings for permission filtering
  • A set of real questions with agreed good answers for evaluation
  • Named owners for each content area

Realistic boundaries

  • The assistant is only as current as the source documents; conflicting or outdated documents need an owner to resolve them.
  • It answers from your content, not general knowledge, and will decline questions its sources do not cover.
  • Decisions with legal, HR or financial consequences stay with the responsible person, who can use the answer as a starting point.

Questions buyers ask

Permissions are captured when documents are indexed and checked again at question time against the user's identity. The model only ever receives passages the person could already open in the source system.

The assistant says it could not find a source and offers to route the question to the owner of that area. It does not fill the gap from general knowledge. See how we build retrieval systems.

Map this workflow with us.

Tell us about the workflow or product. We reply with questions, a suggested first step and who would work on it.