The guest just connected to the Wi-Fi. Now what?

Build the portal if you want. But send the guide first.

Every guest does it. It's the first thing after walking in: look for the Wi-Fi network, connect, take a breath. For most short-term rental hosts, that moment ends right there. A note on the fridge, a card on the table, a message sent earlier. Connected. Done.

But think about what just happened. The guest is inside your property for the first time, phone in hand, browser open or about to open. They have maybe fifteen seconds of peak receptiveness before they drop the bags, open the fridge, start exploring. It's probably one of the highest-attention moments of the whole stay.

And most hosts let it pass.

A recent post in the short-term rental community caught attention for this reason: a host had built a Wi-Fi portal that turned the login page into a mini guest hub — local tips, property info, checkout reminders. The idea was sound. But the conversation that followed revealed something more interesting than the tool itself: the question of when the guest guide should actually reach guests, and through which door.

The Wi-Fi moment is real — but it already arrives late

There's a temptation to treat the Wi-Fi connection as the main distribution point for guest information. It's physical, reliable, universal. Every guest connects. Why not build there?

Because the moment guests connect to your Wi-Fi, they're already inside. They've already followed the arrival instructions, found the entrance, dealt with parking and luggage, handled everything that needed attention along the way. They're relaxed and curious, or tired and a little frustrated. Either way, what they want from the Wi-Fi portal is to get on the internet — not to read a guide.

The productive moment is earlier. The guest opening a link in the booking confirmation on the train towards your property is infinitely more receptive than the guest connecting to the Wi-Fi after arriving. They're still in planning mode, still asking themselves "what do I need to know?" instead of "where's the hot water tap?"

That's why the Wi-Fi connection is best understood as a redundant access point, not a primary one. If you sent the guide earlier and the guest lost it, the Wi-Fi moment gives them a second chance. It's useful. But it's a plan B, not the strategy.

A guide that arrives too late can't do its job

There's a structural problem with guest guides delivered at check-in or later: they answer questions guests already have, instead of preventing the questions from forming.

• "Can I check in early?" — asked two days before arrival, not at the door
• "Is there parking nearby?" — asked the night before, not after circling the neighbourhood
• "What time is checkout, and can I do it later?" — asked at breakfast on the last day, not at the Wi-Fi moment

None of these would come up if the information had arrived earlier. The host who shares a guide link in the booking confirmation doesn't see those messages. The host who delivers the information at check-in — even through a clever Wi-Fi portal — gets them anyway.

The logic isn't complicated: guests ask questions when they don't have the information. Information that arrives before the question forms prevents the question. Information that arrives after the question is asked is customer service. Both have value, but only one reduces the inbox.

What the guide contains — and what stays restricted

Not all information is the same. Some of it is public by nature: the neighbourhood, local tips, general timings, the style of the property. Some is tied to the specific stay: operational details, practical pointers to get oriented, useful references during the stay. And some is sensitive: restricted arrival instructions, access references, personal data, Wi-Fi information appropriate to the type of guide and the session.

A good guest-guide architecture keeps these three layers separate:

• Public guide: general, non-sensitive information accessible to anyone
• Personal Stay Hub: stay-related information, accessible to the guest of the booking
• Sensitive data: shared only when the context allows it — verified session, correct plan, and open time window

A Wi-Fi portal that shows everything in the clear to anyone who connects doesn't respect that distinction. A public guide that pretends to personalize the experience without a linked stay doesn't either. These are boundaries worth keeping clear.

When each part actually matters

A digital guide that treats everything as equally urgent gets ignored. The mental model that works is thinking about when each piece of information becomes relevant to the guest.

Before arrival (from confirmation to the day before): indicative check-in time, how to reach the property, parking and arrival-area pointers, pet policy, early check-in options, allowed arrival instructions according to the property's access type. This is the information that prevents day-of stress. It needs to reach the guest early enough to let them plan.

On arrival (first moments in the property): practical pointers for using the place, how the lights and appliances work, anything unusual that needs an immediate explanation. Here an in-property entry point — a QR on the fridge, a card — works well as a reminder.

During the stay: tips on local restaurants, what to do, markets, transport, nearby events. Guests absorb this content when they're relaxed and planning the day, not while they're still settling in.

Before checkout: checkout procedure, where to leave the keys, whether they can leave luggage, how to leave a review. It needs to reach the guest the evening before checkout, not the morning of it.

The guide can foreground different content depending on the moment of the stay: arrival, stay, checkout. It isn't magic — it's simply stopping to treat the guide as a single PDF and starting to think of it as a page that changes over time.

The persistent-link problem

One reason hosts gravitate toward in-property solutions (Wi-Fi portals, printed booklets, QR codes on the fridge) is that they feel reliable. The guest is there. The information is there. Connection established.

But in-property information has a hidden flaw: it only works while the guest is in the property. The restaurant question comes up while they're out walking. The late checkout request comes up while they're still in bed. The parking question comes up while they're still driving.

A link guests carry on their phone — received earlier, saved in their emails, accessible anywhere — covers all those moments. The guest doesn't have to remember a QR or come back to the property to check. They open the link from the phone, standing on a corner deciding where to have lunch.

That's the structural advantage of a web guide over any in-property delivery method: the guest carries it with them. It travels with them. It doesn't require being in a specific place to access it.

A Wi-Fi captive portal: plan B, not strategy

A Wi-Fi captive portal can be useful — it's a second re-entry point for guests who lost the link, or a way to remind them the guide exists. But it requires hardware and configuration, and it shouldn't become a dependency. A QR on-site or a link shared earlier is often enough as a re-entry point, without needing a custom login page.

The Wi-Fi portal has its place. But the guest who already has the link on their phone and knows what's in it doesn't need the portal to be smart — they need the connection to be fast and stable. The portal becomes what it should be: a quick way back to something the guest already knows they have.

Where it fits in StayFast

With Fast, StayFast can create a personal Stay Hub for the stay: a link accessible without an app, designed to accompany the guest before, during and at the end of the stay. It's a dedicated view, separate from the property's public guide — which stays accessible to anyone arriving via the QR or public link.

That link can be shared in pre-arrival messages or in the booking confirmation, so the guest receives it while they're still in planning mode. By the time they arrive and connect to the Wi-Fi, they've probably already opened it at least once.

The guide can foreground different content depending on the moment of the stay: arrival information and planning surface before the trip; local tips and available Extras come forward during the stay; checkout reminders appear the evening before departure. The guest doesn't get everything at once — they get what's relevant now.

The Wi-Fi moment, in this system, is a natural re-entry point. A QR in the property can point to the same guide the guest already has. The connection feels familiar instead of new. And if the guest lost the link — it happens — the QR gives them a second path to the same place.

Where to actually start

If you want to move the guide from "thing guests find when they arrive" to "thing guests already have before they need it", the steps are direct:

• Create a single link for your guide — not a PDF, not a printed page, but a URL you can send and update
• Share it in pre-arrival messages or in the confirmation, while the guest is still in planning mode
• Put the most useful arrival information first: how to reach the property, practical pointers to get oriented, restricted stay details when the context allows it
• Add a QR in the property as a redundant access point, not a primary one — think of it as plan B, not strategy

The Wi-Fi moment doesn't get wasted because hosts are careless. It gets wasted because the opportunity it represents — a guest with a phone in their hand, ready to receive information — is structurally late. Move the information earlier, and the Wi-Fi connection becomes what it should be: the confirmation that the guest is settled, not the first time they see your guide.

The rule that avoids most mistakes

Before building a Wi-Fi portal, a check-in kiosk, or any other in-property distribution mechanism, ask this question: what would have to be true for a guest to arrive already knowing what I'm about to show them?

Usually the answer is: they should have received it earlier, in a format they carry with them. It's not a technology problem — it's a timing problem. And timing problems get solved by changing when you send things, not by building smarter ways to deliver information at the wrong moment.

Conclusion

The Wi-Fi moment is real. It's a touchpoint, a moment of attention, a natural beat. And it's still late. The guest connecting to your Wi-Fi is already inside, already past the moments where information about arrival, parking and orientation would have been most useful.

The guest guide that does its job is with the guest from the booking confirmation. It's on their phone. They've opened it once. When they connect to the Wi-Fi, they don't need the portal to tell them things — they need the connection to be fast and stable.

Build the portal if you want. But send the guide first.