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

# How does ServiceTitan data sync into Avoca?

> Use CRM Sync to review configured ServiceTitan entities, health, and logs.

Avoca imports configured ServiceTitan data so enabled products can use the relevant CRM catalog and operational records. Sync status is tracked and reported per entity; this is not a promise that every ServiceTitan object or field is copied.

Open [the Avoca dashboard](https://dashboard.avoca.ai), then go to **Settings → CRM Sync**.

## Configuration

Use **Configuration** to review active entities and their sync state. Common entities can include customers, contacts, locations, jobs, appointments, bookings, estimates, invoices, memberships, business units, job types, tags, campaigns, technicians, and employees.

Available entities depend on the integration and team configuration. Customer-facing rows report status; they do not provide per-entity schedule, run, or backfill controls. **Enable All** and **Disable All** affect the complete ServiceTitan sync set and should be used only for an intentional full rollout or pause.

## Analytics and logs

* **Analytics** summarizes sync health and volume.
* **Logs** lets you filter completed and failed runs by time and entity.

If CRM data is missing in Avoca:

1. Confirm the entity is active.
2. Check the most recent run and failure logs.
3. Verify the record exists and is active in ServiceTitan.
4. Allow for the configured sync schedule; not every change appears immediately.
5. Open **Settings → Support** with the entity name, approximate time, and non-sensitive record identifier.

Writes from Avoca back to ServiceTitan are separate, product-specific actions rather than a universal reverse copy of every synced entity.