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

# Overview

> Embed AI-powered SMS conversations, lead recovery, and document collection directly into your platform.

# Partner Integration

Recover provides an AI SMS agent that automates lead recovery, follow-up sequences, and document collection via text message. The Partner API lets you embed Recover into your own platform so your customers get the full experience — white-labeled under your brand — without any setup friction.

## Two Integration Paths

<CardGroup cols={2}>
  <Card title="Embed (iframe)" icon="window-maximize">
    Full dashboard inside your app — conversations, leads, sequences, settings. **1 line of HTML.**
  </Card>

  <Card title="REST API" icon="code">
    Programmatic control — push leads, read conversations, trigger sequences. **Standard REST calls.**
  </Card>
</CardGroup>

Most partners use **both**: the iframe for the end-user dashboard, and the API for backend automation (e.g., pushing leads from your pipeline, reading usage stats for billing).

## What Your Customers Get

* AI-powered SMS conversations with natural language
* Automated follow-up sequences (fixed messages + AI-generated)
* Document collection checklists (bank statements, IDs, pay stubs, etc.)
* Manual human takeover at any point
* Company knowledge base (files + URLs) that trains the AI
* Team management with per-agent phone numbers and call forwarding

## Multi-Tenancy Model

```
Partner (your platform)
  └── Partner API Key
        ├── Sub-Account A (Customer 1)
        │     ├── Phone Number (+1...)
        │     ├── Leads & Conversations
        │     ├── Sequences
        │     ├── Checklists
        │     ├── AI Configuration
        │     └── Context Files/URLs
        ├── Sub-Account B (Customer 2)
        │     └── ... (fully isolated)
        └── Sub-Account C (Customer 3)
              └── ...
```

### Data Isolation

* Each sub-account has a completely isolated data store
* Leads, conversations, messages, sequences, and settings are never shared between sub-accounts
* Your Partner API key can access all sub-accounts, but each sub-account's embed token only accesses that specific account
* Phone numbers are dedicated per sub-account — no sharing

### Phone Numbers

Each sub-account gets a dedicated phone number for SMS. Numbers can be:

* **Auto-provisioned**: Omit `phone_number` on account creation and one is assigned automatically
* **Bring your own**: Pass an existing Twilio number during account creation
* **Ported**: Transfer existing numbers to the platform (contact support)

All numbers are TCPA/CASL compliant with built-in opt-out handling (`STOP`, `UNSUBSCRIBE`, etc.).