The contact it has to make
Most protection policies require an operator that has decided to act to tell the player why, in plain language, and to offer a route to respond. That contact is the part of the duty a player actually experiences, and it is also the part most often done badly: a message that names a rule and a threshold is a different thing from a message that says only that unusual activity was noticed.
- contacts
- 2,400
- responses within 7 days
- 1,680
- response share
- 70.0%
- lifted or reduced
- 480
- confirmed
- 1,200
- no response
- 720
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.
A protection policy normally requires the operator to tell the player what was seen, which rule it met and what is being done, in plain language, and to offer a way to respond. In the sampled desk 2,400 contacts were made; 1,680 were answered within seven days, of which 480 had the action lifted or reduced and 1,200 had it confirmed, and the 720 that were never answered kept the action in place.
A contact is a decision that has already been made
By the time a message reaches a player, the review has happened. The signals were read, the rule was met, a person or a policy resolved it, and the contact is the part that tells the player. That order is worth understanding because it explains the tone of the message: it is not a question and it is not an invitation to explain something before a decision is taken. It is notice of a decision, with a route to challenge it.
That is also why the contents of the contact are usually prescribed in more detail than anything else in the pipeline. A message that says only that unusual activity was noticed cannot be answered usefully by anyone; a message that names the rule, the period and the threshold can. Sample E is the desk in one line: 2,400 contacts, 70.0% answered, half of those answers changing what was in place.
What a useful contact contains
| Element | Why it has to be there |
|---|---|
| What was seen | a rule, a threshold and a period, rather than the phrase unusual activity |
| What is being done | nothing, a message, a limit, a break, a restriction, or closure |
| For how long | a start and, where there is one, an end - a break with no end is the hardest kind to challenge |
| What happens on a reply | who reads it, and what they can change |
| How to complain or escalate | a route that is not the same person who made the decision |
| Support routes | free and confidential help in the player own country |
The fifth and sixth rows are the ones a policy is most often written without, and they are the ones a player in difficulty needs most. A contact that ends with the support routes rather than with the enforcement routes is doing both jobs at once.
What happens when the player answers, and when they do not
Worked example / sample E
- contacts made: 2,400
- answered within seven days: 1,680 (70.0%)
- of the answered: 480 lifted or reduced (28.6%)
- of the answered: 1,200 confirmed (71.4%)
- never answered: 720 (30.0%)
- actions standing after no answer: 720 of 720 (100%)
Two things about that table are usually misunderstood. The first is that a reply is worth sending even without an explanation: 480 contacts in the sample were changed, and a change does not require the player to prove anything - it requires the reviewer to see a reason the rule could not. The second is that no answer is not a neutral outcome. The action was already in place when the message was sent, and 100% of the unanswered contacts in the sample kept it.
The message is not the only contact
A contact can also be made through a channel the player did not choose - a phone call, a pop-up at sign-in, a message in the account rather than by e-mail. Each channel has a different failure mode, and the sampled policy records which one was used because the record is what an appeal reads. A message that was sent and never opened is not a contact that reached anyone, and a policy that counts it as one will overstate how much of its duty it actually performed.
- A contact that names the rule can be answered specifically; one that names only a feeling cannot.
- A contact with an end date can be planned around; a break with no end cannot.
- A contact that carries the appeal route gives the player something to do that is not just wait.
- A contact that carries the support routes gives the player somewhere to go that is not the operator.
- A contact that is unopened should not be counted as performed.