Airbnb Message Templates: The Complete Library (2026)

This is a complete, copy-paste library of 15 Airbnb message templates covering the entire guest journey: booking confirmation, pre-arrival, check-in instructions (including a gated-community version), wifi details, early check-in and late checkout replies, mid-stay check-ins, checkout, review requests, and the difficult ones — noise complaints, refund requests, and discount haggling.

Every template uses {placeholders} so you can drop it into Airbnb's saved quick replies (or your property management software) once and reuse it forever. Each comes with a when-to-send note and one customization tip, because a template sent at the wrong moment is almost as bad as no message at all. Skip to the timing table to see which messages you can schedule automatically versus which need a real reply.

Why templates matter more than most hosts think

Guest messaging isn't just courtesy — it's a ranking and revenue input:

• Response rate affects Superhost status. Airbnb measures whether you respond to new inquiries and trip requests within 24 hours; Superhosts need 90%. Templates make a fast first reply nearly effortless.
• Most guest questions are predictable. Wifi, parking, check-in time, early check-in, checkout rules — a template library turns each from a two-minute typing job into a ten-second paste.
• Consistency drives reviews. A predictable message cadence (confirmation → pre-arrival → check-in → mid-stay → checkout → review request) is the communication backbone of most 5-star operations.

One rule before the library: always personalize the first line. Guests forgive templates everywhere except the greeting. Use their name, reference their trip, and the rest can be 100% boilerplate without anyone minding.

Stage 1: Booking confirmation

Template 1 — Booking confirmation / welcome message

When to send: Within an hour of booking — instantly if you automate it. This is the message that sets the tone for the whole stay and confirms the guest booked the right place.

Hi {guest_first_name}, thanks so much for booking {property_name} — we're excited to host you from {check_in_date} to {check_out_date}!

Here's what happens next:

- About {X} days before arrival, I'll send directions, parking info, and everything you need for a smooth check-in.
- Check-in is anytime after {check_in_time}, checkout is by {check_out_time}.
- If you have questions before then — about the space, the area, anything — just message me here. I'm quick to reply.

Is there anything about your trip I should know to make your stay better (special occasion, arrival time, traveling with kids)?

{host_name}

Customization tip: That closing question isn't filler — it surfaces early check-in requests, celebrations, and extra guests now, while you can still plan for them, instead of at 4pm on arrival day.

Stage 2: Pre-arrival

Template 2 — Pre-arrival details (3 days out)

When to send: 2–3 days before check-in. Close enough that guests are paying attention, far enough that they can still plan around it.

Hi {guest_first_name}, your stay at {property_name} is coming up on {check_in_date} — here's everything you need before you arrive:

Address: {full_address}
Check-in: anytime after {check_in_time} — it's self check-in, so no need to coordinate timing with me
Parking: {parking_instructions}
Getting here: {directions_or_transit_note}

I'll send the door code and step-by-step entry instructions on the morning of your arrival.

One question: roughly what time do you expect to arrive? No pressure either way — it just helps me make sure everything's ready.

Safe travels!
{host_name}

Customization tip: Tell guests when the access code is coming. The single most common pre-arrival anxiety message is "I don't have a door code yet" — you prevent it with one sentence.

Stage 3: Check-in instructions

Template 3 — Check-in instructions (standard self check-in)

When to send: The morning of arrival day, or the evening before for early risers and international travelers. Sending codes earlier than that is a mild security risk; sending them later invites panic messages from the driveway.

Hi {guest_first_name}, today's the day! Here's how to get into {property_name}:

Address: {full_address}
Check-in: after {check_in_time}

1. {parking_step — e.g., "Park in spot #4, directly in front of the unit."}
2. Walk to the {door_location — e.g., "front door with the blue frame"}.
3. Enter code {door_code} on the keypad, then turn the handle.
4. Wifi network and password are on the card next to the router (I'll also message them to you).

If anything at all goes sideways — code doesn't work, can't find the door — message or call me at {phone_number} and I'll sort it out right away.

Enjoy your stay!
{host_name}

Customization tip: Add a photo of the actual door and keypad. Guests who don't read paragraphs do look at pictures, and "which door?" is the #1 arrival question after the code itself.

Template 4 — Check-in instructions: gated community / callbox variant

When to send: Same timing as Template 3 — but this variant exists because gate access is where standard check-in templates fail. If your property is behind a guard gate, callbox, or coded community gate, the guest has to clear two doors, and most template libraries ignore the first one entirely.

Hi {guest_first_name}, today's the day! Getting into {property_name} has two steps — the community gate first, then the unit — so please read both:

Step 1 — Community gate:
{Pick the line that matches your setup:}

- Guard gate: You're on the guest list under "{guest_last_name}." Show the guard your ID and they'll wave you through. If there's any issue, the guard can call me directly.
- Callbox: At the callbox, dial {callbox_code_or_directory_number}. It rings my phone — I'll buzz you in. If I don't pick up within 30 seconds, call/text me at {phone_number}.
- Code gate: Enter {gate_code} at the keypad on the left side of the gate. The gate takes a few seconds to open — don't re-enter the code or it resets.

Step 2 — The unit:
Once inside, {directions_within_community — e.g., "follow Palm Drive to the third building on the right, unit 204"}. Door code is {door_code}.

Heads up: after {time — e.g., "10pm"}, {after_hours_note — e.g., "the guard gate switches to the callbox — same directory number works"}.

Stuck at the gate at any hour? Message or call {phone_number}. I'd rather you wake me than wait outside.

{host_name}

Customization tip: The after-hours line is the one that saves you — gate procedures often change at night (guard shift ends, callbox takes over), and "guest stuck at the gate at 11pm" is the classic gated-community disaster. If your HOA requires a guest list, add guests the day they book, not arrival day.

Stage 4: Wifi details

Template 5 — Wifi message

When to send: With or immediately after check-in instructions. "What's the wifi password?" is reliably the most-asked guest question — send it before they ask.

Hi {guest_first_name}, here are the wifi details for {property_name}:

Network: {wifi_network_name}
Password: {wifi_password} (case-sensitive)

The router is {router_location — e.g., "in the living room TV cabinet"}. If the connection drops, unplug the router for 10 seconds and plug it back in — that fixes it 95% of the time.

Speed is {speed — e.g., "300 Mbps"}, plenty for streaming and video calls{remote_work_note — e.g., ", and there's a desk setup in the second bedroom if you're working"}.

{host_name}

Customization tip: Put the password on its own line, exactly as typed, and say it's case-sensitive — half of all "wifi doesn't work" messages are typos. (And when you change the password, remember it lives in this template too.)

Stage 5: Early check-in requests

Template 6 — Early check-in reply: yes

When to send: As a reply, whenever a guest asks. Never leave an early check-in request hanging — the guest is usually mid-travel-planning when they ask.

Hi {guest_first_name}, good news — the place will be ready early, so you're welcome to check in anytime after {early_time} on {check_in_date} at no charge. Same entry instructions apply.

One small ask: if your plans change and you'll arrive later, no need to update me — the code works whenever you get here.

See you soon!
{host_name}

Customization tip: Only confirm early check-in after you've checked whether there's a same-day checkout. If cleaning is tight, "I'll confirm by {time} the day before" is a perfectly good interim answer — and honest beats optimistic.

Template 7 — Early check-in reply: no (with alternatives)

When to send: As a reply. A flat "no" reads cold and shows up in review scores; a no with alternatives reads like hospitality.

Hi {guest_first_name}, thanks for asking ahead! Unfortunately I can't do early check-in on {check_in_date} — we have guests checking out that morning and the cleaning team needs the full window to get the place perfect for you.

A few options that might help:

- You're welcome to drop your bags at {bag_drop_option — e.g., "the bench inside the gate / with the front desk"} anytime after {time}.
- {nearby_suggestion — e.g., "Café Luna two blocks away is a great spot to wait — good coffee, free wifi."}
- I'll message you the moment the cleaners finish — sometimes that's 30–60 minutes before the official time.

Sorry I can't promise more this time — checkout math is the one thing I can't bend!

{host_name}

Customization tip: The "I'll message you the moment it's ready" line costs you nothing and converts a rejection into a favor. Set a reminder (or an automation) so you actually do it.

Stage 6: Mid-stay check-in

Template 8 — Mid-stay check-in

When to send: The morning after the first night. Early enough to catch small problems before they become review material, late enough that the guest has actually experienced the place.

Hi {guest_first_name}, just checking in — how was your first night at {property_name}?

If anything's not perfect (temperature, wifi, something missing), tell me now and I'll fix it today. And if you want recommendations — {local_examples — e.g., "best breakfast nearby, the hike locals actually do"} — happy to share my list.

Otherwise, I'll leave you to it. Enjoy!
{host_name}

Customization tip: Keep it to three sentences and give them permission to not reply. The mid-stay message is a smoke detector, not a conversation starter — its job is making problems surface on day 2 instead of in the review.

Stage 7: Late checkout requests

Template 9 — Late checkout reply (yes and no versions)

When to send: As a reply, and quickly — guests usually ask the night before or morning of checkout, when your cleaning schedule is already fixed.

Yes version:

Hi {guest_first_name}, that works! You're good to stay until {late_time} on {check_out_date} — no charge. The cleaning team arrives at {cleaner_time}, so that's the hard limit. Enjoy the slow morning!

{host_name}

No version:

Hi {guest_first_name}, I wish I could — but we have guests arriving the same day and the cleaning team needs the full window between stays, so checkout does need to be by {check_out_time}.

If it helps, you're welcome to leave your bags at {bag_option} until {time}, and {nearby_option — e.g., "the lobby café / park across the street"} is a nice spot to land before you head out.

Thanks for understanding — and for asking rather than just staying put, which I appreciate more than you know!

{host_name}

Customization tip: Decide your late-checkout policy once (free when no same-day arrival, paid option, or never) and encode it in the template. Deciding case-by-case at 9pm is how hosts end up resentful or inconsistent.

Stage 8: Checkout

Template 10 — Checkout instructions

When to send: The evening before checkout, around 5–7pm — after the day's activities, before they've mentally checked out.

Hi {guest_first_name}, hope you've had a great stay! Just a heads-up that checkout tomorrow is by {check_out_time}. Before you go:

- {task_1 — e.g., "Leave used towels in the bathtub"}
- {task_2 — e.g., "Load and start the dishwasher if you've used dishes"}
- {task_3 — e.g., "Turn off lights and AC"}
- Lock the door behind you — it locks automatically when you {lock_action}.

That's it — please don't strip beds or take out trash, the cleaning team handles the rest.

It's been a pleasure hosting you. Safe travels home!
{host_name}

Customization tip: Cap the list at four tasks — ten-item checkout chore lists get punished in reviews. Saying what guests don't need to do reads as generous.

Stage 9: Reviews

Template 11 — Review request

When to send: The day after checkout, after you've already reviewed them. Guests have 14 days to leave a review, and neither side sees the other's until both submit (or the window closes) — so reviewing first costs nothing and signals good faith.

Hi {guest_first_name}, thanks again for staying at {property_name} — you were wonderful guests and I've already left you a 5-star review.

If you have two minutes, I'd be so grateful if you'd share a review of your stay as well — reviews are genuinely the lifeblood of a small hosting operation like {ours/mine}.

And if anything during your stay was less than perfect, I'd love to hear it here first so I can fix it for the next guest.

Hope to host you again — safe travels!
{host_name}

Customization tip: The "tell me here first" line routes criticism into a private message instead of a public review. Don't ask for "a 5-star review" outright — it reads as pressure; telling them you already left them five stars accomplishes the same thing gracefully.

Template 12 — Post-review thank-you

When to send: Within a day or two of a guest leaving a positive review. Almost no hosts send this one — which is exactly why it works for rebookings.

Hi {guest_first_name}, I just read your review — thank you, it truly made my day. Guests like you are the reason I host.

You're welcome back at {property_name} anytime. If you're ever planning a return trip to {city}, message me before you book — I'll make sure you get the best available deal as a returning guest.

All the best,
{host_name}

Customization tip: This message is your repeat-booking pipeline. Returning guests are pre-vetted, review kindly, and cost you zero marketing — a two-line thank-you is the cheapest guest-acquisition channel in hosting.

Stage 10: The difficult ones

Templates matter most when you're stressed, because that's when hosts type things they regret. Draft these three calm, before you need them.

Template 13 — Noise complaint (message to the guest)

When to send: The moment a neighbor complains or your noise monitor alerts — tonight's problem does not improve by morning.

Hi {guest_first_name}, hope you're having a good evening. I've had a noise report from a neighbor at the property. I know it's easy for a fun night to carry, and I'm not upset — but I do need to ask you to bring the volume down now, especially {specifics — e.g., "on the patio, where sound carries to the houses behind us"}.

Quiet hours in the neighborhood are {quiet_hours}, and it's part of the house rules we have to take seriously — repeat complaints can genuinely put the listing at risk.

Thanks for understanding, and enjoy the rest of your night — just a bit more quietly.

{host_name}

Customization tip: Firm, friendly, and factual — without accusation ("I've had a report" beats "you're being loud"). The message also creates a written record, which matters if things escalate to Airbnb support.

Template 14 — Refund request: acknowledge and route to a human decision

When to send: Immediately on receiving any refund or compensation request. This is the one message you should never let a template — or an AI — resolve on its own: money decisions need a human. The template's job is to buy time gracefully while committing to nothing.

Hi {guest_first_name}, thank you for flagging this — I'm sorry the {issue} affected your stay, and I take it seriously.

I want to give this proper attention rather than a rushed answer, so let me look into what happened{investigation_step — e.g., " and check with the cleaning team"}, and I'll come back to you by {specific_time — e.g., "6pm today"} with a resolution.

In the meantime, is there anything I can do right now to make the rest of your stay better?

{host_name}

Customization tip: Name a specific time you'll respond by, and hit it. The template deliberately neither admits fault nor promises money — it acknowledges, investigates, and commits to a deadline. How quickly and calmly you engage is what shows up in the review either way.

Template 15 — Long-stay / discount inquiry reply

When to send: As a reply to "what's your best price?" or a monthly-stay inquiry — fast, because discount shoppers message five listings at once and the first substantive answer often wins.

Hi {guest_first_name}, thanks for your interest in {property_name}! For a stay of {length}, the listing automatically applies my {weekly/monthly} discount of {X}% — that's already reflected when you enter your dates, and it's the best rate I offer for those dates.

The price includes {value_items — e.g., "all utilities, fast wifi, dedicated workspace, and weekly linen refresh"}. If your dates are flexible, {flexibility_offer — e.g., "midweek arrivals are sometimes cheaper — happy to check specific dates for you"}.

Would love to host you!
{host_name}

Customization tip: Anchor to a discount that already exists (weekly/monthly pricing) instead of inventing one per negotiation — it lets you say "that's the best rate" honestly and ends the haggle in one message. If you have gap nights to fill, decide your floor before you reply, not during the conversation.

Which messages to schedule, and which to trigger

Roughly half of this library can be fully automated on a schedule; the other half only makes sense as a reply to something a guest said. Mixing those up is the most common templating mistake.

Schedule these (fixed timing, same for every guest):

Reply-only (a human or an AI has to read the guest's message first): early check-in (6–7), late checkout (9), post-review thank-you (12), noise complaint (13), refund request (14), discount inquiry (15).

Airbnb's native scheduled quick replies can handle the scheduled column: it supports exactly three trigger events — booking confirmed, check-in, and checkout — with time offsets, plus shortcodes that auto-fill the guest's name, dates, and address. Two things to know from Airbnb's own documentation: for last-minute bookings and short stays, some scheduled messages are skipped by default unless you enable the per-template "send for last-minute bookings and short stays" toggle, and templates are managed per listing — so a wifi password change means editing it everywhere it appears. Airbnb's separate quick replies feature covers the reply-only column: saved responses you insert manually. For a full walkthrough of the native tooling and what sits beyond it, see our guide to automating Airbnb guest messages. And note that Airbnb's scheduled messages only reach Airbnb guests — Vrbo and Booking.com hosts need a channel manager or messaging tool to run one sequence everywhere.

Templates get you 70% of the way — here's the honest rest

A good template library eliminates most of your typing. It does not eliminate the job, and it's worth being clear-eyed about where the line is.

Templates handle the predictable. Confirmation, check-in, wifi, checkout, review request — same message, every guest, forever. Schedule them and stop thinking about them.

Templates fail on the specific. The real workload isn't the scheduled sequence — it's the long tail of context-dependent questions:

• "Can we check in two hours early on Friday?" — depends on that Friday's checkout and cleaning schedule. No template knows your calendar.
• "We have a truck with a trailer — will it fit?" — depends on your actual driveway.
• "We're stuck at the gate and the callbox isn't ringing" — at 11pm, a saved reply is useless; someone has to respond.
• "Is the pool heated in March?" "Can we get a crib?" "Our flight moved — can we shift one night?" — each takes 30 seconds of your attention, and they arrive at all hours.

Hosts on the Airbnb Community Center describe this precisely: no matter how thorough the listing or the message sequence, guests ask anyway — and they ask at night. Templates compress each answer; they don't remove the interruption.

That last 30% is what AI messaging is for. HostReply reads the guest's question, looks up your property details, FAQs, calendar, and the guest's actual reservation, and replies in your voice — so "can we check in early Friday?" gets a correct answer based on whether Friday has a same-day checkout, not a canned maybe. And for the messages that should never be auto-resolved — refund requests, angry guests, judgment calls — it escalates to you by SMS so a human makes the decision, which is exactly how we'd tell you to handle Template 14 anyway. It works with Airbnb via a Hospitable connection today (OwnerRez support is in final testing), costs $19/property/month, and has a 14-day free trial.

Start with the templates. When you find yourself re-answering the questions the templates can't cover, that's the signal.

FAQ

What should an Airbnb welcome message say?

A welcome (booking confirmation) message should confirm the booking warmly, restate dates and check-in/checkout times, tell the guest exactly when they'll receive check-in details, and ask one open question about their trip. Keep it under 150 words — its job is reassurance and expectation-setting, not information transfer. Template 1 above covers all four elements.

When should I send check-in instructions?

Send full check-in instructions — including door codes — the morning of arrival day, or the evening before for early or international travelers. Send the non-sensitive details (address, parking, directions) 2–3 days out. Codes a week early are a security risk; codes after the guest is en route produce panicked messages from the driveway. If your property is in a gated community, add gate or callbox instructions as an explicit first step (Template 4) — that's where most check-in messages fail.

Do message templates affect my response rate?

Indirectly, yes. Airbnb's response rate measures whether you reply to new inquiries and trip requests within 24 hours — Superhost status requires 90%. Templates collapse the effort of replying, which is what actually moves the metric: a saved reply turns a five-minute composition into a ten-second paste, so inquiries stop sitting unanswered. Scheduled messages to booked guests don't count toward response rate, but they prevent the anxious "haven't heard from my host" messages piling onto your inbox.

Can I automate these templates?

Partially, with Airbnb's built-in tools: scheduled quick replies auto-send templates on three triggers (booking confirmed, check-in, checkout) with time offsets — about half this library, per the timing table above. What Airbnb can't automate: anything requiring a reply to a guest's actual question, conditional logic (a 1-night vs. 30-night stay), or messages on other platforms. For those, you need a property management tool or an AI messaging layer on top.

What's the best review request message?

Review the guest first, then message them the day after checkout saying you've already left them a 5-star review and asking them to share their experience too (Template 11). Two mechanics make this work: reviews are hidden until both sides submit (or the 14-day window closes), so going first is free goodwill — and "if anything was less than perfect, tell me here first" routes complaints into private messages instead of public reviews. Never explicitly ask for five stars; it reads as pressure and can backfire.

Should I use the same templates for every guest?

Yes — that's the point — but personalize the first line every time. Use the guest's name, reference something real about their trip, and the remaining 90% can be identical for every guest without anyone noticing. The exception is the difficult-scenario templates (13–15): match your tone to the situation, since a copy-paste response to an upset guest is detectable and makes things worse. For those, see our guide to the guest messages hosts dread.

How many messages is too many?

Five to six scheduled touchpoints per stay is the comfortable ceiling: confirmation, pre-arrival, check-in, one mid-stay check-in, checkout instructions, and a review request. More starts to feel like being managed rather than hosted — especially on 1–2 night stays, where you should compress the sequence (Airbnb skips some scheduled messages on short stays by default for exactly this reason). Every message should either deliver needed information or invite the guest to surface a problem; if it does neither, cut it.

Want the full playbook around these templates? See our guides to nailing the Airbnb check-in experience and earning consistent 5-star reviews — or let HostReply handle the messages no template can.