> ## 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 Team Alerts

> Send internal operational alerts to the right recipients, optionally by service area and Microsoft Teams.

Open **Settings → Business Info → Team Alerts**. This page is available when Team Alerts is enabled and your role can view workflows.

Team Alerts are internal operational alerts. They are not the same as:

* **Settings → Notifications**, which controls operational email behavior for calls and texts
* **Outbound → Customer Notifications**, which sends customer-facing SMS from eligible ServiceTitan events
* The **Notifications** tabs under the main Messages channel, Google LSA, and Yelp, which are legacy read-only summaries. Configure their recipients in Team Alerts.

## Configure an alert

1. Find the relevant section and alert card.
2. Turn on the alert.
3. Open its editor and choose the recipients.
4. Apply the available workflow type, lead source, or service-area conditions.
5. Save and confirm the card summary reflects the intended rule.

Sections can include **Outbound**, **Speed-to-Lead**, **Dropped Responder**, **Web Chat**, **Google LSA**, **Yelp**, and **Call Volume**. A section can be unavailable when its underlying product is not enabled.

## Use service-area-specific recipients

Turn on **Enable service areas** only when different locations need different recipients. With it off, the configured recipients apply across service areas. With it on, review every active area so a newly added location does not inherit the wrong coverage.

Some Speed-to-Lead rules can automatically apply to newly created lead sources. Use that option only when the same recipient policy should cover future sources.

## Microsoft Teams delivery

If Microsoft Teams delivery is enabled for the team, the page can show a Teams webhook setting for a section. Treat the webhook as a secret, use the intended channel, and send a controlled test after saving.

<Note>
  Team Alerts uses Employee Contacts and other available recipient records. If someone is missing, first confirm that their contact is active and has a valid email address.
</Note>

## Troubleshoot a missing alert

Check, in order:

1. The alert and its product section are available and enabled.
2. The event matches all saved conditions.
3. The lead source, workflow type, and service area are correct.
4. The recipient is active and has valid contact information.
5. The alert was not expected from a different notification system.