Email support is published on the customer-care page. The desk treats email as a slow but auditable channel. Reply window: published on the same page.
Customer care
Known channels beat unknown channels.
Email, in-app ticket and support hotline. Working hours, native-language support and a published escalation path to the grievance officer.
Three channels
Email, in-app ticket and support hotline.
The operator publishes three customer-care channels. The reading desk treats the operator's published channels as the only authoritative route. Verify each channel before relying on it. Phishing callers imitate customer-care, treat unknown channels as suspect.
In-app ticket
The in-app ticket system is the fastest channel for account-specific questions. Tickets are auditable and tied to the account.
Support hotline
The hotline handles urgent requests. Calls are not auditable. Use the hotline for time-sensitive issues, then follow up with a ticket.
Native-language support
Languages the operator publishes.
The operator publishes a list of supported languages on the customer-care page. English and Hindi are usually available. Regional languages may be available for in-app tickets but not for the hotline. Verify the current list before relying on it.
Working hours
Hours and response window.
The customer-care page publishes the working hours and the response window. Email replies within the published window. Tickets are routed within minutes. The hotline is staffed during the published hours. Outside hours, use the ticket system for non-urgent issues.
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. The officer's reply window is published. If the officer does not respond, contact the regulator listed on the operator's terms page.
Support guidePhishing checklist
Six signals of a phishing caller.
- OTP request: the operator never asks for an OTP. A request is a phishing signal.
- Password request: the operator never asks for a password. A request is a phishing signal.
- Private UPI request: the operator never asks for a private UPI transfer. A request is a phishing signal.
- Remote access: the operator never asks for remote-control access. A request is a phishing signal.
- Unknown channel: a contact from an unknown number or email is a phishing signal. Verify the channel against the customer-care page.
- Urgency: a request that pressures the user into a fast action is a phishing signal. Pause the conversation.
Grievance officer
The named officer and the published window.
The operator publishes a grievance officer name and a response window. The desk cites the published name and window. The officer's contact is the second escalation step after the standard customer-care channels.
Source
Where the desk sourced each row.
Three channels, working hours, response window and grievance officer are taken from the operator's published customer-care page, captured 2026-08-17, marked subject to confirmation. The desk updates these rows when the operator publishes a change.
Related reading
Three routes the desk opens after the customer-care desk.
Working hours
How the desk reads the published hours.
The customer-care page publishes the working hours and the response window. Email replies within the published window. Tickets are routed within minutes. The hotline is staffed during the published hours. Outside hours, use the ticket system for non-urgent issues.
Native-language support
Languages the operator publishes.
The operator publishes a list of supported languages on the customer-care page. English and Hindi are usually available. Regional languages may be available for in-app tickets but not for the hotline. The desk cites the operator's list as the live answer.
What the desk will not print
Two columns the desk refuses to print.
The desk does not publish a customer's personal data. Ticket references and account numbers stay on the operator's first-party flow. The desk also does not run a customer-care channel. The desk cites the operator's published channels.
How the desk reads customer care
Reading customer care as a tiered channel system.
Customer care is a tiered channel system, not a single hotline. Email, in-app ticket, support hotline and a grievance officer. Each tier carries its own response window. The desk cites each tier separately.
Three channels the desk tracks
- Email: email support is published on the customer-care page. The desk treats email as a slow but auditable channel. Reply window: published on the same page.
- In-app ticket: the in-app ticket system is the fastest channel for account-specific questions. Tickets are auditable and tied to the account.
- Support hotline: the hotline handles urgent requests. Calls are not auditable. Use the hotline for time-sensitive issues, then follow up with a ticket.
Working hours and response window
The customer-care page publishes the working hours and the response window. Email replies within the published window. Tickets are routed within minutes. The hotline is staffed during the published hours. Outside hours, use the ticket system for non-urgent issues.
Native-language support
The operator publishes a list of supported languages on the customer-care page. English and Hindi are usually available. Regional languages may be available for in-app tickets but not for the hotline. The desk cites the operator's list as the live answer.
Escalation
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. The officer's reply window is published. If the officer does not respond, contact the regulator listed on the operator's terms page.
FAQ
Six questions about customer care.
Which customer-care channels are available?
Email, in-app ticket and support hotline are listed on the customer-care page. Verify each channel before relying on it.
What languages are supported?
English and Hindi are usually available. Regional languages may be available for in-app tickets. Verify the current list before relying on it.
What are the working hours?
The customer-care page publishes the working hours. Outside hours, use the ticket system for non-urgent issues.
How is a complaint escalated?
Escalate to the grievance officer named on the customer-care page. The officer's reply window is published. If the officer does not respond, contact the regulator listed on the operator's terms page.
What if a caller asks for an OTP?
The operator never asks for an OTP. A request is a phishing signal. Pause the conversation and use the customer-care page to verify the channel.
What if a caller asks for a private UPI transfer?
The operator never asks for a private transfer. A request is a phishing signal. Pause the conversation and use the customer-care page to verify the channel.
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
Use the published channels only.
Verify each channel against the customer-care page before relying on it. Preserve the transaction ID and the date for every contact.
Play Now