Most Guest App pages fail for the same reason: they try to be a website. A guest opens one on a phone, mid-journey, looking for one thing. A page that answers that one thing quickly is used. A page that lists everything your property offers is closed.
Give every page one job, and name it after that job before you build it.
Pages worth building
The landing page. Where your token points. It should carry whatever the guest is most likely to want at that moment in their stay, plus buttons to everything else. Pre-arrival that is usually check-in; in-stay it is usually services.
Questions and answers. Check-in and check-out times, parking, whether breakfast is included, how to get from the airport. Group them by heading. This is the page that quietly removes the most work from your front desk.
How things work. The wifi, the air conditioning, the television, the coffee machine. Small guides with a photo each, for the things guests ring reception about at eleven at night.
Local recommendations. Places nearby, with opening hours and how to get there. Say what you would actually say if asked at the desk, rather than listing everything within a mile.
Services. Room service, spa, gym hours, the restaurant. Where a guest can request or book something, put the button on this page rather than asking them to call.
An event or offer. A one-off page for a New Year dinner or a seasonal package, with a clear way to respond. These have a natural end date, so decide now who takes it down afterwards.
Feedback. A short form after the stay. Short genuinely matters: every extra question costs you responses.
Contact. Phone, email, address, map. Unglamorous and opened constantly.
Keeping a page usable
Assume a phone, one hand, poor signal. That is where these are read. Test on a phone before you decide a page is finished.
Cut the page in half, then look again. Almost every draft is twice as long as it needs to be.
Label buttons with the action. "Book a table" rather than "More information".
Use your own photographs. A real picture of your lobby earns more trust than a stock image of somebody else's.
Put the most likely action at the top. Nobody scrolls to find what they came for.
Keeping pages current
A Guest App page ages badly and silently. Restaurant hours change, the recommended bar closes, the seasonal offer ends, and nobody notices because nobody is looking at the page except guests.
Give every page an owner. A page nobody owns is out of date within a season.
Diarise a review. Quarterly is enough for most, monthly for anything with hours or prices on it.
Delete rather than leave. An expired offer page still reachable through an old link does more damage than no page.
Edits are live immediately, and the guest link does not change, so correcting something wrong takes a minute. See Create a Guest App page.
What this does not do
Guests will not find pages on their own. There is no menu and no search. Every page is reached from a button or a link you placed.
A page does not replace a conversation. Guests who cannot find an answer will message you, which is why the Unified Inbox still needs watching.
More pages is not better. Each one is something to keep true. Build the ones you will maintain.
What to do next
To build different versions for different guests, see Personalise a Guest App page. To put a page behind a QR code at reception, see Static page links.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.