The guest Wi-Fi sign-in most travelers expect at a full-service hotel — typing a room number and last name instead of a voucher code — is not something a captive portal does on its own. It requires a RADIUS-based integration layer that bridges the property management system (PMS) to the Wi-Fi platform's captive portal. A property evaluating UniFi for guest Wi-Fi should ask any integrator exactly which bridge product handles that authentication, which PMS platforms it supports, and how often reservation data refreshes into the portal.
What does a PMS-linked Wi-Fi login actually require?
A room-number-and-last-name login authenticates a guest using the stay record itself rather than a code handed out at the desk. That depends on a middleware product sitting between the PMS and the Wi-Fi network. The Mews Guest WiFi Access Control integration is one documented example: it describes itself as providing "a much needed bridge between MEWS and any WiFi platform that supports RADIUS and has a captive portal i.e. UniFi," with guests authenticating via "their room number and last name as authentication," pulled from the reservation on file (Mews x Guest WiFi Access Control). That same listing notes the reservation data "is updated every few minutes" — a detail worth confirming with any integrator if a property handles a lot of same-day walk-ins, since a very recent check-in may not be reflected instantly.
A separate, UniFi-specific captive-portal product is documented in the same marketplace: "Art of WiFi" is listed as a "Captive Portal for UniFi networks offering hotel guest logins based on room number and last name" (Guest Experiences | Mews Marketplace). The pattern across both listings is consistent — the PMS-linked login is delivered by a third-party RADIUS/captive-portal product that is purpose-built to sit on top of a network like UniFi, not a feature that ships inside the PMS or the network controller by itself.
Why does this matter when comparing integrator bids?
If a proposal includes "PMS-linked Wi-Fi login," ask the integrator to name the specific bridge product they intend to deploy, confirm it supports your PMS platform by name, and ask what happens to guest sign-in if that bridge goes offline — does the property fall back to a voucher or open-access method, and who owns configuring that fallback? Because the authentication logic lives in the bridge rather than in the underlying network hardware, bandwidth limits, session length, and how often a guest's record refreshes are all questions to put to whichever RADIUS product is proposed, not assumptions to leave unanswered.
How should guest traffic stay separated from staff and PMS systems?
Whichever sign-in method a property ends up running, ask your network integrator how guest, staff, PMS, and point-of-sale traffic are segmented from one another so a guest device never has a network path to property-management or payment systems. That segmentation decision is worth resolving at the network-design stage, before the captive-portal or PMS-bridge product is even selected. Cave Group's hospitality page covers network infrastructure, PMS integration, and guest-room systems scoped as one coordinated project rather than separate vendor pieces. A related read on how PMS data already drives guest-room systems once a stay begins is Hotel PMS Integration: Opera, Mews, Salto & myRoom XC.
What should a GM ask before signing off on a sign-in method?
Before committing to a PMS-linked login, a GM or IT director should get three answers in writing: which PMS platforms the proposed RADIUS bridge actually supports, how often reservation data refreshes into the portal (the Mews integration cites a refresh interval of a few minutes), and what the front desk's fallback workflow looks like if that integration goes down. These are contract-level questions, not settings inside the network controller.
Frequently asked questions
Does a hotel need a special integration for guests to log into Wi-Fi with room number and last name?
Yes. That sign-in method depends on a RADIUS-based bridge between the PMS and the Wi-Fi platform's captive portal, such as the documented Mews Guest WiFi Access Control integration or a UniFi-specific captive portal product like Art of WiFi — it is not a feature built into the network hardware itself.
How often does PMS-linked Wi-Fi login data refresh?
In the documented Mews Guest WiFi Access Control integration, reservation data used for room-number-and-last-name authentication updates every few minutes, which a property should account for when handling same-day check-ins or walk-ins.
What should I ask an integrator who proposes PMS-linked Wi-Fi login?
Ask which specific RADIUS bridge product they intend to deploy, whether it names your PMS platform as supported, and what the fallback sign-in process looks like for guests if that integration goes offline.
Should guest Wi-Fi share the same network as staff and PMS systems?
No — ask your integrator how guest, staff, PMS, and point-of-sale traffic are segmented from each other regardless of which sign-in method is used, so a guest device has no network path to property-management or payment systems.