Skip to content

AI knowledge agent with cited answers. Every answer, with its source.

Webaroo's Knowledge Agent is an AI agent your team asks in Slack or Microsoft Teams. It answers from the documents and Drive folders you share with it, cites the source every time, and says so when the answer is not there.

Ask Roo: Could an AI agent answer our team's questions and cite the source?

Knowledge AgentScattered sources arc into one body of knowledge. Every answer keeps its line back to the source.
Drive folders / Shared documents / Answer, with its source
Built for
Teams that answer the same questions from the same documents all week: lenders, manufacturers, operations teams and professional services firms
Time to live
Timeline quoted on a call
How it is priced
A fixed fee for a defined scope, quoted on a call, then a monthly Run plan from go-live
Pairs with
Voice Agent, Workflow Agent, AI Assessment

Every answer cited. Every question logged.

Your team asks in Slack or Microsoft Teams and gets a plain answer with its source. When the answer is not in your documents, it says so.

  1. Questions answered where your team already works

    In Slack or Microsoft Teams. No new tool to open, no search box to learn. Ask in plain words and get a plain answer.

    Your team
    “What do our supply agreements say about late deliveries?”
  2. Every answer cites its source

    The document, the section, the date it was last changed. Your team can check it in one click instead of taking the agent's word for it.

    Your team
    “Which version of the expense policy is current, and when did it change?”
  3. It sees only what you share

    The agent reads the Drive folders you share with it and nothing else. Share a folder and it is loaded on the next refresh. Unshare it and it drops out of new answers.

    Your team
    “Can you pull the numbers from the board deck folder?”
  4. It says when it does not know

    If the answer is not in the documents, it says so and names who to ask instead of guessing. Wrong answers your team flags go to a review queue and get fixed.

    Your team
    “Do we waive the late fee if the payment came in a day late?”
  5. Every question logged

    What was asked, what was answered, which sources were used. Your admin can read it any time, and it feeds the report.

    Your team
    “Which questions could the agent not answer last month?”

Examples are illustrative

What ships, and what we keep current.

The agent is the part your team talks to. The document checks and the review of flagged answers keep it right as your files change.

You get

Delivered by go-live.

  1. One knowledge base from the Drive folders you share, in your tone, with written rules on what it will not answer
  2. The agent live in Slack or Microsoft Teams, or on a web chat if you prefer
  3. A citation on every answer, back to the document and section
  4. An audit log of every question and answer, plus an admin runbook for adding and removing folders
  5. A report: questions asked, questions it could not answer, documents most cited

We run

Every month, for as long as it is live.

  • Document checks, so new and changed files are picked up and stale ones are flagged
  • Review of wrong-answer flags and unanswered questions, turned into fixes or new documents to add
  • A report: usage, unanswered questions, and the documents to add
  • Monitoring and backups
Review queue / Step 2Illustrative
  • Answer cited last year’s underwriting checklistFlagged by a loan processor. Corrected: the current checklist is now the only source.Corrected
  • Tooling terms in a supply agreementAnswered from the agreement, with the clause linked. Approved.Approved
  • Question about one borrower’s fileNot in the shared folders. Sent to the underwriting lead. Handoff.Handoff

Live on your own documents.

Step one sets access and picks the folders. Step two loads and tunes them, and step three runs it beside your team before it goes live.

  1. Step 1

    Access and documents

    We set up the service account, your team shares the folders, and we inventory what is there. We agree in writing which groups see what. Persona and tone are written and you approve them.

  2. Step 2

    Load and tune

    We load the documents and test the agent on questions your team really asks. We fix the misses, set the citation format, and open a review queue for wrong answers.

  3. Step 3

    Shadow run, then live

    A few named people use it next to their normal work. We fix what it missed, then open it to the team with the runbook and the date of the first report.

How it is priced

A fixed fee for a defined scope, quoted on a call once we know how many documents and how many people will use it. After go-live, our support and maintenance team runs it on a monthly Run plan. No hourly billing.

Answers first, and then the work they start.

An answer is often the first step. Each of these puts it to work: on the phone, in a workflow, or in a plan.

Phone line / Rulebook / Calendar / Front deskVoice Agent: A call arrives as a wave, passes your rulebook, the written rules your team approves, and settles into one booked slot. Some calls go to the front desk.

Voice Agent

When callers ask questions whose answers live in your documents, not in a script.

See Voice Agent
Received / Classified / Approval / UpdatedWorkflow Agent: Steps run along one line. Approvals fork off to a person and come back.

Workflow Agent

When an answer should turn into an action, with a named person approving it first.

See Workflow Agent
Workflows / Measured / Top 3 / Day 10AI Assessment: The business as a field of workflows. The top 3 rise and get measured in ten days.

AI Assessment

When you are not sure which documents, or which team, to start with. Ten days, one plan.

See the AI Assessment

One question, from the ask to the source.

The same agent, three businesses. Pick one and follow a question from the moment it is asked to the moment a person steps in.

Team channelIllustrative / Example data / No live actions

Your team

What do we need from a self-employed applicant before underwriting can start?

Agent

Two years of business returns, a year-to-date profit and loss, three months of business bank statements, and a signed 4506-C.1,2 The March ops update added the year-to-date profit and loss.3

Sources

  1. 1DriveUnderwriting Checklist v7
  2. 2DocsSelf-Employed Business Income Guide
  3. 3DocsOps Update, March 2026

Answers only from the operations folders shared with the agent. Applicant files are not in scope.

  1. 01Request

    A processor asks in Teams

    The checklist changed twice this year and the processor is not sure which version is current. She asks the agent instead of the senior underwriter.

  2. 02Knowledge

    It knows which version is current

    The answer comes from version 7 of the checklist and the income guide, and it folds in the March ops update that added a document.

  3. 03Action

    The list goes back with sources

    Four documents, named the way the checklist names them, with links. The processor pastes the list into the applicant email.

  4. 04Handoff

    The edge case goes to underwriting

    The processor follows up: the applicant also has rental income. The agent says rental income is covered by a guide it has not been given, and names the underwriting lead.

Asked before any folder is shared. Answered in plain words.

If yours is not here, ask it on the 15-minute call.

Webaroo's Knowledge Agent answers your team's questions in Slack or Microsoft Teams from the Drive folders and documents you share with it. Every answer cites its source, and every question is logged.

Google Workspace today: Drive folders, Docs, and Sheets that your team shares with the agent's service account. Your team asks it questions in Slack, Teams, or Telegram. It reads only what you share and nothing from private drives or inboxes.

A fixed fee for a defined scope, quoted on a call once we know how many documents and how many people will use it. After go-live, our support and maintenance team runs it on a monthly Run plan. There is no hourly billing.

Why we don't bill by the hour

It says the answer is not in the documents it has and names the person or team to ask. It is built to answer only from your documents, and wrong answers your team flags go to a review queue. Unanswered questions go in the report so you can add the missing document.

No. The Knowledge Agent answers; it does not act. When you want an answer to turn into an action with a person approving it first, that is the Workflow Agent, and the two run side by side.

New and changed files in the shared folders are picked up on the next check. Your admin can also run a refresh any time, using the steps in the runbook. The check flags stale documents so someone owns the fix.

Start with the questions your team repeats. A straight answer first.

Knowledge Agent fits a team that answers the same questions from the same documents every week.