Support

An assistant that answers from your own documents

Grounded in your handbook, with a source line under every answer saying which document it came from.

The question

a support assistant that answers from my own documents

Yes, and the answer carries the document it came from. You upload text through the console, and she answers ordinary questions from it. The line naming the source is written by the application rather than by the model, so she cannot cite a document she was not given.

Who this is for

Somebody running support for a product or a service, who is tired of answers that sound right and are not in the handbook.

How it works

A floor, a citation rule, and no document name in the prompt

Three decisions do the work, and each one was made after a run that went wrong.

Passages reach her fenced, numbered and unnamed, so a document title never enters the prompt and she could not cite one by name if she tried. She declares which numbered passages she used; the application checks the answer actually carries them, drops invalid numbers, refuses to attach a source to a refusal, and mints the line itself. Below a measured relevance floor she is handed nothing at all and answers as an ordinary bot.

What it will not do

PDF is refused, deliberately: extraction is a silent quality cliff, and a badly extracted file produces chunks that look like text and retrieve like noise. And when the documents do not cover a question there is no announcement, because a lookup that found nothing is not news.

Which door

What this needs, and what state it is in

Read from the same table the ways-in page renders, so it cannot be current there and stale here.

The doors this touches

Over a chat network built

What runs today: the chat core embedded in-process, with no daemon and no exposed port, one directory as the only SDK importer, and one core hosting every enabled bot with commands serialized and events routed per profile

Over a web server, as an ordinary web assistantstarted

More than nothing, honestly: a demo route drives the real interaction engine, consent logic and persistence over the fake adapter, with a deterministic rules layer, a 25 message budget and synthetic data. The admin console and the public archive are web surfaces rather than chat ways in

The web door is the one most readers of this page assume they are buying, and it is not finished. The door that is built is a chat network you would have to adopt. That is the honest answer, and it will cost us some readers.

Every way in, and its state

Where to go next

The pages that carry the checks

This page makes no claim of its own. Each one below is where the thing is written down with the way to verify it.

What to read

The knowledge base page carries the retrieval steps, the floor and the citation rule, each with where to check it.

The knowledge baseSecurity, claim by claimInstall it