Upload PDF and Markdown Knowledge Files With Care

Prepare a small, clean file set

Before uploading knowledge, decide which customer questions the assistant should answer and select only the documents that support them. Resonoon’s knowledge editor supports PDF and Markdown files. Keep the walkthrough to those formats rather than assuming that a Word document, spreadsheet, web page, or archive can be added in the same way.

Check each candidate file before selecting it. Confirm that it is approved for customer-facing use, current, readable, and relevant to the assistant’s role. Look for expired policies, draft labels, internal-only notes, duplicated versions, and appendices with separate restrictions. The effective per-file limit documented for this editor is 50 MiB. If a file is larger, prepare a compliant approved version rather than splitting or compressing sensitive content without the owner’s approval.

Use descriptive filenames that distinguish the current source from old copies. File names are a useful review aid, not a substitute for reading the contents. If two PDFs state different return windows, identify the authoritative policy with its owner before adding either as the definitive answer.

Upload and inspect the resulting list

Open the existing assistant’s knowledge configuration in the authenticated editor and use the visible controls to add the prepared PDF or Markdown file. Follow the controls shown in your editor; their labels may vary with the interface language or product version. After upload, inspect the file list and verify that the expected documents appear. The list is a practical check that the intended selection is present; it does not prove that every statement is accurate or that the assistant has answered correctly.

If a document is obsolete, use the editor’s visible removal control and confirm the list reflects the change. Before removing it, determine whether another approved source covers the same customer questions. Removing a document without a replacement may create an evidence gap; keeping a duplicate may preserve a contradiction. Resolve the source set deliberately.

After selection, compare the displayed names with the inventory rather than memory. Similar filenames can hide an old revision. If the list does not match the intended set, correct it before testing so later answers are not attributed to the wrong policy version.

After selection, compare the displayed names with the inventory rather than relying on memory. Similar filenames can make an old revision easy to miss, especially when several policies share a title. If the list does not match the intended set, pause and correct it before testing. This simple check reduces the chance of attributing a later answer to the wrong version of a policy.

Do not assume that adding a file instantly updates every live conversation. After a meaningful change, test questions that depend on the document and check any visible status or error. If the result is unclear, follow the controls and feedback the editor actually presents. Record the displayed result and use the available source controls; if the error remains unclear, share its wording with the person responsible for the source.

Test the content, not only the upload

Use the assistant test page to ask a question answered directly by the new file, a paraphrase, and a question that the file does not answer. Record the expected fact or stop condition before testing. Check that the reply preserves important qualifiers, such as dates, eligibility, exclusions, and location limits. A sentence extracted without its condition can be technically present in the file and still mislead the customer.

If the answer is missing, confirm that the selected document is the right version and that it contains the necessary detail. If the answer conflicts with another source, pause and ask the policy owner to resolve the conflict. If the answer overstates what the document says, clarify the role behavior and test the same prompt again. The file list and the test answer provide different evidence: one confirms selection, the other checks the customer-facing response.

Maintain a separate inventory with the source owner and review trigger. When a policy, price, or service changes, identify every file that may be affected, remove superseded material, and rerun the matching questions. Do not rely on memory or a filename to know which copy is authoritative.

Keep format claims precise

The upload workflow covers PDF and Markdown files. Google Docs uses a separate Google Drive Picker flow; selecting a connected account alone does not import documents. Notion, Confluence, and OneDrive knowledge connections are currently unavailable. For material stored there, ask its owner for a reviewed PDF or Markdown copy and agree how revisions will be maintained.

Resonoon’s AI chatbot widget provides context for the assistant’s website experience. Reliable knowledge starts with approved files, a deliberate selection, visible verification, and tests tied to the actual content. Uploading is one step in that process, not a substitute for source ownership or review.