KheloMore login and account access notes for Indian players

KheloMore account access is the layer most users touch every week: signing in, recovering a password, switching devices, updating a phone number, or saving a location for the next booking. This page walks through what to set up before relying on the login, and what to watch for when something does not work as expected on a real device in a real Indian city.

What this page covers

This page is structured so each section can be read on its own. The first sections explain what to look for, the middle sections walk through the practical checks, and the closing sections address common questions raised by Indian parents, players, and team managers who use KheloMore.

Account access is rarely the reason someone installs KheloMore, but it becomes the reason a booking fails, a receipt goes missing, or a referral code does not apply. A few small steps during sign-up remove most of those problems later, and they cost almost nothing in time.

This page is independent editorial guidance. Login, recovery, and account actions should still be completed in the original KheloMore flow on the official app or website; nothing on this site should be treated as an account-management tool.

Set up the account before the first booking

Use a phone number or email address that is checked regularly. KheloMore sends booking confirmations, payment receipts, slot reminders, and refund notices through that channel, so an old number or an unused inbox causes missed slots and lost receipts that are hard to recover later.

Pick a password that does not match the same password used for the email account itself. A separate password for the sports app means one leak does not chain into another account, and the password reset flow stays simple when the user genuinely forgets it.

Save at least one sport category and one location during sign-up. That makes the first launch faster, the first search more relevant, and the first booking less likely to fall back to a generic listing in the wrong city.

Two-factor and recovery options

Two-factor authentication is worth turning on when the account holds payment methods, wallet balance, or active bookings. A second step at sign-in protects the account if the password leaks elsewhere, and it costs a few seconds per login.

Recovery options should be kept current. A backup email and a recovery phone number are the two routes KheloMore typically uses when a password reset is requested. If both are stale, account recovery can take days instead of minutes, especially during weekends and tournament weeks.

Avoid saving passwords in browsers or password managers that are shared across devices. The login flow on a shared family device should sign out fully after each session, especially when a payment method is saved or a wallet balance is loaded.

Common login issues and what they usually mean

OTP not arriving: usually a network delay or a wrong number. Wait two minutes, then retry. If the OTP still does not arrive, switch to the email recovery flow instead of retrying the SMS route repeatedly.

Password rejected when it should not be: usually a case-sensitivity or autocorrect issue on a mobile keyboard. Switch to the desktop flow to test the same password, and reset if the desktop flow also rejects it.

Account locked after several attempts: usually a security hold that lifts after a cooldown window. Use the recovery flow rather than retrying the password repeatedly, which can extend the lockout and add another day to the recovery timeline.

Old booking history missing: usually a sign-in to a different account (for example, the personal number versus a work email). Check the active account name at the top of the profile screen before reporting a data loss to support.

Profile details worth filling in

Saved locations make the first search relevant. A user who plays in two cities should save both, with a short label, so the app does not default to the wrong city on launch, and so the search radius can be set tighter for each city.

Sport categories matter for offers. KheloMore sometimes sends targeted trial discounts based on selected sports. A category that is left blank will not receive those offers, even if the user would qualify under the offer terms.

Notification preferences should match the actual routine. Booking confirmations and slot reminders are useful; promotional pushes usually are not. Tightening notifications early prevents the app from feeling noisy later, which is when most users uninstall.

What the account screen reveals and hides

Active bookings, receipts, and wallet balance are usually visible on the account screen. When a receipt does not appear within an hour of payment, the account screen is the first place to check before contacting support, and a screenshot from that screen is the most useful thing to send.

Saved locations, default sport, and notification preferences are usually editable on the same screen. Reviewing them once a quarter prevents drift between the app's behaviour and the user's actual routine, which is the main cause of stale notifications.

Referral and reward history, where present, are usually on the same screen. Cross-checking referral credit after a friend signs up prevents the small-balance disputes that pile up over a year, and it gives the user a clean record at the end of the year.

When account help is needed

For payment or refund disputes, the booking history screen on the account usually has the most useful details: amount, date, venue, slot, and payment method. Screenshot that screen before contacting support, and redact only the last four digits of any card number.

For login lockouts that do not lift after the cooldown window, the recovery flow on the official KheloMore site is faster than the in-app help form, because the site usually exposes a phone-verification fallback that the app does not.

For account deletion or data export, the privacy policy on this site covers the general right-to-erasure process; the actual request must still go through the official KheloMore flow, and the user should keep a copy of the deletion request email.

Multi-device habits that keep accounts healthy

Sign out from a device when it stops being the primary booking device. Old devices with active sessions are a common source of unexplained bookings and wallet deductions that the user does not remember making.

Review the device list on the account screen once a quarter. Each entry should be a device the user still uses. Devices that have been lost, sold, or passed to a family member should be removed from the account before they cause friction.

Avoid linking the KheloMore account to a shared family Apple ID or Google account. Personal sport bookings deserve a personal sign-in, especially when payment methods are saved.

Common questions