Airbnb Scheduled Messages: A Complete Guide for Hosts

Airbnb's scheduled messages are the closest thing hosting has to free staff. Built directly into the platform, they send your key messages automatically — triggered by bookings, check-ins and checkouts, personalised with each guest's name and dates — so every guest gets timely, consistent communication whether you're at your desk or on a beach. Hosts who set them up properly reclaim hours a month and, more importantly, stop being the single point of failure in their own communication.

This guide covers how the feature works, the exact schedule that serves most listings, the templates to load in, the limitations worth knowing and the companion tools that fill the gaps.

How scheduled messages work

Scheduled messages live in your Airbnb hosting inbox (Menu → Scheduled messages on the host dashboard). Each one is a saved template attached to a trigger event and an offset:

• Booking confirmed — send immediately or a set time after booking.
• Check-in — send a chosen number of days before or after check-in day, at a time you pick.
• Checkout — likewise, relative to checkout day.

Templates support shortcodes — placeholders Airbnb fills per guest, including guest first name, check-in/checkout dates and times, listing name and address, and confirmation code. Write the message once with shortcodes, and every guest receives a personalised version at the right moment for their stay. Messages apply per listing, so multi-listing hosts configure once per property (or duplicate across them).

The schedule that works

Five scheduled messages cover the backbone of great guest communication:

Morning sends for logistics (guests plan their day early), early-evening for the checkout note (last evening, still actionable). The welcome message and review request are better sent manually — the first because arrival times vary, the second because one size doesn't fit bumpy stays.

Templates built for scheduling

The art of a scheduled template is writing one message that fits every guest. Two rules achieve it: keep stay-specific facts to what shortcodes can fill, and point everything else at your guest guide link — which is identical for every guest and always current. Examples (replace bracketed items with your details or Airbnb's shortcode equivalents):

Confirmation: "Hi [guest name], thanks so much for booking [listing name] — we're looking forward to hosting you from [check-in date]! Everything about the stay — directions, house details, our local favourites — is in your guest guide: [link]. I'll message closer to arrival with check-in specifics. Any questions before then, I'm right here."

Pre-arrival: "Hi [guest name], your stay is three days away! Check-in opens at [check-in time] on [check-in date]. Arrival steps, parking and entrance photos are in your guide: [link]. What's your rough arrival time?"

Check-in day: "Morning [guest name] — today's the day! [Listing name] is ready from [check-in time]. Your full entry instructions are in the guide: [link]. Wi-Fi's in there too, one tap to copy. Message me any time — otherwise, enjoy!"

Checkout eve: "Hi [guest name], it's been a pleasure! A reminder that checkout tomorrow is by [checkout time] — keys [instruction], and the guide's checkout section has the (very short) list: [link]. Enjoy your last evening!"

Thank-you: "Hi [guest name], thank you for staying with us — it was a pleasure hosting you! Hope the journey home is smooth, and you'd be welcome back any time."

Limitations worth knowing

Scheduled messages are excellent and bounded, and knowing the bounds prevents surprises. They are Airbnb-only — direct bookings and other channels need their own automation, whether that's a PMS, a dedicated messaging tool, or your own email flow. Conditional logic is minimal — you cannot branch on "guest hasn't replied" or "arrival after 9pm"; edge cases stay manual, which is fine because edge cases should be human. Rotating door codes need care — if codes change per stay, keep the code out of scheduled templates (send it manually) or use a smart-lock integration; the scheduled message safely carries everything around the code via the guide. And scheduled messages don't answer inbound questions — that's what quick replies are for.

One honest caution: automation amplifies whatever you feed it. A stale template mis-sends at scale. Review your five templates quarterly — or better, keep facts out of templates entirely and in the guide, where one edit fixes every future send.

The scheduled message + guest guide system

Every template above leans on the guide link because scheduled messages and guest guides are two halves of one automation. The messages automate timing — the right nudge at the right moment. The guide automates knowledge — arrival steps with photos, tap-to-copy Wi-Fi, live local recommendations, checkout details, all searchable and always current. Hosts who automate only the messages end up with beautifully timed walls of text; hosts who pair them get three-line messages and guests who self-serve. The guide half is free to build: create yours with WelcomeFlo and paste one link into all five templates.

Setting yours up: a 30-minute checklist

1. Write or copy the five templates above; personalise your property's brackets.
2. Add your guest guide link to each (get one free if needed).
3. In Airbnb: Scheduled messages → create each message, attach trigger, offset and send time from the table.
4. Insert shortcodes for name, dates and times wherever facts appear.
5. Book a test stay window in your head and re-read each message as that guest: right info, right day?
6. Turn them on, then handle replies personally — that's the half automation can't do.

Multi-listing setups: keeping templates in sync

Scheduled messages configure per listing, which at portfolio scale creates a quiet maintenance problem: improve your check-in template's wording and you have N copies to update. Two structures keep it manageable.

Write templates property-agnostically. Draft the master versions so that everything property-specific is either a shortcode (name, dates, times — Airbnb fills these per listing automatically) or lives behind the guide link. A template containing zero hard-coded facts is a template you can paste identically into every listing — and improve everywhere by re-pasting once a season.

Let the guide absorb the differences. Parking quirks, entrance steps, bin days — everything that differs between properties belongs in each property's guide, not its message templates. This is where WelcomeFlo's Content Library compounds the effect: shared content (policies, area guides, house-rule framing) is written once across all properties' guides, while each guide keeps its scoped specifics. The result is a two-layer system — identical message templates, per-property guides — where a wording improvement touches N listings via paste, and a content change touches them via one edit.

The test of a good multi-listing setup: onboarding a new property should mean pasting five templates, linking its guide, and done — under fifteen minutes. If it takes an afternoon, facts have leaked into your templates.

The bottom line

Five templates, five triggers, one guide link, thirty minutes of setup — and your communication runs on rails you built once. Start with the table above, copy the templates, and give them a guide worth linking: create your free WelcomeFlo guest guide.