OTP not arriving
OTP messages come from a short-code sender. Check the phone number for typos, then re-request after 60 seconds. If still missing, contact live chat with your registered phone number — never share the OTP with anyone.
khelo bet24 routes questions to the right channel. Use this page to find the support path for account, payments, KYC or game issues, and the right way to reach the verified team.
| Channel | Best for | Response |
|---|---|---|
| In-app live chat | Deposit, withdrawal, login, KYC blockers | Minutes during operating hours |
| Email support | Documented escalations, refund requests | Hours to 1-2 working days |
| Telegram channel | Platform announcements only — not for tickets | One-way broadcast |
| Discord | Community discussion — not for account issues | Community replies |
If you are stuck on one of these, walk through the steps before raising a ticket.
OTP messages come from a short-code sender. Check the phone number for typos, then re-request after 60 seconds. If still missing, contact live chat with your registered phone number — never share the OTP with anyone.
UPI deposits usually credit in under 5 minutes. If a deposit is missing after 30 minutes, share the UPI transaction reference with support.
First withdrawals trigger KYC. Complete PAN + address proof to clear the queue. Subsequent withdrawals should follow the published processing window.
Fantasy teams lock at the official toss time. Late edits are not accepted. Build your team at least 10 minutes before the toss.
Welcome bonuses attach to the qualifying deposit. If a tier was skipped, check the deposit amount against the published welcome structure and contact support with the deposit reference.
Use the deposit limit, play-time limit and self-exclusion tools available inside the verified product. khelo bet24 is a shortlist hub, not the place to set those limits.
The fastest path is the in-app live chat. The button below opens the verified product.
A first reply from the in-app live chat typically includes a request for verification (your registered phone number or your transaction reference) and a short answer. If the answer does not resolve the issue, escalate with the chat transcript attached and ask for a reference number. Reference numbers help the next agent pick up the thread without you having to re-explain.
Ask the agent for a reference number, the expected resolution window and the next step if the first reply does not resolve the issue. Keep the reply factual — agents work from the same script the brand publishes.
Every ticket should have one. Save it for any follow-up.
Ask for the expected time to resolution. Financial issues typically resolve faster than KYC reviews.
If the first reply does not resolve, ask for the escalation path. Most brands have a second-tier team for financial disputes.
When a first-tier agent cannot resolve an issue within their authority, they escalate to a second-tier team. For financial issues (deposits, withdrawals, bonus disputes), the second tier typically includes a finance specialist. For account issues (KYC, login, phone change), the second tier includes an account specialist. For technical issues (game glitches, lobby errors), the second tier includes a technical specialist. The escalation usually happens within 24 hours of the first reply, and you are notified when it happens.
If you are not notified of an escalation, ask. Ask the agent: "Can you confirm the escalation has happened, and can I have the reference number?" The reference number lets the next agent pick up the thread without re-explaining the issue. Keep your replies short and factual. Agents work faster on factual tickets than on long stories, and your reply is more likely to be processed promptly if it is clear what you are asking for.
For high-value disputes (large withdrawals, contested bonus calculations), ask for the senior escalation path. Most brands have a senior escalations team for disputes above a published threshold. The threshold is not advertised on the brand surface; ask the agent if your dispute qualifies.
Outside the published operating hours, the live chat widget shows an offline state but still accepts messages. The next available agent picks up the thread when the desk opens. Email support works around the clock but the replies are slower. Telegram and Discord channels run on a one-way broadcast — they are not for tickets, even if the channel feels active.
For non-urgent issues outside operating hours, send a documented email with timestamps and transaction references. The agent who picks it up the next morning will have full context. For urgent issues — for example, a deposit that did not credit and you need to place a contest entry — open the live chat and leave a clear message with the UPI reference. The agent will see it on the next shift.
A good support answer acknowledges the issue, names the next step and sets a follow-up window. A great answer also gives you a reference number so you can come back to the thread without re-explaining. If your support answer lacks any of these, ask the agent to clarify before closing the ticket.
A bad support answer is vague, omits the next step, or asks you to repeat information you have already provided. If the answer is bad, ask for a senior agent or escalate. Do not accept a bad answer because the agent is friendly — friendliness does not replace resolution.
Keep the chat transcript. Most live chat widgets let you save or email the transcript. Save it before closing the widget — once the widget is closed, the transcript may not be retrievable. The transcript is your evidence if you need to escalate further.
The support desk reads thousands of tickets a day. A clear ticket with a one-line summary, your registered phone number and the relevant transaction reference jumps to the front of the queue. A vague ticket with a long narrative and missing context waits for clarification. Spend two minutes writing a clean ticket; save an hour of back-and-forth.
Use the same template for every ticket: registered phone number, ticket summary, transaction references and timestamps, what you have already tried, what you are asking the agent to do. The template is faster to write and faster to read. Agents who recognise the template respond faster.