---
title: "Improve Answers with Curated Documents"
description: "Upload concise, current material and remove obsolete versions."
category: "Pro Tips"
canonical: "https://www.proxyai.app/help/pro-tips/improve-answers-with-curated-documents"
---

> For the complete documentation index, see [llms.txt](https://www.proxyai.app/llms.txt). Request public content pages with `Accept: text/markdown`.

# Improve Answers with Curated Documents

Use **Configurations → Bot Knowledge** for policies, product details, procedures, and other source content, the [Bot Knowledge Guide](/help/add-ons/bot-knowledge-guide) covers limits, formats and billing. Review each document before implantation. Check the implanted list after upload, and remove outdated or duplicate files so retrieval favors current information.

Enable scanned-PDF enhancement only when a PDF lacks a usable text layer. For easier maintenance, prefer text-based source files when possible.

Documents with the same filename are setup as a replacement and update of the knowledge, use an unique naming for your documents for any other intentions.

### Keep a small, reviewable source collection

Before uploading a file, identify the question it should help answer and check whether an existing document already covers the same policy. Conflicting versions can make a correct answer harder to retrieve. Keep source names clear enough that another team member can tell the document's purpose and decide which version is current.

After implantation, test a question whose answer appears in the document and another question the document does not answer. Check whether the assistant uses the available facts without inventing missing details. Review the source text when an answer is wrong; changing the model alone does not repair an outdated policy.

For a practical explanation of retrieval and source preparation, read [grounding a support bot in your own documents](/blog/grounding-a-support-bot-in-your-own-documents). Keep the selected chatbot in mind throughout the upload and test. Knowledge supplied to one bot should not be assumed available to a different assistant in the same account.
