Core concepts
The vocabulary of AnyBot, space, agent, knowledge, abilities, memory, channels, contacts, leads, and AnyBot Tokens.
Almost everything in AnyBot is built from a small set of nouns. Learn these once and the rest of the docs read easily: a space is your isolated workspace, an agent is the trainable AI inside it, knowledge is what it answers from, abilities are what it can do, memory is what it retains, and channels are how customers reach it. The people who arrive become contacts and leads, and every AI action is metered in AnyBot Tokens (ABT). This page is a hub. Each term links to its full section.
The vocabulary
| Term | In one sentence |
|---|---|
| Space | An isolated business environment: its own agents, contacts, content, billing, team, and brand; agencies run one per client. |
| Agent | A trainable virtual employee that answers, qualifies, books, and sells inside a space. |
| Knowledge | The documents and website content an agent answers from, and only from, so replies stay grounded in your content. |
| Ability (tool) | A real action an agent can take, 122 tools across 19 integration families, shown as Skills in the agent editor. |
| Memory | Long-term facts you teach by chatting as a manager, plus within-conversation working memory. |
| Channel | A place a customer reaches the agent: 8 channels including WhatsApp, Instagram, web chat, email, SMS, and voice. |
| Contact | A person who reaches your agent, tracked per contact in the unified inbox, and syncable to your CRM. |
| Lead | A contact who signals intent; agents capture them with a public-safe lead-capture ability. |
| AnyBot Token (ABT) | The unit that meters AI usage across 6 ABT pools, windowed to your billing date. |
| BotFather | The in-app AI operator that builds and configures your space when you ask it in plain English. |
| Marketplace | A library of pre-built agents you can import with one click, then customize. |
How they fit together
Think of it as one container with everything nested inside. A space holds everything. Inside it you create one or more agents. Each agent draws on knowledge, is given abilities, and keeps memory. That's the anatomy of a single agent. You then connect channels so customers can reach it. The people who message become contacts; the ones who show buying intent become leads. Underneath, every AI reply, tool call, and media generation is metered in ABT, and everything (conversations, content, billing, team, audit trail) is scoped to the space.
The pieces in motion
Nothing here works alone. Knowledge without an agent is just files; an agent without channels can only be tested in the built-in chat; abilities without connected integrations stay dormant. The typical order is: create a space, build an agent and train it on knowledge, grant the abilities it needs, connect a channel, then watch conversations and leads flow into the unified inbox. Memory improves the agent over time as you correct it, and ABT quietly tracks the cost of all of it.
AnyBot meters AI work as ABT across 6 pools. Your plan sets the monthly allowance, see ABT tokens and plans.
A worked example
A clinic creates a space, then an agent trained on its services and hours as knowledge. It grants the agent a calendar ability so it can check availability and book. It connects WhatsApp and web chat as channels. A patient messages on WhatsApp. They're now a contact in the inbox. They ask for an opening; the agent books it (an ability), captures their name and reason for visit (a lead), and remembers their preferred time in memory for next time. Every AI turn in that exchange draws down ABT.
Limits & honesty
Agents answer from your knowledge, not general world facts. That's a feature, not a gap. Nearly all mutations are owner-only (CRM, inbox, finance, and internal-data actions) and can never be triggered by an end-user; a small, deliberate set of public-safe actions (lead capture and appointment booking) are the exceptions, and they're the only writes an end-user can trigger. The split is enforced by design, not by prompt wording.
FAQ
Is an agent the same as a space? No. A space is the container; you can run several agents inside one space, each with its own knowledge and abilities.
Where do contacts and leads live? In the unified inbox for the space, per contact, and, if you connect a CRM, they can sync there too.
Do I pay per message? AI work is metered in ABT against your plan's monthly allowance, not per message. See ABT tokens.
What's the difference between knowledge and memory? Knowledge is the content the agent answers from; memory is what it retains about your business and each conversation over time.