The fastest channel for a support request depends on the problem. Pick the row that matches.
A login reset is not the same workflow as a withdrawal hold. The triage table below matches each problem type to the channel that solves it fastest. The editorial site reads what the queue handles; the queue itself runs in the app.
Match the problem to the channel
Six problem types carry the queue. The table below names the channel that solves each one fastest. The fastest channel is rarely the same across problem types.
| Problem type | Fastest channel | Route |
|---|---|---|
| Login reset, OTP not received | In-app reset from the login screen | /login/ |
| Payment failure, UPI mismatch | In-app help with the transaction reference | /payments/ |
| Withdrawal hold, KYC re-check | In-app help from the wallet screen | /wallet-kyc/ |
| Responsible-play concern | In-app controls and help-line numbers | /responsible-play/ |
| DMCA notice or counter-notice | Notice procedure on the dedicated route | /dmca/ |
| Account deletion | Follow the deletion path | /delete-account/ |
Where the help request actually runs
The help request lives inside the app, not on the editorial site. The editorial site lists the channels and routes readers to the right one; the queue itself runs in-app.
In-app help
The fastest channel for any problem type. Open the app, tap the help icon, pick the category. Most responses land within minutes.
Email customer care
Use for issues that require attachments: KYC re-check screenshots, DMCA notices, withdrawal hold documentation.
Help-line (responsible play)
For responsible-play concerns, the help-line numbers on /responsible-play/ route to independent support, not the operator.
What the queue handles fastest, and what it handles slowly
Response times vary by problem type. Login resets and OTP re-sends resolve fastest; KYC re-checks and withdrawal holds take longer because they require human review.
| Problem type | Typical response shape |
|---|---|
| Login reset | Automated; resolves within minutes. |
| OTP re-send | Automated; resolves within minutes. |
| Payment failure | Automated for known error codes; human review for unknown codes. |
| Withdrawal hold | Human review; KYC re-check adds time on first withdrawal. |
| KYC rejection | Self-serve re-upload; human review only after a second rejection. |
| DMCA notice | Human review; documented procedure on /dmca/. |
What escalation looks like in the queue
Escalation is the path the queue follows when the first response does not resolve the issue. Three steps cover most escalations; a fourth step exists for responsible-play concerns and routes to independent support.
- Step 1, first response from in-app help. Most queries resolve here.
- Step 2, re-open the ticket with the previous reference number and a fresh description.
- Step 3, request escalation to the senior queue via email customer care.
- Step 4 (responsible play only), contact the independent help-line on /responsible-play/.
Documenting a complaint that needs a paper trail
A complaint that needs a paper trail follows three rules: capture the transaction reference, capture the screenshot, send the email with both attachments. The email template on /customer-care/ carries the same rules.
- Always include the in-app ticket reference number.
- Attach screenshots, not typed descriptions, for any UI error.
- Keep one email per issue; do not bundle multiple complaints.
- Reply within the same thread; do not open a new ticket for the same issue.
Closing the wallet and removing the account
Account deletion is irreversible once the wallet is closed. The path on /delete-account/ walks the reader through balance withdrawal, KYC purge and final confirmation. Read the deletion route before opening the request.
- Withdraw the wallet balance to a verified bank account first.
- Confirm any pending contest or tournament entries are settled.
- Open the deletion request from the wallet screen; the request is logged with a timestamp.
- Deletion is final within 30 days; KYC documents are purged from the operator's store.
Where copyright notices live
Copyright notices and counter-notices follow the documented procedure on /dmca/. The route lists the required fields, the contact email and the response window. Notices that miss the required fields are not actioned.
- Required: identification of the copyrighted work, location of the alleged infringement, contact details, good-faith statement.
- Counter-notices follow the same shape with the respondent's identification.
- Response window is published on /dmca/; do not assume a specific timeline.
Five routes the queue points to
The triage table is the entry point. The routes below carry the specific reading for each problem type.
Six questions the support queue handles every day
What is the fastest channel for login issues?
In-app help from the login screen. The editorial site cannot reset credentials; the in-app reset path is the only one that works.
What is the fastest channel for payment issues?
In-app help with a transaction reference. Per-rail timing lives on /payments/.
What is the fastest channel for withdrawal issues?
In-app help from the wallet screen; KYC re-check runs on first withdrawal only.
Where do I send a responsible-play concern?
The /responsible-play/ route lists the in-app controls and the help-line numbers.
How do I file a DMCA notice?
The /dmca/ route lists the notice and counter-notice procedure.
How do I delete my account?
Follow the path on /delete-account/. Deletion is irreversible once the wallet is closed.
Three things the editorial site lists but the queue cannot resolve
The editorial site lists routes that look like support but are not. Three cases sit outside the queue.
- Bonus value disputes: the bonus value lives in the app; the editorial site does not pin a number.
- Sports market disputes: live odds and match settlement are not in the public capture.
- Casino game-specific volatility: the RTP field is per-row; the editorial site does not rank by it.