Issue name first
Login, app, deposit or withdrawal clearly state karein.
Support checks
OK Win Customer Care
OK Win account or payment problem explain karte waqt issue category, account ID, time and relevant reference ready rakhein. Password, OTP, PIN and remote-control access private rakhein.
Support message
OK Win customer care ko issue short and complete format me explain karein
Support ko “payment problem” ya “login nahi ho raha” likhne se context incomplete rehta hai. Better message me account identifier, exact issue, time, relevant amount/reference and already-tried checks include karein.
| Field | Example type | Private? |
|---|---|---|
| Account ID | Profile identifier | Usually okay to share when needed. |
| Issue category | Login / deposit / withdrawal / app | Safe. |
| Amount and time | Transaction value and timestamp | Useful for payment matching. |
| Transaction reference | UPI/bank reference | Useful; share only in relevant support route. |
| Password / OTP / PIN | Authentication secret | Never share. |
Message format
One issue = one clear timeline
Agar ek account me multiple issues hain to har issue ka timeline separate likhein. Example: login error 8:10 PM, deposit success 8:20 PM but wallet pending, app crash 8:30 PM. Mixed statements ke bajaye chronological note useful hota hai.
Time and current status
Approximate time plus latest visible status mention karein.
Relevant reference
Payment issue ho to reference/amount add karein.
Non-sensitive screenshot
Only relevant screen crop attach karein; private notification details hide karein.
Account access support
Password/OTP issue me private details mat bhejein
Support ko password prove karne ke liye actual password dena required nahi hona chahiye. Recovery flow ke verification steps user khud complete kare. OTP forward karna ya screen-share access dena avoid karein.
✓
Password issue
Recovery option and registered number verification use karein.
✓
OTP issue
Signal, latest code and resend interval check karein.
✓
Locked account
Repeated attempts stop karke exact error message note karein.
Payment support
Transaction evidence ko structured rakhein
Deposit/withdrawal problem me account ID, amount, transaction or request time and reference sabse useful records hain. Bank statement ka full screenshot bhejne ke bajaye only relevant non-sensitive transaction section use karein.
Do not send: UPI PIN, banking password, card PIN, OTP, full card number or remote-control permission. Useful: amount, reference, date/time, account ID and current status.
Avoid scams
Unknown “support” contacts ko verify kiye bina trust na karein
Public comments, forwarded messages or unsolicited chats me koi person support representative claim kar sakta hai. Sensitive details ya remote-control access maangna red flag hai. Current account interface me available support option ko preference dein.
Unsolicited OTP request rejected
Remote-control request rejected
Password never shared
Only relevant screenshot used
Issue timeline written clearly
Duplicate messages limited
Related sections
Problem category ke hisaab se detail check karein
Support message bhejne se pehle issue-specific checks complete karna useful hai.
Evidence quality
More screenshots se better relevant screenshot hota hai
Support message me 10 random screenshots attach karne ke bajaye exact error or transaction record ka clean screenshot useful hota hai. Screenshot crop karte waqt OTP notification, full bank balance, personal chats or unrelated private information hide karein.
✓
Login issue
Error text + account ID context enough ho sakta hai.
✓
Deposit issue
Amount + UTR/reference + source status + wallet state.
✓
Withdrawal issue
Request amount + time + status + available reference.
Follow-up
Same issue ke repeated messages ko structured follow-up me convert karein
Agar response pending hai to every few minutes same message resend karne se communication thread clutter ho sakta hai. One follow-up me previous issue time, current changed status and any new evidence add karein.
| Follow-up detail | Include | Avoid |
|---|---|---|
| Original issue time | Approximate date/time | Long unrelated story |
| What changed | Pending → failed/completed etc. | Same screenshot repeatedly |
| New reference | If generated | Password or OTP |
| Current request | What you need clarified | Multiple different issues mixed |
Account identity
Support ko correct profile identify karne me help karein
Agar device me multiple accounts or numbers saved hain to wrong account ID support investigation ko mislead kar sakta hai. Profile open karke correct ID and registered number context note karein. Full private identity documents tabhi use karein jab trusted secure process explicitly requires them.
Correct profile open karein
Current issue jis account me hai uska ID note karein.
Issue time match karein
Relevant activity or payment timeline record karein.
Minimal evidence attach karein
Only necessary non-sensitive screenshot use karein.
Private authentication remove karein
OTP, PIN and passwords hide or omit karein.
Urgency red flags
Pressure tactics ke under sensitive action mat karein
Unknown contact agar “abhi OTP do”, “screen share karo”, “PIN enter karo” ya “withdrawal release fee bhejo” jaisi urgency create kare to pause karein. Legitimate account troubleshooting ko sensitive secret disclosure ke saath mix nahi hona chahiye.
✓
OTP request
Reject and use account recovery flow yourself.
✓
Remote-control request
Unknown remote access deny karein.
✓
Extra fee demand
Live account terms and known support channel verify karein before any payment.
Deep check
Site content issue ko exact location ke saath report karein
Agar OK Win Store content me typo, outdated wording or broken internal route mile to exact URL and visible section name mention karein. Isse site-related correction account-support request se separate clear rehti hai.
✓
What to record
Time, current account identity and exact visible status.
✓
What to change
Only the setting or action linked to the observed problem.
✓
What to avoid
Sensitive credential sharing and multiple unrelated changes at once.
Deep check
Sensitive details ko later message me bhi repeat na karein
Initial message safe ho but later reply me OTP or PIN send kar dena equally risky hai. Entire conversation me authentication secrets private rakhein.
✓
What to record
Time, current account identity and exact visible status.
✓
What to change
Only the setting or action linked to the observed problem.
✓
What to avoid
Sensitive credential sharing and multiple unrelated changes at once.
Support summary
A good issue message four lines me complete ho sakta hai
Long emotional message ke bajaye concise format try karein: account ID, issue, time, evidence. Example structure: “Account ID …; withdrawal pending; requested around …; current status …; reference …”. Sensitive authentication details intentionally omit karein.
✓
Who
Correct account ID.
✓
What
Exact issue and status.
✓
When
Approximate time and relevant reference.
Issue priority
Security issue ko normal inconvenience se higher priority dein
App slow or cosmetic display issue annoying ho sakta hai, lekin unknown login, changed payment detail, unexpected withdrawal or suspicious credential request higher-risk situations hain. Aise case me fresh money action hold karke account security and records first review karein.
| Issue | Priority | First move |
|---|---|---|
| Slow loading | Normal | Network/app checks |
| OTP delay | Normal | Verification checks |
| Unknown activity | High | Secure account + records |
| Unexpected withdrawal | High | Wallet/request evidence |
| Remote-access demand | High | Reject and stop sharing |
Customer care FAQs
OK Win support questions
Short answers for safe, complete support communication.
OK Win customer care message me kya include karein?
Account ID, issue category, approximate time, relevant amount/reference and non-sensitive screenshot. Password, OTP or UPI PIN include na karein.
Login issue aur payment issue ek message me bhejna chahiye?
Possible ho to issues separate rakhein. Clear category and timeline support conversation ko easier banati hai.
Transaction reference share karna safe hai?
Payment issue identify karne ke liye reference useful ho sakta hai, lekin banking password, OTP, PIN or remote-control access share na karein.
Support reply slow ho to kya karein?
Same issue ko rapid duplicate messages me bhejne ke bajaye complete evidence ke saath one clear follow-up rakhein.
Account ID kahan useful hota hai?
Correct account identify karne, wallet entries compare karne and payment timeline explain karne me account ID helpful hota hai.
Unknown person “support” bolkar OTP maange to kya karein?
OTP/password/PIN share na karein. Current in-account or known support route use karein and unknown contact ko ignore karein.