What an intervention can do
An operator that has opened a review has four responses available, and they are ordered by how much they take from the player: nothing, a message, a limit or a break, and a restriction or closure. The order matters because it is also the order of how much the operator has to be able to justify - and because two of the four are protective rather than commercial, which is a distinction players very often cannot see at the time.
- responses
- 4
- no action
- 1,600
- a message only
- 1,440
- a limit or a break
- 640
- restricted or closed
- 320
- accounts changed
- 960
Read the signals
Five comparisons the account already supports, run continuously rather than after a complaint. 6,000 flags in the sample, 96.0% of them relative to the account own history.
Choose a response
Nothing, a message, a limit or a break, or a restriction - one of four, graded by how much it takes from the player. 960 of 4,000 reviews in the sample changed access.
Write it down
Signals, crossing dates, rule version, path, response and outcome - one record per review, including the 1,600 that ended with nothing done.
Take the appeal
A route outside the desk that decided. 480 appeals in the sample, 176 of them upheld, which is 36.7% - high enough that the route does real work.
After a review the operator can do one of four things: take no action, send a safer-play message, impose a limit or a break, or restrict or close the account. In the sampled desk the four split 1,600 / 1,440 / 640 / 320 across 4,000 reviews, so more than half of all reviews leave the account untouched - and the 960 that do not are the only ones that change what a player can do.
A protective restriction and a commercial one look identical from inside
This is the single most confusing thing about a protection duty, and it deserves to be stated before the four responses are described. An operator can put a ceiling on an account for two completely different reasons: because a protection rule found a pattern, or because the account is not commercially attractive to it. From the player side both arrive as a limit. The difference is what the operator owes you afterwards, and it is recorded - one is open to appeal on the basis of the pattern, and the other usually is not.
Desk 89 is about the first kind only. The second kind is a commercial decision by the operator, and although it is a legitimate subject, it is not this subject: a protection review exists to reduce harm, and its whole architecture - the signals, the thresholds, the contact and the record - is designed so that the decision can be tested. A restricted account that came from this pipeline has a document behind it. One that did not, usually has nothing.
The four responses
| Response | What it changes | What the player is owed | Reviews |
|---|---|---|---|
| No action | nothing; the review closes with a note | nothing, unless asked for the record | 1,600 |
| A safer-play message | nothing automatic | the rule and the period behind it | 1,440 |
| A limit or a break | a ceiling on play, or a period with no access | notice, a length and a review date | 640 |
| Restriction or closure | access suspended, or the account ended | a reason and an appeal route | 320 |
The two middle rows are where most of the disagreement lives. A message asks the player to read something and builds a record; a limit or a break changes what they can do. Both are reversible in the sampled policy, and both are recorded - which is what makes the third column more than a courtesy.
Why a limit is usually the first thing imposed
A limit is the only response that reduces harm without removing access. It answers the pattern directly - the pattern was about the size and the pace of play, so the ceiling is on the size and the pace - and it keeps the account open, which keeps the player visible to the operator rather than pushing them somewhere the record does not follow. A break is the heavier instrument, used when the pattern suggests something more than a ceiling can address.
Worked example / sample F
- accounts reviewed: 4,000
- placed on a mandatory break: 480
- 480 / 4,000 = 12.0% of reviews
- of the 480: 320 for 24 hours, 112 for seven days, 48 for 30 days
- 320 + 112 + 48 = 480, so every break in the sample has a stated length
- shortened before it expired: 0
- recorded on the account for 12 months: 96 (20.0%)
The cost of a wrong response
A response that was not needed is not free. Of the 1,600 reviews that closed with no action, 640 had already produced a limit or a break before the review resolved - so a contact and, in 640 cases, a real reduction in access, were imposed on a pattern the rule later explained away. That is the price of a duty that is deliberately set to act early, and any honest description of it has to include the bill.
- 640 accounts met a limit or a break that the review then closed as explained.
- 1,600 reviews produced a contact and no change of any kind.
- 960 accounts had access reduced, whether or not the review confirmed it.
- 480 accounts were placed on a break, none of which was shortened before it expired.
The trade is real and it is deliberately made in one direction: catching a pattern late is worse than catching an ordinary week early. A player who understands that is not being asked to accept it silently - the appeal route on what you are owed is the other half of the same policy.