What's New at spektr

Features

Cases and alerts, together on the customer profile

You can now see a customer's alerts and cases in one place on their profile. The old Alerts tab becomes a "Cases and Alerts" tab with two sub-sections: alerts and cases, each case showing its current stage, including closed and reporting-stage cases. A scope dropdown switches between "This entity only" and "This entity + related entities", so activity across the ownership tree shows without opening each related entity. The alerts widget now counts open alerts only and links straight into the tab. Rolling out behind a feature flag.

What this changes for you: Cases sit in the same tab as alerts on the customer profile, and related-entity activity shows by default, so brief analysts who work from the profile.

A redesigned case page

The case page has a new layout. The customer name moves to the top and doubles as a dropdown for switching between customers, and the Customer Profile tab becomes a "Client Details" dropdown. The two sidebars merge into a single right-hand sidebar, the AI case summary is now collapsible and shows when it was last generated, and the case header shows the SLA. You can also manage case tags directly on the Create Case node. Rolling out behind a feature flag.

What this changes for you: Nothing changes until the flag is enabled. After that, anyone working in cases sees a different layout, so plan to walk investigators through it first.

Case activity on the customer timeline

The customer timeline now shows what happens to a customer's cases, not just when one was created. You can now see when a case is resolved, reopened, linked to or unlinked from the customer, and when a report is filed. Each event shows the case name, who acted, and when, with a link straight into the case. Rolling out behind a feature flag.

What this changes for you: Investigators can read a customer's case history straight from the timeline, without opening each case. No change to existing timeline events.

More flexible transaction monitoring rules

Two new options when building transaction monitoring rules. A relative similarity operator flags transactions whose amounts stay within a set percentage of each other, which catches structuring patterns built from deliberately similar amounts. And a single rule can now combine several named aggregations, summing or averaging across them. Rolling out behind a feature flag.

What this changes for you: No change to existing rules. These are new building blocks for creating or editing monitoring rules.

Improvements

Consumer ID merges reconcile automatically

When two consumer IDs turn out to be the same customer, their history now merges itself. Transactions can carry the list of IDs merged into the current one, and spektr folds the old IDs into the latest on ingestion, so transactions stay attached to the right customer with no manual relinking. Rolling out behind a feature flag.

This release also includes general performance improvements and bug fixes.