---
title: Alerts overview
description: Learn how to use alerts in Technis.
---

[Skip to content](https://support.technis.com/alerts-overview#main-content)

- [English](https://support.technis.com/alerts-overview)
- [Français](https://support.technis.com/fr/alerts-overview)

English

Show submenu for translations

[![Technis KB](https://support.technis.com/hubfs/KB/LogoDark.svg)](https://support.technis.com/?hsLang=en)

Open main navigation

Close main navigation

- - [English](https://support.technis.com/alerts-overview)
    - [Français](https://support.technis.com/fr/alerts-overview)

  English
  
  Show submenu for translations
- [Contact us](mailto:support@technis.com)

[Contact us](mailto:support@technis.com)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [Technis](https://support.technis.com/?hsLang=en)
2. [Alerts](https://support.technis.com/alerts?hsLang=en)

August 14, 2026

# Alerts overview

Alerts help you monitor important conditions in your physical spaces. They notify you when specific criteria are met—such as when a room is crowded, or a device reports an issue—so you can take timely action.

Alerts can be used for:

- **Support safety and compliance processes**: get alerts when visitor numbers exceed safe limits at entrances, stages or popular zones.
- **Queue monitoring**: trigger alerts when checkout or entrance queues become too long, so staff can respond quickly.
- **Indoor air quality**: get alerts when temperature or CO2 levels exceed comfortable thresholds for staff or visitors.
- **Monitor device health:** be notified when sensors go offline or report errors to ensure continuous monitoring.

![Alert inbox screenshot](https://support.technis.com/hs-fs/hubfs/KB/alerts-inbox.png?width=670&height=419&name=alerts-inbox.png)

### Alert types

There are two main types of Alerts to help you monitor your spaces effectively:

- **Device status alerts**: these alerts get triggered whenever a device goes offline or comes back online.
- **Metrics alerts:** which are triggered as soon as a condition on a particular metric is met, such as when visitors inside. Alerts can be created for [any supported metric](https://27034588.hs-sites-eu1.com/en/supported-metrics?hsLang=en).

### How Alerts work

Alerts are generated based on **alert rules** you define. Each rule sets a condition that, when met, will trigger an alert.

For example:

- *Entrance is crowded* rule → triggers when more than 100 people enter a zone.
- *Device issue* rule → triggers on device goes offline or comes back online.
- *Room is empty* rule → triggers when no visitors are detected in a room.

By default, alerts are triggered automatically as soon as their condition is met.  For device status alerts, it can take up to 5 minutes for the first alert to appear for some devices.

When an alert is triggered, it will appear in your **Alerts** dashboard and you will receive a notification via email, SMS or push notification.

To ensure timely delivery of emails, [ensure our domains are approved](https://27034588.hs-sites-eu1.com/en/firewall?hsLang=en).

### Alert lifecycle

Each alert goes through different stages to help you track progress of managing incidents:

1. **New**: Condition has been met for the first time and an alert has been triggered.
2. **Acknowledged**: Alert has been seen and is being taken care of by a team member.
3. **Snoozed**: Alert has been seen but a team member has decided to ignore it until some future time.
4. **Discarded**: Alert has been discarded by a team member due to it not being relevant.
5. **Resolved**: The issue which triggered the alert has been resolved by a team member.

During the whole life cycle of an alert, team members can leave additional comments on the alert page to give more detailed updates on the issue.

Once Resolved or Discarded, alerts are moved into **Alerts \> Log** page form where you can review all status changes and comments. 

### Alert rules

The **Alerts \> Mange rules** page is where you define and manage your alert conditions.

Each rule includes:

- A name (e.g. “Room is empty”).
- A condition (e.g. “Visitors inside more than 100”).
- The site and location it applies to.
- Who and how to notify them when a condition is met.
- Criticality.

You can add new rules or remove existing ones to tailor alerting to your operational needs. [Learn how to create an alert](https://support.technis.com/how-to-create-an-alert?hsLang=en).

- [Getting started](https://support.technis.com/getting-started?hsLang=en)
- [Reports](https://support.technis.com/reports?hsLang=en)
- [Alerts](https://support.technis.com/alerts?hsLang=en)
- [Devices and metrics](https://support.technis.com/devices-and-metrics?hsLang=en)
- [Admin](https://support.technis.com/admin?hsLang=en)
- [Releases](https://support.technis.com/releases?hsLang=en)
- [Announcements](https://support.technis.com/announcements?hsLang=en)

[![Technis KB](https://support.technis.com/hubfs/KB/LogoWhite.svg "Technis KB")](https://support.technis.com/?hsLang=en)

<https://www.linkedin.com/company/technis> <https://www.youtube.com/@technis3029> [mailto:support@technis.com](mailto:support@technis.com)

Copyright © 2026, Technis