Guests log in with details they already have, the platform verifies them against your property management system, and their access ends by itself at checkout.
Almost every guest WiFi problem in a hotel traces back to the same decision: the network has no idea who is staying there. So it is given one password, that password escapes, and from then on the property is providing free internet to former guests, the shop next door and whoever screenshotted it into a group chat. Bandwidth that was sized for eighty rooms is serving considerably more than eighty rooms.
Connecting the WiFi to the property management system fixes the cause rather than the symptom. Occupancy already lives in the PMS and is already accurate - reception maintains it all day because the rest of the business depends on it. Letting the network read that same truth means access begins when someone checks in and ends when they leave, with no new process for anybody to follow.
Underneath, this is ordinary cloud AAA: the portal authenticates the guest, the platform authorises them with the limits attached to their room, and it keeps the accounting. The PMS simply supplies the answer to “is this person really in room 214 tonight?”
They join the property's open network and the captive portal opens in the browser by itself. No app, no password handed over at the desk, nothing printed.
Two things every guest already knows, and the only two the front desk never has to explain twice.
The pair is checked against the property management system: is this room occupied, and is that the name on the booking? Only a match is allowed online.
Speed and data limits, session length and how many devices that room may bring online are applied from the plan attached to the room or rate.
When the room checks out, access stops. Nobody has to remember to revoke anything, and a departed guest's phone in the car park stops using the property's bandwidth.
One key written on a card at reception ends up in a WhatsApp group, on a review site and in the hands of everyone in the building next door. A credential tied to an occupied room cannot spread that way, because it stops working when the room empties.
No codes to generate, no vouchers to print for in-house guests, no explaining a password over the phone at midnight. Vouchers stay available for walk-ins, events and banquet bookings, where they belong.
Checked-out devices, staff phones on the guest network and the neighbouring shop all quietly consume a link that the property is paying for. Tying access to occupancy is the cheapest bandwidth upgrade most hotels can buy.
Sessions are logged against the room and the guest who was in it, rather than an anonymous code, which is the difference between having records and having usable records.
The guest enters their room number and surname on the captive portal and the WiFi platform checks that pair against the property management system. If the room is occupied by that guest, they are let online with the limits attached to that room. The same link is what allows access to expire at checkout rather than staying open until somebody remembers to revoke it.
Rather than publish a list, we check yours. What matters is whether your PMS exposes an interface we can query for occupancy and guest name - many do, through an API or an integration module, sometimes as a paid option from the PMS vendor. Tell us which system you run and we will confirm the integration path before you commit to anything.
Then the property runs on PIN codes, printed QR vouchers or SMS one-time passwords instead, all of which the platform supports, with the same per-user limits and the same records. PMS login is the smoothest option, not the only one - and it can be added later if the PMS is replaced or upgraded.
Yes, and you set the ceiling. A room can be allowed a phone, a laptop and a tablet while still being stopped from sharing its details with the entire floor. The limit is applied per room rather than per login attempt.
Nothing, from their side. Access follows the room's status in the PMS, so an extension keeps them online and an early departure ends it. That is the point of driving it from the PMS rather than from a fixed validity period.
No. The captive portal opens in whatever browser the device already has, on any operating system. Nothing is installed and nothing is downloaded.
We will confirm the integration path before you commit to anything, and set out what the property needs either way. See also vouchers and hotspot billing, the buyer’s guide and hospitality software.
Ask about your PMS