# 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** [**notification schedule**](#create-alert-greater-than-cameras)**.**
{% endstep %}
{% endstepper %}

### 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="/files/uYML32hRYgJjp2h8VugP" alt=""></div>
{% endstep %}

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

### Create Alert > Notification

{% stepper %}
{% step %}
**On Notification, 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, messaging platform alerts, or email notifications.**

<div align="left" data-with-frame="true"><figure><img src="/files/joJ6V2JNVhYtAyRboJyi" alt="" width="438"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Any recipient added to this alert will see it appear under the **Shared Alerts** section of their **Alerts** page.
{% endhint %}
{% 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's** [**optional settings**](#optional-settings)**, or** [**finish the alert**](#finish-the-alert)**.**&#x20;
{% endstep %}
{% endstepper %}

### Optional settings

#### Create Alert > Operations

{% stepper %}
{% step %}
**Toggle on Route to Operations to create a ticket from the alert.**&#x20;
{% endstep %}

{% step %}
**(Optional) Select Ticket Instructions to add information to the ticket and click Done.**
{% endstep %}

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

#### Create Alert > Device Action

In addition to notifying individuals, you can configure your horn speaker to play when an alert is triggered. These alerts can be text-to-speech or an uploaded MP3 file.

{% 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="/files/cmdMXVOCnchM5sxvJbCQ" alt="" width="395"></div>
{% endstep %}

{% step %}
**Click Done and continue to** [**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"><figure><img src="/files/T5Nvt7tMTQqgMsGZ7Vuh" alt="" width="436"><figcaption></figcaption></figure></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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/verkada-cameras/analytics/create-camera-event-alerts/compound-alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.