A captive portal is the welcome screen that opens automatically when a guest joins your network. Until they authenticate, they cannot reach the internet. It serves two purposes: a proper welcome, and recording access under Law 5651.
The right login method depends on the venue. PMS in hotels, vouchers at expos, SMS in cafes, sponsor approval in corporate buildings produce the least friction.
How a captive portal works
- The device joins the network and receives an IP address.
- The controller or firewall marks the device as unauthenticated.
- The first web request is redirected to the portal.
- The guest completes verification.
- The portal tells the network device to open the session; time, speed and quota rules apply.
- The session record is written to a timestamped archive.
This flow is built with controllers such as Ruckus, Cisco, Aruba, Meraki, Ruijie and firewalls such as Fortinet, Palo Alto, Sophos, MikroTik.
Login methods compared
| Method | Identity strength | Guest friction | Cost | Best fit |
|---|---|---|---|---|
| SMS / OTP | High | Low | Per message | Cafe, mall, hospital |
| National ID + SMS | Very high | Medium | Per message | Municipality, public |
| Voucher | Medium | Very low | None | Expo, events, paid access |
| PMS (room + surname) | High | Very low | None | Hotel, resort |
| Sponsor approval | High | Medium | None | Office, factory |
| App API + OTP | High | Low | Development | Retail and restaurant chains |
| Registered user | High | Very low | None | Staff, regular visitors |
SMS / OTP
The guest enters a phone number and receives a one-time code. The most common method; habits are established. Cost per message, and international numbers need a separate plan.
National ID + SMS
Produces a stronger record. Preferred by public institutions and networks with high compliance expectations.
Voucher
Pre-generated codes with time or quota limits. Great for expos, events and accommodation packages; no messaging cost, but distribution must be planned.
PMS room number + surname
Hotel-specific. Identity already lives in the hotel, so login is one step and access closes at check-out. Details: PMS integration guide.
Sponsor approval
A visitor request goes to a staff member for approval, so every access has an owner. Suited to high-security buildings.
App API + OTP
If the brand has its own app, its membership system talks to the portal and ties loyalty to Wi-Fi.
Registered user
Permanent accounts for staff and regular visitors, with device remembering.
Which venue, which method?
- Hotel: PMS + SMS fallback, vouchers for meetings
- Expo and events: voucher + SMS, high concurrency
- Restaurant chain: SMS or app API tied to loyalty
- Mall: SMS alongside store campaign screens
- Municipality and public: national ID + SMS
- Corporate office: sponsor approval + registered users for staff
- Marina and resort: voucher + PMS
Portal experience essentials
- Design mobile-first; almost every guest connects from a phone
- Detect language automatically, allow manual switching
- Keep the privacy notice readable and store consent with a timestamp
- Finish verification on one screen, ask for no unnecessary fields
- Use the success screen as natural campaign space
- Do not re-prompt a returning device while its session is still valid
Rollout checklist
- Is the portal served over HTTPS?
- Are Apple/Android captive-network detection endpoints reachable?
- Are session time, speed limit and quota policies documented?
- Is there a fallback channel for the SMS provider?
- Has peak concurrency been estimated?
- Is the log archive backed up to a second location?
FAQ
How is a captive portal different from a shared Wi-Fi password?
A shared password identifies nobody. A portal ties every session to a verified person and a timestamp.
The portal does not open for a guest — why?
Usually blocked captive-network detection endpoints, missing DNS redirection, or a certificate error.
Can we avoid SMS costs?
Yes. Vouchers, PMS login, sponsor approval and app membership need no messages. Most businesses use those as primary and SMS as fallback.
Must a returning guest log in every day?
No. Session duration and device-remembering policies define how long re-verification is skipped.
Can several methods be offered at once?
Yes. SMS, voucher and PMS login can sit side by side, and policy decides which appears at which location.
Managing hundreds of portals
In multi-site businesses the hard part is not one portal but keeping hundreds consistent. HotSpot manages portals, login methods, speed policies and the log archive from a single panel, applying a change to a whole location group at once.