Where Each Conversation Lives: Four Platforms, Four Inboxes

Four channels means up to four inboxes, and a guest who writes on two of them still expects one answer. Knowing where a thread actually lives is what stops the double reply.

Last updated: October 26, 2026

Four channels means up to four inboxes, and only one of them sits inside LOCALSBNB. Airbnb messages arrive in the LOCALSBNB inbox; Booking.com, Agoda and Trip.com messages stay in each platform's own back office. Nothing travels between them unless you carry it. Knowing which thread lives where is what stops the double reply, and the silence that comes after it.

Key Takeaways

• Each channel keeps its own inbox. A thread lives with the reservation inside the platform it arrived on, not in a shared pool.
• LOCALSBNB connects Airbnb only. An Airbnb message lands in the LOCALSBNB inbox; the other three stay where the guest wrote them.
• Reply windows belong to the platform. They're set per channel and they change, so read the current wording instead of trusting a memorised number.
• One guest can hold two threads. A second enquiry on another channel opens a new record, and that's where double replies come from.
• A fixed sweep beats a merged view. Answer in the same order twice a day, and leave a line saying where each answer was given.

Which inbox a thread lives in

A message thread isn't a free-floating conversation. It's attached to a reservation inside the platform where the guest wrote it, and that platform keeps the record. Airbnb threads sit with Airbnb reservations. Booking.com threads sit with Booking.com reservations. Agoda and Trip.com work the same way. The guest sees one thread. You see whichever one your login opens.

That's the first thing to get straight about your own setup. LOCALSBNB's inbox connects Airbnb today. An Airbnb enquiry arrives there, beside the reservation it belongs to, so the message and the booking sit in the same place. A Booking.com, Agoda or Trip.com message doesn't arrive there at all. It waits in that platform's extranet or partner app until you go and open it.

The rule that follows is short. Before you answer anything, look at where the message came from. If it came through Airbnb, you can answer it inside LOCALSBNB. If it came through another channel, you answer it in that channel's own back office, and your reply stays there. The other three inboxes aren't merged into one view, and planning as if they were is how messages go quiet for a day.

It's worth saying plainly, because most hosts arrive assuming the opposite. Four channels doesn't mean one place to look. It means four places, one of which happens to sit inside the software you already have open.

The window that shapes a reply

Every channel publishes its own expectations about how quickly a host should answer, and those expectations are set by the platform rather than by you. They also change. Whatever a platform states today is what applies today, and a figure copied into a notebook a year ago may no longer match the current terms as published. The habit worth building is to read the current wording for the channel you're on, not to trust the number you remember.

What doesn't change is the mechanics. The clock starts when the message arrives, not when you notice it. The record of how fast you answered sits with the platform, not with you, and it keeps running while you're asleep, driving, or turning a unit over. That's the part hosts underestimate. A message that lands overnight has already spent hours inside somebody else's measurement before you've read a word of it.

So design around the record instead of the rule. If a channel measures your first reply, make the first reply a real one, even when it's short: acknowledge the question, give the one fact you're certain of, and say the rest is coming. Keep the answer in the thread rather than moving the conversation to email, because a reply that leaves the platform may not count where the counting happens. And if a question genuinely needs a rate check or a call to your cleaner, say so in the thread before you go and do it. The guest reads that as competence. Silence reads as a decision not to reply.

One thread, two channels

Guests don't think in channels. The person who booked on Airbnb last spring may message you on Booking.com about a different week, or write to two platforms at once because they can't remember where they booked. Each message opens its own record, in its own inbox, with no visible link between them. From the platform's side, those are two unrelated guests who happen to share a name.

Two things tend to go wrong. The first is the double reply. You answer the Airbnb thread, then answer the same question on Booking.com without realising it's the same person, and the guest receives two answers that may not agree. The second is quieter and more common. You answer on one channel, assume it's handled, and the other thread sits unanswered while its own clock runs.

Both get cheaper to avoid with one habit: when you answer, leave a line in the other place. If a guest wrote on two channels, put a note in the second record saying where the answer was given and what it said. One line is enough. The Airbnb side is easier, because localsbnb.com keeps that thread beside the reservation it belongs to, so the note lands where you'll look next time. The other side needs the same sentence, written inside the platform that owns the record.

Telling the guest is the last step, and most hosts skip it. One line does the work: you've answered on Booking.com as well, so they have it in both places. Without it, a guest with two threads waits patiently on the one you consider closed.

A daily sweep that takes five minutes

A single inbox invites you to check whenever a notification appears. Four separate inboxes need a routine instead, because there's no badge count that tells you the truth about all of them.

The routine is a sweep, run at the same two points every day: once when you start, once before you stop. Same order each time. Airbnb first, inside LOCALSBNB, because that's where most of your threads will be. Then Booking.com, Agoda and Trip.com in whatever order you always use, so no channel gets skipped because you started at the bottom and ran out of attention.

Inside each one, work in two passes. Unanswered messages first, oldest at the top, because those carry a clock. Then the threads you've already answered where something is still owed: a rate you promised to check, a late check-out you said you'd confirm, an arrival time you're waiting on. Those are the messages that turn into complaints, and they're invisible in an unread count.

The sweep itself takes five minutes. The deciding takes longer, so decide once and reuse it. Which questions you answer immediately. Which ones wait for a rate check. Which ones don't belong in a thread at all because they need a phone call. Keep a line of record per message too, with the date, the channel and what you promised, because the promise is what the guest will quote back at you, in whichever inbox they choose.

FAQ

Do all four channels' messages arrive in one place?

No. LOCALSBNB's inbox connects Airbnb today, so Airbnb threads land there beside their reservations. Booking.com, Agoda and Trip.com messages stay in each platform's own back office, and you answer them there. Treat the setup as four inboxes with one routine, not one inbox with four sources.

How fast do I need to answer?

That's set by each channel and published in its own terms, and it changes over time. Read the current wording for the channel you're on rather than relying on a number from last year. Then build a routine that gets a real first reply out early, because the measurement starts when the message arrives.

What if a guest writes on two channels about the same stay?

Answer once, in the channel they'll check, and leave a note in the other record saying where the answer was given and what it said. Then tell them you've answered in both places, so they stop waiting on the second thread.

Four inboxes isn't a problem one clever tool solves for you. It's a map you keep in your head until a routine carries it for you. If you'd rather spend those five minutes on the reply than on remembering where it belongs, localsbnb.com keeps the Airbnb thread next to the reservation it came from, and leaves the other three where they already are.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. How quickly a channel expects a reply, what counts as answered and how message records are kept are set by each platform and change over time. Confirm the current terms of each platform you use before you rely on them.