# Radar

> Monitor CRM risks and act on evidence-backed findings.

Radar watches your records for problems that need attention, such as a deal stuck in a stage or a ticket about to breach its SLA. Instead of searching reports for every risk, Radar checks records on a schedule and creates a **finding** with its evidence, severity, and history.

## Work with findings

Open **Analytics → Radar** to see findings in three tabs: **Open**, **Snoozed**, and **Resolved**. Filter by severity (Critical, High, Medium, Low, Info) or by record type (deals, tickets, projects, orders, and conversations).

Findings come from two kinds of detectors:

- **Built-in detectors**: [Stage Health](https://workstation.repzo.com/docs/sales/pipelines#stage-health) (records that stall in a pipeline stage), Ticket SLA, and Inbox SLA.
- **Monitors** you create (see below).

Open a finding to see:

- the affected record and the detector that found it;
- when it was first and most recently detected;
- a summary and the evidence behind it;
- risk, impact, urgency, priority, and confidence, when scoring is available;
- the full history of what happened to it.

On an active finding you can **Acknowledge**, **Snooze**, **Resolve**, or **Dismiss** it. Snooze when the issue is real but should come back later; resolve when the problem has been handled; dismiss when it should not be acted on. Click **Ask Fox** to discuss the finding with Fox next to the evidence.

Deal, ticket, order, and listing records also show a **Radar Findings** card, so you can see open findings without leaving the record.

## Monitors

Click **Monitors** on the Radar page to manage your own detectors. Click **New monitor** and start from a template, or build one from scratch for contacts, accounts, deals, tickets, invoices, or inbox conversations.

A monitor defines:

| Section | What you set |
|---|---|
| **Conditions** | Which records to check, using native or custom-property conditions |
| **Signals** | Risk signals and scoring, such as days since last activity, days in current stage, close date changes, or upcoming activities (where the record type supports them) |
| **Schedule** | Hourly, daily, or weekly, with a time and weekday where relevant |
| **Delivery** | **Inbox only** (findings stay in Radar) or **Notify immediately**, a minimum severity, and a cooldown in hours |
| **Who gets told** | The record owner, optionally with admins as a fallback when nobody owns the record |

Turn on **Open a Fox conversation with each recipient** to have Fox start an evidence-backed chat when a finding passes the minimum severity.

**Preview** tests your unsaved changes against real records without creating findings. **Run now** evaluates the monitor right away, and **Runs** lists recent evaluations and the findings each one changed.

### Monitor status

| Status | Behavior |
|---|---|
| **Draft** | Being set up; does not run |
| **Shadow** | Runs and records results, but does not notify anyone |
| **Live** | Runs, creates findings, and delivers them |
| **Paused** | Stopped until you resume it |
| **Archived** | Retired |

Use shadow mode to check that a new monitor finds the right records before you go live.

## Permissions

| Permission | Allows |
|---|---|
| `radar.view` | Open Radar and see findings |
| `radar.resolve` | Acknowledge, snooze, resolve, and dismiss findings |
| `radar.manage` | Create, edit, run, and change the status of monitors |

Radar is included with Pro seats; see [Plans & Add-ons](https://workstation.repzo.com/docs/commerce/plans-and-add-ons).

## Related pages

- [Dashboard](https://workstation.repzo.com/docs/analytics/dashboard)
- [Reports](https://workstation.repzo.com/docs/analytics/reports)
- [Pipelines](https://workstation.repzo.com/docs/sales/pipelines)
- [Tickets](https://workstation.repzo.com/docs/operations/tickets)
- [Properties](https://workstation.repzo.com/docs/administration/properties)