# Core Concepts

An Assistant defines how Reecall handles a conversation. A Channel connects callers to it, and an Exchange records what happened. These resources belong to a Project inside your Organization.

## How the resources fit together

<Mermaid chart={`flowchart LR
    O[Organization] --> P[Project]
    P --> A[Assistant]
    P --> C[Channel]
    C -->|routes calls to| A
    A -->|uses| M[AI models]
    A -->|uses| T[Tools]
    A -->|reads| K[Knowledge Bases]
    A -->|conversation recorded as| E[Exchange]
    E -->|entity event triggers| H[Hook]
    H -->|runs| W[Process]`} />

For example, a customer support Project can contain an Assistant with your support instructions and a Knowledge Base of product information. A WebRTC Channel lets customers speak to it from your website. Each conversation produces an Exchange, and a Hook can run a Process that sends a summary to your CRM.

## Explore the concepts

| Article | What it explains |
| --- | --- |
| [Organizations & Projects](/docs/managing-projects) | Resource ownership, project isolation, and choosing a Project for an integration |
| [Assistants & Models](/docs/assistants-and-models) | Instructions, voices, model architectures, Tools, and Knowledge Bases |
| [Channels & Calls](/docs/channels-and-calls) | SIP and WebRTC connections, reusable Channels, and individual calls |
| [Exchanges & Conversation Lifecycle](/docs/exchanges-and-conversation-lifecycle) | Running and completed conversations, transcripts, extracted data, and recordings |
| [Workflows & Hooks](/docs/workflows-and-hooks) | Workflow steps, stored Processes, event triggers, and how Blueprints differ |

To build a working browser conversation, follow the [Quickstart](/docs/quickstart). For API keys and access permissions, see [Authentication](/docs/authentication).
