Request a quote WhatsApp

16 September 2026 · 3 min read

Hotel guest Wi-Fi: how PMS integration works

Login with room number and surname, access that closes itself at check-out, no printed passwords at the desk. How a hotel guest network is built on top of the PMS.

Guest Wi-Fi in a hotel is judged by two questions: can the guest connect the moment they reach the room, and do they ever have to ask reception for a password? PMS integration answers both. The guest logs in with room number and surname, identity already lives in the hotel system, and access closes automatically at check-out.

The gain shows up in three places: guest satisfaction, less load on reception, and 5651 records that can be tied to a person.

How the flow works

  1. The guest checks in; the PMS holds room, name and stay dates.
  2. The guest joins the "Hotel Guest" network and the welcome screen opens.
  3. They enter room number and surname.
  4. The portal queries the PMS and verifies an active stay.
  5. The session opens, bound to the check-out date, with speed policy by room type.
  6. At check-out access closes automatically.

Typical PMS connection types

ConnectionHow it worksNote
Web service / RESTPortal queries the PMS APIMost flexible, two-way
Hotel interface protocol (FIAS-like)Room/stay events over a persistent socketCommon, real time
Database viewQuery against a read-only viewUnder hotel IT control
File transferPeriodic room list exportFallback, delayed

Systems such as Opera, Protel, Elektra, Sistema, Asa and Hotelinking support at least one of these. The hotel IT team and PMS vendor decide which interface is opened.

Policy by room type

  • Standard room: one device at standard speed
  • Premium and suite: more devices, higher speed
  • Loyalty member: upgrade regardless of category
  • Meetings and banquets: separate voucher pool
  • Staff: separate SSID, independent of guest policy

Selling speed upgrades

The free tier is enough for most guests; business travellers and long stays ask for more. Upgrades can be sold in the portal and posted to the room account in the PMS — the single step that turns Wi-Fi from a cost line into a revenue line.

Go-live checklist

  • Is the PMS interface or integration licence enabled?
  • Are a test room and test stay defined?
  • Does surname matching tolerate case and local characters?
  • Do group stays and companion scenarios work?
  • Do sessions close correctly on early or late check-out?
  • Does a fallback login (SMS/voucher) engage if the PMS is unreachable?
  • Does the log archive record the room-to-session match?

For hotel chains

The hard part across properties is that each site runs a different PMS version and different network hardware. HotSpot works per-property: portal design and policies are managed centrally, the PMS connection is configured per property, and reporting comes together in one panel.

FAQ

Does PMS integration copy guest identity data into the Wi-Fi system?

No. The portal only verifies the room-and-surname match; nothing beyond stay validity needs to move.

What if the PMS is temporarily unreachable?

Guests should not be left offline. A fallback method (SMS or reception voucher) is defined and the normal flow resumes when the PMS returns.

Can a guest stay connected after check-out?

The session closes at check-out time, extended when a late check-out is recorded.

How do companions or a second guest in the room connect?

With the same credentials, within the device limit of the room policy; per-person verification can also be enabled.

What about meeting and wedding guests?

They have no room record, so vouchers or SMS login are used, limited to event hours.

Let’s simplify your guest Wi-Fi journey

Keep your existing infrastructure and bring access, engagement and 5651 records into one panel.

Request a Free Demo

We use cookies for visit statistics. Cookie policy