Four ways to reach the lab
PlayExch runs four support channels. Each channel has its own response SLA. The lab publishes the live status of each channel on the customer-care page.
In-app support
Tap the help icon in the app to open a support thread. The in-app channel has the fastest response time — typically under fifteen minutes during business hours. Threads are searchable from the support history.
Email support
[email protected] is monitored seven days a week. Email response SLAs are four hours during business hours and twelve hours off-hours. Complex KYC cases can take up to forty-eight hours.
Phone support
Phone support is available Monday to Saturday, 10 AM to 7 PM IST. The phone number is published on the customer-care page. Phone support is best for KYC escalation and withdrawal queries.
WhatsApp support
WhatsApp support is in beta. The lab verifies your mobile number, then opens a thread in the verified-business chat. WhatsApp response SLAs match the in-app channel.
When KYC needs human review
KYC verification completes within twenty-four hours for straightforward document submissions. Edge cases — name mismatch, Aadhaar-PAN discrepancy, address verification — go to manual review.
Document checklist
KYC requires PAN + Aadhaar (or PAN + Voter ID). The PAN must match the name on the Aadhaar. The Aadhaar address is the default withdrawal address. Updates to the address require a re-KYC submission.
Name mismatch resolution
If the PAN name does not match the Aadhaar name, the lab requests a supporting document — typically a passport, a marriage certificate, or a gazette notification. The lab aims to resolve name mismatches within forty-eight hours.
Address change
Address changes are processed through the Aadhaar re-upload. The lab verifies the new Aadhaar, then updates the account address. Address changes do not reset the KYC timer.
Rejection appeal
If a KYC submission is rejected, the lab sends a reason code and a list of corrective actions. The user can re-submit with the corrections. The appeal process takes up to seventy-two hours.
When a withdrawal stalls
Most withdrawals clear within the standard timelines. When a withdrawal stalls — typically because of a bank-side issue or a KYC hold — the escalation path is well-defined.
Pending withdrawal status
Pending withdrawals show in the wallet screen with a status label — 'initiated', 'bank processing', 'completed', 'on hold'. A withdrawal that stays 'bank processing' for more than four hours is escalated automatically.
Bank-side failure
If the receiving bank rejects the transfer, the lab credits the amount back to the wallet within two hours. The user can re-initiate the withdrawal to a different account.
KYC hold
A withdrawal can be placed on KYC hold if the cumulative withdrawal crosses ₹10,000 without a verified KYC. The hold clears within twenty-four hours of KYC submission.
Fraud-signal hold
If the fraud-signal engine flags a withdrawal, the hold lasts up to seventy-two hours while the lab reviews. The user receives an SMS notification when the hold is placed and when it clears.
Customer Care questions, answered
The most common questions about customer care on PlayExch, with detailed answers.
What are the support hours?
In-app support: 7 AM to 11 PM IST, seven days a week. Email: four-hour response during business hours, twelve hours off-hours. Phone: Monday-Saturday, 10 AM to 7 PM IST. WhatsApp: same as in-app.
How long does KYC take?
Straightforward submissions verify within twenty-four hours. Edge cases — name mismatch, document quality, address verification — take up to forty-eight hours. Manual review escalations take up to seventy-two hours.
What if my withdrawal is stuck?
Check the wallet screen for the status label. If the status is 'bank processing' for more than four hours, the lab has escalated automatically. If the status is 'on hold', the lab sends an SMS with the hold reason and the expected resolution time.
Can I talk to a human?
Yes. Phone support, in-app support, and WhatsApp support are all human-staffed during the published hours. Email support is human-staffed seven days a week. The lab does not use AI chatbots for support.
How do I report a bug?
Tap the help icon in the app, choose 'Report a bug', and describe the issue. The lab's engineering team triages bugs every morning. Bug reports include a device fingerprint so the team can reproduce.
Ready to start with PlayExch?
Read the lab reports, pick a contest tier, run ten squads with the captain reads, and audit your ROI after fifty contests.Within the PlayExch framework, read the lab reports, pick a contest tier, run ten squads with the captain reads, and audit your ROI after fifty contests.
How the lab improves support every quarter
The lab tracks support metrics — first-response time, resolution time, customer satisfaction — and publishes the quarterly review on the disclosure page.
First-response time
The lab's first-response time is 12 minutes median during business hours and 38 minutes off-hours. The lab's target is under 15 minutes during business hours. The metric is tracked weekly and reported in the quarterly transparency report.
Resolution time
The lab's median resolution time is 4.2 hours for standard cases and 18 hours for complex cases (KYC escalation, withdrawal holds, fraud-signal reviews). The lab's target is under 6 hours for standard cases.
Customer satisfaction
The lab's customer satisfaction score (CSAT) is 4.5/5 based on post-resolution surveys. The lab's target is 4.6/5. The lab surveys 20% of resolved cases. The CSAT metric is published in the quarterly transparency report.
Self-service deflection
The lab's FAQ page deflects 38% of inbound support requests. The lab's goal is to deflect 50% by adding more self-service content. The self-service deflection rate is tracked weekly.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.The lab's methodology is built on a five-stage pipeline. On support test, every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. For the support test desk, the pipeline is published in full on the methodology page. Within the PlayExch framework, the lab's edge comes from data freshness and analyst expertise, not from a secret formula. Customer readers should note that other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version This is why the support test desk treats it as a baseline. The lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.The lab pulls data from four primary sources. On support test, match data comes from official tournament data partners, cross-checked against broadcast records. For the support test desk, ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Within the PlayExch framework, contest result archives come from publicly published leaderboards. Customer readers should note that self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark This is why the support test desk treats it as a baseline. The lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. On support test, the lab publishes the safety commitments on the responsible-play page. For the support test desk, the lab refuses to partner with operators that do not enforce responsible-play defaults. Within the PlayExch framework, the lab's reader-safety framework is reviewed annually by an external auditor.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.The lab operates by five public editorial principles. On support test, no sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. For the support test desk, methodology is public — every model's code is published on the methodology page. Within the PlayExch framework, misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Customer readers should note that reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner This is why the support test desk treats it as a baseline.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. On support test, the report is published on the 15th of the month following quarter end. For the support test desk, the most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. Within the PlayExch framework, the report is available on the disclosure page.
