What your guests actually see
Before you put a link in front of a paying booking, you should know exactly what is on the other side of it. This is the whole guest path, including the parts that are not frictionless.
The first thing a guest touches
One link, or a QR code, for their stay. It opens in whatever browser is already on their phone.
There is no app to download, no account to create, and no password. That is a deliberate tradeoff: an app install is the single largest drop-off point in guest-facing software, and a guest standing outside a locked door at 11pm will not clear an app store to get in. A stay link opens in one tap.
What they can ask, and where the answer comes from
The questions that actually get asked are unglamorous and constant. Wi-Fi. Parking. Check-in and checkout times. Which switch is the porch light. How the coffee machine works. Where to put the trash. Whether the beach is walkable.
Every answer is drawn from the material you loaded and approved for that property, and can cite the source. If your material does not support a confident answer, the question comes to you instead of being invented. Guests are not shown an authoritative-sounding guess.
The honest version of this: the portal is exactly as good as the Property Brain behind it. A thin Brain produces a lot of “let me get the host”. The completeness score exists to stop that from being a surprise, and how it works explains how the retrieval is constrained.
When a guest wants something, not just an answer
Questions are only half of guest messaging. The other half is requests, and those arrive as structured items rather than as a paragraph you have to interpret at 7am.
- Concierge requests. Late checkout, extra towels, a restaurant recommendation. Captured with the detail attached and routed to you.
- Maintenance issues. A guest reports the shower, and it reaches you with the property, the detail, and a priority already on it, instead of the words “the bathroom is broken”.
- Safety and urgency. These do not get answered by the assistant. They route to a human, and guests are directed to local emergency services where that is the correct answer.
The review moment
Review prompts are timed to when a guest is actually willing to leave one, rather than fired the moment the stay ends. A guest who got a straight answer at 11pm on their first night is a materially different reviewer from one who waited until morning for it.
What a guest cannot see
This matters as much as the feature list, and it is enforced at the database rather than only in the interface.
- Your other properties.
- Any other guest, stay, or message.
- Internal notes, or anything you have not approved into the Brain.
- Your pricing, your calendar, or your account.
Guest reads and writes are scoped to one property and one stay. Guest contact identifiers are stored as hashes rather than in the clear. The full posture is on trust and safety.
What this replaces, and what it does not
It replaces the repeat questions and the 6-message thread about parking. It does not replace you. A guest who wants to negotiate an early check-in, or who has a real problem, still ends up talking to a human, just with the context already gathered. The guest communication guide covers which messages are worth automating and which ones you should never hand over.
Set up one property and send yourself the guest link before you send it to anyone else.
Start free