In high-volume hospitality, manual voucher generation creates delays, data-entry mistakes and long check-in queues. Reception already knows who is arriving. The Wi-Fi still wants a username typed by hand. The objective was simple: remove routine voucher creation from the desk without giving up control over who lands on which network.
We are not naming the property here. The logos on the hotel Wi-Fi page show who we work with. This write-up sticks to the workflow and what changed at the desk.
The property system already held the booking. A small service accepted those records as JSON, applied the house rules for stay length and network, created the guest credential in RADIUS, and produced print-ready output for the front-desk printer. Staff only touched exceptions: a wrong room, a VIP that needed a different SSID, a voucher that had to be revoked early.
RADIUS mattered because expiry and VLAN choice had to be real. A voucher that never expires on the same network as the office is how a guest laptop ends up next to the server. UniFi carried the wireless. The API did not replace the PMS. It stopped people retyping what the PMS already knew.
What we measured in practice was operational, not a marketing percentage. Front-desk throughput improved because the slip could print while the key was still being discussed. Typo-related access failures dropped because surnames were no longer retyped under pressure. The repetitive admin work moved off the reception shift.
What we did not do: invent traffic graphs for this page, rebuild the property system, or leave the RADIUS box outside the backup conversation. The credential store sits on a server we already manage. If nobody backs it up, you have a lock with one key.
If your desk still retypes every arrival, start with hotel and lodge Wi-Fi or custom API and RADIUS. For a first look on site, book a Wi-Fi site survey.