Networks & Wi-Fi
Why guest Wi-Fi generates complaints, and how to design it out
Why guest Wi-Fi draws complaints in hotels and restaurants, and how to design it out --- surveys, AP placement, captive portals, segmentation and peak load.
Guest Wi-Fi for hotels and restaurants fails on design, not bandwidth. MicroNet Global finds most complaints trace to coverage planned on a floor plan instead of a survey, too many access points shouting over each other, or a captive portal that breaks on modern phones. Survey properly, plan for peak density, segment the traffic, and the complaints stop.
"The Wi-Fi is slow" almost never means the bandwidth is slow
When a guest reports slow Wi-Fi, the first instinct is usually to buy a bigger circuit. That is the least likely fix. A 60-cover restaurant with a 500 Mbps leased line and a sound design will serve a full room comfortably; the same circuit behind a badly planned wireless estate will produce complaints at 8pm every Friday.
The honest causes are duller and more specific. Coverage was drawn on an architect's plan with no account of the plasterboard, the wine store, the mirrored wall or the lift shaft. Someone then added access points to fix a dead spot, all at full transmit power, so every AP now hears every other AP on the same channel and clients spend their airtime waiting to speak.
Then there are sticky clients: a phone that associated in the lobby and clings to that AP at the far end of the terrace, retransmitting at the lowest data rate and slowing everyone else in the cell. Add a contended uplink, DNS that times out and a portal that will not load, and the verdict is always the same three words.
What is a wireless site survey?
A wireless site survey is a measured assessment of how radio behaves in a specific building. A predictive survey models coverage from floor plans, wall materials and ceiling heights before any hardware is bought. A validation survey is walked on site after installation with a calibrated tool, recording signal strength, signal-to-noise ratio, channel overlap and real throughput at the places guests actually sit.
Complaint symptom, real cause, fix
| Guest complaint | Usual real cause | What actually fixes |
|---|---|---|
| "It's slow when it's Co busy" | erage design, not Mo apacity design --- too few APs serving a dense room | e APs at lower ower, narrower channels, band steering to 5/6 GHz |
| "It drops when I walk to the terrace" | ticky clients holding distant AP; no roaming assistance | une minimum data ates, enable 802.11k/v/r, reposition edge APs |
| "Full bars but nothing loads" | o-channel nterference, or DNS/upstream failure | hannel and power plan; esilient DNS; check the uplink, not the radio |
| "The login page never appears" | aptive portal blocked y private relay, DoH or HSTS behaviour | odern portal with orrect detection endpoints; allow-list before auth |
| "It worked yesterday" N | ighbouring venue F changed channels; auto-RF flapping | xed channel plan in dense areas, monitored rather than automatic |
| "Streaming buffers in the rooms" | hared contended roadband; no per-device fair use | usiness circuit with n SLA, plus per-client rate limits and QoS |
Design for the peak, not the average
The only load that matters is the worst one you will ever have. A full restaurant at 8pm on a Saturday, a conference floor at the coffee break, a members' club event where 300 people arrive inside twenty minutes --- that is the design case, and it is a capacity problem rather than a coverage problem.
In dense rooms the question stops being "does the signal reach?" and becomes "how many clients share this radio?" Capacity design means more access points at lower power, each covering a smaller area, with attention to ceiling height and what the ceiling is made of. A single AP in a 120-cover dining room will show full bars and perform badly.
Channel width discipline matters just as much. Wide channels look impressive on a datasheet and reduce the number of non-overlapping channels available, which in a dense venue worsens contention. Narrower channels, sensible transmit power and a deliberate plan for 5 GHz and 6 GHz --- rather than whatever the controller chose overnight --- is what holds up under load. Our note on [[Wi-Fi 7 and the 6 GHz band in hospitality]{.underline}](about:blank) sets out what newer hardware genuinely changes.
Cabling and power are the part nobody budgets
Every access point needs a cable and a PoE port, and in hospitality that is usually the expensive half of the job. Cat6 or better to each AP location, a switch with enough PoE budget for every port to draw its full allowance at once, and ceiling access that will not close a dining room for a week.
In listed buildings, hotels with occupied floors and restaurants trading seven days, the builder's work --- lifting ceilings, containment, making good, working nights --- frequently exceeds the hardware cost. Agreeing AP positions at first fix is far cheaper than chasing them later, which is why wireless design belongs in the [[IT infrastructure design]{.underline}](about:blank) stage rather than at snagging.
The captive portal and the data-capture trade-off
Marketing wants an email address. The guest wants to read a menu. Every extra field on the splash page costs you a share of the people who complete it, and a portal that fails on a modern phone costs you all of them plus a complaint to the duty manager.
Private relay, encrypted DNS and strict transport security all interfere with older portal designs, so the portal must handle modern connectivity-check behaviour and allow the necessary endpoints before authentication. Keep the journey to one screen, and remember that under UK GDPR marketing consent must be freely given and specific --- Wi-Fi access cannot be conditional on accepting marketing. Collect less, honour it properly, and what you hold is worth more.
Guest traffic must never touch the payment estate
Guest Wi-Fi shares a building with card terminals, the property management system, back-office machines, CCTV and door access. Those belong on separate networks with controlled routing between them, client isolation on the guest SSID, and firewall rules that are written down rather than remembered.
This is also how you keep guest wireless out of PCI DSS scope, as covered in our [[PCI DSS checklist for hospitality]{.underline}](about:blank). Flat networks, where a guest laptop and an EPOS terminal share a broadcast domain, remain common in venues that have grown by acquisition.
How MicroNet Global builds and supports it
MicroNet Global is a hospitality IT specialist founded in 2004, supporting 745+ sites across 15+ countries from offices in the UK, US and UAE. Our [[networking, Wi-Fi and connectivity]{.underline}](about:blank) work starts with a predictive design, is validated on site, and is documented so the next engineer inherits a plan rather than a mystery.
Once live, wireless is monitored rather than waited on. Around 90% of network faults we handle are resolved remotely without a site visit, through a 24/7 service desk with a 4-hour remote resolution target. For a demanding room, see the [[Sexy Fish Dubai project]{.underline}](about:blank), or how [[restaurants and bars]{.underline}](about:blank) are supported day to day.
Frequently asked questions
Cost is driven by cabling and access point count, not by the wireless brand. A 40-cover site typically needs two to four access points, a PoE switch, a firewall and a business circuit. Expect the containment, cabling and making-good element to rival or exceed the hardware in an occupied building. A survey first gives you a real number rather than a guess.
Written by the MicroNet Global team. If you are working through any of this for your own estate, the specialists here are happy to talk it through.