Most hotel WiFi upgrades today stop at the same point: give each guest a unique password on a shared network. It is a genuine improvement over a single password for everyone. But it is not personal WiFi. And in 2025, guests increasingly know the difference.
The problem with shared SSIDs
When every guest connects to the same SSID — “HotelGuest”, “StayConnected”, or whatever the property calls it — they are all on a shared network. Each has their own passphrase, but the fundamental experience is shared.
The friction surfaces in predictable ways. Smart TVs, streaming sticks, gaming consoles, and smart speakers don’t auto-connect — they lack browsers for captive portals and don’t recognise a passphrase they’ve never seen. Guests spend time at check-in entering a long random password across six devices. If they move between the room and the lobby, the session can drop. If they return for a second stay, they start over.
These are the WiFi complaints that appear in reviews. They are also entirely avoidable.
What a personal network actually means
Personal WiFi means each guest has their own named SSID — a network that looks, to every device they carry, like their WiFi at home.
Their phone already knows it. Their laptop already knows it. Their tablets, wearables, and streaming devices already know it. Everything joins automatically, without prompts, without passwords, without captive portal friction — because everything has already connected to that network before.
This is what Wiacom Horizon delivers. Not a unique passphrase on a shared SSID — a dedicated named network per guest, provisioned on the hotel’s existing WiFi infrastructure, activated at check-in and removed at check-out.
How it works
When a guest checks in — or before they arrive if pre-arrival provisioning is enabled — Horizon creates a real SSID slot on the hotel’s WiFi controller assigned to that guest.
At check-out, the SSID is revoked automatically and the slot returns to the pool. No staff action required. No credential to manage.
Horizon works on the infrastructure the hotel already has — Cisco Meraki, HPE Aruba, Ruckus, MikroTik, and others — via cloud API, local controller API, or Wiacom Agent for on-premises deployments. No hardware change required.
The compliance dimension
PCI DSS v4.0 (mandatory since March 2025) requires per-device credential rotation and automatic revocation at the end of each stay. Horizon satisfies this natively — each guest gets a unique credential tied to their reservation, revoked automatically on check-out through PMS integration.
GDPR and UK GDPR Article 32 require unique user identification on networks where personal data is processed. A personal SSID per guest satisfies this at the infrastructure level.
The guest experience argument
Hotels compete on experience. WiFi is increasingly part of that experience — not as a background utility but as something guests notice. A guest who connects at check-in, watches every device join automatically, and finds the same personal network waiting at the hotel’s airport lounge on departure day is having a qualitatively different experience from one entering a 20-character passphrase across multiple devices every time they return to their room.
Personal WiFi per stay. A small operational decision with a disproportionate effect on how connected — and how cared for — the stay feels.
Wiacom Horizon provisions personal named SSIDs per guest on any existing hotel WiFi infrastructure. Integrates with Oracle OPERA Cloud via OHIP, with pre-arrival provisioning and automatic check-out revocation.
