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

# LaraCopilot: Multi-Tenant Communications Platform

> LaraCopilot is a cloud communications platform for provisioning VoIP extensions, DID numbers, call queues, SMS, and AI modules across multiple tenants.

LaraCopilot is a multi-tenant cloud communications platform for service providers and enterprises. It gives you a single REST API to manage every layer of a modern phone system — from provisioning SIP extensions and DID numbers to routing call queues, sending SMS messages, recording CDRs, and running AI-powered modules — all scoped to isolated tenant accounts.

## Key capabilities

<CardGroup cols={3}>
  <Card title="VoIP extensions" icon="phone">
    Provision SIP extensions per tenant with individual secrets, voicemail settings, and device registrations.
  </Card>

  <Card title="DID numbers" icon="hashtag">
    Assign direct inward dialing numbers to tenants and route them to extensions or queues.
  </Card>

  <Card title="Call queues" icon="list">
    Build ACD queues with queue agents drawn from provisioned extensions.
  </Card>

  <Card title="SMS messaging" icon="message">
    Send and receive SMS through configurable gateways and track delivery receipts via webhooks.
  </Card>

  <Card title="Billing and CDRs" icon="receipt">
    Capture call detail records and manage access numbers and account verification workflows.
  </Card>

  <Card title="AI modules" icon="robot">
    Attach AI modules to tenant accounts for transcription, sentiment analysis, and call scoring.
  </Card>
</CardGroup>

## Architecture overview

LaraCopilot uses a single-admin, multi-tenant model. One platform administrator authenticates against the API and manages the full lifecycle of tenant accounts. Each tenant is an isolated customer organisation identified by a unique `slug` and `domain`. Resources such as extensions, DIDs, queues, CDRs, CRM contacts, and AI modules all belong to a tenant and are scoped to it at the data layer.

```
Admin (API session)
└── Tenant (slug, domain, timezone, max_extensions)
    ├── Extensions  (extension_number, secret, voicemail_enabled)
    ├── DID numbers
    ├── Call queues
    ├── SMS gateways
    ├── CDRs / billing
    ├── CRM contacts
    └── AI modules
```

All API routes are prefixed at `/api/`. Authentication is session-based: log in once with your admin credentials and include the session cookie on all subsequent requests.

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Authenticate, create a tenant, and provision your first extension in under 5 minutes.
  </Card>

  <Card title="Authentication" icon="lock" href="/authentication">
    Learn how sessions work, how to call `/api/admin/me`, and how to handle auth errors.
  </Card>
</CardGroup>