Why your check-in email reads 'Hello Guest!' — and how to fix it on Airbnb

You set up a beautiful welcome message template. Friendly, specific, useful:

Hi {{guest_first_name}},

Looking forward to welcoming you to {{property_name}} on {{check_in_date}}! A few quick details so you can settle in...

You hit preview. It renders:

You stare at it. You consider sending it anyway. You don't, because it sounds like a broken robot. So you open the message, replace Guest with the actual name from the Airbnb thread, and send it manually. Tomorrow morning, you'll do this again. And the day after.

Now multiply by every booking, every property, every season.

Why the template breaks

Airbnb's calendar feed — the thing every property management tool reads from — doesn't include the guest's name. By design. What it gives you for the guest field looks like this:

Reserved (E1A2B3C4) - Airbnb

A confirmation code, an opaque tag. No human in there. Your template variable has nothing real to fill in, so it falls back to "Guest" or just renders blank.

Calendar tools read this feed. They have no other source of truth. So they pass the placeholder through to your templates, and your templates render placeholder-quality messages, and the whole point of having a template — not having to hand-write personal greetings — quietly evaporates.

Where the real name actually lives

It's in your inbox.

Every time a booking goes through, Airbnb sends you a "Reservation confirmed" email that includes the guest's full name in the body. That email is the only place the platform freely shares the name. Calendars: no. API: no. Email to the host: yes.

So that's the lever.

The fix

Sane Host gives each property a unique forwarding address. You set up one filter in your email — Gmail, Outlook, doesn't matter — that says: "forward Airbnb's reservation-confirmed emails for this property to that address."

That's the whole setup. Two minutes per property, once.

From then on, every new booking on that property gets the real first name attached automatically. The forwarding rule does the routing, Sane Host parses the name, the booking on your dashboard now reads "Kimberly" instead of "E1A2B3C4." Your {{guest_first_name}} template variable starts producing real greetings:

Sendable. Done.

Step-by-step setup is in the help guide.

Why this matters more than it sounds

Templates are a force multiplier when they work and a tax when they don't. Every host we've talked to has, at some point, given up on templated guest comms because they kept rendering as boilerplate — and then quietly drifted back into hand-writing every welcome message, or sending the broken robot version because it was 11pm and they were tired.

The fix isn't writing better templates. The fix is putting the real data back into the template inputs. Once your messages render with real names again, the rest of your template library starts pulling its weight, too: the check-in instructions, the late-arrival note, the "thanks for staying" follow-up. They all stop sounding like a mail merge.

That's the whole pitch. Stop greeting people as "Guest." Two-minute setup. Your future welcome messages thank you.