One Chat, Every Tool: How DocReveal’s RAG Chat Tools Work in Practice

Some questions fit in a sentence. Most of the ones that matter at month-end do not. Which invoices are wrong, and by how much? When did a carrier’s insurance run out, and did anything ship after that? What exactly changed in the price list, and where does it say so?

An answer in plain text leaves the real work to you: copying figures into a spreadsheet, checking dates against a calendar, opening the PDF to find the line. And when the answer says something needs doing, you leave the chat to do it.

Our new video guide shows how DocReveal’s RAG chat handles this with tools. It runs six and a half minutes, you can watch it at the top of this page, and it follows Keldmoor, a fictional distributor, through ten questions in one conversation. Here is what you will see and how it works.

Switch the Agent on, choose the tools

The chat lives in RAG Manager — in the video, it covers twenty Keldmoor documents: contracts, orders, invoices and more. With the Agent switched on, the assistant can use tools. Each tool is one thing it can do, such as finding documents, running a check or drawing a table.

The Tools button lists them by category, each with its own switch, and your choice applies to the current conversation. Badges mark the special ones: “confirm” means the assistant asks you before it acts, “approval” means a person signs off in the Agent Manager, and “external” means the data leaves DocReveal. While the assistant works, the answer panel shows its plan and every tool it calls.

A table, not a paragraph

The first question asks for the September findings in a table: supplier, document, issue and amount. Five findings come back — $15,900.36 that Keldmoor should not pay.

The table is live. You can sort it, filter the rows and export it to Excel, Word or Markdown. It also stays in the conversation as a dataset, which you can export, enlarge or bring into the next question.

The numbers at a glance

The next question builds on that dataset. Key figures arrive as tiles: $66,324.48 invoiced, $50,424.12 under the contract terms, $15,900.36 not payable — and $7,050 of cargo that travelled without valid insurance. A chart then puts the invoiced amounts next to the contract terms for each supplier, and most of the gap turns out to be Stavlund, the fastener supplier.

When did it happen?

Dates hide in every document. Asked to put the orders, deliveries and payment deadlines on a timeline, the assistant draws one lane per kind of event and calculates the early-payment discount deadlines from the payment terms.

Laid out like that, the gap is plain to see: the carrier’s insurance expired on September 15, and the next day the same carrier picked up a shipment for Keldmoor. Two discounts are still open, and the dates can go straight into your calendar as an ICS file.

What changed?

Contracts change by amendment, and invoices do not always follow. Asked what Amendment No. 1 changed in Stavlund’s price list, the assistant puts Annex A of the supply agreement next to the amendment and shows only what changed: from July 1, SF-220 went up from $0.42 to $0.46, and SF-310 down from $1.15 to $1.09.

Untick “Only changes”, and you see the whole price list. The answer also names the invoice that still bills SF-310 at the old price — $720 too high.

Who is connected?

Some risks only show up when you follow the links between documents. Asked who is involved in that shipment and how, the assistant uses the knowledge graph to find the companies and their documents, and draws them as a network: Keldmoor at the top, the order, the carrier agreement, the bill of lading and the insurance certificate in the middle, the other companies below.

Click a node to ask about it or to open its document. The chain spells out the risk: the insurer covered the carrier only until September 15, and the carrier agreement does not allow transport without insurance.

Show me where

A number without a source is an opinion. Asked where the amendment sets the new SF-310 price, the assistant points to section 1.1 and the price table on page 1, links to that exact place and offers a preview of the invoice that still uses the old price. Open the link, and the original opens in File Manager with the SF-310 row highlighted.

These are the same September invoices you may know from Ask your invoices. This time, the answers come back as a table, tiles, a timeline and a graph — and the source line is one click away.

A question back, a file and the next step

Not every question is precise. Asked to compare the contract with the invoice, the assistant finds several pairs that fit, so it asks back and offers options. Pick the carrier, and the run continues: the freight invoice is $939.36 above the carrier agreement.

The check comes as an Excel file to download, and suggested follow-up questions sit under the answer — one click asks the next one.

More than answers

Visual outputs are only one group of tools. The others work across DocReveal: documents and their processing, business rules, labels, agents, help and more.

Ask which documents need attention, and you get the two that failed the business rules, each with what to do next. Ask to run the rules again, and the assistant asks first, because that changes data; approve it, and the run continues. Ask to label a document, and in this workspace the request waits for a person’s approval in the Agent Manager inbox — the same kind of approval you may know from Agents under control.

Your tool set, your rules

More tools come as packs from the Shop: visual outputs, calculations, document actions, registries and web — and maps, which Keldmoor has not installed. Registries, web and maps send data outside DocReveal, and both the Shop and the Tools panel mark them.

In Settings, under Chat tools, you decide for the whole workspace which tools start switched off in every new conversation, and whether to show their technical names.

What to take away

  • Ask for the form that fits. A table to sort, tiles and a chart to compare, a timeline for dates, a comparison for changes, a graph for relationships.
  • Keep the source close. Answers cite their sources, and a highlight takes you to the exact line in the original.
  • Choose your tools. Switch them per conversation, set the defaults in Settings and see at a glance which ones send data outside.
  • Act from the chat, with control. Actions that change data can ask you first, and some can wait for a person’s approval.

Keldmoor and its suppliers are fictional demo data; the screens are the real product.

One chat. Every tool.