Hotel guest Wi-Fi is a network that guests join with their own devices, kept separate from staff and hotel systems. In a well-built setup, the guest signs in on a captive portal with their room number, an SMS code or ID details, gets the speed and quota assigned to them, and the connection records are kept in a tamper-evident way for compliance logging. This guide covers the architecture, login methods and record-keeping duties.

The building blocks of a hotel hotspot

  • Access points and controller: coverage and roaming across rooms, lobby, restaurant and pool.
  • Network separation: guest, staff, PMS, POS and IP camera networks on separate VLANs and SSIDs. Client isolation should be on for the guest network so guests can't see each other's devices.
  • Hotspot gateway: sits at the internet exit and handles the captive portal, authentication, rate limits, quotas and logging.
  • PMS integration: brings stay data into the hotspot so guests can sign in with their room number and surname.
  • Security: IPS and application control at the internet edge, and nothing on the guest network able to reach hotel systems.

A gateway that works at the network exit, independent of the access point brand, means you can renew the wireless estate without replacing the hotspot layer.

How a captive portal works

  1. The guest's device joins the SSID and receives an internal IP over DHCP.
  2. The gateway marks the device as not yet authenticated; internet access is closed.
  3. The operating system sends an HTTP request to a known test address. The gateway intercepts it, and the operating system opens the captive portal window automatically.
  4. The guest signs in; the gateway authorises the device for the session and applies the configured speed and quota.

Requests to HTTPS sites cannot be redirected to the portal without a certificate error, which is why operating-system captive portal detection matters so much. Newer standards (RFC 8910 and RFC 8908) let the network announce the portal address directly through DHCP and router advertisements.

MAC address randomisation: current phones may use a different MAC address for each network. If device recognition relies on the MAC, guests may be asked to sign in again. Tying the session length to the stay when guests sign in through the PMS reduces this.

Login methods

PMS (room no. + surname)SMSID details
Guest experienceFast; no extra stepNeeds a phone number and codeNeeds a form
Link to a personThrough the booking recordThrough the phone numberDirect
Best forStaying guestsLobby, restaurant, visitorsDorms, campuses, long stays

Most hotels combine PMS login for staying guests with SMS for visitors and event attendees. A further benefit of PMS integration is that access ends automatically at check-out.

Speed, quotas and plans

  • Rate limits per room or user: stop one room from consuming the whole internet link.
  • Quotas: for fair use on long stays or in dormitories.
  • Paid plans: free basic access and a paid high-speed plan can run side by side.
  • Evening peak: video traffic climbs when guests return to their rooms. Plan total bandwidth for that hour.

Details that protect the guest experience

  • One-step login: keep the portal simple; it should open in the guest's language and ask for one form at most.
  • One login, every device: a guest's phone, laptop and tablet should connect with the same login, within the device count allowed per room.
  • A session that lasts the stay: asking guests to sign in again every day sends needless complaints to reception. Tie the session length to check-out.

Compliance logging

Many countries require venues that offer public internet access to keep records linking network activity to a device or person. In Türkiye, for example, Law 5651 treats hotels as public-access providers that must keep IP allocation records (which internal IP was given to which device, and when) for one year, signed with a time stamp, and take content-filtering measures. Rules differ by country, so check what applies to your properties.

Whatever the jurisdiction, a few principles hold:

  • Authenticate users so records can be tied to a person: PMS, SMS or ID login all do this.
  • Keep records tamper-evident, for example signed and time-stamped, so their integrity can be shown later.
  • Define retention and delete records automatically when it ends.
  • Limit access to the records and log who views them; data-protection law such as GDPR expects this.

In practice, hotspot records hold the user identity, device MAC address, IP address and session times.

Deployment checklist

  • Is the guest network separated from staff, PMS and POS networks?
  • Does the captive portal open automatically on iOS, Android, Windows and macOS?
  • Does access end at check-out?
  • Is there a rate limit per room or user?
  • Are records signed, retained for the required period and exportable on request?
  • Is there failover if the gateway fails?

With CoreGate Hotspot Gateway

CoreGate Hotspot Gateway comes with a multilingual captive portal branded for your property, SMS and ID verification and PMS login with room number and surname. Speed and quota are set per user, room or plan, and free and paid plans can run together. Session records are signed with a time stamp, retained and exportable. It works independently of your access point brand, and every site of a hotel chain is managed from one console. To protect the internet edge, it runs alongside CoreGate Security Gateway on the same platform.