Support desk

Anything tied to your account or balance goes to the operator. Anything tied to the lobby's index or editorial coverage comes to the desk below.

First line: the operator's help desk

Account state, balance, withdrawals, KYC review and bet settlement are owned by the operator, not by this lobby. Open the in-app help widget first; the operator's team has the account state, the withdrawal pipeline, and the published SLA.

If the in-app widget is unavailable, the operator's web help center is the next stop. A ticket opened on web is visible inside the app on your next login; the two surfaces share one queue and one ticket ID.

What the lobby can answer

How a lobby filter behaves, what a provider room label means, where to find a specific title or campaign, how to interpret the lobby's last-crawled date, how to read the comparison tables on the homepage and the provider profile pages.

Editorial questions about the news desk (corrections, story ideas, source-tagging, reposts) are also lobby-side. Send them via the desk below and the editor replies within one business day.

What to include in a good ticket

Ticket header: one sentence that names the title, the action, and the symptom. Example: "Roulette 1884 - bet settled but balance not credited after 15 minutes". A clear header shortens the time-to-first-reply by routing the ticket to the right specialist on the operator's side.

Ticket body: a screenshot of the issue, the timestamp in IST, your user ID (never your password or full card number), and the device or browser build. The more specific you are, the faster the operator's team can resolve. If the issue involves a withdrawal, include the transaction ID from the cashier; the operator's payment team can trace it directly.

Avoid: requesting a refund on a settled round without a documented bug. The operator's settlement rules are published; the operator's team will not reverse a settled round that followed the published rules. If you believe a bug was involved, describe the bug and the team will review.

Escalation path

If the operator's help desk has not resolved your ticket within the published SLA, send the ticket ID to the lobby via /contact/. The lobby team does not have account access, but the editorial team can flag systemic issues with the operator's product team and request a priority review.

For policy questions (terms, privacy, KYC processes), the lobby pages /terms/, /privacy/, and /legal/ are the canonical statements. If a policy page contradicts what the operator told you, the operator's contract wins; the lobby updates its pages to match.

Self-serve resources

FAQ at /faq/ covers the most common lobby-side questions (filter behaviour, room labels, sitemap, news desk).

How-it-works at /how-it-works/ explains the lobby-to-operator flow, KYC, deposit methods, and the first-session walkthrough.

News at /news/ lists recent lobby changes, promo timing, and policy updates. Subscribe to the RSS feed for one-click delivery to your reader.

Contact at /contact/ is the form for everything else - editorial corrections, partner pitches, and policy questions.

Response times and what to expect

Operator live chat typically responds in under five minutes during peak hours, and under a minute during off-peak. The lobby cannot influence the operator's queue; the lobby's role is to point you at the right channel for the question. If your question is account-scoped - KYC, withdrawal hold, bet settlement - the operator's in-lobby widget is the right path.

Email support typically responds within the operator's published SLA, which is usually 24 to 48 hours for general questions and longer for KYC document review. The lobby does not track the operator's queue and cannot expedite; the desk's editorial line is to give the operator the published SLA before escalating, because premature escalation tends to lengthen the response time, not shorten it.

For lobby-side questions - filter not behaving, room card showing a wrong status, sitemap missing a page - the lobby team reads the inbox daily and routes the message to the writing desk, the crawl pipeline, or the operator liaison depending on the topic. The lobby does not promise an instant response because the editorial verification step is part of the editorial line.

What you should keep on your end: the canonical support URL surfaced in the footer, a habit of including your transaction ID or account reference where relevant, and a clear topic line that lets the operator route your message to the right specialist. The lobby's editorial line is that a well-routed question is faster than an urgent one.

Status, outages, and what the lobby does

The lobby runs a daily HTTP-200 check on each outbound operator route. If a route is marked degraded, the room card flips to ROUTE DOWN with a small status dot, and the news desk publishes a short status update under /news/. The lobby does not hide the room during a transient outage because hiding the room would be misleading; the room is still there, the route is just temporarily unavailable.

Operator-side outages usually fall into three categories. Scheduled maintenance: the operator publishes a window ahead of time, the lobby surfaces the window on the room card and the news desk publishes a heads-up. Unscheduled regional outage: the operator investigates, the lobby surfaces the degraded state until the operator reports a fix. Account-specific issue: this never affects the lobby because the lobby is not account-scoped; if only your account is broken, the operator's in-lobby widget is the right channel.

The lobby's editorial line on outages: prefer to wait until the route is verified before you deposit, but if you have already deposited and the route is degraded, contact the operator directly with your transaction ID. The lobby does not hold your balance; the operator does. Waiting on the lobby for an account-specific resolution will not work; the lobby's degraded flag is about the route, not your account.

What you should keep on your end: the operator's published maintenance window if you are planning a deposit, the URL of the canonical operator support channel, and a habit of checking /news/ before you assume the route is permanently broken. The lobby's news desk is the fastest way to see a real-time status update; the operator's status page is the authoritative source if the news desk is silent.

A short note on privacy and your data

The lobby stores a single cookie to remember your last filter selection. The cookie is functional, not analytics, and it stays on the device; the lobby does not transmit it to a third party and does not use it for advertising. Clearing cookies from your browser clears the filter; the lobby does not maintain a server-side copy.

Optional analytics cookies are off by default and only enabled when you click Accept all on the consent panel. If you decline, the lobby continues to work with the functional cookies only and the analytics pipeline does not see your visit. The consent panel is surfaced on first visit and the choice is recorded for the session; you can change the choice at any time from the footer Cookie settings link.

Account-scoped data - KYC documents, deposit history, withdrawal status - lives with the operator. The lobby never sees that data and never asks for it. If a screen inside the lobby claims to be a KYC screen, it is the operator's screen embedded for your convenience; the data still comes from the operator and the operator's privacy policy applies.

What the lobby will not do with your data. The lobby will not sell visit data to a third party. The lobby will not run advertising networks on its articles. The lobby will not include tracking pixels in any script bundle. The editorial line is that the lobby is an index, not an ad surface, and the privacy posture follows from that line.