Connect with the Vault
Support channels and response standards
Whether you are troubleshooting a pending cashout, checking wagering math, or asking about a specific game round, this contact page is built to route you to the right team quickly. We use a triage model: account security queries first, payment timing issues second, gameplay clarifications third. That order keeps urgent player cases moving even during peak traffic windows.
When you contact support, include your account email, event timestamp, game name or payment method, and a short timeline of what happened. This small preparation step dramatically reduces back-and-forth and helps agents resolve real-money incidents in the first session instead of escalating twice.
Email: [email protected]
Live Chat: Available directly in the mobile app and desktop site. Average response time: 2 minutes.
What we track to improve assistance
Our review team measures response quality, not just speed. We track how often first responses solve the issue, how clear the next-step guidance is, and whether payout-related tickets get proactive updates. These measurements feed into updates on the main review page, especially in customer support and banking sections where actionable detail matters most.
For Australian players, the biggest friction points are usually document mismatch in KYC and confusion around bonus eligibility. We therefore maintain a rolling help script with practical examples so support replies are less template-like and more useful for real account situations.
How to escalate effectively
If your issue is not resolved in the first pass, ask for case escalation and reference your previous ticket timestamp. Keep one thread per issue so context does not get fragmented. This improves continuity and avoids duplicate verification requests. For payout disputes, attach transaction IDs and mention whether your account passed full KYC.
You can also jump back to the homepage sections for deeper guidance: use /#faq for edge-case playbooks, /#banking for expected timelines, and /#safety for account-protection controls before submitting sensitive information.