Skip to main content

Manage Chatbot Documents (Upload + Library)

Quick Setup

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.

RAG hides Agent Wiki controls

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

Documents management page showing the document library with search, filters, and action buttons


Quick Reference

TaskWhere to clickResult
Start an uploadUpload DocumentThe upload flow opens
Choose a fileFile pickerStreamliner checks the PDF first
Send the fileBrowser upload stepThe PDF goes directly to S3
Add a purpose (optional)Purpose stepStaff can see why the document exists
Finish uploadFinishDocument is created and queued
Keep the page openSame browser tabUpload and finalize do not interrupt
Wait for processingAuto-refresh in the listStatus updates without manual refresh
Track wiki updatesTop progress panelVisible only in Agent (Pi) mode
Review Agent Wiki syncAgent Wiki columnVisible only in Agent (Pi) mode
Review conflictsConflicts tab or warning bannerVisible only in Agent (Pi) mode
Apply conflict resolutionsStaged conflict actionsVisible only in Agent (Pi) mode
Retry a failed updateRetry ingestion or Retry wiki updateVisible only in Agent (Pi) mode
Review ingest errorsStatus badge or row messageSee why a document did not finish
Search documentsSearch bar + press EnterList filters by keyword
Filter by statusStatus dropdownShow Active or Inactive only
Enable or disableEnable / Disable actionStatus updates after AVA finishes the ingest job
Delete documentsDelete 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

  1. Go to Chatbot → Documents

  2. Click Upload Document

    ✓ The upload flow opens.

  3. Select a PDF.

    ✓ Streamliner checks the file and prepares the upload.

  4. Complete the browser upload step.

    ✓ The PDF uploads directly to S3.

  5. (Optional) Add a short purpose, then click Continue

    ✓ The purpose is saved with the document.

  6. Review the summary and click Finish

    ✓ You return to the document library.

Keep the tab open

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

StatusWhat It Means
ProcessingThe document is being indexed and is not ready yet
FailedThe background processing job could not start or finish
DeletingThe document is queued for removal
ActiveThe chatbot can reference this document
InactiveThe document stays in the library but is not used
About status updates

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

StatusWhat It Means
QueuedAVA has sent the document to Agent Wiki and is waiting to start
ProcessingAgent Wiki is indexing the document now
ReadyAgent Wiki can use this document
FailedThe ingest did not complete
DeactivatingAgent Wiki is turning off this document
InactiveAgent Wiki is not using this document
Not syncedAgent Wiki ingest has not started yet
About Agent Wiki status

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.

  1. Open Conflicts.

    ✓ The knowledge review queue opens.

    If a warning banner appears on Sources, you can click it instead.

  2. Select a conflict from the list.

  3. Compare Current wiki information and New document information.

  4. Choose one resolution:

    • Keep current wiki information
    • Use information from the new document
    • Provide authoritative information
    • Ignore this conflict
  5. If you choose Provide authoritative information, enter the exact replacement text.

  6. Stage more conflicts if needed.

  7. Click Apply.

    ✓ AVA shows the batch summary at the bottom. ✓ Ignored conflicts do not change the wiki.

  8. Click Confirm and update wiki.

    ✓ AVA starts one wiki update for the whole batch. ✓ The progress panel appears above the tabs.

  9. Wait for the progress panel to finish.

    ✓ Resolved conflicts move to Resolved, Ignored, or Superseded.

Why the batch matters

One submission can cover several conflicts. AVA still starts only one wiki update for that batch.

Search and Filter Documents

  1. Type a keyword in the Search bar

  2. Press Enter to apply the search

  3. Use the Status dropdown to filter Active or Inactive

  4. Click the X in the search bar to clear the search

    ✓ The full list returns.

Enable or Disable a Document

  1. Find the document in the list

  2. Click Enable or Disable

  3. 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.

Why the row can stay busy

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

  1. Click Delete on the document row

  2. Confirm the action

    ✓ The document is removed from the list.

Delete Multiple Documents

  1. Select documents using the left-side checkboxes

  2. Click Delete (n) in the summary bar

  3. 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:

  1. Convert the file to PDF
  2. Retry the upload

File size must not exceed 6MB

What you see: Upload stops and shows a size warning.

Fix:

  1. Compress the PDF or split it into smaller files
  2. Upload one file at a time

Finish button stays disabled

What you see: You cannot complete Step 3.

Fix:

  1. Wait for the browser upload step to finish
  2. If the file link is missing, reselect the PDF and upload again
  3. 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:

  1. Go back to Chatbot → Documents
  2. Start a new upload
  3. Keep the tab open until Finish completes

Search returns no results

What you see: The table is empty after you search.

Fix:

  1. Clear the search with the X
  2. Press Enter after typing a shorter keyword
  3. 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:

  1. Wait a few minutes for the automatic refresh to run
  2. Refresh the page once
  3. 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:

  1. Read the error message on the document row
  2. Confirm the file is still a valid PDF and under 6 MB
  3. Upload a corrected copy of the document
  4. 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:

  1. Click Retry wiki update
  2. Wait for the progress panel to restart
  3. Open the conflict again and confirm the final text
  4. 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:

  1. Keep the page open until the progress panel reaches a terminal state
  2. Wait for the list to refresh
  3. Refresh the page once if the row still looks stale
  4. 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:

  1. Check the chatbot Answer Engine
  2. If it is RAG, the Agent Wiki UI is hidden by design
  3. Switch to Agent (Pi) to manage wiki updates
  4. 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:

  1. Refresh the page and check the status badge
  2. Try the delete again
  3. 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