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, pages on your site it reads, SharePoint files and folders, and published Dynamics 365 knowledge articles. Every draft that uses it shows the source.
Already in SharePoint? Leave it there.
If your answers are already written down — in SharePoint files your team keeps up to date, or in Dynamics 365 knowledge articles — connect them, and inxo drafts from the version your team maintains. There is no second copy for anyone to remember to update.
Your team keeps editing where it already does. inxo keeps an indexed copy for drafting, and reads a SharePoint file again when it changes, checking every hour, day or week. Published Dynamics 365 knowledge articles are kept in sync.
It reads the SharePoint files and folders you connect, within the sites your administrator grants, and the Dynamics 365 environment you choose. It does not apply SharePoint's own permissions to individual files, so connect only what you are happy for drafts to draw on. Anything holding personal information is held for you to review before it can be used in a draft, and a draft that used a connected source shows it.
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, and it won't look up customer records, orders or cases while drafting — it reads only the sources you've connected, ahead of time. 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.