Policy questions answered instantly,
from your actual documents

Why the same questions keep landing on HR’s desk

Every company has a handful of policy questions that get asked constantly. How many vacation days carry over. What the expense limit is for a client dinner. Whether a particular tool is approved for work data. The answer usually exists somewhere, a handbook, a Notion page, a PDF from two reorganizations ago. Finding it takes longer than asking a colleague, so people ask a colleague instead. The colleague answers from memory, which is fine until the policy changed last month and nobody told them.

That creates a quiet inconsistency problem. Two employees who ask the same question on the same day can get two different answers, depending on who they happened to ask. Neither answer may match what is actually written in the current policy. HR and managers end up fielding the same handful of questions over and over. Not because the questions are hard, but because finding the answer in the real source document takes more work than just asking a person.

The cost shows up as interruptions, not one large expense. A manager gets pulled out of focused work to answer something already written down, repeated across a team and across a year. It is rarely dramatic. It adds up, and it gets worse as the handbook grows and fewer people have read the latest version in full.

How the agent answers from your own documents

The agent reads directly from your handbook, policies and SOPs, using retrieval over the actual documents. An answer is grounded in what is currently written, not a general impression of company policy. Every answer comes with the source document cited, so an employee, or a manager double-checking, can see where it came from and judge whether it is current.

Content lives in Notion, Google Drive, or whatever document folder your team already maintains. An admin panel lets someone update that content without a developer. A policy change made this morning shows up in the next answer instead of waiting for a rebuild. Version control is built in for exactly this reason, so an outdated policy document stops getting quoted once it has been superseded.

The agent runs in Telegram, Slack or a web chat widget, whichever matches where your team already asks questions. It also produces a usage report showing the most-asked questions and the gaps in documentation they expose, often as useful to HR as the answers themselves.

What stays a human call

Anything the agent cannot answer clearly from the documents gets routed to HR or a manager rather than guessed at. That routing decision, saying “I don’t know, ask a person” instead of inventing a plausible-sounding policy, is deliberate, not a fallback of last resort.

Deciding what the actual policy should be stays with a human. So does resolving an ambiguous or contradictory document, and handling anything that touches a specific employee’s personal situation. The agent answers only from documents it has been given access to. It does not browse the open internet, and it does not fill gaps with general knowledge about how other companies handle something.

How we keep answers trustworthy

Every answer is cited to its source document. That makes it possible to check an answer against the original text instead of trusting it blindly. The usage report surfaces which questions come up most, and where documentation is thin or missing.

Version control means an edited policy actually replaces the old one in what the agent quotes, instead of both versions floating around. When the documents do not clearly answer a question, the agent escalates rather than answering with confidence it has not earned. That keeps the failure mode visible instead of silent.

Price and timeline

Running cost is usually $15 to $50 a month in model usage depending on question volume, with a budget cap set before launch.

Related

This works well alongside employee onboarding, since new hires generate a disproportionate share of policy questions in their first weeks. Pair it with compliance checklists where the underlying documents need to stay audit-ready. SOP generation keeps the source procedures current, not just answers questions about stale ones. The visa consulting centre case study describes a close relative of this build. A client-facing AI consultant answers from a knowledge base that non-developers can edit live. SENET shows a memory and retrieval engine built for a sellable AI assistant product. For more on the approach, see the AI agents service page and the automation-everything overview.

Want to see your own handbook answer questions instead of your HR inbox? Get in touch and we will look at what documents you already have.

Tired of doing this by hand? We can take the whole routine off your team, not only this step: Routine takeover, from $400 →