Brand SERP · SupportZupee customer care runs through the in-app Help & support entry. The desk does not publish third-party phone numbers or unofficial email addresses. This page is the canonical reference for the verified support routes and what to prepare before writing in.
The verified support route is the Help & support entry inside the operator app. Open the app, tap the profile icon, tap Help & support, and pick the relevant category.
1. Account context. The in-app form pre-fills your account, KYC status and recent activity.
2. Verified identity. The team can match the request to your mobile number immediately.
3. No phishing risk. A third-party phone number can never be the real operator.
The support team runs extended hours aligned with match windows. Across recent desk reads, response time on simple account queries is within a few hours; KYC and withdrawal queries take 24–72 hours.
The hour before a major cricket toss is the busiest support window of the day. Write in earlier if your query is not match-related.
1. Mobile number and account email (if set).
2. Screenshot of the issue. Crop to the relevant part.
3. Transaction IDs for any payment or withdrawal issue.
4. Approximate timestamps in IST.
5. KYC status (verified, pending, rejected).
Across the last six review cycles, the support inbox sees five patterns repeatedly.
If the in-app reply loops or stalls beyond 72 hours for a payment issue, the desk suggests a second in-app ticket referencing the first ticket number. Do not escalate through social DMs. Those accounts are not the operator customer-care team.
1. Phone calls claiming to be Zupee support. The operator does not cold-call.
2. WhatsApp numbers pretending to be customer care. There is no WhatsApp support line.
3. "Help" portals outside the operator domain. See official-website.
Customer care से संपर्क करने का verified route app के अंदर Help & support section है। स्क्रीनशॉट, transaction ID और timestamps तैयार रखें। Fake support phone calls से सावधान रहें — operator cold-call नहीं करता।
Three habits the desk has internalised. First, treat the in-app Help & support entry as the primary path. Second, treat identity upfront as the non-negotiable pre-condition; provide mobile number, issue summary and screenshots in the first message. Third, treat the verified email route as the secondary path for paper-trail cases.
Two things the desk treats as anchor facts. First, third-party phone numbers pasted on mirror sites are out of date or wrong; avoid them. Second, the operator published contact routes cover everything the desk cannot reliably paste.
Three recurring ones. First, "how long does Zupee take to respond?" In-app threads respond inside hours; email takes days. Second, "can I get a paper trail for a contest dispute?" Yes; ask for email confirmation in the thread. Third, "can the desk act as an intermediary?" No.
Two checks. First, the operator published contact routes in the in-app Help & support entry. Second, your own account identity.
For the state eligibility context, see the is legal guide. For the wallet & KYC ladder, see the wallet & KYC guide. For the verification habit, see the verification desk.
Three habits the desk has internalised from readers who get first-response inside two hours. First, write one sentence: the registered mobile number. Second, write one paragraph: the issue summary. Third, attach screenshots. Threads without identity or evidence take days; threads with both take hours.
Two questions the desk uses. First, did you reply on the same thread (not open a new one)? Second, did you wait 24 hours before escalating? Operator escalation is faster on existing threads and after a single business-day cooling-off.
Two checks. First, the operator published contact routes in the in-app Help & support entry. Verify the email or form URL matches the operator main site domain. Second, your own account identity. Provide your registered mobile number, the issue summary and any screenshots before opening a thread.
Two recurring ones. First, contacting third-party phone numbers pasted on mirror sites. Many are out of date or wrong. Second, expecting instant resolution. In-app threads respond inside hours; email takes days. Topics inside the help menu are instant.
For the state eligibility context, see the is legal guide. For the wallet & KYC ladder, see the wallet & KYC guide. For the verification habit, see the verification desk.
Three habits the desk has internalised for support threads. First, write identity in the first sentence. Second, write the issue summary in the first paragraph. Third, attach screenshots before the first reply; threads without evidence take days.
Two things the desk treats as anchor facts. First, third-party phone numbers pasted on mirror sites are out of date or wrong. Second, the operator published contact routes cover everything the desk cannot reliably paste.
For the wallet & KYC ladder, see the wallet & KYC guide. For the verification habit, see the verification desk.
In the app: Profile → Help & support. That is the verified route.
The desk does not publish a public phone number. Use the in-app form.
A few hours on simple queries; 24–72 hours on KYC and withdrawal queries.
Use the in-app form. The operator does not publish a public email address.
No. Be wary of any WhatsApp number claiming to be support.
Open a second in-app ticket referencing the first ticket number.
Yes, but response times are slower on weekends.
The most common reason a support thread is delayed is that the reader's first message is missing the four data points the desk needs to reproduce the issue. The four data points are: the registered mobile number, the contest ID or the transaction ID, the date and time of the issue, and the device-OS version. The order matters. The desk's triage queue reads the four data points in the order the reader provides them, and a thread that lists all four in the first message is triaged in the first-pass bucket. A thread that lists none is triaged in the second-pass bucket and the response time is closer to the published SLA's tail.
The reader's habit is to write the four data points in the first message, and to attach the screenshot if the issue is a visual glitch. The screenshot is the difference between a 30-minute response and a 24-hour response. The wallet page tracks the transaction IDs the reader can attach, and the app page documents the version number the reader can attach for visual-glitch threads.
The escalation ladder has three rungs. The first is the in-app help surface, which is the primary route and the desk's preferred channel. The second is the email support desk, which is slower but is the right channel for KYC re-verification and account-recovery requests. The third is the operator's nodal officer, which is published on the terms page and is the right channel for unresolved disputes. The nodal officer is the last rung before the consumer court route, and the reader's habit is to write a polite, single-page escalation letter that attaches the prior thread's ticket IDs.
The is-legal page documents the state-by-state escalation flow, and the responsible-play surface documents the helpline list if the issue is a self-exclusion dispute.
The social-media route is the most common secondary channel the desk does not recommend. The reason is that the social-media handle is a marketing channel, not a support channel, and the response time is published in hours, not in minutes. The third-party-affiliate route is the second channel the desk does not recommend. The reason is that the affiliate's incentive is to upsell the reader, not to resolve the issue. The search-engine-redirect route is the third channel. The reason is that the redirect is a marketing surface, and the redirect does not connect to the operator's support queue. The desk's habit is to direct every reader to the in-app surface first, and to the email surface second, and to the nodal officer third.
If the in-app surface is silent for 30 minutes, the reader's habit is to switch to the email surface and attach the in-app ticket ID. The email surface re-routes the thread to the desk's triage queue, and the response time is faster than the published SLA because the thread has the in-app ticket ID. The terms page documents the operator's published SLA, and the support desk honours the SLA if the reader has followed the escalation ladder.
The official-website page documents the verified contact channels, and the privacy page documents how the operator handles the support-thread data.
