The Hotel Arrival Page: 5 Do’s and 5 Don’ts.

The QR arrival page is one of the cheapest pieces of digital infrastructure a boutique hotel runs and one of the most disproportionately impression-shaping. A guest scans the QR card in their room within minutes of arrival, and what loads on their phone in the next two seconds shapes their picture of the entire property, often more than the lobby they just walked through.

Most boutique arrival pages are built once, never revisited, and quietly drift out of date over the next 18 months. Here is the small set of design and content rules that keep the page actively earning its keep, and the common mistakes that quietly undo the work.

Do: open to the hotel’s palette

The first half-second of the page load decides whether the guest registers the property as “put together” or “generic.” The page that opens to the hotel’s actual brand colors, with the wordmark in the right place, in the right typeface, reads as deliberate. The page that opens to a template-vendor’s default skin reads as outsourced.

This is the cheapest move on the list and the one most boutiques get wrong. The fix is one afternoon of design work, done once. The compounding payoff lasts as long as the page does.

Do: put the Wi-Fi password one tap away

Wi-Fi is the single highest-utility information on the arrival page. The page should show the network name and password above the fold, with a one-tap “copy password” button. The guest is connecting to the Wi-Fi in the next 60 seconds; everything else can wait.

For the structural side of how the Wi-Fi gets set up in the first place, see hotel guest Wi-Fi, the right way in 2026.

Do: show dining hours that reflect today

The restaurant hours on the arrival page should be the actual hours for this day of the week, not a generic “Mon–Sun 7am–10pm” range. If the kitchen closes at 9 on Tuesdays, the page should show 9 on Tuesdays. The difference matters less for accuracy and more for what it signals: this is a property that updates its own information.

The mechanism is simple: the dining hours live in the same source of truth as the menus, and the page reads from it. Updating once updates everywhere.

Do: include a short neighborhood guide

The neighborhood guide is the highest-leverage section of the page for differentiating a boutique from a chain. Five to seven places, restaurants, coffee, one cultural thing, one walk, with the property’s recommendation in one sentence each. Specific. Not “a great cafe nearby”; “Padaria de Belém, 8 minutes on foot, the pastéis de nata that you actually came for.”

The guide should be reviewed quarterly. Restaurants close. Coffee shops change owners. A neighborhood guide that recommends a restaurant that has been closed for eight months is one of the more damaging cues a guest can encounter on this page; it advertises that nobody has looked at the page since 2022.

Do: keep it readable on the phone they were already holding

Every design decision on the arrival page should assume the guest is reading it on a phone they were already using. This means:

• Text size large enough to read without zooming. Roughly 16px minimum body text.
• Adequate contrast, black on white or near-black on near-white, not light gray on white.
• Tap targets large enough to hit without precision. 44px minimum on phone scale.
• No carousels that auto-advance. The guest is scanning, not waiting.

Don’t: gate it behind an account

The single most common arrival-page mistake is asking the guest to log in or create an account before showing them the Wi-Fi password. This converts at roughly zero percent and signals “we care about capturing your data more than serving you.” The information on the arrival page is not sensitive; no login should be required.

If you absolutely need to collect something from the guest during their stay, ask after they have already gotten value from the page, never before.

Don’t: embed a third-party widget you cannot brand

Almost every boutique we have seen has at some point embedded a third-party booking widget, a weather widget, or a “concierge chat” widget on the arrival page. Two of those almost always read as generic; the third (weather) is information the phone already has.

The rule of thumb: every visible element on the page should belong to the brand. If it does not, it is making the page feel less like the hotel’s and more like a template. The hotel did not pay for the lobby floor so it could put a vendor’s logo on it.

Don’t: bury the page behind a captive portal

Some properties try to gate the arrival page behind the same captive portal that gates the Wi-Fi. The effect is that the guest cannot read the page until they have already connected to the Wi-Fi, which they cannot do until they have read the page. This loops every guest for the first 90 seconds of the stay and is one of the more avoidable self-inflicted wounds in the catalog. The arrival page lives on the open internet; the Wi-Fi connects on the first tap.

Don’t: scatter the source of truth

The arrival page should read from the same source of truth that powers the rest of the property’s information surface. The Wi-Fi password on the page should be the same one in the IT hub. The dining hours on the page should be the same ones on the lobby screen. The menu items on the page should be the same ones on the printable in-room card.

When the source of truth is scattered, when the page is edited in one tool, the IT hub in another, the signage in a third, the property’s information surface drifts apart over months. A guest who reads 9pm dinner service on the arrival page and arrives at the restaurant at 8:55 to find it closed has had a worse experience than if you had never put the hours on the page in the first place.

Don’t: forget to update it

The cheapest digital decay in hospitality. The arrival page launched fresh, then nothing changed, and 12 months later the “current promotions” are from last Easter. The page should be reviewed monthly, a 10 minute walk-through with the GM, with anything stale being either updated or removed.

Step 10 of the broader modernization guide, the monthly tech walk, is where this review belongs. See the field guide for the wider walk.

What to actually put on the page

Pulling the do’s and don’ts together, a strong boutique arrival page in 2026 has, in roughly this order:

1. Hotel wordmark and a short welcome line.
2. Wi-Fi name and password with a one-tap copy.
3. Today’s dining hours (breakfast, restaurant, bar).
4. Room service menu with photos and prices.
5. Amenity hours (spa, gym, pool).
6. The short neighborhood guide.
7. A single contact path (text or call the front desk).
8. A printable in-room card link, generated from the same content.

Eight blocks. Nothing else. The temptation to add a loyalty signup, a survey, an upsell widget, a social feed, resist it. The arrival page does one job exceptionally well, and that job is to make the first ten minutes of the stay frictionless. Every additional element competes with that job.