What is EchoAI, Core concepts
EchoAI is an AI assistant platform: you upload your content — website, FAQ, PDFs, videos, product catalog — EchoAI turns it into a knowledge base, and gives you a chat widget you embed on your own site. Your visitors ask questions in their own language, and the assistant answers strictly from your content, with sources cited. Along the way it captures leads, fills in contracts, and every conversation is reviewable in your dashboard. This page gives you the conceptual map in one read — for the details we link to the right guide at every point.
On this page
Core concepts
These are the main concepts the rest of the manual builds on. Each one links to its detailed guide.
Organization
The top-level unit everything belongs to: assistants, content, leads, contracts, and your subscription. One account can have several organizations, and you can invite teammates. Use the organization switcher at the top of the dashboard to move between them. Details: Team & roles.
Assistant
A standalone AI chat with its own knowledge base, settings, and appearance. A organization can hold several assistants (your plan caps how many). There are three types:
| Type | What it's for |
|---|---|
| Public | A visitor-facing assistant embedded on your website — support, FAQ, product recommendations. |
| Internal | For your team only: internal knowledge base, onboarding material, process docs. |
| Contract | Generates and guides fillable contracts based on a template, inside a conversation. |
Details: Managing assistants.
Content and knowledge base
The knowledge base is the collection of content an assistant draws its answers from — it won't answer about anything it has no content on. A single content item is one unit: one text, one scraped URL, one PDF (up to 50 pages), or one YouTube video. There are two ways to add it:
- Manual upload — you add items one at a time (text, URL, PDF, DOCX, YouTube video). You keep them up to date.
- Synced source — you connect it once (website, WordPress, Framer, YouTube channel, webshop), and it updates itself in the background.
Details: Building your knowledge base.
Lead
The contact details of an interested visitor (name, email, phone, and so on) that the assistant collects during a natural conversation — reading intent rather than matching keywords. Leads accumulate in the dashboard, where you review them by status and quality. Details: Capturing leads.
Contract
From an uploaded template (PDF/DOCX), EchoAI detects fillable fields, then walks through filling them in a conversation or in the dashboard — the result is a finished, downloadable document. A completed contract can also be shared with external parties via a public link. Details: Managing contracts.
Plan and quotas
Your plan (Free, Essential, or Pro) sets your quotas: how many assistants you can have, how much content you can store, and how many messages you can receive.
| Quota | Free | Essential | Pro |
|---|---|---|---|
| Assistants | 1 | 1 | 5 |
| Content items | 75 | 150 | 1000 |
| Messages / month | 75 | 150 | 1000 |
The content quota is a cumulative cap: it never resets; stored items take up space until you delete them. The message quota resets on your billing anniversary (on renewal). Details: Limits & quotas.
Embedding
The process of putting your assistant on your website. Most methods are no-code: a floating chat button via a pasted snippet, an inline widget, a WordPress plugin, or Framer. Details: Embedding on your website.
Visitor and operator
Two sides of the same assistant:
- Visitor — the person chatting with the embedded widget on your website. No account needed; they ask in their own language.
- Operator — you and your team, who set up the assistant in the dashboard, manage content, and review conversations and leads.
How it works end to end
Here's how the concepts come together into a single flow — from uploading content to the visitor conversation and your dashboard follow-up.
- You upload content. Add text or PDFs manually, or connect a synced source (website, WordPress, webshop). Everything goes into the assistant's knowledge base. → Building your knowledge base
- You set up the assistant. Pick the type (public / internal / contract), set the tone, guidelines, and appearance, then try it in the test chat. → Managing assistants
- You embed or share it. Put it on your website (floating button, widget, WordPress, Framer), or simply share the direct link. → Embedding on your website
- The visitor chats. The visitor asks in their own language, the assistant answers from the knowledge base — marking sources as citations, and showing product cards for webshops. → Chat features
- A lead or contract is created. If the visitor is interested, the assistant naturally asks for their contact details (a lead) or walks them through filling a contract. → Capturing leads, Managing contracts
- You follow up in the dashboard. Conversations, leads, and contracts all accumulate in the dashboard — review the history, manage leads, and refine the knowledge base based on real questions.
Where to start
- Getting started — step by step to your first working assistant.
- Managing assistants — types, settings, which one to choose.
- Building your knowledge base — manual uploads and synced sources.
- Embedding on your website — no-code deployment.