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

# FAQ

> Answers to common customer questions about Sozo CRM setup, workflows, and support.

# FAQ

## General

<AccordionGroup>
  <Accordion title="How long does setup usually take?" icon="clock">
    Most teams can complete first-pass setup in under one day, then refine workflows during week one.
  </Accordion>

  <Accordion title="Do reps get earnings visibility?" icon="badge-dollar-sign">
    Yes. Reps can track what they need, while payout logic remains centrally controlled by leadership.
  </Accordion>

  <Accordion title="Can we start small and expand later?" icon="chevrons-up">
    Yes. Start with core pipeline and commission workflows, then expand integrations in phases.
  </Accordion>
</AccordionGroup>

## Integrations and data

<AccordionGroup>
  <Accordion title="What should we integrate first?" icon="plug">
    Start with your daily-critical tools: proposal/design, notifications, and payout visibility systems.
  </Accordion>

  <Accordion title="How do we avoid sync conflicts?" icon="shield-check">
    Assign one source of truth per field and use stable IDs across systems.
  </Accordion>
</AccordionGroup>

## Access and security

<AccordionGroup>
  <Accordion title="How should we assign roles?" icon="users">
    Keep reps scoped to their workflows, managers scoped to team oversight, and reserve admin for system owners.
  </Accordion>

  <Accordion title="What happens when someone leaves?" icon="user-minus">
    Disable access immediately and review ownership of automation or integration credentials tied to that user.
  </Accordion>
</AccordionGroup>

## Technical questions

<AccordionGroup>
  <Accordion title="Can we use Sozo docs with AI tools?" icon="terminal">
    Yes. Use the hosted MCP endpoint at `https://docs.thesozocrm.com/mcp`. See **[Hosted MCP](/mcp)** for setup steps.
  </Accordion>

  <Accordion title="How do we authenticate API requests?" icon="key-round">
    Use an authenticated user token (Firebase ID token) in the `Authorization: Bearer <token>` header.
  </Accordion>

  <Accordion title="What should we do about duplicate webhook events?" icon="refresh-cw">
    Treat webhooks as at-least-once delivery. Build idempotent handlers keyed on stable event or record IDs.
  </Accordion>

  <Accordion title="Where should technical users start?" icon="code">
    Start with **[API Reference](/api-reference/introduction)**, then move to **[Integrations](/integrations)** for rollout patterns.
  </Accordion>
</AccordionGroup>

## Support

* **Support email:** [support@thesozocrm.com](mailto:support@thesozocrm.com)
* **Product access:** [thesozocrm.com](https://thesozocrm.com)