Blog · 2026-09-21
How to kill a shared WiFi password without a single angry phone call
Every property with guest WiFi has the same password problem. One password, written on a laminated card, known by everyone who has ever stayed there and several people who have not. Rotating it punishes the guests who are already on. Not rotating it means it is not really a password.
The fix is per-guest codes. The migration is where people give up.
Do not cut over. Overlap.
Run both sign-in methods at once. On day one the portal accepts the shared password and personal codes, and — this is the part people flinch at — the shared password is printed on the portal page itself, next to the date it stops working.
That single decision converts the event from an outage into a notice. A guest who gets bounced to an unfamiliar screen reads the answer off it, gets on, and sees the deadline while they are there. Nobody calls the front desk to ask what the password is, because the screen just told them.
Every support call is a migration
The guests who do call are the opportunity. The script is not "here's the password", it is "I can give you your own code right now that lasts your whole stay." They say yes, because it is obviously better for them, and that device never needs the shared password again.
A date is a guess. Measure instead.
Here is where most migrations go wrong: someone picks a date, the date arrives, the password is switched off, and it turns out eleven people were still using it — including the monthly residents, who are the loudest and least willing to re-enter anything.
The date was always a proxy for the question you actually care about: has everyone moved? So measure that instead. Schedule the retirement for "once no guest has signed in with the password for seven days", with a hard date as a backstop. If everyone migrates early, it retires early on evidence. If they do not, the date still holds.
Two guarantees make that safe to leave unattended. It will not fire on silence — a portal that recorded no activity at all looks identical to one where everybody migrated, and those deserve opposite answers. And it cannot remove the last remaining sign-in method, because stranding every future guest at 3am is worse than a change not happening.
Go and stand in the car park
The last ten percent do not migrate through software. Pick a day, be on the property, and have the front desk tell callers "he'll come to you — what's your lot number?" Bring the TVs and streaming boxes into the same visit, because those cannot see a captive portal at all and need credentials on the other SSID.
An hour of walking around beats three weeks of hoping.