A guest messaged hours ago. Why didn't you get an email?

Because Airbnb's email is a courtesy copy of the message, not the message itself — and there are at least four ways that copy never reaches you: the thread was already opened in the app, a notification setting was off, the email landed in spam, or a mail rule quietly rewrote it on the way to wherever you route it. The message still counts against your response time either way. Here is where the alerts actually fail, and how to stop a guest question from depending on one email arriving.

The email is a bell, not the mailbox

The Airbnb inbox — in the app or on the website — is the record. Email, push, and SMS are pointers to it. Airbnb makes no promise that every guest message produces an email, and in practice not every one does. If your workflow treats your personal inbox as the place guest messages live, then a missing email is a missing message, and you find out when the guest follows up — or doesn't.

Reading it can silence it

This one we found by testing, not in any documentation. While wiring up messaging on a live listing, we sent a test message and opened it in the Airbnb app first. The thread showed it as read — and no email notification was ever sent. Which is reasonable design in isolation: why alert you to something you've seen? But on a listing with more than one set of eyes — a partner, a cleaner, a co-host — it means whoever opens the thread first, even accidentally, on a phone, in passing, silences the email for everyone whose workflow depends on it. "Read" is not "handled." They only look the same.

The settings that decide what you hear

Airbnb's notification preferences are split by category and by channel: messages, reservations, and promotions each have their own toggles for email, push, and SMS. It is easy to have message emails off without remembering deciding that. It is also easy to lose push silently — a new phone or a reinstall resets the app's notification permission, and nothing tells you. Worth an audit once, and again whenever the hardware changes.

Mail that never lands, and rules that break it

Airbnb's automated mail is exactly the kind of sender that spam and "Promotions" filters sort away from you. And if you route Airbnb mail onward — to a shared inbox, a virtual assistant, or a tool — how you route it matters more than it should: in Outlook, a "Forward" rule rewrites the sender to you and drops the reply headers, which breaks any downstream automation that needs to know the mail came from Airbnb; a "Redirect" rule passes the message through intact. We learned that distinction the practical way, watching forwarded copies arrive broken and redirected copies arrive whole. If anything in your operation consumes Airbnb mail, test the full path with a real message — not once, but on a schedule.

Why a missed email costs more than a slow reply

Airbnb measures your response rate on first replies to new inquiries and trip requests within 24 hours, and shows it to guests considering your listing. An email that never arrived and an inquiry you ignored look identical in that number. Worse, the guest is mid-planning: a question that sits for six hours is often answered by booking somewhere else. The cost of a silent notification failure isn't a late reply — it's a conversation that never happened.

Make every message someone's job

The fix is not more notifications; it is removing the assumption that a notification will come. Keep app push on as the primary channel. Audit the settings quarterly. Agree that whoever opens a thread owns it or explicitly hands it off — never let "read" end a message's life. And if the volume justifies it, put something in the path that watches the message stream itself rather than listening for emails about it. That is how StayPilot treats the problem: every guest message becomes exactly one of three things — answered, drafted for your approval, or escalated to you — and nothing marks it resolved until it actually is. A notification that fails to fire changes nothing, because the answer was never waiting on you seeing a bell.

If you want to see what that looks like on your own listing, paste it into the demo at /try — no account, no connection to your inbox — and ask it the last question a guest asked you. The point isn't that the reply arrives; it's that it can't silently not.