How to reach myteam11 support and what to expect back
Two supported contact routes, six category queues, response windows in hours, not days. The walk-through below lists what to include in the first message so the support agent can act on it.
Two supported contact routes
In-app Help → Chat
Open the app, pick Help on the profile tab, tap Chat. First response in 2 to 6 hours on the test account. Best for: stuck KYC, locked accounts, withdrawal timing.
Email support
The address is published inside the in-app Help tab under "Email us". Response window: 24 to 48 working hours. Best for: refund disputes, document re-submission, account closure requests.
What to include in the first message
- Registered mobile number, with country code.
- Last four characters of the device fingerprint (visible in Profile → Security).
- Contest ID, if the question is about a specific contest (Home tab → My Contests → tap the contest).
- Screenshot of the screen that is failing, if any.
- One sentence on what you have already tried.
Six category queues, and which to pick
| Queue | Best for | Typical first response |
|---|---|---|
| Account access | OTP cooldown, password reset, locked account | 1 to 3 hours |
| KYC and wallet | Document re-upload, withdrawal stuck, UPI handle | 2 to 6 hours |
| Contest and scoring | Result dispute, scoring rule question | 12 to 24 hours |
| Promotions and refer | Welcome code, refer credit missing, contest promo | 12 to 24 hours |
| App and install | APK install, TestFlight, sideload failure | 2 to 6 hours |
| Responsible play | Deposit limit, self-exclusion, timeout | 2 to 6 hours |
There is no phone line
myteam11 does not run a phone support line. Any number that claims to be a myteam11 phone line is a phishing number. Report the number via the customer-care contact form if you want a public note added. The only verified contact routes are in-app chat and email, both listed inside the Help tab.
If the first reply does not solve it
Ask the agent to escalate. An escalated ticket moves to a senior queue with a 24-hour SLA. If the senior reply is still unsatisfactory, the next step is the grievance officer, whose contact is published on /legal/. The grievance officer typically responds within 7 working days.
State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.
How the queues are organized, and what to include in the first message
The in-app Help tab splits support into six category queues: account access, deposits and withdrawals, KYC and verification, contest entry and scoring, app and install, and responsible play. Picking the right queue at the start of the ticket cuts the average resolution time roughly in half because the agent who picks up the ticket is the one who knows that queue.
Account access covers OTP, password reset, locked-account steps, and second-device sign-in. The relevant page is /login/. The first message should include the registered phone number, the last four digits of the device, and a one-line description of the issue.
Deposits and withdrawals cover UPI failures, pending withdrawals, and bonus credit disputes. The relevant page is /wallet-kyc/. The first message should include the contest ID or the transaction reference, the time of the attempt, and the UPI handle used.
KYC and verification covers document rejection, pending review, and what to upload after a rejection. The relevant page is /wallet-kyc/. The first message should include the type of document uploaded, the time of upload, and the error message if any.
Contest entry and scoring covers team locks, scoring disputes, and contest cancellations. The first message should include the contest ID, the team number, and the time of the issue. Scoring disputes have a 24-hour window from contest result.
App and install covers sideload failures, TestFlight link expiry, and permission questions. The relevant page is /app/. Responsible play covers deposit limits, timeouts, and self-exclusion. The relevant page is /responsible-play/.
Email response is 24 to 48 working hours; in-app chat is 2 to 6 hours per the test account. If your ticket is time-sensitive, in-app chat is the faster route. We do not handle operator support; the entry below lists the support routes and the queue structure.
Editorial methodology for the support-routes page
The customer-care reference is the support-routes reference for the myteam11 product brand. We publish the in-app chat path, the email response window, and the information to include in the first message. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a response window.
For the in-app chat path, the source is the in-app Help tab. We do not publish a chat path that the in-app Help tab does not surface. The chat path is the canonical reference; we do not paraphrase the screen labels.
For the email response window, the source is the test account's recorded email interactions. We do not publish a response window that the test account has not observed. The response window is the median of the recorded interactions, not the fastest response.
For the information to include in the first message, the source is the in-app Help tab's required fields. We do not publish a required field that the in-app Help tab does not surface. The required fields are the canonical reference; we do not invent a required field.
For what we do not, the answer is publish a customer-care response. We do not paraphrase a customer-care response, does not publish a quote from a customer-care agent, and does not draw inferences from screenshots of other users' accounts. The support path is the canonical reference; we do not substitute its editorial coverage for the product brand's support.
For what the reader must do, the answer is open the in-app Help tab and follow the path. The chat path is the canonical reference; we do not promise a timeline. The confirmation is the in-app chat transcript, not myteam11play.com.
Update cadence: customer-care contact fields get a fresh review whenever the in-app Help tab changes, the email response window changes, the required fields change, or the product brand publishes a new support policy. The review date is in the footer of every page on myteam11play.com.
What we does not publish
The customer-care reference does not publish a chat path that the in-app Help tab does not surface. We do not publish an email response window that the test account has not observed. We do not publish a required field that the in-app Help tab does not surface.
Our customer-care desk does not publish a response that has not been recorded. We do not publish a customer-care quote that the product brand has not approved. We do not publish a support outcome that the test account has not recorded.
Our role is the editorial coverage. The product brand's role is the customer support. The two roles are separate; we do not overlap with the product brand's customer support, payment processing, or KYC verification. The reader should always contact support through the in-app Help tab.