Most issues are solved faster when you know two things: where to contact support on the official site, and what details to include in your first message. This page explains support channels, what to send for common problems, how to follow up on a case, and how to escalate a complaint if you cannot get a clear answer.
If you are in Australia, keep in mind that availability, payment methods, and processing rules can change. The most reliable information is always inside your account menus and the official policy pages.
Support is usually offered through live chat, email, and a help centre form. The best channel depends on your issue. Live chat is typically best for urgent account access problems, while email or a ticket form can be better for payment tracing and verification questions.
| Channel | Best For | What to Prepare | What to Expect |
|---|---|---|---|
| Live chat | Login issues, quick checks, simple questions | Username or account email, short summary | Fast triage and next steps |
| Email support | Payments, verification, formal follow-ups | Reference IDs, timestamps, screenshots if safe | Written replies and case tracking |
| Help centre form | Structured requests, attachments, complaints | Clear timeline and desired outcome | Ticket creation with a case number |
If you are not sure whether you are on the correct website before contacting anyone, return to the main hub and confirm safe access first on official login basics.
The fastest way to get help is to send a complete first message. That reduces back-and-forth and prevents delays caused by missing details. You do not need to write a long story. You need a clear timeline and the identifiers that let support locate your case.
If your issue is about deposits failing, compare the method rules first using ways to add funds, then message support with the exact method name and timestamp.
These short templates help support understand your request in seconds. Replace placeholders with your details. Do not include sensitive information like passwords.
Hello. My withdrawal is pending. Account: [email/username]. Amount: [amount]. Method: [method]. Time submitted: [date/time]. Status: pending. Reference ID: [ID]. Please confirm what step it is in and whether any verification is required.
Before you send this, confirm you cleared any active promotion conditions and understand how status works in rules for cashing out.
Hello. My deposit failed. Account: [email/username]. Amount: [amount]. Method: [method]. Time: [date/time]. Error message: [text]. Please confirm whether the attempt reached your side and what I should do next.
Hello. My promo code did not work. Account: [email/username]. Code: [code]. Where I entered it: [sign up/deposit screen]. Time: [date/time]. Please confirm eligibility and the correct activation steps.
If the question is about wagering limits or max bet rules, review help with bonus conditions before you continue playing with an active offer.
Hello. I cannot log in on mobile. Account: [email/username]. Device: [model]. Browser: [name/version]. Issue: [blank page/login loop/error]. Time: [date/time]. I tried: [cache clear/network switch]. Please advise next steps.
If your issue is mobile-only, the fastest fix is often browser settings. Use playing on your phone to check cookie and shortcut steps before escalating.
Account security is part of support, not separate from it. If you share sensitive data, you increase the risk of account takeover. Use this list as a hard boundary in every conversation.
If any message asks for something unsafe, stop and verify the request through official channels on the site.
Verification questions are common, especially around withdrawals. If you are asked for documents, the best approach is to respond once with clear files and matching account details, then wait for confirmation rather than resubmitting repeatedly.
For policy context and what verification usually covers, check licences and key rules and focus on KYC, payments, and complaint procedures.
If your issue is not resolved, escalation works best when you keep everything in one case thread and ask for a written explanation tied to a specific rule. Avoid opening multiple tickets for the same problem unless support instructs you to do so.
Player experiences can help you know what questions to ask, but they should not replace official information for your account. If you want to see the types of issues others mention, read player feedback themes, then compare those themes to your own transaction history and support replies.
Send your account email or username, a timestamp, the exact action you attempted, the payment method name if relevant, and any reference IDs from transaction history. Short, structured messages reduce follow-up questions and speed up resolution.
Live chat can fail due to browser blockers, cached errors, or temporary outages. Try a different browser, clear cache for the site, and switch networks. If it still fails, use email or the help form and mention that chat did not load.
Reply in the same ticket thread and include your case number if you have one. Avoid opening multiple new tickets for the same issue unless support specifically tells you to, because it can split your case history.
Never share your password, one-time codes, full card numbers, or banking login details. Support can verify your account using safe identifiers and transaction references, not secret credentials.
Provide the withdrawal amount, method, timestamp, current status, and reference ID. Ask whether verification or bonus conditions are blocking release. A clear request is easier to trace than a general complaint.
Ask which rule triggered the removal and request the specific term text that applies. Check expiry and max bet rules, and confirm whether you had multiple promotions active. If needed, request escalation with a written explanation.
Build a short timeline with dates, amounts, and reference IDs, then ask for escalation and a policy-based response. Keep communication in one thread so the case trail is clear and consistent.