> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Famulor overview

> What Famulor's AI voice assistants do and how the platform fits together

Famulor lets you build, deploy, and operate AI voice assistants that make and receive real phone calls — and talk to visitors on your website. It is a multi-tenant, white-label platform: agencies and resellers can run it under their own domain, branding, and pricing.

Assistants work around the clock and take several conversations at the same time — up to the simultaneous-call capacity in your plan — so callers are answered instead of queued. Routine questions, bookings, and qualification happen without a person involved, and your team steps in only for the calls that actually need one.

## What you can build

<CardGroup cols={2}>
  <Card title="Inbound reception" icon="phone-arrow-down-left" href="/telephony/inbound-outbound">
    A phone number that answers instantly, qualifies callers, books appointments, and transfers to humans when needed.
  </Card>

  <Card title="Outbound campaigns" icon="phone-arrow-up-right" href="/campaigns/overview">
    Automated calling campaigns with a parallel dialer, retry rules, calling windows, and voicemail handling.
  </Card>

  <Card title="Multi-step call flows" icon="diagram-project" href="/flow-builder/overview">
    Visual flows with specialized agents, conditions, data collection, HTTP tools, and warm transfers.
  </Card>

  <Card title="Web voice & chat" icon="message" href="/web-widget">
    Embed the same assistants as a voice or chat widget on any website.
  </Card>
</CardGroup>

## Core concepts

| Concept            | What it is                                                                                                                                 |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Assistant**      | A configured AI agent: prompt or flow, engine mode, models, voice, and behavior settings.                                                  |
| **Flow**           | An optional visual call script — multiple agents connected by labeled edges, plus tools, conditions, transfers, and data-collection steps. |
| **Phone number**   | A number bought through the platform or brought via your own SIP trunk, routed to an assistant.                                            |
| **Campaign**       | Organized outbound calling for a contact list, with schedules, retries, and results.                                                       |
| **Knowledge base** | Documents your assistant can use to answer questions during a conversation.                                                                |
| **History**        | The unified log of every conversation — calls, chat, email, and messaging — with transcripts, recordings, and outcomes.                    |
| **Workspace**      | The shared environment for your team, assistants, channels, and settings.                                                                  |
| **Plan**           | The subscription that includes your workspace capabilities and usage limits.                                                               |

### How a call flows

1. **The call starts.** A caller dials your number (inbound), or the assistant places the call from a campaign, a single test, or the API (outbound).
2. **The assistant listens.** It follows what the caller says as they speak and detects when a turn is finished.
3. **It decides what to say.** Its prompt or flow, plus any tools and knowledge base it has access to, produce the next reply or action.
4. **It speaks.** The reply comes back in the assistant's selected voice.
5. **It acts.** It answers questions, collects information, books an appointment, or transfers to a person when the conversation calls for it.
6. **Everything is recorded.** The transcript, recording, and outcome land in History automatically — ready to review or build an automation on.

How steps 2 to 4 run internally depends on the assistant's [engine mode](/assistants/engine-modes): separate listening, reasoning, and speaking stages, or one continuous voice loop.

## Built for Europe

Consent announcements with optional recording are built in, and recording can begin only after the caller agrees. Calling windows and do-not-contact lists help teams follow their privacy and outreach requirements.

## Where to go next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create your first assistant and test it with a web call in under five minutes.
  </Card>

  <Card title="API & MCP" icon="code" href="/api/mcp">
    Automate everything via REST or connect Claude/ChatGPT through the MCP endpoint.
  </Card>
</CardGroup>