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

# Partner Integration Guide

> Operate multi-tenant partner integrations with clear ownership boundaries, provisioning workflow, and support responsibilities.

# Partners own onboarding quality and operational accountability.

Callaro partners typically run implementation and managed operations across multiple downstream tenants. This guide defines responsibility boundaries so support, billing, and incident response are unambiguous.

## Ownership model

* **Partner-owned**: tenant provisioning workflow, partner key governance, per-tenant onboarding standards, first-line operational triage.
* **Customer-owned**: business policy (contact consent, script approvals), CRM data quality, internal access control.
* **Shared**: go-live sign-off, incident escalation paths, compliance reviews.

## Recommended tenant provisioning flow

<Steps>
  <Step title="Create tenant under partner namespace">
    Use partner APIs to create tenant and capture external customer account ID in your system of record.
  </Step>

  <Step title="Bootstrap baseline configuration">
    Provision default agent template, number routing defaults, webhook target, and billing entity associations.
  </Step>

  <Step title="Issue tenant-scoped keys with minimum scopes">
    Separate keys by workload: campaign ops, reporting export, and optional billing/reconciliation.
  </Step>

  <Step title="Run tenant acceptance tests">
    Validate one full campaign cycle, webhook receipt, and CRM upsert integrity before production launch.
  </Step>
</Steps>

## Multi-tenant key governance

* Keep partner key and tenant keys in separate secret stores.
* Enforce per-tenant key rotation windows.
* Record key owner, purpose, and expiry metadata.
* Disable unused tenant keys before offboarding completes.

## Support and escalation boundaries

| Issue class                      | Primary owner              | Escalation target        |
| -------------------------------- | -------------------------- | ------------------------ |
| Tenant configuration mismatch    | Partner operations         | Partner engineering lead |
| Call quality/runtime anomaly     | Shared (partner + Callaro) | Callaro support/on-call  |
| CRM mapping failures             | Partner implementation     | Customer CRM admin       |
| Billing allocation discrepancies | Partner finance ops        | Callaro billing support  |

<Warning>
  Partners should not run all tenants on one generic integration config. Maintain per-tenant webhook routing, key scopes, and ownership metadata for auditability.
</Warning>

## What to do next

* Review [`./webhook-events`](./webhook-events) for partner-facing event handling patterns.
* Review [`./white-label`](./white-label) if you manage branded downstream environments.
* Review [`../trust/security`](../trust/security) to align incident and key-governance controls.