Platform · 06 Improve
Find the rule creating noise. See where reviews get stuck. Use outcomes to improve the data, controls and customer-model learning behind the next decision—not simply to close the current case.
Reporting & improvement
A lower review rate is not automatically better protection. Risk leaders need to see which rules create work, what investigators find and where genuine customers encounter friction.
The Command Center separates overview, investigation and rule analytics. A live event stream and decision mix give immediate context; rule and case outcomes help explain what the operation is doing.
Enlarge view SENTR.Citadel’s custom report builder: choose a data source, then shape criteria, columns, grouping and schedule.
Start with the operational question—not the spreadsheet export you happen to have.
Connect operational effort to confirmed outcomes. Fraud-loss and false-positive conclusions still need reliable labels, a defined population and enough time for outcomes to mature.
Start with reports and case outcomes. Then improve the part of the system the evidence points to—not automatically the model.
Is the context wrong or missing?
Inspect missing history, inconsistent identifiers or an incorrect field mapping before making a rule less sensitive. A returning customer should not look new because their past never arrived.
Validate the corrected context against relevant events.
Return to Ingest →Is a control creating the wrong work?
Use reports and case evidence to choose a rule, list, scoring profile or policy adjustment. For a rule change, use the relevant tests, backtesting or Monitor before publishing. Keep an accountable owner.
Observe outcomes after the change—not just the drop in alerts.
Return to the control workbench →What can the customer model learn?
Validated outcomes and corroborating signals inform the customer-model feedback process. Training is scheduled and depends on sufficient suitable data; an override is not blindly accepted as ground truth.
Keep model findings and later case outcomes distinguishable.
Inspect customer-specific learning →These are operating paths, not promises of automatic optimisation. AI rule-building assistance is available alongside the operator’s control workbench. A closed case does not instantly retrain a model or guarantee an improvement.
Low-ambiguity events should not consume senior analysts. High-ambiguity money movement should not disappear into an unexplained auto-block. The split has to be visible in policy—and ownership depth has to match the team (SENTR.Citadel vs SENTR.Tower).
Autonomous analyst agents and automated dispute settlement are not part of this workflow. Timing for adjacent product work is on product status.
Illustrative reporting windows show changing activity alongside approve, review and block categories. The bars are synthetic and do not represent customer performance. Compare the decision mix with validated outcomes, rule noise and review workload before changing a control; fewer reviews alone do not prove better prevention.
Policy · humans · ownership model
Illustrative workflow
Login events under a lenient profile auto-allow when contribution stays below threshold. Payout events with beneficiary reuse open a case and notify via webhook.
Volume is handled where policy is clear. Humans stay on material money movement.
Review context itself lives in Investigations. Decision composition lives in Decisions & rules.
Keep the work connected
Close the loop where the evidence points: repair inputs, test detection or adjust policy.
Return to IngestRevisit detectionAdjust the relevant control
Both operating models retain standard visibility. SENTR.Citadel adds custom reporting and direct tuning; SENTR.Tower keeps configuration guided.
Compare the exact controls ↗Choose guided presets or direct workflow control. We can help map the right setup to your review process.