Give Echo the facts it needs

Overview

The knowledge base is what makes an Echo feel specific instead of generic. Start with your website, add PDFs, DOCX files, FAQs, catalog metadata, internal notes, and media descriptions. Echo uses that source material to answer questions, recommend products, explain policies, and decide when it should ask a human for help. Public Echos can be indexed for discovery, while internal Echos stay private and noindexed. The goal is simple: your AI should know what your business actually knows, not improvise from generic internet patterns.

What you get

• Website import - Scan pages, pull clean text, infer logos, and turn public content into usable knowledge.
• Document import - PDF and DOCX content becomes searchable context for accurate answers.
• Media context - Product images and uploads carry descriptions that Echo can use in conversation.
• Internal mode - Business plans can create private intranet-style Echos blocked from indexing.

How it works

• 1. Import what already exists - Paste a URL or upload documents instead of rewriting everything manually.
• 2. Review extracted knowledge - Clean up facts, add missing FAQs, and decide what should stay private.
• 3. Publish with confidence - Echo cites your real content and avoids unsupported answers.

Who it is for

• Service businesses - Turn service pages, pricing documents, intake rules, and policies into instant answers.
• Internal teams - Use private Echos for onboarding, SOPs, product docs, and team knowledge.

Frequently asked questions