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

# Overview

> What OurAiCalling is and how the pieces fit together

OurAiCalling 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.

## 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**       | An outbound calling job over a list of leads, executed by the server-side dialer.                                                          |
| **Knowledge base** | Documents your assistant can search during a call (RAG).                                                                                   |
| **Tenant**         | A white-label workspace with its own domain, branding, plans, and users.                                                                   |
| **Plan**           | The subscription that gates features and limits (assistants, parallel calls, minutes, and more).                                           |

## Built for Europe

The voice engine runs in the EU (Frankfurt), and SIP traffic can be pinned to EU infrastructure. Consent announcements with conditional recording are built in — recording only starts after the caller agrees, which matters for GDPR and German law (§201 StGB). Calling windows and do-not-call lists in campaigns support UWG-compliant outbound calling.

## 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>