Skip to main content

How Witzo Works

Understand the path from signup to grounded answers, including knowledge processing, usage tracking, and retraining.


Overview

Witzo follows a structured pipeline. From account creation to AI response generation, every step is tracked and validated so your widget answers accurately and respects plan limits.

1. Account creation - Users sign up or log in with Email OTP or Google authentication, then enter the guided setup flow.

2. Widget creation - A widget key is generated to connect your site, validate usage, and route conversations.

3. Website scraping - Witzo crawls submitted URLs, extracts readable text, and filters unsupported pages.

4. Response generation - Relevant knowledge chunks are retrieved and used to generate grounded answers for visitors.

Visitor Query Lifecycle

Follow these steps each time a visitor sends a message:

  1. Message sent - The widget sends the visitor message to the Witzo backend
  2. Verification - The system verifies the widget key and checks plan limits
  3. AI answer - Knowledge retrieval runs, then the AI generates a grounded response
  4. Recorded - Usage is recorded and the response appears in the widget

Retraining

When you update your data sources, Witzo refreshes the indexed content and replaces outdated knowledge.

  1. Go to Dashboard - Open Data Sources from your dashboard
  2. Update content - Add, modify, or remove URLs and uploaded documents
  3. Click retrain - Rebuild the knowledge index with the latest information

Behind The Scenes

When retraining occurs, the following processes run:

  • Re-scrapes content - The system re-reads updated source pages and documents
  • Re-chunks data - Updated content is split into smaller retrieval-ready chunks
  • Rebuilds index - The refreshed data is reindexed for future conversations

Important Notes

Limitations

  • Access - Private or password-protected pages are not scraped by default
  • Language - Multilingual support depends on source content quality
  • Enterprise - CRM integration remains Enterprise-only