A unified inbox pulls every guest conversation — Airbnb, Booking.com, Agoda, WhatsApp, Telegram, direct — into one timeline per guest, so nothing gets answered late because it arrived in the wrong app. The honest mechanics in 2026: direct channels (WhatsApp, Telegram, a guest app) run fully two-way with instant AI replies, while OTA messages flow in and the AI drafts the response — with automatic send-back to the OTAs still rolling out across the industry, not finished anywhere. That drafting alone removes most of the pain: the 3am Agoda message is triaged, translated and answered-in-draft before you wake up. Here's how it works, what to check before trusting any vendor's 'all channels' claim, and how setup actually goes.
The tab-switching tax is real and it compounds: three OTAs plus WhatsApp means four notification streams, four read-states, four places a check-in question can sit unanswered while you're looking at the other three. Miss one on Airbnb and your response rate — a ranking factor — takes the hit. The unified inbox is the oldest good idea in this category; the AI layer is what recently made it more than a convenience.
What a unified inbox actually is
A unified inbox is one conversation timeline per guest, regardless of channel — not merely one app with four tabs. The difference shows on the third message: when the guest who booked on Booking.com switches to WhatsApp for the door code, a real unified system shows both in one thread with the reservation context attached, so anyone (human or AI) answering knows the whole story. Channel-tabs-in-one-window still make you reassemble the story yourself.
How OTA unification works — and its honest limits
Under the hood there are only three ways messages get in: official APIs (cleanest, requires certification per OTA), connection through a PMS that already has them (how layers like Hostella inherit Hostaway's threads via its connector), and mailbox parsing of OTA notification emails (the pragmatic universal fallback). Inbound is a solved problem. Outbound is where claims need checking: sending replies back into Airbnb/Booking/Agoda programmatically requires per-OTA certification, and across the industry — from PMS giants to AI startups — automatic OTA send-back is at various stages of rolling out. Hostella's own status, stated plainly: OTA messages flow in and the AI drafts every reply; send-back is rolling out; full two-way auto-send is live today on WhatsApp, Telegram and the guest app. Ask any vendor the same question: which channels are two-way today, in which mode?
Setup, realistically
The honest walkthrough for a Hostella-style setup: connect channels (WhatsApp/Telegram take minutes; OTA inbound flows via connector or forwarding), sync calendars over two-way iCal so every conversation carries reservation context, then run the AI in learning mode — it drafts everything, you approve everything, and it absorbs your voice and house rules from your edits. Promote routine categories (Wi-Fi, directions, check-in logistics) to auto-send as trust builds; keep money and complaints behind the approval gate permanently. Most operators go from four apps to one timeline inside a day — the autonomy ramp then takes as long as your comfort does.
Four notification streams → one timeline
Every guest conversation in one inbox with reservation context, AI drafts on every thread, and live two-way on WhatsApp, Telegram and the guest app. From €29/month.
See how it works