Automated internal alerts help your team stay on top of compliance, fraud prevention, and responsible gaming — without manual monitoring. By triggering real-time notifications based on player activity, you can reduce manual work, respond to potential risks faster, and keep your Risk & Payments team informed at every step.
This guide walks you through setting up a Slack alert that fires every time a player requests a large withdrawal. The alert will be sent to a Slack channel monitored by your Risk & Payments team so they can review and approve the withdrawal promptly.

Before You Begin:

For this to work, you will need to set up your Slack Integration first. If you are not using Slack, you can use any channel that accepts a webhook — for example, Microsoft Teams — via a Callback action. Please contact your Partner Manager if you need assistance with this.

⚒‍ Setup

Create a new activity and set the type to Automated/Recurring. This ensures the alert fires every time the trigger conditions are met, rather than just once.
Firing Conditions
Firing Conditions
Set the activity end date to as long as you want the alert to remain active. A far-future date (e.g. 1 January 2300) is a common convention for "no end date" — adjust this to suit your operational needs.
Set Fires per user to Unlimited, since the alert should go out every time a player requests a large withdrawal, not just the first time.
Next, we will set up our Trigger with the following rules:
Big Withdrawal Segment
Big Withdrawal Segment
Configure the trigger to fire on withdrawal requests above your chosen threshold. In this example, any withdrawal request over €500 is considered a large withdrawal.
The Segment for our activity will target All Players:
Set the segment to target All Players. This ensures no qualifying withdrawal is missed, regardless of which player initiates it.
Next, select Send Slack as the action and compose the message you want your internal team to receive.
Creating a Send Slack Action
Creating a Send Slack Action
This message uses dynamic #-variables to populate real-time player and payment information. The variables used in this example are:
VariableDescription
#user_details-username#
The player's username
#UserId#
The player's unique ID
#Currency#
The player's currency
#amount#
The withdrawal amount requested
#payment_id#
The payment reference ID

↩‍ Alternatives

You can build a wide range of automated internal alerts in Fast Track by swapping out the trigger in Step 3. The rest of the setup remains the same. Here are a few common examples:
Sportsbook bet settled of €1,000 or more Trigger the alert when a sportsbook bet is settled above your threshold — useful for flagging large wins for your trading or risk team.
Big Sportsbook Win Trigger
Big Sportsbook Win Trigger
Casino win of €1,000 or more Fire the alert when a player records a large casino win, allowing your team to review the session if needed.
Casino Big Win trigger
Casino Big Win trigger
Deposit of €500 or more Notify your team whenever a high-value deposit is made, supporting AML checks and responsible gaming reviews.
Big Deposit
Big Deposit
Tip: These examples can also be combined or adapted — for instance, you could set up separate alerts for different thresholds, or route different alert types to different Slack channels depending on which team needs to act on them.