How to play on the 11Tiger brand — a working guide
A working how-to-play page: sign-up, KYC, captain choice, contest review, points reading and the lock-and-walk-away rhythm.
A how-to-play page built for the first-time reader and the league veteran. Each step is grounded in the platform’s actual flow rather than a marketing description; each step links to the desk’s own methodology on the relevant page.
Step 1 — Sign up
Sign up with a personal email and a personal phone number. Each platform enforces an email + phone + 2FA stack at sign-up; the reader who uses a personal contact stack at this step saves a round-trip later when KYC requires a phone match.
Where the reader has signed up before and re-sites on a new email, the KYC record from the prior sign-up is the strongest path through the platform’s verification trails. A brand-new sign-up is fine, just slower.
Step 2 — KYC
KYC is a three-document step: PAN, address proof, a clear photograph in daylight. The PAN is mandatory for paid fantasy-cricket contests in India; the address proof confirms the address on file; the photograph binds the document to the holder.
The wallet & KYC guide walks the reader through the documents the platform expects and the photo conditions that produce the fastest verification. The deposit flow is paused while KYC is in review.
Step 3 — Pick the captain
Captain is the single highest-leverage decision in any contest. The captain-vice-captain page carries the six matrix rules and a worked example. The working summary: pick captain from your strongest role category, not your favourite player. Place vice-captain in a different matchup so the 1.5× insurance stays live. Avoid last night’s top scorer.
The captain is locked at the toss, not at the probable XI publish. The reader who locks captain against the probable XI is the reader most likely to lose the insurance when the playing XI swaps two names.
Step 4 — Pick the contest
Pick the contest that fits the team. A ceiling team in a head-to-head is a recipe for silent rounds; a floor team in a mega contest is a recipe for a low finish. The four common contest types are small leagues, head-to-heads, mega contests and practice contests.
Set a contest budget before team save. The reader who sets the budget at the start of the week has stopped chasing last night’s loss by the second match.
Step 5 — Read the points
Step 6 — Withdraw
Frequently asked questions
How long does KYC take?
KYC varies by platform. The desk’s median across the platforms it tracks is 24-48 hours. A clear daylight photograph with edges visible shortens the window.
When should I lock the captain?
After the toss. Locking against the probable XI is the most common way to lose the insurance.
Where do I read the points reference?
On the points-system page. The page is grounded in the platform’s published rule book and updated when the platform updates.
What is the working contest budget?
A weekly budget set before the first match and not topped up between matches. The discipline compounds across a season.
Does the desk’s methodology promise a return?
No. The methodology makes decisions visible. The contest decision belongs to the reader.
Continue reading
Reading checklist
A working checklist for the reader who lands on this page to complete a first-time fantasy-cricket workflow. The page walks through sign-up, KYC, captain, contest, points and withdrawal in the order the desk actually works.
Three questions to ask. Is the account in a sign-up-ready state with email, phone and 2FA? Are the KYC documents photographed in clear daylight, with edges visible? Is the captain pick locked at the toss, not the probable XI?
What the desk does well. The six-step workflow is published in the order the deck actually works. The four common blockers are named with the fix. The settlement windows are published per funding source.
What the desk is still working on. A reader-side worksheet for each workflow step. A public table of the deck’s measured KYC time on the partner brand’s reviewed cases.
A reading cadence the desk recommends. Read the page once before the first sign-up. Re-read the captain step whenever the captain-matrix rules shift on the captain-vice-captain page.
Desk note: the workflow as the deck actually works it
The how-to-play workflow on this page is the deck’s working order, not the order the partner brand’s marketing describes. The order is sign-up, KYC, captain, contest, points and withdrawal. Each step is grounded in the platform’s actual flow.
Sign-up is the first step. A reader who uses a personal email, a personal phone and a personal 2FA stack at sign-up has the cleanest path through the KYC step. A reader who uses a family-member phone or a shared email spends the KYC step on a verification loop the deck recommends avoiding.
KYC is the second step. The documents are PAN, address proof and a photograph. The photographs should be in clear daylight with edges visible. The desk’s KYC blocker list on the wallet-kyc page is the working note.
Captain is the third step. The captain-matrix rules sit on the captain-vice-captain page. The reader’s captain pick is locked at the toss, not the probable XI.
Contest is the fourth step. The four common contest types are covered on the predictions page and the how-to-play page. The reader’s contest pick is set before team save; top-ups between matches are off the menu.
Points is the fifth step. The points reference on the points-system page is the working note. The deck’s worked examples show the points on a real player-score profile.
Withdrawal is the sixth step. UPI is fastest for matched sources; bank transfer is slower; card refund is the cleanest audit trail. The deck’s settlement-windows note on the wallet-kyc page is the working summary.
Limits of the workflow
The workflow on this page describes the deck’s working order rather than the partner brand’s published flow. A reader who lands on the page from a fresh sign-up should walk the workflow in the order the deck publishes; the partner brand’s own published rule book is the live authority on the contest decision.
The workflow’s KYC step is the second-most-missed step across the platforms the desk tracks. A reader who submits a document with glare on the photo strip or the holographic overlay is queuing for a rejection; the desk’s recommendation is to re-photograph in clear daylight with edges visible.
The workflow’s captain step is the third-most-missed step. A reader who locks captain against the probable XI is locking the captain before the toss; the desk’s recommendation is to read the confirmed XI at the toss and lock the captain then.
Caveats on the how-to-play workflow
Three caveats the desk publishes on the how-to-play page. The workflow describes the deck’s working order, not a guarantee. The KYC review time is partner-dependent; the deck publishes the desk’s median across the platforms it tracks, not a guarantee for any individual platform.
The second caveat: the captain step is the third-most-missed step on the platforms the deck tracks. A reader who locks captain against the probable XI is locking the captain before the toss; the deck’s recommendation is to read the confirmed XI at the toss and lock the captain then.
The third caveat: the withdrawal step’s settlement time varies by funding source. UPI is fastest for matched sources; bank transfer is slower; card refund is the cleanest audit trail.
A reader who has found a workflow-step behaviour the deck has not named is welcome to send the corrections email; the next how-to-play-page refresh reflects the new caveat.
Closing note from the desk
The how-to-play desk closes its read with a note on the six-step workflow. The workflow is sign-up, KYC, captain, contest, points and withdrawal. Each step is grounded in the platform’s actual flow rather than a marketing description.
The three common blockers the deck publishes are name mismatch, document glare and source change. Each is named with the fix the deck recommends.
The two habits that hold are the account-ready state at sign-up and the captain-lock discipline at the toss. The two habits compound across a season.
The miss record on the workflow is published alongside the worked examples on this page. Where the deck’s worked example disagrees with the partner’s published calculation, the partner’s calculation prevails; the deck corrects the worked example on the corrections cadence.
The desk’s coverage area is published on the about page. A reader who wants a different area of coverage is welcome to send a corrections email with a proposed coverage-area addition.