Skip to content

Alerts

Overview

The Alerts system lets you define conditions that trigger notifications when conversation analytics match specific criteria. For example, you can get alerted when a quality score drops below a threshold, when compliance issues are detected, or when sentiment is negative.

The Alerts page has four tabs: Events, Incidents, Rules, and Preset Gallery. The last two are not shown to everyone: Rules to those who may view rules, Preset Gallery to those who may create them. The Incidents tab lists incidents created from analysis reviews, each with a Resolve button and a View Record link.

The Events tab: filters, bulk actions and the list of triggered alerts

The Open signals card on the Summary tab of the dashboard counts active alerts — not yet acknowledged or resolved — right now: the dashboard’s period does not apply to it. With exactly one project selected in the Projects filter the card counts that project only; with several, the filter does not apply to it. Its Alerts screen link opens this page without the card’s filters, with alerts of every status.

Alert Rules

Owner Admin Supervisor (edits only in projects they administer)

Alert Rules define the conditions that trigger alerts.

Creating a Rule

  1. Navigate to Alerts in the sidebar.
  2. Click Create Rule. The Create Alert Rule panel opens on the right.
  3. Fill in the form:
    • Project — the project the rule belongs to. A rule works in one project; the first project in the list is preselected, and the project cannot be changed when you edit the rule.
    • Rule Name — descriptive name (e.g., “Low Quality Alert”)
    • Description — optional note on what the rule monitors
    • Category — Quality Assurance, Compliance, Sales Performance, Sentiment, or Custom
    • Severity — Low, Medium, High, or Critical (a new rule starts at Medium)
    • Throttle (seconds) — caps how often the rule sends a new notification. 0 means never throttled. A non-zero value allows at most one notification per rule within that window; every matching conversation is still recorded as an alert event regardless — throttling only skips the outbound notification while a previous one is still within the window. New rules default to 3600 seconds (one notification per hour); critical-severity presets default to 0 (never throttled), since a compliance or policy breach must not be silently rate-limited.
    • Alert Condition — define conditions using the visual rule builder (JSONLogic); at least one condition is required
    • Enable this rule — on by default; switch it off to save the rule without activating it
  4. Optionally turn on Apply to existing records to run the rule against previously analyzed conversations (backfill).
  5. Click Create.

The form has no notification-channel setting. Who receives a fired alert, and through which channel, comes from notification settings — see the Notification Channels section below.

If a condition references a field the analysis doesn’t produce, Aelo rejects the rule when you save it and lists which field(s) are invalid — this applies both when creating a new rule and when editing an existing one, so a rule can’t be saved in a state where it would silently never fire.

Create Alert Rule form

Condition Builder

The condition builder uses a visual interface for defining rules without code:

  • Select a field (e.g., Quality Score (0-100), Overall Sentiment (-1 to +1), Sale Probability (0-1))
  • Choose an operator (equals, greater than, less than, etc.)
  • Set a value (e.g., score < 40)
  • Combine conditions with AND / OR logic, and nest them with + Add Group

The condition builder in the rule form

Example conditions:

  • Quality score below 50
  • Overall sentiment below 0 (negative) AND sale probability below 0.3 (30%)
  • The built-in criterion “Disclosed call recording” triggered — the recording notice was not given

Criteria as fields. If your organization uses call criteria, the field list has a Criteria group with every criterion that is neither archived nor paused: a yes/no criterion as triggered (yes or no), a score criterion as its score from 0 to 100, a list criterion as the chosen value. A condition on a criterion fires only on a conversation where the criterion has an answer for this processing of the conversation and its current wording. If the criterion was not applicable, the model could not answer with confidence, or the criterion was not evaluated, the rule does not fire — so a rule “criterion did not trigger” does not fire on calls the criterion never checked. Once a criterion is archived, the rules that use it are marked as having a field that no longer resolves; the same goes for a rule that compares a list criterion with a value archived since. Such a rule does not fire, and it cannot be switched back on until its condition is changed. The same goes for a criterion whose scope does not cover the rule’s project: the criterion is not evaluated on that project’s conversations, so such a rule cannot be saved, and a rule whose criterion was later limited to other projects is marked the same way — widen the criterion’s scope to the rule’s project or pick another criterion. A paused criterion, a built-in or your own, stops counting as a field in the same way: it is not asked of new conversations, so a rule on it does not fire — not even on an answer the criterion gave before the pause — until you resume the criterion. Unlike an archived criterion, a paused one is not “gone”: the rule card carries an amber mark “Criterion … is paused — the rule stays silent until it is resumed”, and the condition, on the card and in the rule builder, names the criterion as “… (paused)”. Resume the criterion and the rule works again. A rule that has no answer for one of its fields is skipped as a whole — including the other branches of an OR — so keep a criterion condition in a rule of its own rather than OR-ing it with other fields. For a criterion condition, the alert in the app shows the criterion’s own quote from the call to people who can open that call and its criteria — from the answer that raised the alert, even if the call was processed again since, and only for the criteria whose part of the condition matched. A quote shows its time in the call when that moment is known, and clicking the time opens the call there. When there is no quote, the alert says why: “No quote: event not found” when what the criterion looks for was not found in the call, and “Quote unavailable” when the answer that raised the alert is no longer there or found the event without a usable quote. Notifications — email, Telegram, webhook and the team channel — do not include the quote.

Built-in criteria in rules. The Criteria group also lists the built-in criteria your organization has — the ones Aelo words for you, shown in Analysis Setup → Criteria in the Built-in section. A rule can use them like any other criterion, and a built-in is always a yes/no criterion, so the condition is on triggered. A rule on a built-in that is paused does not fire: the paused criterion is not evaluated and no longer counts as a field, so the rule card carries the amber mark “Criterion … is paused — the rule stays silent until it is resumed” (the red “Field not found … — rule never fires” mark is for archived or missing criteria). Resume the criterion in Analysis Setup → Criteria and the rule works again. Aelo can also pause a built-in itself; you cannot resume that one, and rules on it stay silent until Aelo lifts the pause.

Managing Rules

  • Enable/Disable — use the switch on a rule card to turn a rule on or off without deleting it; switching a rule off asks whether to Disable only or Disable & resolve active alerts
  • Edit — change the name, description, category, severity, throttle, condition, or the on/off state (the project stays fixed)
  • Duplicate — create a copy of a rule as a starting point
  • Delete — permanently remove a rule, after a confirmation

Rule cards with the switch, Edit, Duplicate and Delete

Owner Admin

The Preset Gallery offers pre-built alert rule templates; each card shows its category:

The Preset Gallery with the project selector

CategoryExample Presets
QualityLow QA Score, Attention flag raised
ComplianceRecording Disclaimer Missing, Rep used a forbidden word
SentimentNegative Sentiment, Client Sentiment Declined
SalesClosing Not Attempted, Poor Objection Handling

To enable a preset:

  1. Go to the Preset Gallery tab.
  2. Under Select Project, choose the project the rule is for (the first one is preselected).
  3. Find the preset card. It shows the category, name and description and, if the preset has thresholds, the thresholds under Configurable: with their default values.
  4. Click Enable Rule. The rule is created at once, switched on, with Medium severity and the default thresholds; the card then reads Already Enabled and the Rules tab opens.
  5. To change a threshold, the severity, or anything else, open the rule in the Rules tab and click Edit.

Alert preset card

Three presets exist only on built-in criteria: Recording Disclaimer Missing (on “Disclosed call recording”), Rep used profanity (on “Rep used profanity”; only the rep’s lines count — the customer’s profanity is not an alert) and Rep used a forbidden word (on the criterion of the same name; only the rep’s lines count, and while its word list is empty the criterion is paused and the alert does not fire). When you enable one, the rule is saved on the criterion itself: these presets have no analysis-field form, and the former Profanity detected preset (any speaker) has been removed. Recording Disclaimer Missing waits for the “Disclosed call recording” criterion, which starts paused for a new organization — switch it on first. A preset on a criterion is offered only while that built-in is active and covers the selected project; while the list of criteria cannot be loaded, the gallery says so and holds such presets back. Rep used profanity and Rep used a forbidden word are offered only to organizations that have built-in criteria.

Alert Events

Owner Admin Supervisor

The Events tab shows a chronological history of all triggered alerts.

Each event row shows:

  • Rule name that triggered
  • Record that triggered the alert (clickable link)
  • Time since the alert fired
  • Severity badge (Low / Medium / High / Critical)
  • Status badge (Active / Acknowledged / Resolved)

Alert event row

Opening an event shows its card with the evidence the rule fired on. For a rule on the attention flag, the card also shows the moment of the conversation the flag rests on — time, speaker, label and quote — when the analysis has pinned the flag to one thing said in the conversation and found that quote in it; it is visible to anyone who may open the call itself. This moment is shown in the app only: notifications (email, Telegram, webhooks, team channels) do not include it.

The card also has Acknowledge — only while the alert is active — and Resolve, until the alert is resolved; they change the alert’s status.

An alert opened: severity, status, record, rule and the evidence

Filtering events:

  • By severity
  • By status (Active / Acknowledged / Resolved)
  • By rule name (search box)

Next to the filters, Acknowledge (N) and Resolve (N) act on the alerts of the current page, and Resolve all matching (N) resolves every alert that matches the severity and status filters, not only this page. The rule-name search is not applied to it — the confirmation warns about this when the search box is filled.

Notification Channels

Alerts reach each person through that person’s own notification channels — the rule does not pick them:

ChannelDescription
In-appNotification bell in the Aelo header
EmailEmail to your account address, or to a custom one if you set it
TelegramMessage via Telegram bot
WebhookHTTP POST to a custom URL
Bitrix24 Group ChatMessage to a Bitrix24 group chat by its Chat ID; offered only while Bitrix24 is connected to the organization

Configure the channels in Settings > Notifications and keep the Quality Alerts category selected under Notification Categories — rule-based alerts arrive in that category.

What is sent instantly

Through the personal channels — email, Telegram, webhook, Bitrix24 group chat — an alert is sent at once only when its severity is High or Critical. A Low or Medium alert is not sent through the personal channels at once: it waits in the app (the notification bell) and goes into the digests. The threshold is set at the organization level, the same for all its users, and is currently “High”; it cannot be changed in settings. The project’s team channels have their own threshold, independent of this one: lowered to Low or Medium, it sends such alerts to the team channel at once — see Minimum severity.

What actually reaches you is shown by the What you receive right now summary in Settings > Notifications: which notification categories arrive, through which channels, the line “Sent out immediately from severity High and above; anything lower waits in the app and in digests.”, your regular digests, supervisor feedback on your conversations, and — for the Owner and the Admin — money notices. The summary is computed from your subscriptions and enabled channels, so it answers “why did this alert not reach me”.

Team Alert Channels

Owner Admin

Besides the personal channels above, each project also has its own team alert delivery configuration — a shared destination for alerts that isn’t tied to any individual’s subscriptions. Find it under Project Settings → Alert delivery; the Team channels by project card in Settings → Notifications leads there too.

Supported channels:

ChannelDescription
TelegramMessage via a Telegram bot
WebhookHTTP POST to a custom URL
Bitrix24 chatMessage to a Bitrix24 chat (embedded installs)
In-appNotification bell in the Aelo header

Telegram, webhook and Bitrix24 chat each have a Test button to verify delivery once the channel is saved; in-app delivery has none.

A project’s Telegram channel is connected with a one-time link from the bot, not by typing a chat ID. In Project Settings → Alert delivery, press Connect via Telegram, and in the tab that opens choose your team’s group and add the bot; the chat is bound to the project automatically. The channel then shows as connected, with a switch and a Test button. The switch can only turn a connected channel off; to turn it on again, press Connect via Telegram and use a new link. If the bot is already in the group, the link cannot add it again: send the command shown under the button (/start@<bot> <code>) in the group instead.

One Telegram chat serves one project: when you connect a chat to another project through the bot, the Telegram channel of the project it was connected to before is switched off.

Minimum severity

Team alert channels only fire above a configurable minimum severity — Low, Medium, High, or Critical — set independently from anyone’s individual notification subscriptions. It defaults to High, so out of the box the team channels only receive High and Critical alerts.

Only users who can edit the project’s settings can view or change this configuration.

Minimum severity of a team channel

Backfill

When creating a new rule, the Apply to existing records switch runs the rule against all previously analyzed records in the rule’s project. This is useful when you want to retroactively check past conversations against a new criterion.

Backfill runs in the background and may take time for large datasets. It runs only for a rule created switched on: a rule saved switched off is not run against past records. An alert it raises is dated by when the conversation was analyzed, not by the backfill run, so past calls do not swell today’s counts. For a rule on a criterion, a past conversation counts only where the criterion has an answer for the conversation as it now stands and for the criterion’s current wording.

Access by Role

FeatureOwnerAdminSupervisorRep
Create/edit rules✅✅✅ (in projects they administer)❌
Delete rules✅✅✅ (in projects they administer)❌
View rules✅✅✅❌
Use presets✅✅✅ (in projects they administer)❌
View events✅✅✅ (project-scoped)❌

A supervisor sees the Create Rule button and the Preset Gallery, but can create, change or delete a rule only in a project where they are the project admin (for example, a project they created). In any other project Aelo refuses the save.

Tips & Best Practices

  • Start with presets — they cover common scenarios and can be customized.
  • Use severity levels wisely: High or Critical for compliance violations, Medium for quality drops, Low for informational patterns.
  • Combine multiple conditions with AND/OR for precise alerting.
  • Set up at least one compliance rule to catch recording disclaimer issues early. Use the Recording Disclaimer Missing preset and check in Analysis Setup → Criteria that “Disclosed call recording” is not paused — a rule on a paused criterion does not fire. (The criterion starts paused for a new organization — switch it on first, otherwise the rule has nothing to match.)
  • Make sure the people who must see critical alerts have the In-app and Email channels switched on in Settings > Notifications, with the Quality Alerts category selected.
  • Review Alert Events weekly to tune rules — too many alerts cause alert fatigue.