Your documentation,
finally answering questions by itself
Most knowledge bases are written once and then searched badly. A search box returns ten articles and asks the reader to find the answer themselves. This agent reads the actual documents and gives a direct answer with the source cited, so the knowledge base finally earns its keep.
Why a search box is not an answer
Writing good documentation and having it actually get read are two different problems, and most businesses solve only the first. A customer with a question searches the help center and gets a list of ten articles. Often they give up and message support anyway, asking the exact question the documentation already answered three paragraphs into article seven. The knowledge base becomes something written once for compliance’s sake, not a tool customers actually use.
What the agent answers, and how it proves it
The agent reads your actual documentation, policies, FAQs, product guides, and answers questions directly instead of returning a search results list. It cites the specific document and section the answer came from, so a customer, or your own team checking its work, can verify it instantly. It runs embedded on your site, inside Telegram and WhatsApp, and in an internal version for staff questions about policy or process that would otherwise interrupt a manager.
When a question has no good answer in the existing documents, it says so instead of guessing, and logs the gap. That gap report becomes a genuinely useful to-do list. It shows your team exactly which questions keep coming up with no documented answer. That beats guessing at what might be missing.
The internal staff version runs under the same citation discipline as the customer-facing one. That matters. An employee asking whether a discount is allowed needs an answer traceable to an actual policy document, not a confident-sounding guess that turns out to be outdated. When a document is updated, the agent’s answers update right away. They do not lag behind a cached version, a common failure point in static FAQ pages that quietly go stale for months. Usage data also shows which documents get cited constantly and which never get touched. That is a more honest signal of what customers actually read than any page-view count on the help center.
What your team still owns
Writing and maintaining the actual documentation stays with your team. The agent answers from what exists. It does not invent policy. Reviewing the weekly gap report and deciding what to document next is a team decision.
How we keep answers accurate
Every answer cites its source document, so nothing is asserted without a traceable basis. The agent is built to decline rather than guess when the documents do not cover a question, with every such gap logged rather than papered over. New or updated documents get tested with a batch of real past questions before going live, to confirm the agent actually finds and uses them correctly.
Outdated answers are caught two ways: automatically, when a cited document is updated or removed, and manually, when a customer or staff member flags an answer as wrong. Both feed into the same correction queue your team reviews. For businesses with seasonal policies, holiday shipping cutoffs, limited-time terms, documents can be scheduled to activate and expire on specific dates. The agent never cites an expired policy as current. The agent introduces itself as an AI assistant at the start of every conversation.
Price and timeline
| Option | Price | Timeline |
|---|---|---|
| Agency runs it | from $2,000 + support plan | 2 to 4 weeks |
| Full control, handover-ready | from $3,000 | 4 to 6 weeks |
“Agency runs it” keeps the agent on our infrastructure with a monthly support plan covering tuning and monitoring. “Full control, handover-ready” delivers the agent on your own servers and accounts with documentation, source and credentials, so your team can run and change it without us. It costs more up front, because the handover package, your-infra deployment and internal documentation are built in from day one.
Related
See the AI agents overview for how we build and guard these systems, and Routine takeover for the services that often pair with this one. Inside the agents catalogue: Customer support agent for messengers, Self-service portal agent, Technical support tier-1 agent. For a narrower, single-process version of this work, see FAQ answering, RAG knowledge base with citations in the automations catalogue. For how the same guard patterns held up on real systems: Analytics hub with AI analyst in Telegram.
Want this running for your team? Get in touch and tell us where the messages pile up.
FAQ
How much does a FAQ and knowledge base agent cost?
From $2,000 to build the knowledge base from your existing documents and connect it to your site and messengers, live in 2 to 4 weeks.
How long before it is live?
2 to 4 weeks, depending mostly on how much of your documentation already exists versus needs writing first.
Which channels and tools does it work with?
Your website as a chat widget, Telegram, WhatsApp, and an internal version in Slack or Telegram for staff. It reads from your actual help center, PDFs, policy documents or wiki, whatever already holds the answers.
What if the agent cannot find a real answer?
It is built to say it does not know rather than guess when the documents do not cover a question. Every such gap is logged in a weekly report, so your team can see exactly what to write next.
Is our documentation and customer data safe?
Documents stay in your own storage or help center. The agent reads them to answer and does not alter the source. Every question and the source it cited are logged.