Your team asks in the chat.
Your documents answer.
Employees ask in Slack, Telegram, by email or in your own portal. Answers come from your manuals, procedures and handover notes and name the page. When the documents don't cover a question, the assistant says so instead of guessing.
Answers where the question comes up.
One plant, four places where people ask. Every answer names the document it comes from.
A technician sends a photo of the alarm on the press panel in Telegram. The assistant replies with the cause, the fix and the manual page.
A shift lead signs in to the plant portal and asks what happened on press 3. The answer sums up the last three handover notes, each with date and shift.
The manual says nothing about an alarm after a die change, so the assistant says so and tags the line's planner. Her answer is saved, and the next person gets it with its source.
A new colleague emails the safety desk about cleaning the paint booth. The reply lists equipment and steps from the current revision, with section and date.
Stop searching shared drives for the right page.
Today an answer depends on who is on shift and which binder sits at the line. With the assistant, everyone asks the same documents and sees where each answer comes from.
Finding the right page
Today: Search the shared drive for the right PDF and scroll to the page, or walk over to the office
With the assistant: Ask in the chat and get the value with the manual and page it comes from
See what your team asks and where the documents fall short.
Every question is recorded with its answer, the passages found and the cost, so these numbers need no extra tracking.
Questions without an answer
Runs without an answer are tagged, and a dashboard chart counts them per week, so you see which documents are missing.
Answers backed by a passage
A judge checks a sample of answers, for example whether the value matches the cited passage, and tracks the average over time.
Questions per team and channel
Dashboards filter by assistant and channel, so you see how many questions come from each site, chat and the portal.
Cost per answer
Every run shows its cost, and dashboards chart each assistant's cost over time.
Answers you can check, from knowledge each team may see.
Every answer names its source, each assistant searches only the knowledge you allow, and the sources keep themselves current.
- Every answer shows its passage
- Each passage comes back with its document, the page for PDFs and a link to the original file. The assistant names them next to the answer.
- Answers follow the current document
- SharePoint and OneDrive, Confluence and Notion sync on a schedule, from every 15 minutes to weekly, and only changed files are processed again.
- Each site and team sees its own knowledge
- Knowledge is split by site and team, and each assistant searches only the parts you allow. In your portal, answers can follow each person's groups from your company sign-in.
- Every question is on record
- Each question is kept with the passages found, the answer and its cost for your plan's retention period.
What the assistant may search is a file your engineers review.
For your engineers: sources are connected once in the dashboard. Which knowledge the assistant searches, how it answers and where it may write is one YAML file in your code.
- Sources are connected once
- Under Retrieval › Sources, pick the SharePoint sites and folders, a namespace such as
plant2.manualsand a schedule. After the first sync, only changed files are downloaded. - Search and write rights in one block
- The assistant may search
plant2andsafetyand store notes only inplant2.fixes. Any other search or write is denied, also when your own tools call it. - Checked on every deploy
- Deploys check the rules and fail with the file and the rule that is wrong, before anything goes live.
version: "1.0"
name: plant2-assistant
description: "Answers shop-floor questions for Plant 2"
model: connic/claude-sonnet-5.5
system_prompt: |
You answer technicians and shift leads at Plant 2.
Search plant2 and safety with retrieval_query first.
Name the document and page for every value you give.
If no passage answers the question, say so and name
the planner for that line. Don't guess.
tools:
- retrieval_query
- retrieval_store
access:
retrieval:
plant2:
search: true
plant2.fixes:
search: true
store: true
safety:
search: true