The answer you know by heart — but never wrote in the guide

You already have the perfect answer. You've given it dozens of times. You type it almost without looking at the screen — and some nights, literally without looking.

"Where's the most convenient parking?" "How does the washing machine work?" "What time is check-out and what do I need to know before I leave?"

The knowledge exists. It's accurate, it's useful, it covers exactly what guests need to know. The problem is that it lives only in your head — and in your WhatsApp, every time, from scratch.

This isn't a time-management problem. It's a translation problem. The gap between what you know about your property and what guests can find on their own is where most of the friction in hospitality lives.

Why hosts don't write things down (even when they promise themselves they will)

It's not laziness. Most hosts have thought at least once about creating a real guide — maybe they've even started. A Word document. A PDF. A printed sheet left on the table.

What usually happens is that the guide gets created once, at the beginning, and then stops being updated. The restaurant that closed stays on the list. The new parking rule doesn't get in. The check-out instructions change, but the PDF doesn't. Eventually the guide contains wrong information, so it stops being sent, and the answers go back to WhatsApp.

The other reason things don't get written: they seem obvious. Hosts spend so much time in their own property that they forget guests arrive from a completely different place. The free parking that "everyone knows is past the traffic light" — guests don't know. The shortcut to the sea that "takes five minutes" — guests don't know which direction to walk. What feels self-evident to you is genuinely invisible to someone who has never been there.

There's a useful concept for framing this: the difference between tacit and explicit knowledge. Tacit knowledge is what you carry without knowing you carry it. Explicit knowledge is the same thing, written down so someone else can use it.

Your property is full of tacit knowledge. Your guests need explicit knowledge.

Recurring questions are the ones that matter most

Repetition itself is useful data. If you've answered the same question twenty times, it belongs in the guide. If you've never been asked it, probably not.

The most frequent categories, the ones that actually land in hosts' inboxes:

**Arrival and access.** Where exactly is the property? (The full address isn't enough — GPS sometimes leads to the wrong side of the building.) How does arrival work? Where to find access instructions when they're available? What steps does the guest need to follow in the first minutes?

**Appliances and systems.** The washing machine. The induction hob. The shower pressure. The air-conditioning remote. The boiler. Things that aren't complicated but aren't obvious either — and the manual isn't what guests want to read.

**Wi-Fi.** Always Wi-Fi. Every single time.

**Check-out.** What time, what needs to be done, where to leave the property, whether anything needs to be sorted before leaving.

**Local orientation.** The nearest supermarket. The pharmacy. Parking. A restaurant that doesn't disappoint. The thing worth knowing about this neighbourhood that the tourist guides don't mention.

There's an important difference between the public guide and information tied to a specific stay. In the general guide you put orientation, appliance instructions and local tips. Sensitive details — like the actual access, codes or Wi-Fi credentials — appear in the verified Stay Hub of each guest, visible only in the context of their stay and protected by plan and session.

These five categories often cover most of the questions that land in inboxes. If they all have a clear answer in a guide that guests find before needing to ask, most of the message volume disappears.

To dig into why this layer of guest communication is systematically put last, even by hosts who are highly organised about everything else, there's an article on why hosts buy the PMS first but keep losing time on guest communication — it covers exactly this pattern and what changes when it's addressed.

Timing matters as much as content

A well-written guide that arrives at the wrong moment still doesn't work. The moment guests actually need information shifts during the stay.

Before arrival, they need to know how to get there and how to orient themselves. They're often building the itinerary in their head, double-checking logistics. A message two days before check-in with the link to the guide and the general arrival instructions lands exactly when they're thinking about it.

On arrival, they need the practical layer: how things work in the apartment, where to find what they need. At this point they're in a new space, trying to settle in. A QR code on the door or a link in the welcome message that opens right away beats a PDF attachment they have to find, download and zoom into.

During the stay, they need local context — restaurants, activities, transport, up-to-date information about the area. This is the part of the guide they'll come back to, not the arrival instructions.

For the guide to replace the back-and-forth on WhatsApp, it has to be the right information, at the right moment, in a format that opens on the phone without friction.

The writing problem most hosts run into

Even hosts who sit down to write the guide get stuck. Not because the information isn't there, but because writing a guide feels like writing — and writing feels like work.

A more useful frame: you're not writing a document. You're answering the questions you always get asked, in order, one time.

Start with the five most frequent questions. Write the answer you'd give if a guest asked you on the phone — informal, direct, useful. Don't correct the tone. Don't try to make it professional. The answer that sounds like you is the most useful answer, because it's the most accurate.

Once those are written, add one thing: the local knowledge guests always appreciate when you mention it. The shortcut. The bar that doesn't show up on Google. The thing that makes the stay slightly better than expected.

That's a guide. It doesn't have to be complete on day one.

How it works in StayFast

StayFast is built on the idea that the guide should reach guests before they need to ask — not after. The Stay Hub is a personal link for each booking: it opens on any phone, no app, and contains everything the host has configured for that stay.

With the Fast layer, you build the guide once — practical info, local tips, appliance instructions, a map with your recommendations — and it becomes the link you send before arrival. Guests arrive knowing where to go, how to orient themselves, what to do with the washing machine. The questions that usually land on WhatsApp at 9pm mostly don't land at all.

The guide is also alive: if you update it, guests see the update. Did the parking rules change? One edit, and every current guest has the right information. No new PDF, no new message, no new send.

With Boost+, Concierge AI can answer guests using the information you've already confirmed — without you having to be in the loop for every exchange.

The starting point is simpler than it sounds: sit down for an hour, write the answers to the five questions you always get asked, and put them in a place guests can find before they think to ask.

Where to actually start

• Open a blank document. Write the five questions you've answered most often this year.
• Write each answer as if you were talking to a guest on the phone — plain language, no formality.
• Add the local knowledge guests always appreciate.
• Add the general access and check-out instructions.
• Put it in a place guests can open on their phone before arrival.

The guide doesn't have to be perfect to be useful. An imperfect guide guests actually open is worth infinitely more than a perfect one sitting in a folder.

The rule that avoids almost every mistake

Before writing any section of the guide, ask yourself: *if a guest asked me this on the first evening, would I be able to answer right away?*

If yes, it belongs in the guide.

If you'd need to think about it, probably not — or you need to check first.

The guide isn't an exhaustive manual. It's the set of things you already know, made findable.

Conclusion

The knowledge is already there. You've been answering the same questions for months, maybe years. The guide isn't something you need to research — it's something you need to transcribe.

Once it's written, it works every time. Every guest, every booking, every check-in. The same answer, delivered before the question lands.

It's not less personal. It's more reliable.