> ## 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 Responder notifications

> Control call-summary delivery, content order, and action-required priorities.

Open **Products → Responder → Notifications** to configure notifications generated from Responder calls. These settings are separate from the general **Settings → Notifications** page.

## Choose where notifications go

Use the notification toggles that apply to your team:

* **Filter Text Recipients by Team:** limits text notifications to technicians on the relevant team when this option is available.
* **Email for Transferred Calls:** emails the manager when a call is transferred.
* **Microsoft Teams:** sends call summaries to a Teams channel through its incoming-webhook URL.

When Microsoft Teams delivery is enabled, enter a valid webhook URL. You can also limit Teams messages to calls whose action-item priority is **High**, **Low**, or **No action needed**. Leaving every priority unchecked sends notifications for all calls.

Click **Save** at the top of the page after changing these settings. Treat a Teams webhook URL as sensitive configuration and do not paste it into public documents or messages.

## Arrange summary and subject content

The page has separate editors for **Job Summary Content Order** and **Email Subject Content Order**.

1. Drag fields from **Available Fields** into **Content Order**.
2. Reorder or remove fields as needed.
3. Click **Save Order** in that section.

Only fields that apply to a call appear in the final email. If the order is empty, Avoca uses the default content and order.

<Note>
  **Action Required** must be present in the email subject before it can be added to the job summary. Removing it from the subject also removes it from the summary.
</Note>

## Tune action-required guidance

When **Action Required** is in the email subject, use **Action Required Guidance** to define what your team considers high priority, low priority, or no action needed. High- and low-priority items trigger the subject tag, and the classification controls how routine action-item digests are grouped.

Save the guidance with its own **Save** button, then review several real notification emails to confirm the wording and priority match your operating process.