How do I open the app?
Sign up via mobile number → OTP → name → email. KYC clears at first deposit (PAN + bank/UPI).
The FanCode help desk covers common questions on the app, KYC, withdrawal, contests and compliance. The primary channel is the in-app Help & Support tab; the desk publishes the verified channels and the escalation pattern.
Top questions
How do I withdraw?
In-app → Wallet → Withdraw. Pick UPI / net-banking / cards. Withdrawal processing is 1-3 working days.
Where is the customer-care number?
The operator does not publish a long-term phone number. The primary channel is the in-app Help & Support tab.
What states are restricted?
Andhra Pradesh, Assam, Odisha, Sikkim, Telangana, Nagaland. Meghalaya operates a permitted list.
How do I find the squad builder?
Open a fixture → "Create Team" → pick 5 or 7 → pick captain and vice.
What is the latest APK?
v6.4.2 as of 22-Jul-2026. The APK page carries the build banner.
Troubleshooting
- App crash on Android Uninstall any old build, install the latest. If the crash repeats, raise an in-app ticket with the device model and Android version.
- App crash on iOS Force-quit, restart the device. If the crash repeats, raise an in-app ticket.
- Live score not updating Check network signal; the live feed is dependent on the operator's score pipeline. If the issue persists, raise an in-app ticket.
- OTP not received Wait 60s · tap resend · check DND settings on your registered mobile.
- Contest not visible The contest register rotates per fixture window. The relevant contest is visible inside the open fixture.
Help channels
- In-app Help & Support Profile → Help & Support (primary channel)
- Operator email Customercare [at] fancode.in
- Verified socials @fancode (X) · @fancodeapp (Instagram)
- Editorial corrections compliance [at] fancodein.com (editorial only, not for account issues)
Related lanes
Picking the right help channel — a short guide
For app / wallet / KYC / withdrawal issues, use the in-app Help & Support tab. For editorial corrections or compliance questions, write to compliance [at] fancodein.com. For source tips, write to tips [at] fancodein.com. The desk's three lanes are not customer success — they are editorial.
When to escalate
If your in-app ticket is not acknowledged within 48 hours, escalate via the operator's email channel. If the email channel is not acknowledged within 7 working days, post on the verified socials. For unresolved financial disputes, the consumer forum under the Consumer Protection Act, 2019 is the next step.
A reading note — when the desk can and can't help
The desk is editorial, not customer success. We don't see your wallet, your deposits, or your paid contest entries. Where the issue is account-level (KYC, withdrawal, contest register), the operator's in-app Help & Support is the path. Where the issue is editorial (a correction, a compliance question, a source tip), the desk's editorial lanes are the path.
If you don't know which lane fits, default to editorial — we re-route account-level issues to the operator's ticket inbox. We promise to acknowledge a redirect within 24 hours.
What the desk covers — full scope
The desk's help lane covers the editorial surface across fancodein.com. Top questions fall in three buckets: account-level issues (KYC, withdrawal, deposits), app-level issues (crash, install, live-score latency), and editorial issues (corrections, compliance, source tips). Each bucket has its own canonical route.
Account-level issues route to the operator's in-app Help & Support tab. The desk does not handle account-level issues directly — we don't see your wallet, your deposits, your paid entries. Where the issue is unclear, the desk reads the ticket description and forwards the right way.
App-level issues typically fall in one of three categories — install (download or APK), crash (specific OS or device), live-score (network vs operator pipeline). The desk's help page walks each. Where the issue is specific (e.g. "crash on Samsung A52 with Android 12"), the in-app ticket carries the device model and the OS version to the operator's engineering team.
Editorial issues are the desk's lane. Corrections, source tips, compliance questions are three published contact lanes — editor, compliance, tips. Each has its own SLA published on the lanes. Press accreditation and content partnership use the desk handle.
A reading note on routing — what to do first
When you have a question, the desk recommends three questions to ask first: (1) is the issue about my account or wallet, or about editorial coverage? (2) is the issue about the app's behaviour on my device, or about the operator's published policy? (3) is the issue about a contest result or about a published claim?
Account / wallet issues route to the operator's in-app Help & Support tab. App behaviour issues route to the operator's engineering team via the in-app ticket. Editorial issues route to the desk.
If you're unsure which lane, write to compliance [at] fancodein.com with a brief description. We re-route within 4 hours.