Skip to main content
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 one or more Teams channels through Incoming Webhook URLs, optionally routed by service area, voice assistant, and a route description.
When Microsoft Teams delivery is enabled, add one or more named channels. Each channel needs an Incoming Webhook URL. You can also:
  • Service areas: leave empty so the channel is eligible for every zip (a default on that dimension), or pick specific areas.
  • Voice assistants: leave empty so the channel is eligible for every assistant, or pick specific assistants. Area and assistant filters on the same channel both have to match.
  • If any area-assigned or assistant-assigned channel matches the call, only those assigned channels receive the message. Unassigned default and description-only channels are skipped in that case.
  • Description for routes: optional natural-language instructions (for example, “only cancellations” or “emergencies only”). Empty descriptions always send when the channel is in the routing pool; non-empty descriptions are classified with the same GPT-4.1 routing used for employee contacts.
  • Notify when action item priority is: limit that channel to High, Low, or No action needed. Leaving every priority unchecked sends notifications for all calls on that channel. If an assigned channel matches the zip/assistant but not the priority, routing falls through to default channels.
Click Save at the top of the page after changing these settings. Saved webhook URLs are shown redacted after load; paste a new Incoming Webhook URL only when you want to rotate it. Treat Teams webhook URLs as sensitive configuration and do not paste them 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.
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.

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