Before you schedule a guest message: four checks to run

Product disclosure: This guide is published by the maker of the paid Host Automation Kit. The checklist below is free to use. The examples contain fictional property details.

A reusable guest message can still contain the wrong Wi-Fi name, an unfinished placeholder, or instructions meant for another property. Before you schedule a message, test the text that the guest will actually receive. You can do this with a plain text file and a small checklist; buying a tool is optional.

For this walkthrough, we ran the local template filler included in our Host Automation Kit. It reads the templates and substitutes the property details you supply. It does not connect to a booking account or send messages. The distinction matters: preparing a message and delivering it to the right guest are separate jobs.

1. Test the property details with fictional values

Start with a copy of your draft. Use obviously fictional values so the test cannot be confused with a real arrival message. We supplied DEMO_WIFI as the network name, EXAMPLE_ONLY as the password, and Demo Host as the host name. The pre-arrival template produced this excerpt:

WIFI
Network: DEMO_WIFI
Password: EXAMPLE_ONLY

The filler substituted those values in the local test. That result proves the text replacement worked for those fields. It does not prove a Wi-Fi network exists, that a password is correct, or that a guest received anything. For a real stay, verify the network and password at the property before replacing the test values.

2. Find every unfinished field

Search the resulting message for [[ and ]]. In our partial test, the door-access and parking instructions remained in brackets because we had not supplied them. That is a useful failure to catch before sending. A template is not ready merely because the Wi-Fi section looks finished.

Also look for fields such as %guest_first_name% and %check_in_date%. In this kit, those are reminder tokens for the booking platform's own personalization fields. They are not proof that an arbitrary pasted token will resolve. Insert the supported fields using the platform's editor and inspect its preview. Airbnb describes its quick-reply and scheduling options in its official quick-reply guide.

3. Separate recurring facts from a particular incident

A network name may be reused while it remains valid. A complaint, a maintenance problem, or a promised update time needs a fresh review. Our house-rules reminder deliberately retains a bracketed description of what happened. The filler does not invent an incident or decide what a guest did.

Keep a note beside each draft identifying what is stable, what changes with the reservation, and what must be written for the current situation. If a message describes noise, damage, a refund, or a service failure, check the actual facts and the wording before sending it. Do not let an old example become an accusation about a new guest.

4. Check the recipient and timing separately

Once the wording is complete, review the reservation, property, time zone, and intended delivery time in the service that will send it. Check whether a late booking, a changed arrival date, or a cancellation needs different handling. These are review scenarios, not claims that this local filler monitors those events.

For multiple properties, keep each property's drafts and details together and label them clearly. Avoid sharing a real door code or guest record in a public demonstration. The examples in this article use fictional inputs and never send a message to a guest.

A free pre-send checklist

• Correct property, guest, reservation dates, and time zone.
• Current access, parking, and Wi-Fi details verified at the property.
• No unfinished brackets or unsupported personalization tokens.
• Incident-specific wording checked against what actually happened.
• Delivery preview and schedule reviewed in the sending service.

Save the checklist with your drafts and use it on the final preview. A useful test result is a specific issue caught, such as a missing parking instruction. Avoid treating a filled template as evidence of time saved or improved guest ratings until you have measured those outcomes.

Where the paid kit fits

The Host Automation Kit includes twelve message templates and local tools, including this filler and a calendar overlap checker. It suits someone who wants editable files and is comfortable running a local Python script. If you need an inbox, automatic guest messaging, or live booking inventory management, this kit alone does not provide those services.

You can watch our original calendar-tool demonstration to see another part of the kit, or use the free checklist above with your existing drafts.

View the Host Automation Kit — listed at $29

Paid product sold by this site's publisher. Check the checkout page for the current price and any applicable tax. This is a local demonstration recorded on September 9, 2026, using fictional data; it is not a customer testimonial or a claim of earnings.

Choose the right tool before buying

If you are comparing templates with a fully hosted service, our free Host Kit buyer guide explains what is included, what requires setup, and what the tools cannot do. It includes English and Korean answers. The checklist above remains free to use.