ALPR Hit Alerts

An ALPR hit is generated when a license plate captured by an ALPR source matches a plate on one of your active hotlists. A hit can notify you through several channels at once: an on-screen alert in Fusus, an email, and/or a call to an external system (webhook). ALPR alerts are part of the Fusus consolidated alerts experience, which also surfaces 911 and Watch Me alerts in the same panel.

Alert types at a glance

Tab What it does
Fusus Shows the hit inside Fusus - an on-screen toast and an entry in the Alerts panel. Enabled with the Create an alert in Fusus toggle.
Email Sends an email notification to everyone on the alert list whenever the hotlist produces a hit.
Vehicle Controls which vehicles on the hotlist generate alerts and which alert categories are active. By default all vehicles and enabled categories alert; you can narrow to selected vehicles.
Person Alert Alerts a specific person or user group - chosen by your admin - for the alert categories you select. Off by default.
API Sends the hit to an external system by calling a webhook (HTTP) endpoint, so tools like CAD/RMS or a GSOC dashboard can react automatically.

A hotlist can use any combination of these - for example, an on-screen Fusus alert plus an email, or a webhook only. With no alert types enabled, matching reads are still recorded and searchable, but no notification fires.

Turning on hotlist alerts

Alerts are configured per hotlist, not as a single system-wide switch. Each hotlist's Settings -> Alerts panel controls how that hotlist's hits are delivered, across five tabs - Fusus, Email, Vehicle, Person Alert, and API. You reach these from the hotlist's settings gear; see ALPR Hotlist Management for how to open them. This page explains what each alert type does once it's turned on.

Fusus (in-app) alerts

When a matching read comes in, a toast notification appears on screen, and Fusus plays an audible notification. The toast includes the hotlist name, the camera location where the read was captured, the license plate image, and the parsed plate number and state. From the notification, select Dock Cameras to open the associated camera feed.

Alerts panel

Open the Alerts panel from the bell icon in the upper-left. It shows a running list of active ALPR alerts, each with the hotlist name, camera location, timestamp, and license plate details. Select an alert to expand its Detection Details view: camera source, and vehicle make, color, and body type. Dock Cameras is available from any alert.

Dismissed alerts

Alerts are designed for real-time awareness and automatically move to the dismissed section after a few minutes. To view them, select the "..." menu next to the alert count -> View Dismissed Alerts. To return to the live list, select the "..." menu -> Show Active Alerts. Dismissed alerts retain their full detection detail, so an alert you didn't get to is still reviewable.

Filtering alerts

When many hotlists are active, use the filters at the top of the Alerts panel to focus on what's relevant to you. Filtering only changes what you see in the panel; it does not change which hits are recorded or which emails and webhooks fire.

  • Filter by location (dropdown).
  • Alert Boundary - draw a boundary on the map so only alerts reported within that area are shown.
  • Personal Alert Radius - uses your browser's GPS to create a boundary around your current location, especially useful on mobile.
  • Filter by hotlist / category - turn individual hotlists on or off and select specific alert categories.

Filter controls at the top of the Alerts panel.

Alert Boundary — only alerts within the drawn area are shown.

Filtering by hotlist and category.

Snoozing alerts

Snoozing an individual plate from the Fusus alert is not yet available; see ALPR Hotlist Management for the current workaround in evidence.com.

Email alerts

The Email tab sends a notification whenever the hotlist produces a hit. When a license plate of interest is detected, all users on the alert list receive an email, with details specific to their role and agency. This is useful for people who need to know about a hit but aren't actively watching the Alerts panel - the email identifies the hit (the plate, the hotlist it matched, the alert category, and the capture location and time), so recipients can begin triage from their inbox.

Email alerts are configured per hotlist and are independent of the Fusus in-app toggle: a hotlist can send email without showing an in-app alert, or do both.

Vehicle alerts

The Vehicle tab controls which vehicles on the hotlist generate alerts and which alert categories are active. By default, all vehicles are enabled for alerts and all enabled categories are active. To limit alerting to certain vehicles:

  1. Select Selected vehicles only.
  2. To add a vehicle, select it from the Vehicles Not Alerted list to move it to the Vehicles Alerted list.
  3. To remove a vehicle, select it from the Vehicles Alerted list to move it back to the Vehicles Not Alerted list.
  4. If needed, scroll down to add or remove alert categories.
  5. Save your changes.

Person alerts

The Person Alert tab lets an admin alert a specific person or user group when the hotlist produces a hit. By default, no persons or categories are active. To set it up:

  1. Turn on Person Alert on the Person Alert tab.
  2. Add people or user groups by entering a name in the Search People field.
  3. Select the Alert Categories this person or user group should be alerted for.
  4. Save your changes.

To stop alerting a person or user group, select the X next to their name.

API (webhook) alerts

The API tab delivers hits to an external system through a webhook. When the hotlist produces a hit, Fusus sends an HTTP request to the endpoint URL you configure, so downstream tools - a CAD/RMS integration, a GSOC dashboard, or an automation workflow - can act on the hit without a person copying it over. The request carries the hit's key details (plate, state, hotlist, alert category, camera/source, timestamp, and available vehicle attributes).

Webhook alerts are configured per hotlist, so you can route only the hotlists that matter to an integration. The exact request payload format and delivery/retry behavior follow your integration's specification - coordinate the endpoint and payload contract with your Axon integration contact when setting this up.

Auditing

Every change to a hotlist's alert configuration - and to the hotlist itself - is recorded in the ALPR Hotlist Management Audit Report.