Every Guest Message in One Thread, Beside the Booking
The conversation is never where you need it
A guest emails to ask whether you allow an early check-in. You answer. Three weeks later they message again — this time through the booking platform — asking about parking. You answer that too. Then the day before arrival they reply to your automated confirmation email with a question about the door code.
Three messages, three different places. None of them sitting next to the booking they belong to. When you finally open the reservation to remember what was agreed, the actual conversation is scattered across your personal inbox, an OTA’s message centre, and a reply buried under a confirmation email. You end up reconstructing the story from memory — and memory is exactly the thing that drops a guest’s request on a busy turnover day.
This is the quiet tax of running bookings across channels. The booking lives in one system; the conversation about it lives somewhere else entirely. Airflow closes that gap. Every booking in Airflow carries its own communication thread, and the messages tied to that booking show up right beside it.
A thread per booking, built automatically
Open any booking in your portal and, alongside the guest details and the money, you’ll find a communication thread: a single chronological timeline of everything that’s passed between you and that guest about that stay.
You don’t create the thread. You don’t tag messages into it. Airflow assembles it for you by pulling together the things that already happen around a booking:
- The original booking email — the OTA confirmation or enquiry that started it all — sits at the top as the first event.
- Guest emails picked up from your connected Gmail account, matched to the booking by the guest’s email address.
- Replies you’ve sent to that guest, so the timeline shows both sides of the conversation.
- Automated emails Airflow sent on your behalf — confirmations and the like — logged in the same place.
The result is one screen that answers the question you actually have when you open a booking: what’s been said, and is anything waiting on me?
How the thread gets built
There are no pre-made “conversation” records sitting empty, waiting to be filled. A thread is simply the booking itself, viewed as a timeline. When you open the thread, Airflow gathers every message connected to that reservation — across your inbound booking emails, the emails Airflow sent for you, and the guest emails scanned from your Gmail — and lays them out in order.
That matters for one practical reason: nothing falls through the cracks because it was filed in the wrong folder. A message is part of the thread because it relates to the booking, not because someone remembered to attach it. The booking is the thread.
Your guest emails, threaded in
If you connect your Gmail account, Airflow periodically scans it for emails to and from your booking guests’ addresses. When it finds one, it works out the direction — a message from the guest is something awaiting your reply; a message from you is a reply already sent — and drops it onto the right booking’s timeline. Emails from the OTA platforms themselves are filtered out, because the booking pipeline already handles those. What lands in the thread is the real back-and-forth with the actual guest.
So the early-check-in question your guest sent to your personal email three weeks ago? If it came from the address on the booking, it’s there in the thread, in order, next to everything else.
Send the next message without leaving the booking
The thread isn’t just a record to read — it’s also where you reply. The booking page has a Send message card with a live preview, so you can write to the guest and see exactly how the email will look before it goes out.
Airflow sends it the right way for your setup: through your connected Gmail if you have one, or through Airflow’s own mail otherwise. Either way, the message you just sent appears in the thread immediately, so the timeline stays complete and you never have to switch to another app to keep a conversation going.
This is the part that turns “a place to look things up” into “a place to actually work.” You open the booking, read the full history, answer the question, and you’re done — all on one screen.
Where this is today, honestly
We want to be precise about what’s live, because messaging is an area where it’s easy to oversell.
What’s live now: every booking has its own communication thread on the booking detail page. It brings together the original booking email, automated emails Airflow sent, guest emails scanned from a connected Gmail, and the replies you send from within Airflow. There’s also a Threads view in your portal’s Messages page that lists your bookings as conversations, with a full-timeline page for any one of them.
What this isn’t — yet: this is not a single unified inbox that pulls live messages out of every OTA’s messaging centre in real time. Guest email threading today works through a connected Gmail account and the booking emails that flow through Airflow. Replies inside an OTA’s own message system still live in that platform. We’re building toward a fuller picture over time, but we’d rather tell you exactly what the thread contains than imply it captures every channel the moment it happens.
What it does deliver right now is the thing that saves you the most: the conversation tied to each booking, in one place, beside the booking — instead of reconstructed from three inboxes every time you open a reservation.
Why a thread per booking beats one giant inbox
It’s tempting to think the answer to scattered messages is one enormous inbox with everything in it. But a flat inbox just moves the problem: now everything is in one place, and none of it is connected to the booking it’s about. You’re still scrolling, still matching a name to a reservation, still guessing which “Hi, quick question” goes with which stay.
Tying the conversation to the booking is what actually helps:
| Scattered across channels | One flat inbox | Thread per booking (Airflow) | |
|---|---|---|---|
| Find a guest’s history | Hunt across email + OTA + replies | Scroll and match by name | Open the booking — it’s right there |
| See what’s awaiting reply | Hold it in your head | Skim everything | The thread shows the last message and direction |
| Context for the stay | Cross-reference manually | None — inbox doesn’t know the booking | Sits next to dates, guest, and payments |
| Reply | Switch apps | Switch apps | Send from the booking, logged to the thread |
The booking is the natural home for the conversation, because the booking is what the conversation is about. Everything you’d want while reading a guest’s message — the dates, the property, what they’ve paid — is already on the same page.
The principle
You shouldn’t have to be your own filing system. The message a guest sent and the reservation it concerns belong together, and keeping them together shouldn’t be a manual job you do in your head on a turnover morning.
Open the booking, and the conversation is already there. The booking email that started it, the guest’s questions, the emails you sent — one timeline, beside the dates and the money, ready for your next reply. That’s the whole idea.
Want to see how a booking becomes the hub for everything about a guest? Read Deposit Now, Balance Later — and the Books Stay Right to see the payment side of the same booking, or take a closer look at how Airflow handles direct bookings. If you’re not set up yet, get started here.