Customer Care

How to reach Cricplay’s customer-care team.

In-app routes, email, responsible-play channels, expected response times, and what to do when support is slow. Editorial guidance, no shortcuts.

In-app route When support is slow

Section One

The in-app route: the only route you should use first.

The in-app customer-care route is the right first contact for any platform issue. The route opens a ticket tied to your account, your KYC file, your deposit history and your session log. The customer-care team can see everything they need to resolve the issue without asking you to repeat it.

How to open an in-app ticket

Open the app and sign in.
Tap the menu icon (usually top-left), then “Help” or “Support”.
Select the issue category that matches your problem: deposit, withdrawal, KYC, table, app, responsible play, or other.
Write a short description. Include the timestamp of the issue, the amount (if relevant), and any error message you saw.
Attach a screenshot if the issue is visual. Tap the attachment icon and select the screenshot from your gallery.
Submit. The platform generates a ticket ID; note it for follow-up.

When to use the in-app route

Use the in-app route for any issue that the platform can resolve without contacting an external party: deposit credit, withdrawal, KYC, table lag, app behaviour, bonus credit. The in-app route is also the right place for responsible-play requests including cooling-off and permanent exclusion.

Section Two

Email: when the in-app route is unavailable.

Use email when the in-app route is unavailable: the app is failing to sign in, the platform is in a maintenance window, or your account has been locked and you cannot reach the in-app menu. The platform’s customer-care email is published in the website footer and in the responsible-play section of the app.

How to write a useful customer-care email

The most useful customer-care emails share three things: the registered mobile number, the issue summary, and the timestamp. The less useful emails share a long description of the user’s feelings about the platform. The customer-care team can resolve technical issues; they cannot resolve frustration. Keep the email factual.

Following up

If you do not receive a response inside the platform’s stated email-response window (commonly 24 to 48 hours on working days), follow up with the same email thread. Do not open a new email thread for the same issue; the customer-care team’s ticketing system will treat the new thread as a separate case and may duplicate effort.

Section Three

Responsible-play channels: a separate path.

Every reputable Indian rummy platform runs a responsible-play channel separate from the customer-care channel. The responsible-play team handles cooling-off and permanent exclusion requests, account closure, family-member concerns, and self-exclusion appeals. The team is reachable through a different menu path and a different email address; the platform publishes both in the responsible-play section.

No explanation required

You do not need to explain why you are requesting a cooling-off or permanent exclusion. The responsible-play team will apply the exclusion on your behalf without further questions. The platforms that ask for an explanation are the platforms that misunderstand the responsible-play mission; the platforms that apply the exclusion without question are the platforms that understand it.

Family-member concerns

If you are a family member concerned about a player’s behaviour, the responsible-play channel is the right place to write. The team can apply a cooling-off exclusion on the player’s behalf, with appropriate verification. The team will not share account details with the family member; the team will share that an exclusion has been applied.

Section Four

What to do when customer-care is slow.

Customer-care response times vary. The platforms that publish a response-time SLA on their help page are the platforms whose support teams are actually held to it. The platforms that do not publish an SLA are usually the platforms whose support teams are understaffed. If you find yourself waiting longer than the published SLA, follow these three steps.

Step one: check the platform’s status page

The status page lists ongoing incidents: deposit rail outage, withdrawal delay, KYC queue backup. If your issue matches an open incident, the team is already working on it. Add your ticket ID to the incident’s watchlist; you will be notified when the incident closes.

Step two: follow up the same ticket

Send a short follow-up to the same ticket thread: “Following up on ticket 12345, raised on Monday at 10am. Issue still unresolved. Please confirm the next step.” Do not open a new ticket. The system will treat the new ticket as a duplicate and may de-prioritise the original.

Step three: escalate to the responsible-play channel

If the customer-care team has not responded inside 72 hours on a working day and the status page shows no related incident, escalate to the responsible-play channel. Responsible-play teams typically have shorter response windows and broader authority to escalate to a manager.

Section Five

Outside help: when to escalate beyond the platform.

If the platform’s customer-care team has failed to resolve a withdrawal, a KYC issue, or a bonus credit after 14 working days, you can escalate beyond the platform. The escalation paths depend on where the platform is licensed.

For Indian platforms

The state gaming authority where the platform is licensed is the first escalation. The authority’s complaint form is published on its website. Provide the ticket IDs, the timestamps, and the supporting screenshots. The authority will write to the platform on your behalf.

For consumer-protection issues

The National Consumer Helpline (1915) and the consumer forum route are available for cases involving unfair trade practice, misleading advertising, or contract non-performance. The consumer forum is slower than the platform’s own escalation path but is the right destination when the platform has stopped responding.

Section Six

What the customer-care team can and cannot do.

The customer-care team can resolve most platform issues. They cannot resolve every issue, and they cannot resolve issues that are outside the platform’s control. The list below is editorial, not contractual.

What the team can resolve

Deposit credits that did not arrive in your wallet.
Withdrawal delays beyond the platform’s stated window.
KYC review questions, document re-uploads and name-match errors.
Bonus credit queries, including missed referral codes.
App and web client bugs, including lag and session failures.
Account recovery, password reset and trusted-device management.

What the team cannot resolve

Bank-side issues with your deposit or withdrawal. These are routed to your bank.
UPI rail issues, including failed OTPs and PSP outages. These are routed to your UPI provider.
Income-tax or GST queries. These are routed to your chartered accountant.
Legal questions about state-wise eligibility. The platform publishes its state-wise eligibility page; legal questions are for a lawyer.

Open the responsible-play chapter Is rummy legal?

Section Seven

Preparing a useful support ticket.

The most useful support tickets share four things: a clear subject line, a short summary of the issue, the relevant timestamps and amounts, and any screenshots. The platform’s customer-care team reads hundreds of tickets a day; a useful ticket gets resolved faster because it requires fewer follow-up questions.

The subject line

The subject line should name the issue category and the specific problem. Examples: “Withdrawal pending since 02 Aug”, “PAN KYC rejected, re-uploading”, “Referral bonus not credited for invitee XYZ”. The platform’s ticketing system groups tickets by subject line; a clear subject line routes the ticket to the right team faster.

The summary

The summary should describe the issue in two or three short sentences. Avoid the long story. The customer-care team needs the facts, not the feelings.

Timestamps and amounts

Include the timestamp of the issue (in DD MMM YYYY HH:MM format) and the amount involved (deposit amount, withdrawal amount, KYC rejection reference). The platform’s back-office tools can pull the exact transaction by timestamp.

Screenshots

Attach a screenshot if the issue is visual: a withdrawal stuck in processing, a KYC rejection message, an error popup. The screenshot should show the full screen including the timestamp if possible.

Open the responsible-play chapter Wallet & KYC

Working the channel

Why the in-app route is the first route, every time

Customer-care is the channel most players use once and never again. The first contact usually goes well, because the ticket is fresh and the operator can find the account quickly. The second contact, weeks or months later, often goes worse, because the ticket references an older session and the operator has to reconstruct the history. The pattern is consistent across platforms.

The in-app route is the first route for a reason. The ticket is tied to the account automatically; the operator sees the device, the platform version, and the most recent transaction log without asking. The reader who uses the in-app route gets a faster first reply and a more accurate first diagnosis. The reader who uses email instead pays the cost of the operator reconstructing what the in-app route would have shown.

The honest caveat is that some platforms treat the in-app route as a triage layer, not a resolution layer. The first reply is a ticket acknowledgement. The actual fix happens after the operator escalates to a specialist team. The reader who expects a resolution in the first reply is the reader who is surprised when the second reply takes longer than the first.

If the in-app route stalls, the next step is to ask for the ticket reference number and the escalation timeline in writing. A ticket reference number, with a date, is the difference between a tracked complaint and an untracked one. The desk has used ticket references to escalate complaints that would otherwise have sat in a queue for weeks.