How is the Confidence Score Calculated?
The Confidence Score is calculated using your configured alert settings for primary, contributing, and mitigating factors. Each factor influences the score and reflects the system’s confidence in suspicious activity.
Prerequisites
Permissions to view and edit alert settings required
Overview
The Confidence Score is calculated using your configured alert settings for primary, contributing, and mitigating factors. Each factor influences the score differently to reflect the system’s confidence in suspicious activity. Kinectify calculates each Confidence Score on a 1–100 scale, where a higher score indicates greater confidence that suspicious activity occurred. The score is built in stages:
Primary factors establish the base score
Contributing factors increase the score
Mitigating factors reduce the score
The score never drops below 1 or exceeds 100. These scores follow the same Low, Medium, High thresholds defined in your Risk Score Settings (e.g., 0–40 = Low, 41–75 = Medium, 76–100 = High).
The score is then compared with the escalation threshold for the alert type. Activity at or above it becomes an alert; activity below it is recorded in the Non-Escalated Events log. If Deep Analysis is turned on, past investigation outcomes at your property also inform whether the activity becomes an alert.
How the Score is Calculated
Primary Factor
The base score is set when the criteria for the primary factors are met or exceeded.Contributing Factors
Each contributing factor adds points to the base score based on the weight you set with the factor's slider on the alert type's Risk assessment tab in Settings → Property → Alerts (Beta).The added points are calculated as a percentage of the remaining points up to 100.
Example: If the base score is 85 and a contributing factor has a 50% weight, it adds 7.5 points (50% of the 15 remaining points), resulting in a score of 92.5.
Order Matters
Contributing factors are applied in the order listed in the settings. If multiple factors are met, each one adds to the score in sequence.Mitigating Factors
These reduce the score based on the weight you assign.Example: A mitigating factor with a 50% weight reduces the total score by 50%.
Mitigating factors are also applied in order and can stack.
Use high-weight mitigating factors only when you're confident they should significantly reduce the likelihood of suspicious activity.
Example: Structuring Alert
One of the mitigating factors for structuring alerts is based on the number of days over a set amount of funds within a defined time period. This mitigating factor is commonly used to align with the CTR threshold. For example, you can configure this to 3 days over $10,000 within 1 month, where $10,000 aligns with the CTR (Currency Transaction Report) threshold. This setup helps reduce the alert score when the pattern suggests the patron is consistently exceeding the CTR reporting threshold.
See the specific articles for each alert type to learn how settings and alert scoring works for each one:
Structuring (Inbound and Outbound)
Walks With Chips (WWC)
Unknown Chip Source (UCS)
Dormant Funds
Immediate Withdrawal
Minimal Play