Manage Chatbot Documents (Upload + Library)
Upload a PDF and manage the library in about 5 minutes. Keep the page open until the upload finishes.
This guide helps you upload PDFs to the chatbot knowledge base and manage the document library. AVA checks the file first, then your browser sends it directly to S3. This guide also helps you review Agent Wiki conflicts and retry failed updates when the answer engine is Agent (Pi). If the answer engine is Agent (Pi), you also see an Agent Wiki status column and a Conflicts tab. AVA refreshes the list automatically while documents, ingests, or conflict updates are processing. When a terminal update finishes, AVA keeps refreshing document rows until the final status appears.
If the chatbot answer engine is RAG, you only see the document library. The Agent Wiki column, Conflicts tab, warning banner, and resolution workspace stay hidden. Switch to Agent (Pi) to review wiki updates.
Go to: Chatbot → Documents

Quick Reference
| Task | Where to click | Result |
|---|---|---|
| Start an upload | Upload Document | The upload flow opens |
| Choose a file | File picker | Streamliner checks the PDF first |
| Send the file | Browser upload step | The PDF goes directly to S3 |
| Add a purpose (optional) | Purpose step | Staff can see why the document exists |
| Finish upload | Finish | Document is created and queued |
| Keep the page open | Same browser tab | Upload and finalize do not interrupt |
| Wait for processing | Auto-refresh in the list | Status updates without manual refresh |
| Track wiki updates | Top progress panel | Visible only in Agent (Pi) mode |
| Review Agent Wiki sync | Agent Wiki column | Visible only in Agent (Pi) mode |
| Review conflicts | Conflicts tab or warning banner | Visible only in Agent (Pi) mode |
| Apply conflict resolutions | Staged conflict actions | Visible only in Agent (Pi) mode |
| Retry a failed update | Retry ingestion or Retry wiki update | Visible only in Agent (Pi) mode |
| Review ingest errors | Status badge or row message | See why a document did not finish |
| Search documents | Search bar + press Enter | List filters by keyword |
| Filter by status | Status dropdown | Show Active or Inactive only |
| Enable or disable | Enable / Disable action | Status updates after AVA finishes the ingest job |
| Delete documents | Delete or Delete (n) | File(s) removed after confirmation |
Plan Access
- Chatbot document tools require a paid plan.
- Free-tier accounts see an upgrade prompt instead of the document library.
To upgrade, go to Settings → Billing & Subscription.
Before You Start
Confirm these requirements:
- You have permission to manage Chatbot documents
- Your file is a PDF between 1 KB and 6 MB
- You are signed in to Streamliner
- You keep the tab open until upload and finalize finish
Upload a Document
-
Go to Chatbot → Documents
-
Click Upload Document
✓ The upload flow opens.
-
Select a PDF.
✓ Streamliner checks the file and prepares the upload.
-
Complete the browser upload step.
✓ The PDF uploads directly to S3.
-
(Optional) Add a short purpose, then click Continue
✓ The purpose is saved with the document.
-
Review the summary and click Finish
✓ You return to the document library.
Do not close, refresh, or navigate away while upload or finalize is running. If the tab closes, start a new upload from Chatbot → Documents.
What happens next
The document enters processing. The list keeps checking for updates until the file finishes indexing.
Understand Document Status Badges
| Status | What It Means |
|---|---|
| Processing | The document is being indexed and is not ready yet |
| Failed | The background processing job could not start or finish |
| Deleting | The document is queued for removal |
| Active | The chatbot can reference this document |
| Inactive | The document stays in the library but is not used |
New uploads may stay in Processing for a short time. The page updates the list automatically until the status changes. If processing fails, the latest error stays visible until you retry with a new upload.
Understand Agent Wiki Status
| Status | What It Means |
|---|---|
| Queued | AVA has sent the document to Agent Wiki and is waiting to start |
| Processing | Agent Wiki is indexing the document now |
| Ready | Agent Wiki can use this document |
| Failed | The ingest did not complete |
| Deactivating | Agent Wiki is turning off this document |
| Inactive | Agent Wiki is not using this document |
| Not synced | Agent Wiki ingest has not started yet |
You only see this column when the answer engine is Agent (Pi). When you disable a document, you may see Deactivating before Inactive. The page keeps refreshing while this status is Queued, Processing, or Deactivating. When the run reaches a terminal state, AVA refreshes document rows until their final status is visible. If the update fails and Retry ingestion appears, use it to restart the job. Inactive appears only after AVA finishes the Agent Wiki update. If retries run out, the row can show Failed instead.
Review Agent Wiki Conflicts
Use this when the page shows a conflict count or the Conflicts tab appears. The queue stays live while Agent Wiki works.
-
Open Conflicts.
✓ The knowledge review queue opens.
If a warning banner appears on Sources, you can click it instead.
-
Select a conflict from the list.
-
Compare Current wiki information and New document information.
-
Choose one resolution:
- Keep current wiki information
- Use information from the new document
- Provide authoritative information
- Ignore this conflict
-
If you choose Provide authoritative information, enter the exact replacement text.
-
Stage more conflicts if needed.
-
Click Apply.
✓ AVA shows the batch summary at the bottom. ✓ Ignored conflicts do not change the wiki.
-
Click Confirm and update wiki.
✓ AVA starts one wiki update for the whole batch. ✓ The progress panel appears above the tabs.
-
Wait for the progress panel to finish.
✓ Resolved conflicts move to Resolved, Ignored, or Superseded.
One submission can cover several conflicts. AVA still starts only one wiki update for that batch.
Search and Filter Documents
-
Type a keyword in the Search bar
-
Press
Enterto apply the search -
Use the Status dropdown to filter Active or Inactive
-
Click the X in the search bar to clear the search
✓ The full list returns.
Enable or Disable a Document
-
Find the document in the list
-
Click Enable or Disable
-
Confirm the action
✓ The status updates in the table. AVA keeps polling the ingest job until it finishes. You may see Deactivating for a short time before Inactive appears.
AVA now waits for the final ingest result before it updates the document status. If the background job cannot start, AVA marks the document Failed.
Delete Documents
Delete a Single Document
-
Click Delete on the document row
-
Confirm the action
✓ The document is removed from the list.
Delete Multiple Documents
-
Select documents using the left-side checkboxes
-
Click Delete (n) in the summary bar
-
Confirm the action
✓ The list refreshes after the delete job completes.
Troubleshooting
Only PDF files are allowed
What you see: Upload fails with a PDF-only error.
Fix:
- Convert the file to PDF
- Retry the upload
File size must not exceed 6MB
What you see: Upload stops and shows a size warning.
Fix:
- Compress the PDF or split it into smaller files
- Upload one file at a time
Finish button stays disabled
What you see: You cannot complete Step 3.
Fix:
- Wait for the browser upload step to finish
- If the file link is missing, reselect the PDF and upload again
- Try Finish again
The tab closed during upload
What you see: The upload does not appear in the library after you close or refresh the page.
Fix:
- Go back to Chatbot → Documents
- Start a new upload
- Keep the tab open until Finish completes
Search returns no results
What you see: The table is empty after you search.
Fix:
- Clear the search with the X
- Press
Enterafter typing a shorter keyword - Remove the Status filter to show all documents
A document stays in Processing
What you see: The status stays Processing for a long time.
Fix:
- Wait a few minutes for the automatic refresh to run
- Refresh the page once
- If it still does not change after 30 minutes, contact support
A document shows an ingest error
What you see: The row shows an error message or Agent Wiki shows Failed.
Fix:
- Read the error message on the document row
- Confirm the file is still a valid PDF and under 6 MB
- Upload a corrected copy of the document
- If the same error returns, contact support
A conflict update failed
What you see: The selected conflict shows Failed or the batch stops updating.
Fix:
- Click Retry wiki update
- Wait for the progress panel to restart
- Open the conflict again and confirm the final text
- If the same error returns, contact support
Document rows look stale after a conflict update
What you see: The conflict is resolved, but a source row still looks pending.
Fix:
- Keep the page open until the progress panel reaches a terminal state
- Wait for the list to refresh
- Refresh the page once if the row still looks stale
- If it still does not settle after 30 minutes, contact support
Agent Wiki controls are missing
What you see: You cannot see the Agent Wiki column, Conflicts tab, or review banner.
Fix:
- Check the chatbot Answer Engine
- If it is RAG, the Agent Wiki UI is hidden by design
- Switch to Agent (Pi) to manage wiki updates
- If Agent (Pi) is already selected, refresh the page and try again
Delete fails or does nothing
What you see: The document remains after confirming delete.
Fix:
- Refresh the page and check the status badge
- Try the delete again
- If it persists, contact support
Still Stuck?
Contact success@vouch-technologies.com if:
- ❌ Uploads fail after multiple attempts
- ❌ Documents stay in Processing for more than 30 minutes
- ❌ Documents show the same ingest error after you re-upload them
- ❌ Deletes do not complete after refresh
Helpful to include:
- File name(s) and status
- Screenshot of the document table
- Time the issue started