Most articles on the common guest questions Airbnb hosts receive sort them by theme. Access, wifi, parking and heating make easy headings. They do not help you decide what to do next. The useful split is by hour: what arrives in the morning should usually have been prevented, what arrives late at night has to be handled.
- Sort by hourThe same question means different things at different times
- Morning slotDoor code, early check-in and time confirmation are sequence issues
- Night slotBreakdowns and locked doors are not prevented by a template
Why sorting by hour works
A thematic list tells you what the guest is asking about. It does not tell you whether the answer belongs in a scheduled message, in the house manual or in a live reply.
Take an access question. At 10 am on arrival day, it usually means the check-in sequence did not land early enough or clearly enough. At 10 pm, it usually means the guest is already at the property and something has gone wrong. Same theme, different operation.
Here is the real shape of that day, measured on a three-property portfolio.
Guest messages received, by local hour
The highest point of the day is 8 pm. Roughly one message in two lands outside the 9 am to 7 pm window. The thread only really stops between 2 am and 5 am.
461 guest messages received by a host running three properties, measured in our database over eight months ·Two things read off that curve. The evening peak falls after office hours, when guests arrive and discover the property. The night gap is real but short: it lasts three hours, not eight.
Sorting by theme produces folders. Sorting by hour produces a decision: prevent, answer or escalate.
The send side and the reply side sit in the same thread. Three system messages exist per booking, and you can add as many custom messages as you want per property, placed from thirty days before to thirty days after arrival or departure. Each scheduled message goes out in strict mode, the production default. It can also go out in reinterpret mode, where the resolved template is rewritten at send time in your tone with the property instructions and the thread history. Your template stays the reference version.
Connected to your PMS
For the scheduling mechanics themselves, Airbnb automated messages covers the send side in detail.
Morning 8 am to noon
The cleanest slot to reason about. If a guest asks for the door code, asks whether early check-in is possible or asks you to confirm a time on the morning of arrival, the question is usually preventable. Not because the guest did anything wrong: they are travelling and want certainty. If certainty has not reached them at the right moment, they ask for it.
A good morning send is short. It carries only what the guest needs in the next few hours. Anything else dilutes the message and pushes the essential detail out of view.
Use this send only for facts the guest needs before arrival. Keep local tips, parking detail and house rules out of it unless they are essential for entry.
Morning questions are also where the difference between a fixed template and an adapted send starts to matter. In strict mode the text goes out word for word. In reinterpret mode the same scheduled message can avoid repeating what was already settled yesterday: if the guest confirmed a late arrival, the message does not ask again.
Noon to 5 pm
This slot is less about entry and more about logistics. Address, parking, transport and luggage storage land here because the guest is on the move. Still largely preventable, but not by the same message as the morning.
They are prevented by coherence. If the address sits in one message, the parking note in another and the luggage rule in a PDF the guest will never reopen, the question comes back.
That is where the house manual earns its place. Airbnb's own self check-in guidance treats autonomous arrival as a method and a set of instructions, not just a keypad code. In practice the route to the building, the entry steps and the on-site basics have to be where the guest finds them without effort.
A midday question is therefore not always a messaging problem. Sometimes it is a documentation problem. If you are mapping that side of the stay, Airbnb self check-in is a more useful frame than a library of generic replies.
Evening 5 pm to 9 pm
Evening is where prevention starts to lose ground. The guest is arriving, opening the door, looking for the wifi and testing the heating. Some of these questions are still preventable. Some are not.
If the property instructions are precise, a reply can still be immediate and useful. It draws on the guest's message, the thread history with an explicit instruction not to repeat itself, the booking status and phase, the arrival and departure dates, availability and the property knowledge base built automatically and enriched conversation after conversation.
This slot is only half preventable, because the property decides the rest. A clean set of instructions helps. It does not make locks, batteries and boilers behave.
Night 9 pm to 2 am
At night, the category matters less than the ability to answer fast and to pass the case on. Breakdown, noise complaint and locked door share one operational fact: none could usefully have been solved by a scheduled send. You can reduce some of the night traffic with better daytime instructions. You cannot prevent a failure on site with a prettier template.
This is where the line between answering and inventing matters. Anything outside the known scope comes back to you instead of being guessed, and the context travels with the escalation.
Pick the level the property can support- CopiloteThe safer start while the property is still being documented. The reply is drafted, you send it.
- HybrideAutonomous inside the hours you set, back to you outside them.
- AutopiloteFits a stable property with well-documented routines. The edge case still comes back to you.
What a shared template will never cover
A shared template can standardise wording. It cannot standardise the moment in which the wording lands. That is why so many lists of common guest questions become repetitive: they collect topics and flatten time. Yet time is what decides whether the right tool is a scheduled send, the house manual or a live reply.
| Slot | Typical question | What prevents it | What handles it |
|---|---|---|---|
| 8 am to noon | Door code, early check-in, arrival time | Scheduled arrival send | Short live follow-up in the same thread |
| Noon to 5 pm | Address, parking, transport, luggage | House manual and arrival instructions | Reply that points to the right instruction |
| 5 pm to 9 pm | Access friction, wifi, heating | Better property instructions, partly | Reply based on property knowledge and thread history |
| 9 pm to 2 am | Breakdown, noise, locked door | Very little | Immediate reply, then escalation with context |
If you keep one distinction from this article, keep this one: a question asked early points to a missing send, a question asked late points to a live operational problem. The template is still useful. It is just not the whole job.
