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

# Manage catalog data and service areas

> Sync CRM job types, business units, and tags, then define the postal-code areas your team serves.

Open **Settings → Business Info** to manage the CRM catalog records Avoca can use and the geographic areas your team serves.

<Note>
  The connected CRM remains the source of truth for its catalog. Use Avoca to import the records you need and configure how Avoca may use them; do not create a duplicate just because a CRM record has not been synced yet.
</Note>

## Job Types

Open **Job Types** to review the types of work available from the connected CRM.

* ServiceTitan teams see the ServiceTitan job-type editor.
* AccuLynx teams see the corresponding Trade Types editor.
* If neither supported connection is present, the page links back to **Integrations**.

For ServiceTitan:

1. Choose **Sync from ST** to find job types that have not been imported into Avoca.
2. Review the unsynced list and import only the job types Avoca needs.
3. Add or generate a clear definition when the CRM name alone is ambiguous.
4. Review the available **Book**, **Reschedule**, and **Cancel** controls for each type.
5. Review any feature-gated controls, such as hiding an appointment, masking its date, or priority behavior, only if they appear for your team.
6. Test a representative booking after changing a customer-facing capability.

The ServiceTitan priority badge is read-only and reflects the priority currently returned by ServiceTitan. Avoca-specific priority controls can also appear when priority overbooking is enabled; do not change them simply to match the badge.

## Business Units

Open **Business Units** to review ServiceTitan business units and the actions Avoca may perform for each one.

1. Choose **Sync from ST** and import the required unsynced units.
2. Give each imported unit a useful definition.
3. Review **Book**, **Reschedule**, and **Cancel** independently.
4. If **Mask Appointment Date** appears, enable it only when the agent should withhold the appointment date or time for that unit.

Business Units requires a ServiceTitan connection. If the page is empty, verify the integration before adding records elsewhere.

## Tags

Open **Tags** to import and configure ServiceTitan tags.

* **Include in Job Tags** controls whether the tag is available in supported job-tag behavior.
* Additional **Reschedule**, **Cancel**, or **Hide Appointment** controls appear only when the corresponding feature is enabled.
* **Enable All** turns on every available tag toggle for every imported tag. Review the entire list before using this bulk action.

Prefer importing selected tags. Removing all synced records or enabling every tag can affect several products at once.

## Service Areas

Open **Service Areas** to group the ZIP or postal codes your team serves.

### Add an area manually

1. Choose **New Service Area**.
2. Give the area a clear operational name.
3. Add comma-separated ZIP or postal codes, or use **Import from CSV** on the area card.
4. If a timezone selector is available, choose a timezone or leave it set to inherit the team's timezone.
5. Choose **Save Changes**.

Wildcard patterns are supported. For example, `*` matches all codes, `90*` matches US ZIP codes from 90000 through 90999, and `M5V*` matches Canadian postal codes beginning with M5V. Use the narrowest pattern that represents the actual service boundary.

### Import ServiceTitan zones

For ServiceTitan teams, you can import a zone as a new service area or add its valid ZIP codes to an existing area. You can also associate one or more ServiceTitan zones with an area.

After saving the associations:

* **ST Sync** runs the same zone-to-ZIP update used by nightly sync.
* **Sync nightly** keeps associated areas updated automatically.
* **Allow sync to remove zips** also removes codes that no longer exist in the associated ServiceTitan zones.

<Warning>
  Leave **Allow sync to remove zips** off until you have verified the zone associations. Turning it on can shrink a live service area during the next sync.
</Warning>

Use **Export to CSV** when you need a reviewable copy of the current service areas. Deleting a service area also deletes all booking windows associated with it after you save, and the action cannot be undone. Review those booking windows before typing `DELETE` to confirm removal.

## Validate a catalog or geography change

1. Confirm that the intended record exists in the CRM and is imported into Avoca.
2. Review its definition and enabled actions.
3. Check the relevant Booking Windows, Capacity, campaign, or Responder configuration.
4. Test one customer who should qualify and one who should not.
5. Confirm the resulting booking or routing in the CRM.

If a CRM record disappears or changes name, correct it in the CRM first, then sync again. If a service area is unexpectedly empty, review manual removals, wildcard syntax, zone associations, and the setting that permits nightly sync to remove ZIP codes.