Event center: every alert in one place

The Xeqmate event center gathers plate, face and video analytics triggers on a single screen — each with an image, the source camera, a status and a handling history. The alert arrives in real time over popup, push, Telegram or webhook, and the response is recorded for auditing.

Real-time alerts Handling with a status Auditable history Webhook to your system
Concept

What is the event center?

The event center is the Xeqmate screen that gathers the events the system raises — plate alerts, face alerts and video analytics triggers — for review and handling. Each event carries an image, the source camera, a description and a status that tracks the response, with a complete history of who changed what. It is the single point where the operation looks, decides and documents each incident.

In practice, it turns loose alerts into manageable incidents: instead of notifications that get lost, the operation — a central station, a company or a public agency — works a queue with filters, statuses and comments.

Inputs

Which events land in the center

Everything the platform AI detects becomes an event in the same place.

Operation

Review and handling: look, decide, record

Filtered search

Filter by account, devices, period, event type and status — and even by specific plates (up to 5 per search, legacy or Mercosur format). The list columns can be sorted, and the "view events" links on alerts open the screen already filtered by the source alert.

The whole event on screen

Each row shows the event image, the type, the timestamp, the description, the current status as a coloured tag, and the camera details: name, city/state and account. In the detail window the image can be downloaded and adjusted.

Status and comment

The operator changes the event status and records a comment of up to 1,024 characters explaining what was done — "patrol dispatched", "false positive", "escalated to supervisor". Nothing is left unanswered.

Auditable history

Every change goes into the event Change History, with timestamp, status, user and comment. The record is permanent and supports the audit of the response — who handled what, and when.

Beyond the event queue, the platform offers smart search across AI events to locate incidents the analytics detected inside the recordings. Access to the center requires a specific permission, granted by the administrator per user.

Notifications

How the alert reaches you

The event shows up in the center — and the notice goes out through several channels at once, so nobody has to be staring at the screen.

  • Popup in the platform: the alert appears on the screen of whoever is on duty.
  • Push in the app: a phone notification (Android/iOS), with alert preferences set in each user profile.
  • Telegram: in the user profile or in Telegram groups, with a send test right in the configuration screen.
  • Webhook to external systems: plate, vehicle-attribute and face alerts sent as an HTTP POST with a fixed JSON shape, a Bearer token and an HMAC signature — straight into the software the operation already uses. Details on the integrations page.
  • Alert groups: they define who gets notified per account when a plate or face alert fires — platform users, a Telegram group and up to 5 third-party email addresses per group, with visibility restricted to the participants when needed.
On shift

The heart of the monitoring shift

In a central station, the event center organises the routine: whoever takes over the shift pulls the pending events from the previous period and handles or escalates each one; during the shift, every trigger follows the rule look → decide → record; and at handover, the status and comment history shows the incoming operator exactly what is still open. Combined with plate and face alerts, it turns reactive monitoring into a documented response.

FAQ

Questions about the event center

The events the system raises: plate and vehicle-attribute alert triggers (LPR), facial recognition alerts and video analytics — motion, person, vehicle, object, fire and PPE detection.

The operator opens the event, sees the full detail (image, timestamp, type, camera), picks a new status and can record a comment of up to 1,024 characters. The change goes into the Change History with timestamp, status, user and comment.

A popup in the platform, push in the app, Telegram (in the user profile or in groups), third-party emails through alert groups, and a webhook to external systems with a Bearer token and an HMAC signature.

Yes. Every status change is recorded permanently in the event history, with who changed it, when and with which comment — on top of the platform general audit trail, which logs user queries and actions.

Yes. Search accepts up to 5 plates per query, in the legacy (AAA0000) and Mercosur (AAA0A00) formats, on top of the account, device, period, type and status filters.

Yes. Plate, vehicle-attribute and face alerts are delivered over webhook — an HTTP POST with a fixed JSON shape to your system URL, with camera and event-type selection and an external code per camera. See the integrations page.

Live demo

Watch an alert fire and get handled, live

30 minutes with our team: we connect one of your cameras, you watch the event land in the center, and you leave with the cost for your own scenario.

We reply within one business day · no credit card, no install, no commitment