A house manual is hard to judge. You write it once, it looks complete, and the same questions keep arriving. That is almost never a content gap. It is a question of timing and placement, and the two are fixed separately.
- Two documentsThe manual and the instructions do not travel together
- The measurementWhat guests really ask, counted
- The blind spotThe questions no manual can absorb
Two documents, two clocks
Airbnb does not give you one manual. It gives you two documents, stored in two places on the listing and released under two different rules.
The house manual explains how the home works. The Help Centre gives its own examples: how to switch on the water heater, where to find an extra blanket. Only guests with a confirmed reservation can open it.
Check-in and checkout instructions live elsewhere. They cover access first and departure second. Guests receive detailed arrival instructions 48 hours before check-in, while checkout instructions can be read before booking. Those checkout instructions are capped at 140 characters, which is enough to say where to leave the keys and not much else.
| House manual | Check-in instructions | |
|---|---|---|
| What goes in | how the home works | access and departure |
| Who can see it | confirmed reservation | confirmed reservation |
| When | from confirmation | 48 hours before arrival |
| Length | free | checkout capped at 140 characters |
Placement decides the reading date. A door code kept in the manual becomes readable at confirmation, sometimes three months before the stay. The same code placed in the arrival instructions appears 48 hours out. Both choices are defensible, and they do not produce the same messages.
Airbnb also asks you to declare an arrival method from a closed list: smart lock, keypad lock, secure lockbox, building staff, in-person handover or a custom method. That declaration changes what the guest sees before opening the manual at all.
What actually arrives
A manual is almost always written from memory, based on what the host expects to be asked. Here is what really arrives, counted across inbound messages on one portfolio of listings.
Inbound guest messages by theme
- Arrival
- 89 messages
- Access and keys
- 23 messages
- Departure
- 21 messages
- Incident
- 20 messages
- Linen and beds
- 19 messages
- Heating
- 9 messages
- Waste
- 8 messages
- Wifi
- 7 messages
- Parking
- 6 messages
Arrival outweighs every other theme combined. Wifi, which opens nearly every published house manual, lands behind bed linen.
456 guest messages over 180 days ·Two readings follow, and the second one matters more.
First: the manual is written for the wrong half of the stay. The water heater, the extra blanket, the wifi code are questions from a guest already settled in. They exist, and there are few of them. What saturates the inbox happens before the door opens.
Second: of those 456 messages, 300 touch none of the themes a manual covers. Among them, 155 are thanks or acknowledgements, and only 35 carry a question. A large share of the traffic is not a request for information at all. It is conversation, and a document does not replace it.
The questions that slip through
They share one manufacturing defect: the answer depends on something other than the property. No static document can handle them, however long it gets.
| The question | What the answer depends on |
|---|---|
| "Can I arrive at 2pm?" | the previous reservation's checkout |
| "Could you hold our bags?" | who is on site that day |
| "What time does cleaning come?" | somebody else's schedule |
| "My train is late, is that alright?" | the actual hour, not the rule |
| "The code does not work" | the state of the hardware right now |
| "It is cold, how do we turn it up?" | the model installed in THIS home |
| "Can we leave later?" | the next arrival |
| "Where exactly is the parking?" | which space is actually free |
| "Do you have a cot?" | stock, not the listing |
| "Which bin is for glass?" | the local collection day |
| "There is no hot water" | an incident, not a manual |
| "We are two more, is that fine?" | a decision from the host |
Six of those twelve arrive before check-in, so before the guest has opened anything. Three depend on a reservation that is not theirs. Two are incidents. Exactly one, the heating control, genuinely calls for a line in the manual.
The test before adding a line: would the answer be identical in six months, for any guest? If yes, the manual is the right place. If not, it is an answer to give, not a note to write.
Writing the manual as a knowledge base
A useful manual is not a longer document. It is a list of stable facts, each attached to the property it belongs to, and searchable at the moment the question lands.
- Separate what is stable from what depends on a date. The boiler model is stable, the earliest possible check-in never is.
- Write one fact per line, naming the object exactly. "The round thermostat by the front door" beats a paragraph about heating.
- Put access in the check-in instructions rather than the manual, unless you want it readable from confirmation.
- Write checkout instructions in under 140 characters, since that is the cap. A truncated instruction is not half read, it is not read.
- Take your last twenty messages and check which ones the manual would have prevented. That is the only measurement that counts.
What is left once the manual is done
A complete manual does not remove messaging. It changes its composition. What remains are the questions whose answer depends on a state, and they land at the hours nobody wants to answer.
Three ways to handle what remains- CopiloteSentioo drafts the reply from the property's own facts, you read it before it goes. Useful while you check that the base tells the truth.
- HybrideQuestions with a stable answer go out on their own, anything that commits money or a decision comes back to you.
- AutopiloteSentioo answers directly on covered topics, and alerts you the moment a request falls outside them.
The difference with a manual fits in one sentence: a manual waits to be opened, a knowledge base is queried when the question arrives. The content can be identical. The outcome is not.
