About and contact · customer care

Betinia customer care: the verified support channel and the dispute rescue route

A reference for the verified support channel the desk links to. The desk refuses to publish a phone number, a WhatsApp handle or an email address on the editorial page; the verified channel is the operator's in-app help center.

Reading time · 5 min Last reviewed · 2026-08-10 Source-led

Section 01 · Verified facts

01

What the desk links to and what the desk refuses to publish

The betinia editorial desk links to the operator's in-app help center as the verified support channel. The desk refuses to publish a phone number, a WhatsApp handle or an email address on the editorial page because the desk cannot verify the identity of any contact that is not the operator's published channel.

The desk confirms the dispute rescue route on the canonical safety explainer. If the in-app help center cannot resolve the dispute, the player's next step is to write to the operator's grievance officer with the transaction IDs and the screenshot of the unresolved ticket; the player's final step is the state consumer forum if the grievance officer does not respond within the statutory window.

Detail block

Three facts the desk confirms about customer care

  1. Verified channel — the operator's in-app help center is the verified channel; phone, WhatsApp or email not on the operator's help center is refused.
  2. Dispute rescue — the next step after the in-app ticket is the operator's grievance officer with transaction IDs and the ticket screenshot.
  3. State forum — the final step after the grievance officer's statutory window is the state consumer forum.

Reader checklist

Five items the reader records before contacting the operator

  • Ticket IDthe in-app ticket ID from the unresolved complaint
  • Transaction IDsthe UPI or net-banking transaction IDs
  • Screenshotthe screenshot of the unresolved ticket
  • Date and timethe date and time of each contact attempt
  • Grievance officerthe operator's published grievance officer email

Escalation deep read

Three desks and three timelines the desk refers a reader to

The desk refers a reader to three external desks when the in-app help center and the operator's grievance officer have not resolved the report. The first external desk is the consumer-forum desk: the consumer court at the reader's district, with a 30-day filing window from the date of the unresolved ticket. The forum reads the ticket trail the reader keeps against the operator's published record. The desk's standing rule is that the forum is the cheapest escalation route and is the right first external step for any report that has crossed the operator's grievance officer's 14-day response window.

The second external desk is the cyber-crime desk at the reader's local police jurisdiction, for reports involving suspected fraud, account takeover or unauthorised transactions. The cyber-crime desk reads the operator's transaction record the reader keeps against the bank or wallet statement. The desk refers a reader to the cyber-crime desk only when the in-app help center and the operator's grievance officer have been silent for at least 30 days; a reader who escalates to the cyber-crime desk before exhausting the operator's published path will be redirected to the operator's path by the cyber-crime desk.

The third external desk is the appellate gaming desk at the state level, for reports involving the operator's state-eligibility block. The appellate desk reads the operator's published state block against the state's official gaming or home-department notice. The desk refers a reader to the appellate desk only when the operator's state block contradicts the state's official notice; a reader who escalates without that contradiction will be redirected to the operator's grievance officer.

The desk's standing rule across the three external desks is that the reader keeps the ticket trail for at least 90 days from the date of the unresolved report. A trail kept for less than 90 days cannot be used at the consumer-forum desk because the filing window is 30 days from the date of the unresolved ticket, and the appellate gaming desk requires the trail's last entry to be no more than 60 days old.

The desk also publishes a non-desk resource: the operator's published incident log, when the operator maintains one. An incident log is a public record of the operator's own reports, including dates and brief descriptions. The desk treats an operator's incident log as a canonical source for the operator's response history; a reader who reads the incident log before contacting the help center can avoid repeating a step the operator has already published as resolved.

Continue reading

Three pages the desk suggests after this read

Hub · Safety

Safety and KYC explainer

The canonical safety explainer with the dispute rescue route and state consumer forum step.

Continue →
Hub · Owner

Owner and operator record

The owner and operator record the desk cites for the grievance officer address.

Continue →
Hub · Responsible play

Responsible play toolkit

Limit-setting, deposit caps and the verified support channels.

Continue →

Section 04 · Dispute detail block

04

The four-row dispute path the desk follows when the operator does not respond

The desk treats a non-responsive operator as a four-row dispute task. The first row is the operator's grievance officer; the desk asks the reader to confirm the operator's grievance-officer contact against the operator's help center and to submit a written grievance with the operator's published turnaround in mind. The second row is the operator's appeal channel; the desk asks the reader to confirm the operator's appeal channel against the operator's help center and to refuse any appeal channel that routes through a third-party partner the operator does not name on the help-center page.

The third row is the operator's escalation path; the desk asks the reader to confirm the operator's escalation path against the operator's help center and to record the date of the escalation against the operator's stated acknowledgement turnaround. The fourth row is the operator's state-level escalation; the desk asks the reader to confirm the operator's state-level escalation against the operator's licence register and to submit a written escalation to the state regulator where the operator remains non-responsive across the third-row turnaround.

The desk's standing rule is that no dispute is closed until the operator's grievance officer has acknowledged the dispute in writing. The desk asks the reader to record the operator's acknowledgement against the operator's help-center page and to escalate to the state regulator where the acknowledgement is not received within the third-row turnaround.

Reader questions

Three questions the desk keeps answering on the dispute surface

How long does the operator's grievance officer take to acknowledge?

The operator's stated acknowledgement turnaround is published on the operator's help center; the desk records the turnaround and not a desk-measured turnaround. Where the operator routes grievances through a third-party partner, the partner's turnaround is the one the desk records. The desk asks the reader to confirm the turnaround before submitting the grievance and to escalate where the turnaround is missed.

Can a reader submit a dispute over the phone?

Yes, but the desk asks the reader to follow the phone submission with a written submission on the operator's verified domain. The desk's standing rule is that no dispute is recorded without a written submission, because the written submission is the row the desk references against the operator's status page. A phone-only submission is not auditable and the desk does not record it.

What does the desk record when the operator's grievance officer is unreachable?

The desk records the operator as friction-observed against the grievance-officer row and stamps the verdict chip with the date of the check. The desk asks the reader to verify the grievance-officer contact against the operator's help center and to escalate to the state regulator where the contact remains unreachable across two separate checks.

\n
\n
\n
\n
\n

Reading cadence

\n

How the desk re-issues the customer-care surface against the operator's record

\n
\n
\n

The desk re-issues the customer-care surface on three cadences. The first cadence is per quarter: the desk reads the operator's customer-care surface against the four-row reference and re-issues the verdict chip on the operator's customer-care surface. The second cadence is per half: the desk reads the operator's customer-care surface against the most recent MeitY notice and PROG Act 2025 standard, and re-issues the verdict chip on the operator's customer-care surface.

\n

The third cadence is per incident: where a reader reports a customer-care event that crosses the desk's incident threshold, the desk verifies the event against the operator's published record and re-issues the verdict chip only when the operator's record changes. The desk refuses to combine the three cadences into a single "last updated" line; the changelog records the date, the row the desk re-scored, and the verdict chip issued at the close of the check.

\n

For the per-row verification, the desk asks the reader to confirm the operator's customer-care surface against the four-row reference and to refuse any operator that buries the grievance-officer contact in a help-center article. The desk's standing rule is that no operator passes the customer-care criterion without all four rows being visible in-app; the desk records a buried row as a friction observation and stamps the verdict chip with the date of the check.

\n
\n
\n