myteam11 Indiaeditorial reading desk

Support guide

Pause, preserve, then use the published channel.

Three moves the desk makes when a problem opens. Six problem patterns and the desk's first response. Three escalation steps to the grievance officer.

Play Now Customer care
Matte headset on a desk beside a small notepad and a potted plant

Find a channel

Three moves the desk makes when a problem opens.

1

Pause account activity

Pause deposits, withdrawals and contest entries. Pause any active contest entry only after the contest has closed, since mid-contest edits are not allowed.

2

Preserve the record

Save the transaction ID, the date, the rail and the channel used. Save a redacted screenshot of any communication. Save the operator's reply window.

3

Use the published channel

Open the customer-care page. Verify each channel before relying on it. Email is auditable, the hotline is not.

Six problem patterns

Common issues and the desk's first response.

  • Deposit not credited: wait one rail cycle, then check the operator's deposit-status page. If still missing, raise an in-app ticket with the transaction ID.
  • Withdrawal pending: confirm KYC is complete. If KYC is complete and the withdrawal is still pending past the published window, raise an in-app ticket.
  • Bonus not credited: confirm the bonus code is entered at the right step. If the code is correct and the bonus is missing, raise a ticket with the deposit ID.
  • Login fails: check the URL bar, the certificate and the domain spelling. A cloned login form is one of the most common phishing patterns.
  • App crash: read the permissions list. Reboot the device. Re-install only from the operator's verified entry.
  • Account compromise: pause the account, change the password, raise a ticket and preserve the record. The operator's fraud team publishes a contact channel.

Escalation

What to do when a first reply does not resolve.

Preserve the transaction ID, the date and the channel used for every contact. If a first reply does not resolve, escalate to the grievance officer named on the customer-care page. If the officer does not respond, contact the regulator listed on the operator's terms page.

Customer-care guide

Phishing checklist

Six signals the desk treats as suspect.

  • OTP request
  • Password request
  • Private UPI transfer request
  • Remote-control access request
  • Unknown contact channel
  • Pressure to act before the published reply window closes

Source

Where the desk sourced each row.

Three moves, six problem patterns and the escalation steps are taken from the operator's published customer-care and help pages, captured 2026-08-17, marked subject to confirmation. The desk updates these rows when the operator publishes a change.

What the desk does not do

Two things the desk refuses to do.

The desk does not act as a customer-care channel. The desk cites the operator's published channels. The desk also does not publish a customer's personal data. KYC uploads and account numbers stay on the operator's first-party flow.

Related reading

Three routes the desk opens after the support guide.

Customer care Wallet & KYC Responsible play

Six problem patterns

Common issues and the desk's first response.

  • Deposit not credited: wait one rail cycle, then check the operator's deposit-status page.
  • Withdrawal pending: confirm KYC is complete, then raise an in-app ticket.
  • Bonus not credited: confirm the bonus code is entered at the right step.
  • Login fails: check the URL bar, the certificate and the domain spelling.
  • App crash: read the permissions list, reboot the device, re-install from the verified entry.
  • Account compromise: pause the account, change the password, raise a ticket.

Escalation path

Three steps when a first reply does not resolve.

  1. Preserve the transaction ID, the date and the channel used for every contact.
  2. Escalate to the grievance officer named on the customer-care page.
  3. Contact the regulator listed on the operator's terms page if the officer does not respond.

What the desk will not print

Two things the desk refuses to do.

The desk does not act as a customer-care channel. The desk cites the operator's published channels. The desk also does not publish a customer's personal data. KYC uploads and account numbers stay on the operator's first-party flow.

How the desk reads a problem

Reading a problem as a three-step response.

A problem is a three-step response, not a single contact. Pause account activity, preserve the record, use the published channel. Each step is a row the desk can verify.

Three moves the desk makes

  1. Pause account activity: pause deposits, withdrawals and contest entries. Pause any active contest entry only after the contest has closed.
  2. Preserve the record: save the transaction ID, the date, the rail and the channel used. Save a redacted screenshot of any communication. Save the operator's reply window.
  3. Use the published channel: open the customer-care page. Verify each channel before relying on it. Email is auditable, the hotline is not.

Six problem patterns

  • Deposit not credited: wait one rail cycle, then check the operator's deposit-status page.
  • Withdrawal pending: confirm KYC is complete. If KYC is complete and the withdrawal is still pending past the published window, raise an in-app ticket.
  • Bonus not credited: confirm the bonus code is entered at the right step. If the code is correct and the bonus is missing, raise a ticket with the deposit ID.
  • Login fails: check the URL bar, the certificate and the domain spelling. A cloned login form is one of the most common phishing patterns.
  • App crash: read the permissions list. Reboot the device. Re-install only from the operator's verified entry.
  • Account compromise: pause the account, change the password, raise a ticket and preserve the record.

Six phishing signals

  • OTP request
  • Password request
  • Private UPI transfer request
  • Remote-control access request
  • Unknown contact channel
  • Pressure to act before the published reply window closes

FAQ

Six questions about the support desk.

What if my deposit is not credited?
Wait one rail cycle, then check the operator's deposit-status page. If still missing, raise an in-app ticket with the transaction ID.
What if my withdrawal is pending?
Confirm KYC is complete. If KYC is complete and the withdrawal is still pending past the published window, raise an in-app ticket.
What if my login fails?
Check the URL bar, the certificate and the domain spelling. A cloned login form is one of the most common phishing patterns.
What if my bonus is not credited?
Confirm the bonus code is entered at the right step. If the code is correct and the bonus is missing, raise a ticket with the deposit ID.
What if my account is compromised?
Pause the account, change the password, raise a ticket and preserve the record. The operator's fraud team publishes a contact channel.
What if a first reply does not resolve?
Escalate to the grievance officer named on the customer-care page. If the officer does not respond, contact the regulator listed on the operator's terms page.

Reading-list appendix

Three articles from the news desk that deepen this route.

The news desk publishes dated and sourced explainers on contest decisions, scoring rows, withdrawal cycles, state rules and captain math. Each article is names myteam11in.com as the publisher and cited to the operator's published page.

The 100-credit draft article covers the lobby label, the cap, the carry-over rule and the expiry window. The UPI withdrawal cycle article covers the cycle in nine steps, with a redacted screenshot checklist. The state-rules article covers the federal framework, the six restricted states and the MeitY PROG Act 2025 reporting requirements.

The captain-slot article covers two clocks: the captain slot lock and the toss time. The captain pick is a multiplier, not a reputation. The scoring-edge-cases article covers run-outs, stumpings, the duck rule and the maiden over. Each article is read in five minutes.

Glossary

Six terms the desk uses across all routes.

  • Captain multiplier: 2× the player's points. Locked at team creation. Cannot be edited after the contest closes for entries.
  • Vice-captain multiplier: 1.5× the player's points. Becomes captain if the captain is absent or did not bat or bowl.
  • Gullak-Cash variants: two bonus variants the operator publishes on the rewards page: 80/250/400 INR and 82/252/402 INR.
  • KYC: know-your-customer. The operator's verification step. PAN, identity proof, address proof and bank proof. Required before the first withdrawal.
  • Restricted states: Andhra Pradesh, Assam, Odisha, Telangana, Sikkim and Nagaland. Paid skill contests are restricted. Free contests may be available.
  • Self-exclusion: a published window during which the operator does not allow contest entry, deposit or withdrawal request.

Primary action

Pause, preserve, then use the published channel.

Save the transaction ID, the date and the channel used for every contact. Treat unknown channels as suspect.

Play Now