Answers from your own documents.
Down to the page.
Your team and your customers get answers from your handbooks, wikis and help articles, in chat, by email or in your own app. Every passage comes back with its source, and connic keeps the index current.
Answers where people already ask.
On a course page, in the intranet, in a shared inbox or at the service desk, answers come from your own documents and name their source.
Students ask about this week's lecture next to the material. The assistant answers from the slides and names the slide and page.
Uses
- Chat connector
- Slides and reader
Employees sign in with their company account and search HR, IT and finance pages from one box.
A student emails a question about exam rules. The agent replies with the answer and the paragraph of the regulations it comes from.
Uses
- Email connector
- Exam regulations
When a technician closes a ticket, the agent writes the fix into the IT how-tos. The next person who asks gets it as an answer.
Uses
- Webhook connector
- IT how-tos
Change the wiki, and the answers change with it.
Connect sources such as Notion, Confluence, SharePoint and OneDrive or a website once. connic syncs them on your schedule and only reprocesses what changed.
- Current without uploading again
- Connected apps sync as often as every 15 minutes and websites every 12 hours, or as rarely as weekly. Sync now runs one right away.
- Deleted pages stop showing up
- Choose whether content that disappears from the source leaves the index too.
- The files your team already has
- Upload PDFs, Office documents, spreadsheets, presentations, emails and images. Answers name the page of a PDF and the slide of a presentation.
Each agent searches only what you allow.
Wrap retrieval_query in a tool with one job. The model asks the question, and your code decides where it searches and how much comes back.
- One purpose-built tool
- The model only sees
search_policies(question). Namespace, score floor and result count stay fixed in your code. - Read-only by configuration
- The
retrievalblock limits people-assistant topolicies.hrand blocksretrieval_storeandretrieval_delete, also from custom tools. - A source in every result
- Each match carries its entry ID, namespace, score and metadata, plus the page for PDFs and the slide for presentations.
version: "1.0"
name: people-assistant
description: Answers employee questions from HR policies
model: connic/gpt-5.6-terra
system_prompt: |
Answer only from search_policies results.
Name the source and page for every fact.
tools:
- handbook.search_policies
retrieval:
namespaces: [policies.hr]
prevent_write: true
prevent_delete: truefrom connic.tools import retrieval_query
async def search_policies(question: str) -> list[dict]:
"""Search the HR handbook and wiki for matching passages.
Args:
question: The employee's question in their own words
"""
result = await retrieval_query(
query=question,
namespace="policies.hr",
min_score=0.35,
max_results=4,
)
return [
{
"passage": item["content"],
"source": item["entry_id"],
"page": item.get("page_number"),
}
for item in result["results"]
]