Airbnb Check In Instructions That Actually Get Read
In Q1 2026, a guest texted me at 10:47 PM asking where the door code was. I had sent the code three separate times — at booking, in the 72-hour reminder, and in the day-of message. All three had the code in plain text. They hadn't read any of them.
That's not a guest problem. That's a formatting problem.
After running 12 properties across Austin, Columbus GA, and the Smokies, I've rebuilt my check-in instruction system twice. Here's what actually works — the templates, the timing, and the setup that cut my "where's the door code?" texts from about 8 per month down to 1.
What Check-In Instructions Actually Are
Airbnb gives you two places to put check-in information: the listing's Arrival Guide (under Guest Resources in your hosting dashboard) and your pre-arrival message templates. Most hosts fill out one and ignore the other. You need both, and they serve different jobs.
The Arrival Guide is persistent — guests can pull it up anytime in the Airbnb app, even offline. Your messages are transient — they land in the inbox and get buried under booking updates and payment receipts. Use the Arrival Guide for access details and property basics. Use messages to surface the most critical arrival info and link back to the guide for the rest.
Airbnb also lets you attach a House Manual with up to 4,000 characters. Most hosts write a wall of text. Guests read the first paragraph and stop.
Why This Actually Matters
Each "where's the door code?" text costs roughly 4 minutes — reading, context-switching, finding the reservation, typing a reply. At 8 of those a month across my properties, that's 32 minutes of reactive support every month. Add "what's the wifi?" and "where do I park?" and you're at 90 minutes of monthly messages that good instructions prevent entirely.
The bigger problem is reviews. In June 2025, I had a guest who couldn't get into a property with a Yale Assure 2 lock. The code was correct. I hadn't mentioned that the front door requires a firm push-then-pull to seat the bolt before the code accepts. Guest panicked, messaged me, I resolved it in 10 minutes via text. They still wrote "confusing entry" in the review. At my ADR of $147/night, that one phrase probably cost me 30 or more future bookings over the following year.
The fix was four words added to my check-in instructions: "firm push, then pull."
How to Write Instructions That Get Read
This is information architecture, not creative writing. Follow this structure.
- Lead with access, not welcome. The first question a guest has when standing at your door is not "what are the house rules?" It's "how do I get in?" Start there — door code, parking spot, building entry method.
- Use numbered steps for the entry sequence. "Press any key to wake the pad, enter the code, push door firmly" beats a paragraph every time. Three steps maximum. If your entry honestly requires six steps, simplify the hardware.
- Bold the door code on its own line. Make it impossible to miss. When a guest is squinting at a phone at midnight in a dark driveway, bold text on its own line is the difference between a successful check-in and a support call.
- One paragraph per topic. WiFi gets its own paragraph. Parking gets its own. Checkout gets its own. Never bundle them.
- Attach a photo of the lock keypad. This alone cut my entry-confusion messages by about 60%. A Yale Assure 2 keypad looks different from a Schlage Encode Plus. Show guests what they're looking for before they leave home.
- Give them a direct contact for emergencies. "If anything goes wrong, message me here and I'll respond within 10 minutes." This prevents the panic spiral that turns minor friction into a 3-star review.
- End with one hospitality line. One specific thing: "Coffee and tea are in the cabinet above the coffee maker — help yourself." Not three paragraphs of excitement. One useful, warm, specific note.
The 3-Message Timing Sequence
Three messages. Not one, not five.
- 24–48 hours after booking: Short confirmation. Confirms dates and check-in time, tells them full access details are coming 72 hours before arrival. Builds trust without overwhelming them six weeks before they need the information.
- 72 hours before check-in: The full access message. Door code in bold on its own line. Parking. WiFi. Entry steps numbered. Photo of the lock keypad. Link to the Arrival Guide. This is the message that does the real work.
- Day of check-in (by 10 AM): Short reminder. Recap the code in bold. One hospitality note. Invite them to ask anything before they leave home.
Get the 72-hour message right first. Day-of is a safety net. Booking confirmation is relationship-building. In that order of priority.
10 Ready-to-Copy Check-In Templates
These are the actual templates I use. Replace the bracketed placeholders with your specifics.
Template 1 — Booking Confirmation
Hi {guest_name}, thanks for booking {property_name}! Confirmed for {check_in_date}–{check_out_date}. I'll send your full access details 72 hours before check-in. Questions about the area before then? Just ask.
Template 2 — Full Pre-Arrival (72 hours out)
Hi {guest_name}, you arrive in 3 days. Here's everything you need to get in:
Door code: {door_code}
Entry: {entry_step_1}. {entry_step_2}. {entry_step_3}.
Parking: {parking_details}
WiFi: network "{wifi_name}" / password: {wifi_password}
Check-in is after {check_in_time}. Full house info is in your Airbnb Arrival Guide. Message me here if anything's unclear.
Template 3 — Day-Of Reminder
Good morning, {guest_name}. Reminder: door code is {door_code}. {one_useful_local_tip}. Message me if anything comes up — enjoy your stay.
Template 4 — Late Check-In (after 10 PM)
Hi {guest_name}, heading your way tonight — neighbors are on the quieter side after 9 PM, so keep it low-key on arrival. Door code: {door_code}. Everything's ready for you.
Template 5 — Entry Troubleshooting
Hi {guest_name}, if the code isn't working: (1) press any key to wake the keypad, (2) enter {door_code}, (3) {property_specific_action}. Still stuck? Call me at {phone_number} — I can fix most things remotely in under 5 minutes.
Template 6 — Local Event Warning
Hi {guest_name}, quick heads-up: {local_event} means {traffic_or_parking_note} this weekend. Leave a few extra minutes. Door code: {door_code}. {wifi_line}.
Template 7 — Group or Family Arrival
Hi {guest_name}, excited to have your group. Checklist on arrival: (1) door code {door_code}, (2) parking: {parking_capacity} cars at {parking_location}, (3) {useful_detail_for_group}. Message me if anyone gets stuck.
Template 8 — Mid-Stay Check-In
Hi {guest_name}, just checking in — hope the first night went well. Let me know if anything needs attention.
Template 9 — Pre-Checkout Reminder
Hi {guest_name}, checkout is {check_out_time} tomorrow. Leave {checkout_tasks} and you're all set — no need to strip beds or do dishes. The door locks automatically. Safe travels.
Template 10 — Post-Stay Thank You
Hi {guest_name}, thanks for being a great guest. I've left you a review — if you have a moment, I'd appreciate one in return. You're welcome back anytime.
Common Mistakes That Kill the Check-In Experience
Burying the code in a paragraph. If a guest has to read three sentences to find the door code, you've already failed at the one job these instructions need to do. The code should be identifiable in 2 seconds.
Sending access info at booking. A 600-word message sent 45 days early won't be remembered on arrival day. People don't save booking confirmations in long-term memory. Send the code 72 hours before check-in, not the day they book.
Assuming one channel is enough. Some guests never open the Airbnb app. Others only use it, never the message thread. Cover both — the pre-arrival message and the Arrival Guide should each stand alone.
Generic troubleshooting language. "Try the code again" is useless. "Wake the keypad first by pressing any key, enter the code, then turn the handle immediately before the green light fades" is actionable. Your Schlage Encode Plus has specific behavior. Document it.
No photo of the entry. One clear photo of your lock keypad, attached to the 72-hour message, does more work than a paragraph of description. Guests know what they're looking for before they arrive.
Smart Lock Setup for Better Check-Ins
Physical keys and lockboxes create the largest single category of check-in friction. A good Airbnb smart lock generates unique per-guest codes that expire automatically at checkout — no lockbox to find, no physical handoff, no codes that stay valid after a guest leaves.
I've used the Yale Assure 2 and Schlage Encode Plus across different properties. Both work without a hub and support per-guest codes with expiration times. The Yale has one quirk worth noting in your check-in instructions: the keypad goes to sleep after 30 seconds of inactivity. Guests need to press any key to wake it before entering the code. Skip that detail and every single guest will enter the code, get no response, and text you. Add one sentence and the problem disappears for good.
For the Nest 3rd-gen thermostat I have at two properties, guests always ask. I include one line in the check-in message: "Thermostat is pre-set. Outer ring adjusts temperature; hold to lock in." That one line saves me around 15 minutes of thermostat questions per month.
Automating the Sequence
Writing perfect templates is half the job. Not forgetting to schedule them across every reservation is the other half. The BiggerPockets STR forum is full of hosts who hit 3+ properties and moved to dedicated Airbnb messaging software to handle the sequencing automatically. Hospitable (starting at $29/month in 2026) handles trigger-based scheduling and is the most focused tool in the STR messaging category. Hostfully (starting at $109/month) adds a polished digital guidebook builder alongside messaging, useful if you want a more branded guest welcome experience.
I run my messaging through Koohost now at $30/month (Pro Host tier). The detail that mattered most to me: the door code shortcode only fires once the code is confirmed on the physical lock — the template never sends a stale or pre-generated code that hasn't been pushed to the device yet. There are 80+ shortcodes covering guest name, property address, check-in and checkout time, WiFi credentials, and more.
Where This System Breaks Down
About 5–10% of guests will text you "where's the code?" regardless of how clear your instructions are. Some will message you four minutes after the bolded 72-hour message landed in their inbox. That's not fixable with better formatting. The goal is eliminating the preventable 90% — not achieving zero support messages. You still need to be available and responsive.
Also worth saying: if you're managing 20+ properties with a team, check-in message automation is necessary but not sufficient. You'll need a platform with owner statements, team access controls, and multi-property calendar management — the kind of tooling that a dedicated Airbnb management platform handles better than a messaging-focused tool does. If you're evaluating the full stack, the Hospitable alternatives page covers the major options with current 2026 pricing.
FAQ
When should I send Airbnb check-in instructions?
Send the full access message — door code, parking, WiFi, and entry steps — 72 hours before check-in. That's close enough to arrival that guests will remember it, but early enough that it's not a surprise when they're standing at your door. Back it up with a shorter day-of reminder that bolds the code again.
What should Airbnb check-in instructions include?
In order of priority: (1) the door code or access method, (2) entry steps as a numbered list, (3) parking, (4) WiFi credentials, (5) check-in time, (6) a troubleshooting note specific to your lock model's behavior, (7) how to reach you if something goes wrong. Everything else — house rules, local tips, amenities — belongs in the Arrival Guide, not the pre-arrival message.
Can I automate Airbnb check-in messages?
Yes. Airbnb has a native scheduled messages feature for basic timing. Third-party tools like Hospitable ($29+/month) or Koohost ($15–30/month) add more trigger types, live lock-code integration, and 80+ shortcodes. The messaging software comparison breaks down the differences if you're evaluating options.
How do I handle guests who never read check-in instructions?
Bold the code. Put it on its own line. Attach a photo of the lock. Send the 72-hour message and a day-of reminder. That sequence reduces entry questions by 80% or more for most hosts. The remaining 5–10% who still text are non-readers regardless of what you do — keep a quick phone macro ready so your reply takes 15 seconds instead of 2 minutes.
What is the best smart lock for Airbnb check-in?
The Yale Assure 2 and Schlage Encode Plus are both solid for STR use — no hub required, per-guest codes with expiration, auto-lock. The main difference: Yale's keypad sleeps after 30 seconds (document this in your instructions), Schlage's stays active longer. Both require a specific note in your check-in instructions about their behavior. The smart lock guide covers setup and exactly what to include for each model.
Do I need separate check-in instructions for Airbnb vs. VRBO?
The template content is identical across platforms. The delivery timing and UI differ slightly. If you're using a PMS or messaging tool, you write one set of templates and the software handles cross-platform delivery. Managing each OTA manually, copy the same templates and adjust for the platform's character limits and formatting rules.
If you want to test a system that handles the timing, code sync, and template sequencing automatically, try Koohost free for 30 days — no credit card.
Ready to try Koohost? Plans from $15/mo. No credit card to start.
Start free 30-day trial