Skip to main content

Retraining and Updating Knowledge

Retrain your data sources to ensure the AI answers reflect current website content, removed pages, and updated documents.

Why Retraining Matters​

Witzo relies on indexed content. If your website or documents change, retraining makes sure the agent uses the latest information instead of stale data.

When to Retrain​

  • website content changes
  • pages are removed from your source
  • documents are updated or replaced
  • pricing, policies, or product details change

Full Retrain vs Selective Refresh​

ActionBest forWhat it does
Full retrainMajor updates across many pages or filesReprocesses the whole connected source and rebuilds the index
Manual re-scrapeFast refresh of website contentPulls the latest website content before retraining
Targeted document replacementOne updated documentReplaces a specific file and then retrains the source

Retraining refreshes the indexed knowledge base.

Manual Re-Scrape​

Use manual re-scrape when you need the latest website content immediately.

  1. Go to Dashboard > Data Sources.
  2. Select your website source.
  3. Click Re-Scrape Now.
Re-scrape action in the dashboard

Manual re-scrape detects modified pages and newly added content before retraining.

Auto Re-Scrape Intervals​

Choose an interval that matches how often your website changes:

  • every 7 days
  • every 15 days
  • every 30 days
1

Enable Auto Re-Scrape

Screenshot for step 1: Enable Auto Re-Scrape
2

Choose a Scrape Interval

Screenshot for step 2: Choose a Scrape Interval

Runtime Expectations​

  • Retraining time depends on source size and document count.
  • Small updates generally finish faster than full source refreshes.
  • The widget can remain published while the knowledge base is being refreshed, but answers may continue using the previously indexed content until the retrain completes.
  • For large changes, retrain during lower-traffic periods if content accuracy is business-critical.
  • No global per-plan retrain frequency cap is published in this docs set. If your workspace has an operational limit, the dashboard action state should be treated as the source of truth.

Handling Large Updates​

For major content changes:

  • remove outdated sources first
  • confirm new content is live
  • run a full retrain

This prevents duplicate or conflicting information from being indexed together.