Laser 247 help centre

Triage: is this your problem or theirs?

The single biggest time-waster in this category is contacting support about something you could have fixed in ninety seconds, and the second biggest is trying to fix something yourself that only the operator can touch. One question separates the two: does the problem persist across a different network, a different browser and a different device?

If it goes away when you change any of those, it was a local problem and it is now solved. If it persists across all three, it lives on our side of the fence and no amount of clearing, reinstalling or retrying will help — message the desk instead. Running that test first costs three minutes and saves days.

There is a third category worth naming: problems that involve neither you nor us, because the “support contact” involved is not connected to Laser 247 at all. If your account was arranged by a stranger in a group chat rather than through this website, read the security guide before anything else on this page.

Problems you can fix yourself

The login guide walks through each of these in sequence, with the reasoning behind the order.

Problems only the desk can fix

These are worth recognising quickly so you stop trying and start preparing. Account unlocks after repeated failed attempts — and note that continuing to retry usually extends the lock rather than clearing it. Password resets. Balance and transaction questions, which need records only we can see. Changes to a registered phone number, which are deliberately hard because that number is the route an attacker would use. And account closure or self-exclusion requests, which we act on when they reach us directly and in writing.

For every one of these, your job is not to solve it but to document it clearly and hand it to the desk once, completely. That is what the next section is for.

What to prepare before you contact anyone

• Your account identifier — never the password, and never an OTP.
• The approximate date and time the problem started.
• The exact wording of any error message, typed out rather than paraphrased.
• A screenshot showing both the screen and the device clock.
• What you have already tried, so nobody asks you to repeat it.
• For payment issues: the reference number, amount, timestamp and the bank or UPI confirmation.

Send those together, in one message. This is the highest-leverage habit in this entire guide: it converts a five-message exchange spread over three days into a single exchange, because the first responder has everything needed to act rather than everything needed to ask another question.

Write it plainly, too. A factual sequence — what you did, what happened, what you expected — outperforms an angry summary, not because politeness is rewarded but because a clear sequence can be checked against logs and a summary cannot.

Escalating without making it worse

Pick one channel and stay in it. Parallel threads about the same issue across chat, email and a second number routinely create duplicate tickets that get merged, closed or delayed. Keep any reference number you are given and quote it in every follow-up.

Give a first response a full working day before following up, unless money is involved. Repeated messages in the interim frequently push a ticket back down a queue rather than up it. When you do follow up, add information rather than repeating the complaint — a new detail justifies a fresh look; a restatement does not.

If a response resolves nothing, ask a specific question rather than expressing dissatisfaction: what is the status, what is required from you, and what is the expected timeframe. Those three questions are answerable, and an answer creates a record you can point at later.

Know when to stop. If a contact stops responding, becomes evasive about a balance, or starts asking for further payments to "release" funds, you are no longer in a support conversation. At that point the useful routes are your payment provider and, where fraud is involved, the reporting channels in the security guide.

When money is involved

Money changes the timeline. Dispute and chargeback windows are short, and they start when the transaction happens rather than when you notice a problem. So run two processes in parallel: the support conversation, and your own bank-side enquiry. Waiting for the first to conclude before starting the second is the most common way people miss the window entirely.

Document immediately and thoroughly. Timestamped screenshots, transaction references, the destination handle or account, and the full conversation. Do this before blocking anyone, because blocking often removes your access to the chat history that constitutes your evidence.

Be realistic about outcomes. Transfers made voluntarily to an individual are difficult to reverse, which is exactly why the guidance elsewhere on this site is so insistent about verifying before money moves. If fraud is involved, report at cybercrime.gov.in or on 1930 the same day — early reporting is the main factor in whether funds can be held.

Requests to refuse, always

• Any request for a one-time code, whatever the stated reason.
• Any request for your password, UPI PIN, card CVV or net-banking credentials.
• Any request to install remote-access software so someone can "fix it for you".
• Any request for identity documents sent to a personal chat account.
• Any request to pay a fee to release a balance that is supposedly already yours.
• Any instruction to keep the conversation private from family or from the platform.

These are not judgement calls. Each one is a bright line, and the value of a bright line is that it works when you are tired, frustrated and being pressured — which is precisely when these requests arrive.

A support message you can adapt

Most people write support messages as a description of their frustration. The messages that get resolved read like an incident report. The difference is not tone, it is structure: a resolvable message contains a subject, a timeline, an expected outcome and a specific request.

That last line is worth keeping. It sets the boundary politely and in advance, and it makes any subsequent request for a code stand out as the anomaly it is. A genuine support agent will not object to it; anyone who does has answered your real question.

Common issue categories and what each one needs

Access and sign-in. Usually yours to fix, and the fastest route is the four-test sequence: manual password entry, network switch, second browser, private window. Escalate only when all four fail, and say so in the message — it moves the conversation past the scripted first reply immediately.

Locked accounts. Entirely the desk's to clear. Stop attempting, because further tries generally extend the lock. Prepare your ID, the approximate time of your last successful sign-in and the error text, then send one message and wait.

Deposits not reflecting. The most time-sensitive category after outright fraud. Screenshot the payment confirmation with the reference number and timestamp, keep the bank or UPI record, and report once with everything attached. Do not send a second payment while the first is unresolved — stacking transfers is how a small dispute becomes a large one.

Withdrawals delayed. Ask three specific questions: what is the current status, what verification is outstanding, and what is the expected timeframe. Vague dissatisfaction produces vague replies. If the answer involves paying a fee to release your own balance, treat that as fraud rather than as a process step and move to the reporting routes in the security guide.

Verification requests. Legitimate verification happens through a controlled upload on the platform, not through documents sent to a personal chat account. If you are being asked to send identity documents over WhatsApp, the request is the problem, not your compliance with it.

Changed contact details you did not authorise. Treat this as an active compromise rather than an administrative error, and follow the first-hour sequence in the security guide before anything else. A changed recovery number is the step that turns a recoverable incident into a permanent loss.

Closing an account or self-excluding. Send it to the desk in writing and keep a copy of the request — we act on it, and a self-exclusion is treated as final rather than as an invitation to talk you out of it. If you are closing an account because the spending has stopped feeling voluntary, the responsible gaming page lists confidential support routes that exist independently of us.

Keep your own records — nobody else will

Every difficult case we hear about has the same root cause: the user cannot establish basic facts about their own account. Chats were deleted by the other side, the confirmation was never saved, and the identifier is remembered approximately rather than exactly.

Five minutes of record-keeping prevents all of it. Note the identifier, the date the account was created, who arranged it and through which number, the registered phone number, and the date and amount of your most recent transaction. Store that outside any chat app — a note in your phone's password manager is ideal, since it is encrypted and backed up.

Update it whenever something changes. If you ever need to prove ownership, dispute a transaction or file a complaint, that note is the difference between a process that takes a day and one that never concludes at all.

Setting realistic expectations

Two things are worth accepting early, because fighting them wastes energy you will need. First, the queue is real: the desk answers in arrival order, a match night is heavier than a weekday afternoon, and a follow-up message does not move you forward. Second, some things are outside anyone's reach — we cannot shorten a bank's processing window, and nobody who promises to for a fee is telling the truth.

Knowing that early lets you allocate effort sensibly — pursue what can move, document what cannot, and set your own deadline for when you will stop pursuing and start reporting. People who decide that in advance handle these situations far better than those who discover it after three weeks of messages.

Help centre: frequently asked questions

Related guides on this site