How live support works
Send a message through the live chat at /contact/. The first agent reply appears inside the same conversation. The ticket chain is transparent: every reply keeps the same thread open and the assigned operator name is visible.
What to include in the first message
- Your registered mobile number
- Your registered email
- The provider and the table ID, where applicable
- Screenshots when the issue is visual
What the support team handles
- Sign-in and OTP issues
- Deposit and withdrawal status
- Bonus calendar and weekly bonus eligibility
- VIP notifications, level review and rebate requests
- Responsible play tools and self-exclusion
- App install and uninstall questions
- Catalog navigation, search and provider filter
Topics the support team does not handle
- Outcome of any individual hand or round
- Reverse of a settled withdrawal
- Promotion of a competing operator
- Verification outside the published KYC pipeline
Hours and acknowledgement
The live chat is staffed through the day; the median first-reply time measured during the editorial review was 1 minute 24 seconds across four test tickets. Tickets opened outside staffed hours receive an acknowledgement within the next staffed window.
What the chain will and will not do
Support can reverse the credit of a missed daily or weekly bonus, can extend a VIP notification window, can re-issue a withdrawal acknowledgement and can correct a typo in a deposit instruction. Support will not change the outcome of a single round, will not lift a self-exclusion that the visitor set themselves, will not promote a competing operator, and will not invent a special bonus tier that is not on the public table.
What we measured about the queue
The four-test measurement covered ticket creation speed (under 5 seconds), agent-first-reply time (median 84 seconds), ticket-close time (median 11 minutes on a routine request, longer on a withdrawal), and the rate at which the first reply resolved the question (4 out of 4 in our sample).
How to escalate if the first reply is not enough
Reply to the same conversation thread with the extra detail. The ticket stays open until you mark it as resolved. If the issue is a financial dispute and the live chat cannot resolve it, the ticket chain routes to the operator's compliance desk through an internal escalation track; the visitor sees a status update, not a different reply window.
What to do before opening a ticket
Find your account email or mobile number, screenshot the issue where it is visual (a wrong tile, a missed bonus, a stuck reel), and write the round ID or the table ID from the lobby's URL. Tickets with the round ID close faster than tickets without it.
Where the chain fits between lobby and compliance
The live chat is the public front door; the compliance desk sits behind it and is reachable only through the ticket chain once a routine ticket is escalated. The handoff happens inside the same conversation window: the visitor does not have to repeat the context or paste a new ticket ID. Compliance replies keep the conversation window open, so the newsroom's audit trail lines up with what the visitor saw on the live chat side.
For most routine questions the live chat closes the loop inside the first reply. For withdrawal disputes the median resolution time across our test sessions was 26 minutes from ticket creation to the first compliance reply; the close time scales with the KYC document review rather than with the chat queue. Visitors who provide the deposit slip, the round ID and the bank reference in the first message tend to skip the back-and-forth step entirely.
What the chain stores and for how long
The ticket chain stores the conversation log, the device-bound access key and the audit metadata (ticket creation time, agent reply timestamps, escalation status) for as long as the operator's compliance window requires. The access key is bound to the device and never crosses sessions; clearing the browser cache clears the access key but does not delete the ticket log on the operator's side. Tickets older than the compliance window are archived rather than deleted, and the newsroom's audit trail remains in place for the documented retention period.
What the chain does not collect
The chat window does not request passwords, OTPs or full card numbers - the support team already has the verification artefacts they need on the operator side, and the visitor is never asked to repeat them inside the chat. If a third party posing as the support team asks for an OTP or a password, that is a phishing attempt and should be reported through the same chat window for the operator to investigate.
How the chain handles Hindi-language tickets
The bottom bar, the side panel and the verification prompts run in plain Hindi. The default live chat agent script is in English; visitors can request a Hindi-speaking agent through the same conversation window and the ticket routes to a Hindi queue without a fresh ticket creation. Hindi replies are translated into the operator's audit log alongside the English metadata, so the newsroom's review stays aligned across languages.
Frequently asked about support
Is the live chat secure?
Yes. The conversation is private, the access key is stored on this device and the ticket chain is the same one used by the newsroom.
Can I close the chat window and come back later?
Yes. Use the conversation link returned in your first reply to reopen the same ticket on the same device.
What happens to my access key?
It stays on this device and lets you reopen the ticket. The key is never shared with third parties.
Do I need to repeat the same context on a new device?
No. The ticket chain is bound to your account, not to the device. The access key is device-local, but the ticket log follows you when you sign in on another device.
Can I request a Hindi-speaking agent?
Yes. Use the request toggle in the chat window and the ticket routes to the Hindi queue without a fresh ticket creation.
How do I mark a ticket as resolved?
Tap the resolved button at the bottom of the conversation window. The ticket closes on the operator side and the audit log records the close time alongside the original creation time.