A unified inbox for
every property.
Every guest, every channel, every property in one queue, and the controls to let someone else answer it without handing over the keys to everything else.
Laurie saved $4,000 last year when he switched to Host Port.
“I was paying hotel money for software I needed a training call to understand. Host Port does the same job for a fraction of it. One calendar, every channel, and nothing I have to think about on a changeover day. Moving all four took less than an hour to do.”
Laurie hosts four stays around Manly, NSW.See them on Airbnb
One listing is a trickle. Ten is a stream.
At one property the failure mode is writing a rushed reply. At ten, spread across four platforms and arriving at all hours, the failure mode is not seeing the message at all. A single queue across every property and every channel is what makes that tractable.
Unread counts per property, and one for everything
A badge on the inbox for the whole portfolio, and a count against each property inside it, so you can tell at a glance which building is waiting on you.
Live, without refreshing
Threads and messages update in place as they arrive. If someone on your team replies while you are looking at the same screen, you see it happen.
Replies leave the way the guest arrived
You type in one box. The message goes out through Airbnb, through Booking.com, or as email, whichever channel that guest booked on, so the conversation stays where they expect it.
Receipts on anything sent by email
Accepted, delivered, opened, bounced. A bounced message is marked failed with the reason and can be retried, rather than sitting in a sent folder looking fine.
Delivery receipts apply to messages that go out as email, your direct bookings and Vrbo. Airbnb and Booking.com messages travel inside those platforms, which do not report back an open.
One guest can arrive as four conversations.
A booking does not produce one tidy thread. It produces an inquiry before there is a reservation, a fresh channel thread ID at confirmation, and messages afterwards that may attach to either. Left alone, that is four fragments of one conversation.
An inquiry lands with no reservation attached to it yet.
The channel issues a brand new thread ID for the same guest.
More messages arrive, some against the booking, some against the old thread.
One thread. One guest. One stay.
The pre-booking inquiry, the confirmation and everything after it resolve to a single conversation, with the booking and its dates attached to it. You are never cross-referencing a reservation code against a chat window to work out who you are talking to.
Delegate the inbox without handing over the books.
Access is granted per person, per property. These are the three presets that ship with the product, and every one of them can be adjusted switch by switch if none of them is quite your situation.
Sees the calendar, can chat with guests
- CalendarView only
- PricingNo access
- Guest messagesFull access
- Listing detailsView only
- Channel connectionsNo access
Runs the day to day, sees no financials
- CalendarFull access
- PricingFull access
- Guest messagesFull access
- Listing detailsFull access
- Channel connectionsView only
Everything you can do
- CalendarFull access
- PricingFull access
- Guest messagesFull access
- Listing detailsFull access
- Channel connectionsFull access
Pricing is the master switch for money: set it to no access and every dollar figure disappears for that person, nightly rates, booking totals, the reservation panel in the inbox. And because access is checked in Postgres rather than in the interface, a person without message access on a property cannot reach those threads by any route at all.
A draft in your voice. You still press send.
Volume is mostly repetition, the same questions about parking, late check-in and whether the dates are free. Suggest a reply drafts an answer from the replies you have already written, with the real availability and rates for that property in front of it.
It writes into the message box and stops there. Nothing sends on its own, nothing is saved to the thread, and you can rewrite or discard it like anything else you typed.
What it reads first
- Your own past replies, matched to the question asked
- Live availability across the next 90 days
- Current rates for that property
- Where the guest is in the stay, enquiring, arriving, checked in
- Any standing instructions you have written for that listing
What you get free, and what costs $10.
We would rather you understood the line than found it after signing up. Here it is.
Unlimited listings. No credit card, no trial clock.
- One-way iCal sync with Airbnb, Booking.com and Vrbo
- Unified calendar across every listing
- Manual bookings, blocks and notes
- Mobile app with push alerts
- Commission-free direct booking page for every listing
- Team and cleaner access, unlimited seats
Per listing, per month, in AUD.
- Everything in Free
- Two-way real-time sync in under 60 seconds
- Airbnb, Booking.com and Vrbo on two-way sync
- Unified guest inbox across every channel
- Automated pricing and stay rules
- Priority support, one-hour first reply
Team members and permissions are free and always have been. Pro is what connects Airbnb and Booking.com directly, which is what carries their guest messages into the inbox.
Common questions
How many people can I add?
As many as you need, on every plan including free. We bill per listing, never per person, so adding a co-host or a second cleaner does not change your invoice.
Can I limit what someone sees?
Yes, and per property rather than across the whole account. Five areas, calendar, pricing, guest messages, listing details and channel connections, each set to no access, view only or full access, independently for every property you grant.
Can someone answer guests without seeing what I earn?
Yes. Pricing is the single switch that governs whether a person sees any dollar figures at all, nightly rates, booking totals, the lot. Set it to no access and give them full access to messages, and they can run guest communication without ever seeing revenue.
Is that enforced, or just hidden in the interface?
Enforced in the database. Access to message threads is checked by a row-level security policy in Postgres rather than by the app, so a person without message access on a property cannot read those conversations through the app, the API, or anything else.
Which channels feed into the inbox?
Airbnb and Booking.com messages arrive through a direct channel connection and go back out the same way. Vrbo works through its relay address, and your direct booking page uses branded email with replies routed back into the thread.
Does everyone see the same read state?
Yes, read state is on the conversation, not on each person, so a thread one of you opens shows as read for the team. That is deliberate for a small team working one queue, but it does mean the inbox is not a per-person to-do list.
How is this different from the Airbnb and Vrbo inbox page?
That page is about collapsing two platforms into one screen. This one is about what happens after that, several properties, more than one person answering, and needing to control who can see what. If you are a solo host on two channels, start there.
What does it cost?
Team access and permissions are free. Pro at $10 AUD per listing per month is what connects Airbnb and Booking.com directly, which is what brings their guest messages into the inbox, on free, the inbox carries your direct-booking conversations.