dreamcatcher customer care: support channels and resolution paths.
A working reference for adult readers who need to contact a skill-game platform. The page walks the support channels, the typical response windows, the complaint escalation pathway and the documents to keep on file before opening a ticket.
Support channels and when to use each
Email support
The standard first stop. Most platforms publish a support email on the footer of every page. Email tickets create a written record that can be escalated later if needed. Typical response window: 24 to 48 hours.
In-app help
Most platforms offer an in-app help section with the most common questions. Use the in-app help for routine questions about KYC, deposits or withdrawal windows before opening a ticket.
Live chat
A few platforms offer live chat during business hours. Live chat is faster than email for an urgent issue but does not create a written record by default. Ask the chat operator to email the transcript after resolution.
Phone support
A few platforms offer phone support. Phone support is useful for KYC and withdrawal escalations but is rarely available 24/7. Note the name of the operator and the time of the call in your own record.
Documents to keep on file
PAN copy
A copy of your PAN submission. The PAN is required for TDS on real-money winnings above a threshold.
Aadhaar copy
A copy of your Aadhaar (masked to the last four digits). The masked Aadhaar is the standard KYC address proof.
Address proof
A copy of your address proof submission, dated within the last three months.
Withdrawal reference
A record of every withdrawal reference number with date and amount.
Support transcripts
A copy of every support response, in writing, with timestamp.
Platform changes
A record of every platform-side change (deposit cap, withdrawal window, KYC re-verification).
The complaint escalation pathway
Layer 01
Platform support email. First stop, most issues resolve here.
Layer 02
The platform\'s complaint officer (if named on the platform\'s responsible-play page).
Layer 03
The state gaming regulator named in the platform\'s licence disclosure.
Layer 04
The state consumer forum. Filing fees are nominal. Hearings are public.
Where the desk routes each type of platform question.
The desk is an editorial publication, not a customer-care desk. The desk does not accept wagers, run tables or hold player balances. Where a reader has a personal question about a specific platform, the desk routes the reader to the platform's own customer-care channel. The list below names the routes the desk recommends for each type of question.
Account or KYC question
Route to the platform's in-app support inbox. The platform's support inbox carries the reader's account identifier; the platform can answer a question that requires the reader's KYC submission on file without asking the reader to resubmit documents.
Withdrawal delay
Route to the platform's withdrawal-appeal inbox, where the platform publishes one. Where the platform does not publish a withdrawal-appeal inbox, route to the platform's general support inbox with the withdrawal reference number attached. The desk's wallet and KYC explainer lists the withdrawal reference numbers a reader should keep on file.
State eligibility
Route to the platform's state-eligibility check at sign-up. The platform's eligibility check asks for the reader's state and confirms whether real-money play is permitted in that state. Where the platform's eligibility check confirms the reader is ineligible, the platform does not accept the deposit.
Responsible-play question
Route to the platform's responsible-play tab. The tab carries the deposit cap, session-time prompt, cool-off period and self-exclusion pathway. Where the reader wants to set a self-exclusion window, the platform's responsible-play tab is the right channel. The desk's responsible-play page lists the helpline numbers a reader can call if appropriate.
App or technical issue
Route to the platform's in-app support inbox or the platform's app-store listing. The app-store listing carries the publisher name and the platform's app version. Where the reader has a specific technical issue, the platform's support inbox is the right channel because the platform's support team can read the reader's app logs.
Where to escalate when the platform does not respond.
Consumer forum
Where a platform does not respond to a withdrawal-appeal request within the platform's published window, the reader can escalate to the consumer forum at the district where the reader resides. The consumer forum handles disputes between consumers and service providers; the forum's process is documented on the consumer forum's website.
State regulator
Where the platform is licensed by a state regulator and the platform does not respond to the consumer forum, the reader can escalate to the state regulator. The state regulator's contact details are published on the state regulator's website. The desk's state-by-state eligibility page lists the state regulator for each state where the desk has published guidance.
Cyber cell
Where the reader suspects fraud — for example, an unauthorised withdrawal, a phishing impersonation or a stolen KYC submission — the reader can escalate to the cyber cell at the district where the reader resides. The cyber cell handles cybercrime complaints; the cell's process is documented on the cybercrime.gov.in portal.
What the desk does not do
The desk does not act as an intermediary between a reader and a platform. The desk does not publish customer-care phone numbers not already published on the platform itself. The desk does not guarantee that an escalation will resolve the reader's dispute; the desk publishes the escalation pathway so the reader can decide.
How the reader resolves a dispute with a platform.
Step 1: in-app support
The reader's first step is the platform's in-app support inbox. The platform's support team can read the reader's account history and answer a question that requires the reader's account details. The reader should attach the account reference number and the relevant transaction reference number to the support message.
Step 2: withdrawal-appeal inbox
Where the reader's question is about a withdrawal delay, the reader's second step is the platform's withdrawal-appeal inbox. The withdrawal-appeal inbox is a published channel for delayed withdrawals; the platform's published window is the platform's commitment to the reader. The reader should attach the withdrawal reference number.
Step 3: consumer forum
Where the platform does not respond to the withdrawal-appeal request within the published window, the reader can escalate to the consumer forum at the district where the reader resides. The consumer forum handles disputes between consumers and service providers. The reader files the complaint with the relevant transaction reference number.
Step 4: state regulator
Where the platform is licensed by a state regulator and the platform does not respond to the consumer forum, the reader can escalate to the state regulator. The state regulator's contact details are published on the state regulator's website. The desk's is-legal page lists the state regulator for each state where the desk has published guidance.
Step 5: cyber cell
Where the reader suspects fraud — for example, an unauthorised withdrawal, a phishing impersonation or a stolen KYC submission — the reader can escalate to the cyber cell at the district where the reader resides. The cyber cell handles cybercrime complaints; the cell's process is documented on the cybercrime.gov.in portal.
What a reader can ask the platform's customer-care team to do.
Ask for a status update
The reader can ask the platform's customer-care team for a status update on any pending request — for example, a withdrawal, a KYC re-verification or a closure. The platform responds with a status update within the platform's published window. The reader records the status update for future reference.
Ask for an explanation
The reader can ask the platform's customer-care team for an explanation of any decision — for example, a KYC rejection, a withdrawal reversal or a closure refusal. The platform responds with an explanation in writing within the platform's published window. The reader records the explanation for future reference.
Ask for an escalation
The reader can ask the platform's customer-care team to escalate a request to a senior reviewer. The platform escalates the request within the platform's published window. The senior reviewer responds within the platform's published window. The reader records the escalation reference number.
Ask for a written record
The reader can ask the platform's customer-care team for a written record of any communication. The platform provides the written record within the platform's published window. The reader keeps the written record on file for the duration of the dispute plus twelve months.
Ask for a phone call
Some platforms offer phone support as well as in-app support. Where the platform offers phone support, the reader can ask the platform's customer-care team for a scheduled call. The platform schedules the call within the platform's published window. The reader records the call reference number.
How to read this customer-care reference.
The reference above walks through the customer-care channels the desk recommends for each type of platform question and the escalation pathway the desk recommends when the platform does not respond. The desk does not act as an intermediary; the desk publishes the pathway so the reader can decide.
How the desk handles a customer-care question
The desk reads customer-care questions sent to the editorial email. The desk does not act on behalf of the reader; the desk directs the reader to the platform's own customer-care channel. Where the reader has a specific complaint about a platform's behaviour, the desk directs the reader to the escalation pathway above.
How the desk handles a published phone number
The desk does not publish customer-care phone numbers not already published on the platform itself. Where the reader wants to verify a phone number, the desk directs the reader to the platform's own contact page. A phone number published only by the desk and not by the platform is a warning sign.
How the desk handles a regulatory question
Where the reader's question is about state eligibility, federal carve-outs or regulatory consultation, the desk directs the reader to the is-legal page and the legal reference page. The desk does not publish legal advice; the desk recommends that the reader consult a lawyer for personal legal advice.
Three pages that complete the picture.
The rules ledger, the safety explainer and the responsible-play framework.