Dex: Created page with "= I.T. Sanding and the Guest Experience in Hospitality = == When Infrastructure Is Felt, Not Seen == In most industries, good I.T. is invisible. In hospitality, good I.T. is felt. A guest may never see your switches, firewalls, or authentication systems — but they will absolutely feel the difference between a network that was thrown together and one that was designed for visitors. The guiding idea of this article is simple: : ''Great hospitality I.T. doesn’t impr..."

2026-04-19T17:25:35Z

Created page with "= I.T. Sanding and the Guest Experience in Hospitality = == When Infrastructure Is Felt, Not Seen == In most industries, good I.T. is invisible. In hospitality, good I.T. is felt. A guest may never see your switches, firewalls, or authentication systems — but they will absolutely feel the difference between a network that was thrown together and one that was designed for visitors. The guiding idea of this article is simple: : ''Great hospitality I.T. doesn’t impr..."

New page

= I.T. Sanding and the Guest Experience in Hospitality =

== When Infrastructure Is Felt, Not Seen ==
In most industries, good I.T. is invisible. In hospitality, good I.T. is felt.

A guest may never see your switches, firewalls, or authentication systems — but they will absolutely feel the difference between a network that was thrown together and one that was designed for visitors.

The guiding idea of this article is simple:

: ''Great hospitality I.T. doesn’t impress guests — it relaxes them.''

== The Guest Is Not Here for Your Network ==
A hotel guest arrives with multiple devices, low patience, high expectations, and zero interest in your infrastructure.

They do not want a lesson in security, a complex captive portal, or a sense that they are being monitored. They want their phone to connect, their laptop to work, their TV to cast, and their stay to feel effortless.

The moment I.T. becomes noticeable, hospitality has already failed.

== The Myth: Security vs Guest Experience ==
There is a persistent belief that you must choose between strong security or a pleasant guest experience. This is a false dichotomy.

In reality, the most secure hotel networks are often the most comfortable — because they are clear, intentional, and predictable. The key is staging trust, not granting it blindly.

== The Walled Garden Reimagined ==
A ''walled garden'' is often treated as a penalty box: you cannot do anything until you authenticate. That framing is wrong.

A well-designed walled garden is more like a hotel lobby — safe, calm, clearly bounded, and genuinely useful. Instead of offering nothing, a good garden offers essential services, local resources, clear next steps, and a sense of place.

The goal is not restriction. It is hospitality before trust.

== Full Client Isolation Is the Correct Baseline ==
Hotel Wi‑Fi is uniquely hostile: thousands of unknown devices, constant churn, no shared trust model, and high abuse potential.

For this reason, full wireless client isolation should be non‑negotiable. Each guest device exists in its own bubble with no guest‑to‑guest traffic, no broadcast leakage, no lateral movement, and no accidental discovery.

This protects guests from each other quietly and completely, but isolation alone is not enough.

== Selective Connectivity: Isolation Without Loneliness ==
Modern guests expect some things to just work — casting to the room TV, printing documents, discovering nearby services. The solution is not disabling isolation, but mediating discovery.

=== mDNS / Bonjour Done Properly ===
Protocols such as mDNS and Bonjour do not have to be a security nightmare. When implemented correctly, discovery is proxied, visibility is scoped, direction is controlled, and abuse is prevented.

The guest device never sees other guests. It sees its TV, hotel printers, and approved local services. This is not a hole in the network; it is a curated window.

== TVs and Printers: Perfect Garden Services ==
Televisions and printers are ideal walled‑garden citizens. They are purpose‑specific, predictable, locally relevant, and easy for guests to understand.

When mapped intelligently by room, access point, or location, casting and printing feel natural without leaking anything unintended.

Guests do not think the network is well‑engineered. They think it was easy — which is exactly the point.

== Proxies and Local‑Only Services ==
A pleasant walled garden often includes explicit web proxies, update mirrors, local DNS helpers, onboarding pages, and help or status portals.

These services act as gentle bridges: you can do these useful things safely right now. They provide utility, reassurance, and context while dramatically reducing guest frustration and support calls.

== RADIUS, WiSPr, and Quiet State Transitions ==
Behind the scenes, systems such as RADIUS and WiSPr quietly manage session state, time‑boxing, re‑authentication, and transitions through access stages.

The guest does not need to see any of this. What matters is that access progresses cleanly and honestly:

Untrusted → Limited → Verified → Trusted

Each stage has clear capabilities, honest boundaries, and predictable behaviour.

== Why Hospitality Notices Good I.T. ==
Most industries only notice I.T. when it breaks. Hospitality notices when it works.

Well‑designed guest networking results in fewer complaints, fewer support calls, better reviews, calmer staff, and happier guests. It directly supports the core business: comfort.

== The Goal: Civilised Networking ==
Great hospitality I.T. is calm, predictable, respectful, and quietly protective. It treats guests not as attackers, but as visitors who have not yet been introduced.

A good walled garden is not empty — it is welcoming. And when guests leave without thinking about your network at all, you have done something very right.

I.T. Sanding and the Guest Experience in Hospitality - Revision history