Support: the shape of the question decides the answer
Most conversations that lead nowhere start with a general question. A specific question, with dates and amounts, gets answered first time.
What to include every time
Approximate date and time, amount, payment method, transaction reference if you have one, and what you expected to happen. With those five an agent can look at your case; without them they can only repeat the site's general policy, which is already published.
And one closed question at the end: 'which specific document is missing?', 'on what date was it processed?', 'which clause was applied?'. Open questions get open answers, and that stretches any matter without resolving it.
In writing, always
If the conversation starts on the phone, ask for the answer in writing to the account's email address. That is not distrust: it is the only way to have a dated version if the matter later becomes a formal complaint.
Keep screenshots of the cashier and of the terms as they stood when the problem happened. Terms get rewritten, and a promotion reworded afterwards does not describe what you accepted. That documentation is what a complaint stands on.
Questions worth asking before you play
Which RTP build the operator serves for this title, whether the game counts toward a specific promotion's wagering and at what weighting, and the balance consumption order when a bonus is active. All three answers change decisions.
They are entirely legitimate questions. At a licensed operator the correspondence between what a game declares and what it serves sits inside supervised technical requirements, so asking about RTP is not impertinent: it is reading the label.
The set of available methods and the limits depend on the account and on the operator: minimums, fees and timings are checked in the cashier before you move money, not on a page like this one.
When it stops being a support matter
When the published timing passes with no explanation, when the answer contradicts the written terms, or when a clause is applied that was not there. At that point the right move is a formal complaint to the operator, with the documentation you already kept.
If the complaint is not resolved, the route is the regulator that issued the licence: a licensed operator is obliged to handle complaints and an authority with sanctioning power sits behind it. That backing is what distinguishes the regulated market.
What support cannot do
It cannot change a game's RTP, which the studio sets and the operator contracts. It cannot accelerate a banking stage. And it cannot reinterpret a clause in your favour if it is clearly written. Asking for those three consumes time without changing anything.
It can tell you which document is missing, what state a request is in and which clause was applied. Those three answers resolve nearly everything, and they are obtained by asking for exactly them.
Frequently asked questions
What should I include when writing to support?
Approximate date and time, amount, payment method, transaction reference if you have one, and what you expected to happen — plus one closed question at the end.
Why ask for the answer in writing?
Because it is the only dated version you will have if the matter becomes a formal complaint. Keep screenshots of the cashier and of the terms as they stood at the time as well.
Can I ask about the game's RTP?
Yes, and it is a legitimate question. At a licensed operator the correspondence between declared and served figures sits inside supervised technical requirements.
When do I file a complaint instead of writing to support?
When the published timing passes with no explanation, when the answer contradicts the written terms, or when a clause is applied that was not there.
Read on
Last updated: September 2026