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

# Integrations

> Connect Sozo CRM with your core tools for cleaner handoffs and faster operations.

# Integrations

Connect only what your team uses daily, then scale in phases.

## Integration priorities

<CardGroup cols={2}>
  <Card title="Phase 1: Must-have" icon="zap">
    Proposal/design, notifications, and payout visibility tools.
  </Card>

  <Card title="Phase 2: Operational depth" icon="layers">
    Installer coordination, accounting sync, and analytics exports.
  </Card>
</CardGroup>

## Recommended rollout sequence

<Steps>
  <Step title="Map system owners">
    Assign an owner for each integration before enabling it.
  </Step>

  <Step title="Define source of truth">
    Decide which platform owns each field to avoid sync conflicts.
  </Step>

  <Step title="Dry run with test records">
    Validate create/update paths before production traffic.
  </Step>

  <Step title="Launch with monitoring">
    Watch first-week sync health and exception counts daily.
  </Step>
</Steps>

## Data reliability checklist

<Check>
  Use stable IDs, not names, as your cross-system join key.
</Check>

<Check>
  Make retry-safe writes (idempotent updates).
</Check>

<Check>
  Log failures with enough context to replay safely.
</Check>

## Technical implementation notes

<AccordionGroup>
  <Accordion title="Authentication and access model" icon="shield-check">
    Use authenticated requests tied to a real Sozo user context. Enforce access by role and team scope.
  </Accordion>

  <Accordion title="Idempotency and retries" icon="refresh-cw">
    Assume duplicate delivery can happen. Design create/update handlers so replaying the same event is safe.
  </Accordion>

  <Accordion title="Field ownership" icon="git-branch">
    Define one source of truth per field before go-live to prevent bidirectional overwrite conflicts.
  </Accordion>

  <Accordion title="Observability" icon="activity">
    Track success rate, retry counts, and dead-letter failures for every critical sync workflow.
  </Accordion>
</AccordionGroup>

## Need API-level details?

Use **[API Reference](/api-reference/introduction)** for auth patterns and integration implementation guidance.