Add knowledge to your chat app
Knowledge is the library your chat app searches when it answers your customers. Put your price list, policies, product guides, and FAQ in it, and the app can quote from them instead of guessing.
Where knowledge lives
Open your chat app and switch the header toggle from Preview to Configure. The Knowledge section sits near the top of the page, between the chat model row and Instructions.
You also get the chance to add knowledge while creating the project: the chat app’s setup screen has an Add knowledge dropzone alongside the instructions field. Documents you add there land in the same library you manage from Configure later.
What you can add
The picker accepts:
- PDFs
- Word documents
- PowerPoint presentations
- Excel spreadsheets
- CSV files
- Plain-text and Markdown files
You can drag files onto the section or click Add files. For content that exists only in an email or on a page somewhere, click Paste text and paste it in — pasted text becomes a document like any other, and you can edit it later from its row’s ⋯ menu.
Each document has a size cap, and the library has a cap on how many documents it holds. The current caps are listed on the limits page.
What happens after you upload
Spark processes each document in the background, reading its text so the app can search it. This takes a few minutes; the Configure toggle in the header shows a small spinner while processing runs, and a notice confirms when a batch has landed. You can keep working in the meantime.
Once processed, documents are searchable in the preview first. Open the preview and ask a question a document should answer — that is the fastest way to check the app found what you uploaded.
If an upload fails, its row says why and offers Try again. When several files from one drop fail, a single line beneath the list counts them and retries them all at once.
Preview first, live when you publish
New documents follow the same arc as everything else you change: the preview updates, then you publish. Until you publish, new rows are tagged Unpublished — your customers keep getting answers from the live library, and the Publish button carries a dot to show something is waiting. Publishing knowledge uses that same button. Even if documents are the only thing you changed, one publish takes them live.
Removing a published document is staged the same way. The row stays in the list, tagged Removes on publish, and the live app keeps answering from that document until your next publish. Changed your mind? Choose Restore from the row’s ⋯ menu and the document stays.
Knowledge and instructions
The two sections sit next to each other in Configure and do different jobs. Instructions shape how your chat app responds — its tone, its rules, what it should and shouldn’t do. Knowledge is reference material the app searches for facts when a customer asks. A rule like “always offer the annual plan first” belongs in instructions; the annual plan’s actual price belongs in a knowledge document.