a score nobody can unpack
When a score cannot be broken down, the review then becomes a debate concerning trust.
Nova works on every page of the platform and inside the AI tools your team already uses. Give it any manual task in your own words, ask it anything about your data, and it runs the task. It also reads your screening profiles, rules, customers, and monitoring schedules, then returns tuning suggestions with the evidence attached. Settings never change without your approval.
Request the five highest-risk customers for this week, or instruct Nova to assign a case and set its status; the system will carry out the task, state its findings and those things it could not confirm, and suggest the next step.
Profiles and rules are configured at launch by people who have since moved on. Nobody touches them, because nobody can predict what a change will do. Meanwhile analysts click through the same menus to pull the same reports. Nova takes on both: the tuning nobody dares start and the manual steps nobody should repeat.
When a score cannot be broken down, the review then becomes a debate concerning trust.
A parameter isn't altered if its effect can't be measured.
The reason for setting a threshold was discussed in a meeting that produced no minutes.
Deterministic detectors proceed by going through the screening profiles, applying the rules, taking the dispositions, calculating the customer scores, and checking the monitoring schedules. At this stage, no model makes a call. These are facts derived from your own data.
A signal is only important if it stands out; Nova compares each one against your personal history and anonymized sector benchmarks and removes the normal ones.
The items discovered, why they matter, the supporting records, Nova's confidence, and the anticipated impact on false positives. All the information an approver needs is contained on a single card.
When Nova reaches the proposal, approving it opens the draft rule or pending setting change in your normal review process; if it is rejected, the reason is sent back, so the same suggestion won't reappear unchanged.
You don't need a second login or a copy-paste procedure; Nova detects the context of the screen you're on, carries out what you request, and then returns the decision.
Each point in the score traces back to its module, weight, and source.
The evidence points to the record rather than paraphrasing it.
A suggested value and the effect it has on alert volume. This can only be applied following approval.
Each proposal, whether it was accepted or rejected, and when.
The source content is presented alongside any translation, regardless of the original language.
The answer is located beside the decision it relates to. There is no separate tool needed.
Whether you approve, reject, or defer, all of your choices are recorded; and when a suggestion is rejected, the reason for the rejection is sent back to Nova so that the same suggestion will not afterward reappear as it was.
No suggestions for this product right now.
When a suggestion is approved, it becomes a draft rule or a pending change to a setting, along with the evidence, and then proceeds through your normal change process.
Nova can write drafts. It cannot change live configuration.
A short note is added to the finding when a rejection occurs, so the next reviewer knows the reason and Nova stops raising that point.
A suggestion engine becomes noise within a month without feedback.
An answer isn't too late right now; the result will appear in the next run window rather than remaining unread in the queue.
The suggestions have the same effect on a team as alerts do, so Nova keeps a record of what was seen and when.
With the regulator pack, all analysis runs, all findings they produced, and all decisions your team made are saved and exported.
When an auditor asks why a threshold moved, the response is the finding, the evidence, the approver, and the date.
An assistant that works on every page of the platform and inside the AI tools your team already uses. You give it tasks and questions in your own words; it reads the context of the screen you are on, carries out the request and shows its work.
Manual tasks such as listing this week's five highest-risk customers, assigning a case or setting its status. Nova carries out the task, states what it found and what it could not confirm, and suggests the next step.
It runs your request, but proposes first before anything bulk or permanent. A single case assignment happens when you ask; a change across many records waits for your confirmation.
No. Nova can write drafts but cannot change live configuration. An approved suggestion opens as a draft rule or a pending setting change and goes through your normal change process, with the approver recorded.
Your screening profiles, rules, dispositions, customer scores and monitoring schedules. These are usually configured at go-live and left untouched, because nobody can predict what a change will do. Nova measures that before anyone decides.
Deterministic detectors count what already happened in your data, and no model makes a call at that stage. Nova then compares each signal with your own baseline and anonymised sector benchmarks, and keeps only the ones that stand out.
The finding, why it matters, the supporting records, Nova's confidence and the expected impact on false positives, all on one card. Evidence references point to the record itself rather than paraphrasing it, so the approver can check every claim.
Yes. Each point in the score traces back to its module, weight and source record. A review then starts from what built the score, not from a debate about whether to trust it.
The reason is stored on the finding, so the same suggestion does not come back unchanged. The next reviewer sees why it was turned down, and Nova stops raising that point. A deferred suggestion returns in the next run window instead.
Yes. Every run, finding and decision is recorded, with detector versions, evidence, confidence, and who decided and when. The history is exported with the regulator pack, so when an auditor asks why a threshold moved, the answer is already on file.
We run it against a sample of your screening and monitoring history and walk through what it found.