Eckho Bot is a web platform for building AI bots that answer questions from your own content. You create a bot, add knowledge to it (upload documents, point it at a web page, paste text), and the bot can then hold a conversation about that material — giving grounded answers with citations back to the source.

You can use a bot yourself inside the Eckho Bot workspace, or publish it as an App — a clean, shareable chat page you send to customers, staff, students, or anyone else, with no Eckho Bot account required on their side.

Everything runs in your web browser at eckho.ai. There is nothing to install.

Common use cases

Bots people build with Eckho Bot (from eckho.ai/usecases):

The pattern is always the same: take material that lives in someone's head or scattered documents, train a bot on it, and give people a link to ask it directly.

How answers work, in brief

When someone asks a bot a question, Eckho searches the bot's knowledge base for the most relevant passages, then asks a large language model (GPT) to write an answer using only those passages. The answer comes back with citations naming the source document and page. If the knowledge base does not contain the answer, the bot says so rather than guessing.

What Eckho Bot is not

• It is not a general chatbot that knows everything — a bot only knows what you have added to it (plus light general knowledge, and only with permission — see Section 15).
• It is not a website builder — Apps are single chat pages, not full sites.
• It does not change or store your original files as documents you can download back — it reads them to build a searchable knowledge base.

Sign in

Go to eckho.ai and log in. Every Eckho Bot screen requires a logged-in account; you will be sent to the login page if your session has expired.

The guided onboarding

The first time you use Eckho Bot, a short prompt appears on the Dashboard to walk you through the three things every new bot needs. It advances as you complete each stage:

1. Create your first bot — you have no bot yet.
2. Train your bot — you have a bot but it has no knowledge.
3. Create and share an App — your bot is trained but not published.

Each prompt has a button that takes you straight to the right screen. Click outside the card to dismiss it for the session; it comes back next visit until that stage is done.

The 3-step path

1. Create a bot— + New Bot in the left menu (Section 6).
2. Add knowledge— open the bot, go to Add Knowledge, upload files or add a URL (Section 8).
3. Use or share it— chat with it in Quick Chat / Studio, or publish an App (Section 16).

Every Eckho Bot screen shares the same dark left menu. On a phone it collapses behind the menu button in the top bar.

Navigation between screens happens without a full page reload.

The Dashboard is your home screen. It lists every bot you own.

• Grid View / Table View — toggle at the top; your choice is remembered.
• Each bot shows its icon, name, type badge (Personal or Business), created date, and description.
• If you have no bots yet, the Dashboard shows a prompt to create your first one with the + New Bot button in the left menu.

Per-bot quick actions

Each bot card / row has four buttons:

Click + New Bot in the left menu (or the onboarding prompt's "Create My First Bot" button). A dialog collects:

• Bot name — what the bot is called throughout the workspace and, by default, in Apps.
• Description — a short line shown on the Dashboard.
• Bot type — Personal or Business. This is a label for your own organisation; it does not change how the bot works.
• Bot icon — optional; a coloured initial is used if you don't set one.

When you create the bot, Eckho sets up its private knowledge base behind the scenes. The new bot appears in the left menu and on the Dashboard immediately, ready for you to add knowledge.

Build & Share (also reached by More on the Dashboard) is the bot's control panel. It is organised into tabs:

On a phone the tabs collapse into a dropdown button showing the current tab name.

The Add Knowledge tab (also titled Ingest Data) is where a bot learns. There are three ways to add knowledge:

The pre-flight check

Before anything is ingested, Eckho runs a quick check and shows one of three results:

Credit estimates for files are approximate — the actual amount used can differ slightly.

What adding knowledge costs

• Adding knowledge spends credits. The estimate is shown before you confirm.
• It also uses capacity — the total amount of knowledge (in characters) your plan lets a bot hold. When a bot is near capacity, remove old Sources you no longer need (Section 11) or upgrade.
• Chatting with the bot afterwards does not spend credits — see Section 18.

After ingesting

Processing runs in the background. Once it completes, the content is searchable and the bot can answer from it. New Sources appear under the Sources tab.

A non-removable platform safety layer is always applied on top of your system prompt, so bots cannot be talked into unsafe behaviour or into revealing configuration.

A simple form that gives the bot a consistent identity. It generates a natural-language personality paragraph from five short answers:

• Your name is… (e.g. Jarvis)
• You like being… (e.g. Professional, witty, and helpful)
• You are a helpful… (e.g. Real Estate Assistant)
• You can help with… (e.g. Local property laws and current market trends)
• Your owner's name is… (your name or your organisation)

Click Generate & Save Personality. The generated paragraph is shown below the form and is combined with your System Prompt on every answer, so the bot always speaks in this voice while staying grounded in your knowledge base.

The Sources tab lists every item that has been added to the bot — each uploaded file, each URL, each crawl.

• See what the bot currently knows.
• Delete a Source to remove its content from the knowledge base. The bot stops answering from it, and its capacity is freed.
• Deleting a Source does not refund credits already spent to ingest it.

The Basics tab holds the bot's identity and administrative settings:

• Bot name and description.
• Bot type (Personal / Business).
• Bot icon.
• Plan / access information for the bot.

Changing the name here updates it across the workspace.

Studio is the all-in-one screen for working with one bot. Everything — chats, the conversation, and knowledge management — is on a single page in four columns.

The dividers between columns can be dragged to resize them; your widths are remembered.

Column 2 — Chats / Projects

A toggle switches Column 2 between two modes:

• Chats — a flat list of all your conversations with this bot. Click one to open it in Column 3; start a new one at any time.
• Projects — conversations grouped into projects. Expand a project to see its chats. Use projects to keep, say, "onboarding questions" separate from "billing questions".

The current chat is highlighted. Loading indicators show while lists fetch.

Column 3 — The chat

The full bot conversation — identical to Quick Chat. See Section 15 for how it behaves (streaming answers, citations, conversation memory, Stop button, Copy/Share).

Column 4 — Add Knowledge and Sources

• Top: the same Add Knowledge tools as the Build & Share tab (upload files, add a URL) — so you can train the bot without leaving the conversation.
• Bottom: the Sources list with delete, so you can see and prune what the bot knows while you work.

Quick Chat is a stripped-down, full-screen conversation with one bot — the left menu plus a chat list plus the conversation, nothing else. Use it when you just want to talk to a bot and don't need the knowledge tools that Studio adds.

Quick Chat and Studio share the same underlying chat and the same saved history — a conversation you start in one appears in the other.

However you reach it — Quick Chat, Studio, or a published App — the conversation behaves the same way.

How the bot answers

1. Your message is searched against the bot's knowledge base.
2. The most relevant passages are selected and re-ranked for quality.
3. GPT is given those passages and asked to answer using only them, in the bot's configured voice.
4. The answer streams back, followed by its citations.

What you see

• Streaming answers — text appears as it is written.
• Markdown formatting — headings, lists, tables, bold, links, code.
• Citations — the answer names the source file (and page) the information came from.
• Welcome message — shown at the top of a fresh chat if the bot has one configured.
• Stop button — cancels an answer mid-generation.
• Copy / Share — copy a single message, or copy/share the whole conversation.
• The input box re-focuses after each answer so you can keep typing.

Conversation memory

The bot remembers the recent back-and-forth within a conversation (about the last ten exchanges), so follow-up questions like "and what about the second one?" work. In a published App, this memory lasts for the browser session and is cleared on refresh.

When the answer isn't in the knowledge base

The bot will say it could not find the answer in the current documents and ask whether you want it to answer from general knowledge instead. It only uses general knowledge after you say yes, and labels that part of the answer clearly. It does not have live internet access.

If answers look wrong

• The knowledge base may be missing the document — add it under Add Knowledge.
• A document may be out of date — check Sources and replace it.
• The question may be too broad — ask something more specific, or name the document.
• A scanned PDF may have contributed no readable text — use a text-based version.

An App is a public-facing chat page for one bot that you share with your own audience. They do not need an Eckho Bot account — they just open the link and chat.

Creating an App

Build & Share → Create App → + Create New App:

Save, and Eckho generates the share link. You can create several Apps for one bot (for example, a public one for your website and a password one for staff).

Managing Apps

Each App on the Create App tab shows its link with Copy and Share buttons, plus Edit and Delete. Deleting an App makes its link stop working immediately.

What a visitor sees

A clean chat page: the bot's welcome message, a message box, streaming answers with citations. Password-protected Apps show a password gate first. The App works on phones as well as desktop. Visitor conversations are not saved — there is no account to save them to — but memory works within their session until they refresh.

Best practice

• Use password-protected for anything internal or commercially sensitive.
• Give the App its own welcome message (set it in Bot Behaviour) that tells visitors what the bot can help with.
• Test the App link yourself, logged out or in a private window, before sharing it.

My Collections lets you group several Apps into one shareable panel — useful when you want to hand someone a single link that opens a small menu of bots rather than one bot.

Creating a Collection:

• Collection Name and Description.
• Collection Icon (optional).
• Sharing Type — Public or Password-protected (with an access password).
• Assign Apps — tick the Apps to include. An App can belong to more than one Collection.

Each Collection has its own link with Copy, Share and Open URL. Grid and Table views are available, and Collections can be edited or deleted.

Plans

Your live figures are shown in Account & Bots and Usage.

Credits — what they measure

Credits measure training, not chatting.

• Adding knowledge spends credits — uploading files, adding URLs, crawling. The pre-flight check estimates the cost before you confirm.
• Chatting does not spend credits. Your own conversations and your App visitors' conversations are tracked for analytics only and are never deducted from your balance. Audience chats on shared Apps are always free.
• Plan credits refresh monthly. You can also buy top-up credits (about $1 per 1,000 credits) — these never expire and carry over month to month.
• Removing a Source does not refund the credits spent to add it.

Capacity

Separately from credits, each bot can only hold so much total hosted knowledge — measured in characters, but easier to think of in pages (see the table above). A rough guide: a page of a normal document ≈ 1,000 characters; a web page or a PDF page ≈ 200 characters of extracted text. The pre-flight check warns you as a bot nears its capacity. To make room: delete Sources you no longer need, or move to a higher plan.

The Usage screen

Settings → Usage shows:

• Credits Balance — what you have left.
• Credits Used — training spend in the selected month.
• Bot Usage Breakdown — per-bot upload and knowledge-credit figures.

Billing

Settings → Billing handles your subscription and payment details, and is where you upgrade or change plan.

Eckho is two products (with a third in development), easy to confuse:

• Eckho Desktop — the left menu's Eckho Desktop item links to install it or read more. If your question is about indexing local folders, a file viewer, or a desktop agent, use the Eckho Desktop guide, not this one.
• Eckho Companion — a personal-memory product, listed on eckho.ai as in development. Not available yet; no guide.

The two products share the same knowledge idea — make your knowledge usable — but Eckho Bot hosts your content to share it, while Eckho Desktop keeps everything on your machine and is not for sharing.

Under Settings in the left menu:

Bot

One AI assistant with its own knowledge base, behaviour, personality and Apps.

Knowledge base

Everything added to a bot — what it answers from.

Add knowledge / ingest / train

Feeding content into a bot (file upload, URL, or crawl).

Source

One ingested item (a file, a page, a crawl), listed on the Sources tab.

Pre-flight check

The Allowed / Warning / Blocked check shown before an ingest, with a credit and size estimate.

Chat

A saved conversation with a bot.

Project

An optional grouping of related chats, in Studio.

App

A shareable public chat page for one bot (Public, Password-protected, or Invite-only).

Collection

A shareable panel grouping several Apps under one link.

Credit

The unit measuring training usage. Adding knowledge spends credits; chatting does not.

Capacity

The maximum total knowledge (in characters) a bot can hold on your plan.

System Prompt

The core instructions defining how a bot answers. Edited in Bot Behaviour.

Welcome Message

The first message shown in a new chat or App.

Voice & Style

The personality builder — five fields that generate the bot's persona.

Plan / tier

Subscription level: Trial, Startup, Standard, Pro, Advanced, Enterprise.

Studio

The four-column working view for one bot.

Quick Chat

A minimal full-screen chat with one bot.

Build & Share

The tabbed settings/management screen for one bot.

Bump -g2, -g3, … for text-only corrections against the same plugin version. Start a new v<plugin-version>_g1 file when ragteck_plugin ships a version with material user-facing changes.