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

# Configure and monitor CRM Sync

> Review synchronized CRM entities, monitor sync health, and investigate failed or stale runs.

Open **Settings → CRM Sync**. This page appears when CRM synchronization is enabled and your role has access to it.

CRM Sync is not the initial CRM connection. Use **Settings → Integrations → CRM** to connect the provider first; use CRM Sync to control and monitor the recurring data flow after that connection exists.

## Configuration

The **Configuration** tab groups available entities by purpose. For ServiceTitan, categories include core, CRM, memberships, scheduling, marketing, and metadata. The exact list differs by CRM.

Each entity row shows whether the sync is active, its last status, sync cursor, last successful time, and any visible error. Search for an entity or expand its category to inspect the datasets your Avoca products rely on.

The page also offers **Enable All** and **Disable All** as bulk actions. Individual entity rows are status-only for customers, so use the bulk actions only for an intentional full rollout or pause—not to troubleshoot one dataset.

<Warning>
  **Disable All** stops ongoing synchronization. CRM-backed audiences, analytics, booking context, and customer notifications can become incomplete or stale until the required syncs are re-enabled and catch up.
</Warning>

## Analytics

Use **Analytics** to review:

* Average sync duration
* Records synced
* Sync health over time
* Per-entity table statistics
* The count of active and healthy syncs

Filter by entity and time range so one high-volume sync does not hide a smaller failing one. A healthy connection does not guarantee every required entity is enabled; compare the active count with the products your team uses.

## Logs

Use **Logs** for run-level investigation. Filter to **Successful** or **Failed**, narrow the entity and time range, and inspect the most recent failure before changing configuration.

When data looks stale:

1. Confirm the CRM integration is still connected.
2. Confirm the required entity is enabled in **Configuration**.
3. Check **Analytics** for unhealthy or unusually slow syncs.
4. Find the latest entry for that entity in **Logs**.
5. Record the entity, timestamp, and visible error when contacting Support.

Some downstream pages state which ServiceTitan syncs they require. Confirm that those entities are active before activating the feature. If one required entity is inactive or failing, contact Avoca Support with the entity name and visible status rather than disabling or re-enabling every sync.