Answers from what your business actually knows.
A workspace's knowledge base is the material inxo drafts from: uploaded documents (PDF, Word, Markdown), FAQ entries you paste in, and pages on your site it reads. Every draft that uses it shows the source.
Start with three entries.
Your pricing, your policies, your hours. Most teams see the difference on the first day; the base grows as you notice what the inbox keeps asking.
Sources on every draft.
A draft that used a document names it — on the approval card and over the API. Reviewers check the claim, not the whole conversation.
Per brand, by construction.
Each workspace has its own knowledge base. Nothing crosses between brands, and nothing crosses between customers.
"How long does a warranty repair take, and do I need the original receipt?"
Warranty repairs are finished within five working days of arriving at the workshop. You don't need the original receipt — the serial number on the base plate is enough for us to find your purchase.
The draft cites what it used. If the knowledge base doesn't contain the answer, inxo is instructed not to invent one — and the sources show you what it did use.
What it won't do.
It won't browse the web or look inside your other systems. If the answer isn't in the conversation or your knowledge base, inxo is instructed not to invent one — and because every draft shows the sources it used, a draft with nothing behind it is visible to the person approving it.