Two channels, one queue, six specialist teams

The /faq/ route documents the same twelve decision questions the helpdesk agents answer in chat. Reading the FAQ before opening a chat is the fastest path to a one-message resolution.

The /responsible-play/ route documents the responsible-play rules the support team applies at the withdrawal screen.

When the lobby is unreachable (install issue, login lockout, network error), the support inbox form on the contact route is the formal channel.

Three situations route outside the lobby by default: install failure on a fresh device, login lockout after three wrong PINs, and a network error during deposit. In all three, the inbox form is the documented formal channel.

The form on /contact/ is polled every five seconds and reaches the same agent queue as the in-app chat.

The support team on khelo bet24 handles six categories of queries. The categories are the dropdown entries inside the in-app chat; each entry routes to a specialist team inside the same agent queue. The categories are documented below in the order the dropdown presents them.

Account and KYC. Document re-uploads, rejection reasons, address changes, mobile-number changes. Most queries resolve within the same session because the rejection reason is shown on the wallet screen and the re-upload is a single tap. The team handles PIN recovery via the OTP path; lockout after three wrong PINs is on the same team.

Deposits and withdrawals. UPI and bank transfer rails, settlement windows, transaction status. KYC must be on file before the first withdrawal; the team routes the reader to the KYC document set on /wallet-kyc/ when the query is about a withdrawal blocked by KYC. The team handles partial settlement and rail-specific issues.

Bonuses and promotions. Welcome tier terms, wagering requirement progress, Daily Race tier band, refer-and-earn milestone ladder. The team reads the same wagering math the wallet screen displays; queries about progress are resolved from the wallet state. Queries about the underlying terms route to /bonus-code/ and /promotions/.

VIP and Daily Race. Tier progress, comp-point rate, personalised bonuses unlocked at tier 5 and tier 11. The team includes VIP managers for tier 11 and above; the chat dropdown exposes the category even for lower tiers but the routing rule is different.

Technical and app. Install issues, signed APK verification, in-app navigation, network errors, PIN recovery. The team reads device logs and signed APK hashes; queries about the install path on Android route to /apk-download/ and queries about the iOS add-to-home-screen path route to the standard Safari flow.

Responsible play. Deposit caps, cooldown windows, self-exclusion. Applied per withdrawal screen. The team handles the responsible-play rules on /responsible-play/; the same specialist team handles exclusion requests and the cooling-off window for cap raises.

The in-app chat and the support inbox form on /contact/ both reach the same agent queue. The channels are not separate queues; the conversation id is preserved across them. Choosing between them is about context, not routing.

The in-app chat is the right channel when the reader is inside the lobby and the question is tied to the current state of the wallet. A question about a recent stake, a recent deposit, the current KYC status or the current tier band is best handled in chat because the agent can read the wallet state from the chat session.

The inbox form on /contact/ is the right channel when the reader is outside the lobby (install issue, login lockout, network error) or when the question needs an offline record (a complaint, a data-deletion request, a regulatory inquiry). The inbox form is polled every five seconds and forwards to the same agent queue.

The first-response target is minutes for chat and 24 hours for the inbox. KYC and withdrawal queries resolve within 48 hours regardless of channel. The team's response window is on the homepage footer and on /about/.

The response windows on khelo bet24 are stated in the operator's published copy and re-verified on every editorial review. The windows are not aspirational; they are the SLA the support team is measured against.

The in-app chat window is minutes, not hours. The chat is open 24/7 and the first-response target is within minutes for any query that does not require a specialist. Specialist queries (KYC review, VIP manager, responsible-play officer) may take longer because the routing rule pulls a specialist from the queue.

The inbox window is 24 hours for first response. KYC and withdrawal queries resolve within 48 hours regardless of channel. The KYC review SLA is 12 hours on average; the 48-hour resolution target is for queries that require additional documentation or escalation.

Where the response window is not met, the agent queue logs the miss and routes the query to a senior specialist. The editorial reference does not publish per-channel SLA hits; the operator's own surfaces are the authoritative place for that data.