Revati Kolhatkar

An open pocket notebook lying on a pale sand-coloured linen tablecloth in soft window light, its ruled page empty, a pencil across it and a small wooden hourglass standing at the notebook's top edge with a thin stream of pale sand falling, nothing else on the plain cloth around them.

Revati writes the pages for the worst five minutes of a login: the lock screen, the reset link that never comes, the support chat that suddenly wants a code. Her rule for every page is that it should tell a worried reader what to stop doing before it tells them what to do.

She came to the subject from helping relatives with banking apps. The pattern she kept seeing was the same across very different services: the account was rarely lost to a clever attack, and very often lost to a helpful stranger during a lock-out.

Independent sign-in help · not Instamatch · no forms, no numbers

What she covers

Why accounts lock. How failed-attempt limits work in general, why repeated tries tend to lengthen a pause, and why nobody outside a platform can say its exact rule.
Where support really sits. Inside the account's own site or app, reached from an address the reader opens personally, and nowhere else.
What support never asks for. Codes, passwords, fees, remote access, a UPI PIN.

Independent sign-in help · not Instamatch · no forms, no numbers

How she works

She writes only what a reader can confirm on their own screen, and she marks plainly what nobody outside a platform can know, such as its lock thresholds or its payout times. She does not name agents, channels or numbers.

Independent sign-in help · not Instamatch · no forms, no numbers

Outside the site

Revati keeps a folder of screenshots of lock messages from many apps, with the personal details cut out, and uses it to explain what each wording usually means.