Create and View Deal Alerts

Created by Rohith Patel, Modified on Fri, 17 Apr at 9:18 AM by Aye Myat

Note: Feature(s) Pending Rollout

Features and functionality described on this page are part of our April 2026 release, which is rolling out to eligible customers April 16-April 29, 2026. See our Release Notes here to learn more.

Objective

Deal Alerts enable admins and sales managers to configure automatic risk signals that surface directly in the Opportunity grid. Instead of manually scanning every deal to identify issues, alerts automatically highlight at-risk opportunities the moment a defined condition is met — such as a deal going silent, a close date slipping, or too few prospects being engaged. This article explains what Deal Alerts are, who can use them, and how to configure and view them in Outreach.

Applies To

  • Admins, can create, edit, and manage org-wide alert configurations
  • Sales Managers, can view and act on alerts for their team's deals
  • Account Executives (AEs), can view alerts on their own deals and take action
  • Sales Leaders (e.g., VP Sales) and RevOps, can monitor pipeline health using configured alerts

Note: Only Admins can create or modify alert configurations. AEs and Managers can view alerts but cannot change the alert settings.

Before You Begin

  • You have Admin access in Outreach to create or edit alert configurations.
  • Opportunity data (close dates, activity logs, prospect involvement) is synced and up to date in Outreach.
  • You have reviewed the available alert types in the table under the Procedure section to determine which alerts are relevant to your team.
  • For alerts with default templates (e.g., No seller activity, Close date overdue), no setup is required to start, they are pre-configured with default thresholds. Admins may adjust thresholds as needed.

Procedure

Creating a Deal Alert

  1. Log in to Outreach as an Admin.
  2. Open the Agents & AI > Agent Studio.
  3. Click New Agent.
  4. Under Deal Alerts section select an alert type from the list of available alert templates (see table below).
  5. Define the condition for the alert, for example, "No activity in the last 15 days" or "Close date moved more than 30 days."
  6. Set optional condition filter criteria to control which opportunities the alert applies.
  7. For alerts with default templates, review and adjust the threshold criteria as needed.
  8. Save and Activate the alert. It will now appear in the Opportunity grid for all applicable deals.

Available Alert Types

The following alert types are available in the April 2026 release:

Alert NameCategoryCondition (Default)Default Template?
No seller activityEngagementNo activity in last 15 daysYes
Number of prospects involvedEngagementLess than 2 for last 30 daysYes
No Upcoming meeting scheduledEngagementIn the last 10 days with prospect persona matching any persona and meeting typeYes
Deal amount changed toDeal AttributesIncreased/decreased by $xx or xx%Yes
Deal amount thresholdDeal AttributesAbove/below $xxxNo
Close date pushed outDeal AttributesMore than 30 days outYes
Close date is overdueDeal AttributesPast due dateYes
Meeting attendees includeEngagementRole matching [x] for 7 daysNo

Viewing Alerts in the Opportunity Grid

  1. Go to the Opportunity grid in Outreach.
  2. Locate the dedicated Alerts column, this column displays active alert signals for each deal at a glance.
  3. Click on a deal row to open the deal slideout panel.
  4. Select the Health & Alerts sub-tab to see full details of all alerts triggered for that deal.
  5. Review the alert condition and take the appropriate action on the deal (e.g., log activity, update close date, add prospects).

Note: Alerts can also be used as filter(Alert type, Has alerts) criteria in Smart View filters to quickly surface all deals matching a specific risk signal across your pipeline.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article