Automate Check-In Instructions for Direct Bookings 2026

Sending every direct-booking guest a separate email with the gate code, the Wi-Fi password and directions past the turn everyone misses eats into an evening you don't have in July. Set up an automated check-in message that fires off your booking confirmation and lands 24-48 hours before arrival, and that job leaves your list for good.

TL;DR

Automate guest check-in instructions for direct bookings by triggering a templated message off booking confirmation, not by hand.
Send full arrival details 24-48 hours before check-in so codes and Wi-Fi passwords are still current.
A Zapier link between your booking form and an email or SMS tool covers most direct-booking setups in 2026.
Keep one master instruction document per property so a changed lock code updates everywhere at once.
Build a manual fallback for same-day bookings that land inside the automation window.

Why this matters

Guests who book directly with you, rather than through Airbnb or Booking.com, still expect the polish those platforms trained them on: instant confirmation, then arrival details without having to chase you. If you're running two or three self-catering places across Louth, Meath or down towards the Mournes, handling that manually for every booking is where things slip. The wrong code goes to the wrong cottage. Nobody follows up until the guest is already standing at a locked door at half nine on a Friday night.

Automation removes that risk without removing you from the conversation. It handles the routine part — the same eight pieces of information every single guest needs — so your attention goes to the things that actually need a person.

Direct booking is only worth the effort if the experience feels handled. Sos Stays lists self-catering homes and guest houses across the Boyne Valley, Louth, Meath and the Mourne and Wexford coasts on exactly that basis, and automated check-in messaging is one of the cheapest ways to close the gap between a direct booking and a platform booking in 2026.

Before you start

Gate everything here, because a missing piece at step four means starting over.

A booking form or booking system that captures the guest's email address at the point of reservation. No captured email means no trigger, and no trigger means no workflow. If you currently take bookings by phone or DM, that's the first thing to fix.
An email or SMS sending tool connected to that booking system. Plenty of booking platforms include messaging natively. Where yours doesn't, a Zapier connection to Mailchimp, Twilio or a plain transactional email service does the same job.
The gotcha that catches nearly everyone: if your check-in details live inside multiple message templates, one lock code change means editing every template separately — and one of them gets missed. Build a single master instruction document per property first, then copy from it. Never type the code straight into five different automations and hope you remember them all next March.

One more practical note before you start building. Decide now whether you're sending by email, SMS or both. Email carries more detail and survives being re-read at the car park; SMS gets opened. Most hosts running this well in 2026 send the full details by email and a two-line SMS on the morning of arrival pointing back to it.

Set up your booking confirmation trigger

This is the event everything else hangs off. Get it wrong and you'll be sending arrival codes to people who never paid.

In your booking software or form tool, find the trigger usually labelled New Booking or Reservation Confirmed.
Set the condition so the trigger fires only on a confirmed booking, not an enquiry and not a pending payment. Look for a field named Booking Status and set it to Confirmed or Paid.
Map three fields from the booking record into the automation: guest email, guest name and arrival date. Everything downstream depends on those three.
If you run more than one property, map the property name too, and add a filter step so each property routes to its own template.
Save the trigger, then put one test booking through your own system using a personal email address.

Expected result: your test booking generates one automation event within a minute or two, visible in the activity log of your automation tool. If nothing fires, the status condition is almost always the culprit.

Configure your check-in message template

In your email or SMS tool, create a new template and name it clearly by property — for example Check-in — Boyne Valley. Vague template names cause the wrong-code problem more often than bad automation logic does.
Insert the merge fields for guest name, arrival date and property address. Click Insert Merge Field or the equivalent in your platform and select each one rather than typing the field name manually.
Copy in the gate code, Wi-Fi network and password, parking arrangement and key safe location from your master instruction document. Not from memory.
Add one honest, specific line about the approach — the turn that's easy to miss coming from the main road, the gate that sticks in wet weather, the fact that the last stretch is a single-track lane. Vague directions generate more questions, not fewer.
Add a check-in window and a line telling guests how to reach a human if something goes wrong. A phone number in the message prevents most of the panicked 11pm emails.
Set the Send Delay or Scheduled Send field so the message queues rather than firing the instant the booking lands.

Expected result: previewing the template against your test booking shows the real guest name, real dates and real property address — not placeholder brackets.

Schedule the send time

Set the delay condition to fire 24-48 hours before the arrival date, using the arrival date field you mapped in the first section.
Add a second conditional branch: bookings made inside that window send immediately instead of waiting on a delay that has already passed. This is the single most common gap in a first-pass setup.
Test both paths. Make one test booking for a fortnight out and one for tomorrow morning, and confirm each behaves differently.
Check the timezone setting on your automation tool. A tool defaulting to UTC will send Irish bookings an hour out through the summer months of 2026, which is harmless but looks sloppy.

Expected result: the fortnight-out booking queues a delayed send with a visible scheduled timestamp; the next-day booking sends within minutes.

Send check-out instructions the same way

The same structure runs in reverse, and building it takes about ten minutes once check-in works.

Duplicate the whole workflow. Change the trigger condition from arrival date to departure date minus one day. Swap the template for check-out details: what time to leave, where the key goes back, bin collection day, and any last request like stripping the beds or leaving the heating off.

Keep it to five lines. Check-out messages get skim-read at best, and a long one guarantees the important instruction gets missed.

Expected result: a test booking generates two scheduled messages — one before arrival, one the evening before departure — from a single confirmed booking.

Troubleshooting

The guest says the email never arrived. Check spam first. Transactional email from a new sending domain routinely lands there for the first few sends. Adding SPF and DKIM records with your email provider fixes it permanently and takes about twenty minutes.
A same-day booking got no instructions at all. Your conditional branch isn't catching bookings inside the 24-48 hour window. Re-test with a booking dated tomorrow before you trust it in a busy week.
Merge fields render blank instead of the guest's name. The field name in your booking form doesn't exactly match the one mapped in the automation. Field names are case-sensitive in most platforms, so Guest_Name and guest_name are two different things.
The guest changes arrival time on the day. No automation catches this. Keep a short manual text template saved on your phone for same-day amendments — the workflow handles the routine, you handle the exceptions.
Two names on one booking, two email addresses. Decide upfront whether both people get the message or only the lead booker. Most tools map the primary contact only, by default, and the second guest ends up with nothing.

Customize your workflow

Once check-in and check-out run themselves, the same trigger extends in both directions without new software.

A short mid-stay message on day two — one line asking whether everything's alright — catches problems while you can still fix them, rather than reading about them in a review. A review request sent the day after check-out, while the break is still fresh, converts far better than one sent a week later.

A pre-arrival message a week out is worth adding too, with the practical things guests actually ask about: nearest shop, whether there's a decent walk from the door, what to do if it rains for three days. That one does more for a direct booking than any confirmation email, because it's the part a platform never sends.

If you're managing several properties and the manual side is still eating your week in 2026 — messaging, changeovers, the constant small decisions — that's the gap a commission-based management arrangement is built to close, rather than a bigger spreadsheet and a later bedtime.

See how direct booking looks in practice

Browse the self-catering homes Sos Stays lists across Louth, Meath, the Boyne Valley and the Mournes.

**Explore Sos Stays**

One last thing

The step almost everyone skips is the master instruction document — the single file every template copies from. Skip it and the day a lock code changes, you're hunting through four templates trying to work out which one still carries the old one. Build that document first, before you touch a single automation setting, and every message that goes out for the rest of 2026 stays honest without you checking it.