Login help, walked through the OTP flow.
PlayerzPot sign-in is a phone-number + OTP flow. The OTP arrives by SMS to the phone number you registered with. This desk page is the plain-language walkthrough of the flow, the four common OTP failure modes, and the in-app cache-clear path when a sign-in is stuck on the OTP screen.
Phone number, OTP, in-app verification.
PlayerzPot sign-in is a three-step flow. Each step has a common failure mode and a known fix — the desk walks both.
Step 1 — Enter the registered phone number
Open the app and tap Sign In. Enter the phone number you registered with — the same number that received the original sign-up OTP. The country code defaults to India (+91); if you registered with a different country code, tap the flag to switch. Do not add spaces or dashes; the field accepts digits only.
Step 2 — Wait for the OTP
The OTP arrives by SMS within sixty seconds. If the OTP does not arrive within sixty seconds, tap Resend. The desk’s read: the first resend is free; subsequent resends carry a one-minute cooldown. If the OTP still does not arrive after two resends, switch to the failure-mode walkthrough below.
Step 3 — Enter the OTP and confirm
Enter the six-digit OTP in the field. The field accepts digits only and auto-advances after the sixth digit. If the OTP is correct, the app signs you in and lands on the lobby. If the OTP is rejected, the failure is one of four modes — see the walkthrough below.
Failure mode 1 — wrong phone number
The most common OTP failure is entering a phone number that does not match the registered number. The app does not tell you the number is wrong; it just does not deliver the OTP. Fix: tap the back arrow, re-enter the registered phone number, and retry.
Failure mode 2 — SMS delivery delay
The second most common failure is SMS delivery delay, usually caused by the carrier’s SMS gateway throttling. Fix: wait sixty seconds, then tap Resend. If the second OTP does not arrive either, switch to Wi-Fi or move to a location with stronger signal.
Failure mode 3 — OTP expired
OTPs expire after five minutes. If you typed the OTP after the expiry window, the rejection message reads “OTP expired.” Fix: tap Resend, wait for the new OTP, and enter it within five minutes.
Failure mode 4 — too many failed attempts
After five consecutive OTP failures, the app locks the sign-in for fifteen minutes. The lock is a carrier-level throttle, not an account-level block. Fix: wait fifteen minutes, then retry. The desk does not recommend uninstalling the app to clear the lock — the lock is on the phone number, not the binary.
When to clear the in-app cache
If the sign-in is stuck on the OTP screen even after a successful OTP entry, the failure is a stale session token. Fix: from the phone’s app settings, clear the in-app cache (not the data — clearing the data will sign you out and reset the KYC anchor). The cache-clear does not affect your wallet, contest history or KYC status.
To verify: the OTP delivery timer and the resend cooldown are visible inside the app’s Sign In screen. The desk’s description above is a structural walk-through — confirm the actual OTP screen inside your own app before flagging a sign-in failure.
Three passes through any login-help page.
Sign-in is phone-number + OTP only.Verified
The lockout fires after five failed OTPs.Verified
Cache-clear resets a stuck session token.To verify
Build tonight's team on PlayerzPot.
Open the in-app lobby, pick a contest, and lock a team using the points-system cheat sheet from our desk. New users can enter from a practice contest — verify the current entry fee inside the lobby.