Cricket customer care — helpline, support path, dispute escalation
Customer care — the verified path, helpline and escalation.
This page is a customer-care reference. It covers the helpline hours for the major cricket operators, the standard support path, the published SLA (service-level agreement) and the dispute-portal links for the regulator. Where the operator’s customer-care hours are shorter than the user expects, the desk publishes that fact on the operator page.
The desk treats customer-care the way it treats a fixture — three sources before publishing a helpline number, an editor’s note when the source changes, and a clear note when the operator doesn’t publish a helpline.
Five steps from “help me” to a written answer.
Open the operator’s in-app support
Most operators carry a chat channel inside the app. The desk recommends the in-app channel for fastest response.
Attach the issue number
Every chat transcript carries an issue number. Save it. The issue number is what the supervisor or the regulator will need.
Ask for a supervisor
If the first agent can’t resolve in fifteen minutes, ask for a supervisor by name. The supervisor has the authority to escalate.
Request written reply
Ask the operator to send a written reply by email. A written reply is what survives a regulator dispute.
Escalate via the regulator’s portal
If the written reply is not received in five working days, escalate via the regulator’s dispute portal. The desk publishes the portal links on the legality page.
Support path
A support path that gets followed is the support path that gets the operator to respond. The desk publishes the steps above because they cover what every legitimate operator’s customer-care team is set up to handle.
What the major operators publish, and what the desk has measured.
Operator-published hours
Most operators publish 9–9 helpline hours, with chat-only support outside those hours. The desk publishes the published hours on the operator page.
Measured response time
The desk runs a monthly measurement of the in-app chat response time. The published score is on the operator page, with the methodology on the verification page.
Public SLA
Some operators publish a service-level agreement for response time. The desk cross-checks the published SLA against the measured response time every quarter.
When the operator can’t help — the regulator portals.
Every regulated operator in India is bound to a dispute-resolution process through the regulator. If the operator’s written reply is not received in five working days, the regulator’s dispute portal is the next step. The desk publishes the portal links on the legality page, with the regulator name, the dispute form URL and the standard SLA.
For users outside India, the equivalent portal is the jurisdiction’s regulator. The desk publishes international regulator links on the operator page where applicable.
Customer-care questions, answered.
What’s the average response time?
Most operators respond inside four minutes on the in-app chat during published hours. Outside published hours, the response is the next working morning.
What about the helpline number?
Most operators publish a helpline number. The number on the operator’s home page and the verification page should match.
What if the operator doesn’t publish a helpline?
The desk flags the operator on the warning list. A legitimate regulated operator must publish a customer-care channel.
Where do I send a complaint?
The regulator’s dispute portal. The customer-care page has the portal links.
Can I escalate on Twitter / X?
Most operators carry a customer-care presence on X. A public complaint tends to surface a written reply faster than a private chat.
What about the app store complaint path?
App Store and Play Store complaints do not resolve financial disputes. They resolve app-store-specific issues (refund, account deletion).
Do you publish a satisfaction score?
No — the desk does not aggregate satisfaction scores across operators. The verification page publishes the desk’s measured response time.
What about supporting documents?
The desk recommends attaching a screenshot of every chat reply, plus the issue number, plus a copy of the original complaint. The regulator’s dispute form accepts these as supporting documents.
The customer-care pages publish every month with the measured response time.
Editorial coverage of the customer-care path — with the helpline, the SLA and the regulator links on the page.
Response time, first-contact resolution, dispute rate.
The editorial desk runs a monthly measurement of three customer-care signals across the operators we link to. The measurement is published on the methodology page, with the per-operator scores broken out. The three signals are response time (the median time between a user opening a chat and the first agent reply), first-contact resolution (the percentage of chats resolved without a supervisor) and dispute rate (the percentage of resolved chats that escalate to the regulator within thirty days).
Response time is the most-watched signal. Most operators publish a response-time target of “under five minutes” during published hours. The desk measures the actual response time on a rolling thirty-day window and publishes the median. Operators with a measured response time of under five minutes are flagged as passing; operators with a measured response time of 5–10 minutes are flagged as borderline; operators with a measured response time of over ten minutes are flagged as failing.
First-contact resolution is the second signal. Most legitimate operators aim for first-contact resolution of over 80%; the desk publishes the measured score. Operators with a measured score of over 80% are flagged as passing.
Dispute rate is the third signal — and the one that catches the operators the regulator has been slow to act on. The desk tracks the percentage of operator-resolved chats that escalate to the regulator within thirty days; operators with a rate of over 2% are flagged as borderline; operators with a rate of over 5% are flagged as failing and removed from the desk’s recommendation list.
The desk publishes the methodology and the per-operator scores on the customer-care page. The page is updated on the first Monday of the month, with a rolling thirty-day window.
The four things a good support channel should do.
A good customer-care channel should do four things, in order: acknowledge the issue within the published SLA; escalate to a supervisor when the first agent can’t resolve; deliver a written reply by email; record the chat transcript against the user’s account so the issue persists if it recurs.
The acknowledgement is the SLA — typically a response time of under five minutes during published hours. The desk measures the actual response time on a rolling thirty-day window. Operators that fail the SLA are flagged on the methodology page.
The escalation is what separates a good support channel from a great one. The first agent can resolve straightforward issues; the supervisor can resolve issues that require account-level action (refunds, KYC reversals, manual verifications). A support channel that escalates within fifteen minutes for the right issues delivers first-contact resolution above eighty percent.
The written reply is what survives a regulator dispute. A chat transcript is perishable; an email is durable. The desk recommends requesting a written reply before the chat closes, and the operators that fail to deliver a written reply are flagged on the methodology page.
The persistence of the chat transcript against the account is the fourth quality signal. A support channel that records every interaction ensures that a recurring issue doesn’t restart from zero every time the user returns.
The dispute path, when the operator can’t help.
When an operator’s support channel can’t help within the published SLA, the next step is the regulator’s dispute portal. The portal is the operator’s last-resort path — the operator is bound to respond to the regulator’s notice within the published timeframe, and the regulator has the authority to escalate the dispute to a binding decision.
The dispute portal’s form usually asks for the issue number (from the operator’s chat transcript), the operator name, the dispute type (refund, KYC, withdrawal, account suspension), the dispute narrative (what happened, what the user wants), and the supporting documents (chat transcript, screenshot of the original issue, copy of the regulator’s registration confirmation). The desk recommends attaching all five.
The regulator’s response time on a dispute is published on the regulator’s website. Most regulators respond within seven working days for a simple dispute, and within thirty days for a complex dispute. The regulator’s decision is binding on the operator — the operator must comply within the published timeframe.
The desk publishes the regulator dispute portal links on the legality page. The links are to the regulator’s official portal, with the operator’s licence number and the dispute-form URL. The user is responsible for completing the form; the desk does not submit on the user’s behalf.