How does the minimal play alert work?
The minimal play alert identifies players who did not utilize enough funds for play.
Prerequisites
Permissions to View/Edit Alerts Settings required
Overview
This alert is designed to detect players who deposit or withdraw funds but engage in minimal wagering activity. You set a maximum utilization percentage, and when a player’s wagering is at or below it, activity can become an alert. Utilization is the amount wagered divided by the funds deposited or withdrawn.
The Confidence Score starts from how low the utilization is (lower utilization gives a higher score) and is adjusted by contributing and mitigating risk factors. Contributing risk factors increase the score, while mitigating risk factors, such as large wins or extended time played, reduce it. These settings help replicate how analysts assess whether minimal play behavior is suspicious.
For Active Alerts
If Active alerts are turned on for your organization, the minimal play alert is set up in Settings > Alerts (Beta). Choose the property at the top of the page, then open the Minimal Play card. The card has four tabs:
Detection criteria – The Detection window (the standard number of days, or a Custom window), the Volume threshold and the Max utilization. Activity that meets these is recorded as an event.
Risk assessment – The Contributing risk factors and the Mitigating risk factors (Win Amount and Minutes Played), each with a weight. Together with how low the utilization is, they produce the event's Confidence Score.
Escalation qualification – The Threshold score an event's Confidence Score must reach to become an alert. If pattern qualification is available for your property, you can also require a Minimum qualifying events count within an Evaluation period before an alert is produced.
Escalation prioritization – The High priority threshold. Alerts at or above this Confidence Score are marked High Priority.
On Active alerts, this alert type can include the Cash - Denominations contributing factor. It looks for cash transactions in the bill denominations set in your alert settings. For details, see the contributing factors article.
Steps to Configure the Minimal Play Alert
Access the Alert Settings Page
Click the gear icon in the bottom-left navigation bar
Select the AML module, then click Alerts (Beta) in the left-hand menu
Choose the property at the top of the page, then open the Minimal Play card.

Set the Detection Window
The detection window defines how far back the system looks for transactions each time alerts are run.
A common setting is 30 days, meaning the system analyzes the past 30 days of activity.
The alert window should be equal to or longer than the frequency of alert runs (e.g., if alerts run every 14 days, the window should be at least 14 days).
A shorter window may result in gaps in analysis. Consult your Client Success Manager before reducing the window below 30 days.

Configure the Detection Criteria
Volume threshold: Events are produced when the total of all transactions during the detection window exceeds this amount.
This ensures the alert only evaluates accounts with meaningful financial activity.
Ask yourself: What is the minimum amount of money involved in minimal play that would justify filing a SAR?

Set the Max Utilization
Max utilization: The highest utilization percentage that can produce an event, entered as a percentage “or less”. Lower utilization percentages produce higher Confidence Scores.
Utilization is calculated by dividing the total amount wagered by the total funds transacted, measured separately for inbound and outbound transactions. Both are shown on the alert’s Analytics tab.
If utilization is at or below the percentage you set, the activity is recorded as an event and given a Confidence Score.

Set the Contributing Risk Factors
Contributing risk factors increase the Confidence Score. On Active alerts, a higher score can decide whether an event is escalated to an alert.
These help validate that the behavior is potentially suspicious.
Clear the checkbox to the left of a factor to turn it off.

Set the Mitigating Risk Factors
Mitigating risk factors decrease the Confidence Score. On Active alerts, a lower score can keep an event below the escalation threshold, so it is not escalated to an alert.
Two mitigating factors are available:
Win Amount: Large wins may explain why a player stopped playing. Reduces the Confidence Score if the player’s winnings are the configured percent or more of the total volume.
Minutes Played: Longer play sessions may indicate legitimate activity despite low utilization. Reduces the Confidence Score if the player’s minutes played reach or exceed the configured number of minutes.
Each mitigating risk factor has a weight that sets how much it reduces the score. Use them only if they reduce confidence that minimal play occurred.

For more information on how mitigating factors influence the Confidence Score, see the knowledge base article How is the alert score calculated.
Expected Result
Once configured, the system will generate a Minimal Play alert when a player’s utilization is at or below the Max utilization and the total transaction volume exceeds the Volume threshold. The Confidence Score will be adjusted based on any contributing or mitigating risk factors turned on. If no qualifying activity is found, no alert will be produced.
Frequently Asked Questions
How is utilization calculated?
Utilization is calculated by dividing the total amount wagered by the total funds transacted, measured separately for inbound and outbound transactions.
Where does the Time Played data come from for the mitigating factor?
The time played is sent from the client’s source system. It is provided as part of the metadata and represents the duration of gameplay in minutes for each gaming activity.
What if no alert is generated even though a player has low wagering?
Check that the total transaction volume exceeds the Volume threshold. An event is produced only when both conditions, low utilization and sufficient volume, are met. On Active alerts, the event also needs a Confidence Score that reaches the Threshold score to become an alert; events that fall short are recorded in the Non-Escalated Events log.