Contacting Raja Luck support is more effective when your first message contains the right facts. “My account is not working” gives an agent very little to check. A clear note with the account identifier, time, exact error, transaction reference and the steps already tried can reduce back-and-forth. At the same time, you must protect passwords, OTPs and banking secrets.
This article explains six details to keep ready, how to describe common issues, and how to recognise a person who is only pretending to be support.
Use an official contact route
Open support from the account or a website address you have already verified. Do not trust a phone number placed in a social-media comment simply because it uses the Raja Luck name or logo. Search results and messaging groups can contain copied profiles.
Check the support page, help area or contact option after a safe Raja Luck login. If you are contacting this independent information website, use our Contact Us page. We can explain published information, but we cannot open a player account, see a wallet, credit a reward or approve a withdrawal.
1. Registered mobile number or account ID
Provide the account ID or the registered mobile number in the format requested by official support. If privacy is a concern, ask whether the last few digits are enough for an initial enquiry. Do not provide someone else’s number or create a new account to report the old one.
Never include the password. Support can verify an account through approved checks without knowing the secret used to sign in.
2. Exact date and time
Write the date and approximate time when the problem began. Include the time zone if the issue involves an offer deadline or a user travelling outside India. For a transaction, use the time shown in the bank or payment app as well as the time shown in the Raja Luck record.
“Yesterday evening” is less useful than “8 September at about 6:20 pm IST”. Precise timing helps the team find the relevant system record.
3. A plain description of the problem
State what you expected, what actually happened and where it happened. Mention whether you used the mobile website or app, and name the page: login, deposit, withdrawal, reward, profile or game lobby. Copy the exact error words if they are visible.
For example: “After entering my registered number and new password, the login page returns to the same screen without an error.” This is much clearer than “Login bad”.
4. Transaction or request reference
For a deposit, keep the UTR, UPI reference or bank transaction number. For a withdrawal, keep the request ID and any transfer reference supplied after processing. For a reward, keep the activity name, qualifying transaction and claim time. For password recovery, note how many OTPs were requested and whether any arrived.
Send the reference as text so it can be copied, and include it in the screenshot. Double-check every digit before submitting the message.
5. A safe, relevant screenshot
A screenshot should show the error, status, amount, time or reference that matters. Crop the image so unrelated notifications, contacts, balances and other transactions are not visible. Cover full card numbers, document numbers and private addresses.
Do not send a screenshot containing a password, OTP, UPI PIN, CVV or banking password. These details should never be requested in a normal support conversation. General cyber-safety information is available from India’s official CERT-In website.
6. Steps you have already tried
List the safe checks already completed. You may have restarted the app, changed the network, checked the account number, waited for the stated processing time, requested one password reset or reviewed the activity terms. This stops support from repeating basic questions and shows the exact stage of the problem.
Do not claim that you completed a step if you did not. Accurate information is faster than guessing.
A message format you can use
Keep the note short enough to scan but complete enough to investigate:
Hello. My registered mobile/account ID ends with ___. On ___ at ___ IST, I tried to ___. I expected ___, but the screen showed ___. The reference number is ___. I used the mobile website/app on ___. I have already tried ___. I have attached one cropped screenshot. Please confirm the present status and tell me whether any action is required from me.
Add only the details relevant to your case. Keep the ticket number and continue in the same conversation instead of opening several duplicate requests.
Different issues need different evidence
Password or login problem
Include the registered number ending, error message, device, browser or app version and time of the attempt. Do not include the password or OTP. Our password recovery article lists safe checks to complete first.
Deposit not credited
Include amount, method, UTR or UPI reference, bank status, Raja Luck deposit status and exact time. Do not make a second payment while the first is pending. See the deposit troubleshooting article.
Withdrawal pending
Include amount, request ID, destination ending, current status and how long it has remained there. Check the full processing window first. The withdrawal article explains the seven checks.
Reward missing
Include the activity name, opt-in time, qualifying action, progress, claim attempt and screenshot of the terms. Explain which eligibility rule you believe was met.
How long should you wait for a reply?
Use the response time stated by the official channel. Complex payment or identity cases can require checks with another provider and may take longer than a simple question. Avoid sending “hello?” every few minutes because repeated messages can make the thread harder to follow.
If the stated response window passes, send one polite follow-up with the same ticket number: “Please share an update on ticket ___ raised on ___. The issue remains unchanged.” Keep a record of the reply.
How to recognise fake support
- The person contacts you first from an unknown personal account.
- They ask for your password, OTP, UPI PIN, card CVV or banking password.
- They request payment to unlock a withdrawal, reward or account.
- They ask you to install a remote-control or screen-sharing app.
- They promise a guaranteed win, refund or instant withdrawal.
- They create panic and demand action within a few minutes.
- The address or profile does not match the official support area.
End the conversation when these warning signs appear. Save non-sensitive evidence of the approach and report the account through the relevant platform if appropriate.
Do not send more personal information than necessary
Support may need to verify identity for certain account actions, but the request should be specific and come through a trusted process. Ask why a document is needed, which part is required, how it will be used and whether you can mask unrelated fields. Never upload a full gallery of personal documents “just in case”.
Do not send information about family members or another person’s bank account. Keep your account and payment method in your own name where required.
Stay calm during a payment dispute
A missing payment can feel urgent, but anger often produces incomplete messages and risky decisions. Do not deposit more, increase stakes or borrow while waiting. Keep essential money separate and take a break from play. The Responsible Gameplay page explains practical boundaries.
Support should help trace facts; it cannot change the uncertainty of game results. Do not ask an agent for a “sure game” or recovery strategy after a loss.
Frequently asked questions
Will support ever need my Raja Luck password?
No. Keep the password private and use the official reset option if it must be changed.
Can I send my full bank statement?
Send only the relevant transaction evidence requested through a trusted process. Cover unrelated entries and sensitive identifiers.
Should I open several tickets for the same issue?
No. Keep one ticket and follow up there unless official support tells you to use another channel.
Can this website solve an account-specific payment problem?
No. We publish independent information and cannot access Raja Luck systems or user wallets.
Conclusion
A useful Raja Luck support request contains six things: the correct account identifier, exact time, plain problem description, reference number, safe screenshot and the checks already tried. Use a verified channel, keep one ticket and protect every password, OTP and banking secret. Clear facts help; panic, repeated payments and private “agents” do not.
Disclaimer: This independent website is not the Raja Luck operator or customer-support system. We cannot access accounts, payments or personal platform records. Use the official account support route for account-specific help.