Knowledge base

Upload your price list, policies, and FAQs once, and your assistants answer callers from them — your material, spoken in the assistant's voice.

What it is#

The knowledge base is a library of your own documents — FAQs, price lists, policies, opening hours, product details. You upload a document once, then attach it to whichever assistants should know it. On a call, the assistant consults the attached documents whenever a caller's question needs your specific information, and answers from them.

What you can do with it#

• Answer routine questions automatically — opening hours, prices, cancellation policy, directions: callers get the answer from your material instead of "let me take a message".
• Share one source of truth — attach the same document to several assistants; when the content changes, you update it in one place and every assistant attached to it uses the new version.
• Keep each assistant on-topic — a bookings assistant gets the menu and opening hours, a support assistant gets the troubleshooting FAQ; each assistant only uses what you attach to it.
• Pause content without losing it — disable a document on one assistant (a seasonal menu, a promotion that ended) while other assistants keep using it, then re-enable it later. A disabled document is simply not used on that assistant's calls.
• Update as things change — replace a document's text at any time; there is nothing to re-attach or re-train.

How to set it up#

Everything is configured through OnCore's REST API. You create a document — sending the text directly or uploading a plain-text (.txt) file — then attach it to each assistant that should use it, where it can be enabled or disabled at any time. The step-by-step flow is in the Knowledge base guide, and every endpoint is detailed in the Documents API reference. Assistants themselves are covered in the Assistants guide.

Limits & FAQ#

• Documents are plain text (.txt), up to 1 MB of text each.
• A document can be attached to any number of assistants, and each attachment can be enabled or disabled independently without detaching it.
• A document that is still attached to an assistant cannot be deleted — detach it everywhere first (or just disable it where it shouldn't be used).

How does the assistant use the documents? During the call, it looks up the enabled documents whenever the caller asks something that needs your information, and answers from what it finds — there is no training step or waiting period.

What if the answer isn't in our documents? The knowledge base adds your material to what the assistant already does from its instructions — it doesn't replace them. For questions you'd rather a person handled, pair the knowledge base with call transfers so the assistant hands over instead of guessing.

Do we re-upload when our content changes? No. Update the document's text through the API and every assistant it's attached to uses the updated content.