Customer care — how to get help, and how to escalate

Support channels and what they handle

Writing a good support ticket

• Note your registered phone number and the partner operator app version.
• Describe the issue as a fact, not an emotion — “I joined contest X and the points table does not show player Y” reads better than “your app is broken”.
• Include the screenshot or screen recording in the ticket; not in a separate email.
• Reply with the ticket ID if you escalate.

When and how to escalate

If the first ticket is unresolved, request an escalation. Mention that you want the ticket re-opened with a named case owner. The partner operator is required to provide escalation paths under IT-Act and consumer-protection rules.

The desk’s editorial pathway

If your issue remains unresolved after the partner operator’s escalation pathway, the desk can publish a public note in our news desk describing the issue, the ticket, and the elapsed time. We do not publish user PII. We do publish patterns of unresolved complaints.

The dispute pathway

If a contest result or a withdrawal is in dispute, the formal pathway runs through the partner operator’s customer-care team. The desk publishes a correction pathway if the dispute reveals a partner operator process gap, but the dispute itself must be handled through the partner operator.

When to escalate

If the first ticket is unresolved for 48 hours, request an escalation. If the escalation is unresolved for 7 days, file a complaint with the partner operator’s regulator-facing consumer-care channel. Each Indian state has a consumer dispute resolution pathway.

How the desk can help

The desk can publish a public note describing the unresolved pattern. We do not publish user PII. We publish the pattern so other readers can be aware of the same issue and adjust their partner-operator contact approach accordingly.

Common unhelpful responses — when to escalate

“Your issue is not covered by the support policy.” A specific appeal of this ruling is required before escalation. “Your account has been reviewed and no error was found.” A second appeal with new evidence is required. The desk publishes a representative sample of unhelpful responses in our corrections ledger when a pattern develops.

When the desk can help

The desk can publish a public note describing an unresolved pattern. The desk can refer the partner operator’s escalation team to specific cases where editorial coverage is material. The desk can publish corrections if the dispute reveals a partner operator process gap. The desk cannot resolve individual account issues; the partner operator is the right destination.

State-specific pathway

If your state’s consumer dispute resolution body is engaged (through a state consumer court or consumer protection cell), the desk can publish a public note describing the case with a verification date. We do not publish user PII; we publish the pattern.

Keeping the trail

Keep the ticket ID. Keep the time of the original complaint. Keep the email screenshots or chat logs. These trail records speed up escalation and help the partner operator’s customer-care team identify the case. The desk can reference the trail in a public note if needed.

What the desk cannot do

The desk cannot resolve individual financial disputes (partner operator is the right destination). The desk cannot reverse a state-level restriction (the player must respect jurisdiction). The desk cannot override a partner operator’s terms-of-service decisions (the operator is the publisher of its own rules).

The desk’s reading of the support pipeline

Most partner operators run a three-tier support pipeline: tier 1 (email or chat), tier 2 (escalated by ticket ID), tier 3 (helpline for KYC lockouts or payment failures). The desk reads each tier’s published SLA and cross-references with the partner operator’s actual response time on public social channels.

What the desk tracks

Average response time. Average resolution time. Frequency of escalation. Frequency of unresolved tickets. Frequency of partner operator responses that reference internal policies. The desk cross-references these signals against the winners ledger quarterly.

The desk’s reading

The desk reads each published support pipeline note as editorial reference. The reader can use the desk’s reading to inform their own support experience. The desk does not run a parallel support team and does not collect user tickets.

The desk’s customer care reading

The desk reads each published customer-care pipeline as editorial reference. The reader can use the desk’s reading to inform their own support experience. The desk does not run a parallel support team and does not collect user tickets.

When the desk can publish a note

The desk publishes a public note about an unresolved pattern when: (a) the partner operator’s escalation pathway has been exhausted; (b) the pattern is material (multiple users affected); (c) the verification reviewer can confirm the pattern. The note carries a verification date and a corrections pathway.

The desk’s three asks

First, document the issue with screenshots, ticket IDs, and timestamps. Second, escalate through the partner operator’s full pathway before reaching the desk. Third, keep the trail organised — the easier the trail, the faster the desk can publish.

What the desk will not respond to

Individual account issues. Wallet or KYC questions. Tier-2 escalation requests the partner operator can handle directly. The desk publishes editorial reference, not support.

The desk’s three pipeline asks

First, document the issue with screenshots, ticket IDs, and timestamps. Second, escalate through the partner operator’s full pathway before reaching the desk. Third, keep the trail organised — the easier the trail, the faster the desk can publish. The desk’s role is editorial reference; the partner operator runs the support pipeline.

The correspondence archive

The desk maintains a correspondence archive of customer-care patterns. The archive is read-only and is available to any reader who requests it through the contact pathway. The archive is part of the desk’s quality signal.

What the desk publishes on support

Public notes on unresolved patterns. Verification reviewer names on each note. Corrections pathway entries when the partner operator fixes the gap. The desk does not publish individual user tickets.

Dispute pathway detail

If a contest result or a withdrawal is in dispute, the formal pathway runs through the partner operator’s customer-care team. The desk publishes a correction pathway if the dispute reveals a partner operator process gap, but the dispute itself must be handled through the partner operator.

The desk’s three customer care asks

First, document the issue with screenshots, ticket IDs, and timestamps. Second, escalate through the partner operator’s full pathway before reaching the desk. Third, keep the trail organised — the easier the trail, the faster the desk can publish.

The correspondence cycle

Receipt (logged with a date) → review → acknowledgement within 7 days → resolution or correction (if applicable) → closure. The desk maintains a correspondence archive of customer-care patterns. The archive is read-only and is available to any reader who requests it through the contact pathway.

Public notes on support

The desk publishes public notes on unresolved patterns. The notes carry verification dates and corrections pathways. The desk does not publish individual user tickets. The desk publishes editorial reference; the partner operator runs the support pipeline.

Closing thoughts on support

The desk’s role on support is editorial. The partner operator runs the support pipeline. The desk reads each pipeline note, publishes a public correction when the partner operator identifies a process gap, and maintains a public ledger of unresolved patterns.