# Compound Alerts

Compound Alerts allow users to create multi-condition alert rules that combine different detection types into a single alert. Instead of receiving separate notifications for each condition, users receive one alert only when all specified conditions are met simultaneously.

A Compound Alert consists of two conditions: one trigger and one filter. Both must be satisfied for the same person or vehicle before an alert is generated.

Requirements fall into two categories:

#### Triggers

Triggers detect specific camera analytics events on a given person or vehicle:

* **Motion Detection** — person or vehicle is detected in the camera's field of view.
* **Loitering** — person or vehicle remains in a defined area beyond a configured duration.
* **Line Crossing** — person or vehicle crosses a virtual boundary drawn on the camera view.

#### Filters

Filters match characteristics of the trigger event to a user-defined condition:

* **People Filters** 
  * **People List (POI)** — face matches against a configured People List (e.g., watchlist, VIP list).
  * **Smart List** — face matches against an automatically curated Smart List (New People or Frequently Seen People).
  * **AI Query** — describe a visual characteristic in plain text (e.g., "person wearing a red jacket") and the system uses AI-based image matching to detect it.
* **Vehicle Filters**
  * **AI Query** — describe a visual characteristic in plain text (e.g., "black SUV") and the system uses AI-based image matching to detect it.

{% hint style="warning" %}
Limitations and requirements:

* Compound alerts are supported on Verkada 2nd and 3rd-generation cameras.
* The feature is also available for Command Connector cameras with advanced analytics enabled. 
* Face Detection must be enabled on cameras when using People List or Smart List filters.
* People attributes must be enabled on the cameras using AI Query filters. 
* Compound alerts may take up to 1 minute before generating the event. 
  {% endhint %}

***

### Configure Compound Alerts 

#### Create Alert > Cameras <a href="#create-alert-greater-than-cameras" id="create-alert-greater-than-cameras"></a>

{% stepper %}
{% step %}
**On the Command homepage, in the left navigation, click Alerts.**
{% endstep %}

{% step %}
**At the top, click New Alert.**
{% endstep %}

{% step %}
**Select one of the supported triggers.**

* Motion Detection&#x20;
* Line Crossing&#x20;
* Loitering
  {% endstep %}

{% step %}
**Select a supported motion type: People or Vehicles.**
{% endstep %}

{% step %}
**Select a filter to be used for the compound alert.**

* People List (people motion type only)
* Smart List (people motion type only)
* Custom Query (people and vehicles)&#x20;
  {% endstep %}

{% step %}
**Continue the alert-specific configuration steps.**&#x20;
{% endstep %}

{% step %}
**Configure the filter:**

* **People List** – Select specific individuals or broader People Lists
* **Smart List** – Choose a Smart List and person type (New, Frequently Seen, or All)
* **Custom Query** – Enter a natural language query
  {% endstep %}

{% step %}
Click **Done** and continue with the alert [recipients](#create-alert-greater-than-recipients).
{% endstep %}
{% endstepper %}

### Create Alert > Recipients

{% stepper %}
{% step %}
**On Recipients, add users individually or assign the alert to a group.**
{% endstep %}

{% step %}
**Select the dropdown menu next to a user or group to choose their notification method(s). Recipients can be notified via push, SMS, or email notifications.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-a30e5c666efe865b169b36f277c2ab798ad76c5d%2F3a9609d9912905edd0f35abfff403a95e0b820c8.png?alt=media" alt="" width="289"></div>
{% endstep %}

{% step %}
**(Optional) By default, you will be an alert recipient. Select the dropdown menu and click Delete to remove yourself.**
{% endstep %}

{% step %}
**Click Done and continue with the alert** [**notification schedule**](#create-alert-greater-than-notification-schedule)**.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Any recipient added to this alert will see it appear under the **Shared Alerts** section of their **Alerts** page.
{% endhint %}

### Create Alert > Notification Schedule

{% stepper %}
{% step %}
**On Notification Schedule, specify the days and times for the alerts to send notifications. Alerts generate 24/7 by default.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-b9042c786a9dd12580abefdd20f412fe59cbac5e%2F7b61969c185d482c85ec3b7f15a687d75aee8d13.png?alt=media" alt="" width="563"></div>
{% endstep %}

{% step %}
**Click Done and continue to** [**device actions**](#create-alert-greater-than-device-action) **or** [**finish the alert**](#finish-the-alert)**.**
{% endstep %}
{% endstepper %}

### Create Alert > Device Action

{% stepper %}
{% step %}
**On Device Action, select the horn speaker(s) you want to play your message.**
{% endstep %}

{% step %}
**Select your notification preference (Text to Speech or Audio File).**

a. For **Text to Speech,** enter a message up to 200 characters.\
b. For **Audio File,** drag and drop the file or click **choose a file** to upload your audio clip.

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-6eebd070cac52d81c895573628cb7b21ba245804%2Fbd7aa4597a411933461874e312ac1e72683f4dab.png?alt=media" alt="" width="263"></div>
{% endstep %}

{% step %}
**Click Done and continue with** [**finish the alert**](#finish-the-alert)**.**
{% endstep %}
{% endstepper %}

### Finish the alert

{% stepper %}
{% step %}
**In the bottom right of the configuration window, click Next.**
{% endstep %}

{% step %}
**Enter a descriptive name for the alert.**
{% endstep %}

{% step %}
**Click Done to complete the setup.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-75fcc30636d14fdd34cc9e376db710c1542f4ef2%2F943420792c6bfe40aee47eab735038e52669e4ac.png?alt=media" alt="" width="188"></div>
{% endstep %}
{% endstepper %}

***

### Best practices

* **Write specific AI descriptions** — for AI Query filters, use clear and specific text (e.g., "person wearing a high-visibility vest" rather than "worker"). More specific descriptions improve match accuracy.
* **Optimize camera placement** — place cameras in well-lit areas with clear sightlines. For POI and Smart List requirements, ensure faces are clearly visible (straight-on view, adequate lighting).
* **Review and iterate** — periodically review alert results and adjust requirements or thresholds to maintain the right balance between alert volume and relevance.