Fair warning: this post is about one of our own products, the BenStay AI concierge. I’ll spend the first half on the problem, because I think it’s worth understanding even if you never use what we built.
The problem is simple. A guest lands at Narita at 11pm, their phone is on 4% battery, and they want to know how to get into the building. They don’t want a ticket number or “we’ll reply within 24 hours”. They want the door code and the right exit from the station, in a language they can read.
We’ve automated a lot of our guest messaging. Door codes, directions from the station, luggage storage, trash separation, how the air conditioner works: a chatbot grounded in each property’s own information answers those in seconds, and it’s usually more accurate than a tired human at 11pm.
One group of messages still comes to me, though, and I don’t think that’s going to change: “Can we move our dates?”, “One of us can’t come anymore, can we get money back?”, “We arrived late because of a typhoon, can you refund the first night?” These are the ones that take real judgment, so this post covers how we handle them.
Every guesthouse operator I know eventually asks the same question: “Should I be using WhatsApp for guest messaging?” For a lot of markets, sure. For guests staying in Japan — including a large share of the domestic and Asian traffic that fills the shoulder season — the answer is almost always LINE, with Korean guests being the main exception, since they typically default to KakaoTalk instead.
A few years into running guesthouses in Tokyo, I noticed something that should have been obvious sooner: I was answering the same questions over and over, just from different people. “How do I get in?” “Where’s the nearest station exit?” “Can I leave my bag before check-in?” Different guests, same script, every single day.
Every host I know has the same complaint: the messages never stop. WiFi password at 11pm, “where’s the trash bin” at checkout, “can we check in early” three times a day. It feels chaotic and unpredictable — but when you actually sit down and categorize a few hundred guest messages, it isn’t random at all.
A few years into running guesthouses in Tokyo, I noticed something: the properties with the fastest message replies weren’t just getting better reviews — they were getting more bookings, even at the same price as similar listings nearby. That wasn’t a coincidence.
It’s 11pm. You’re about to sleep. Your phone lights up: “Hi, where is the entrance? I’m outside but I can’t find the door.” You’ve answered this exact question forty times this year.
The pre-arrival message is one high-impact operational habit a short-term rental operator can develop to reclaim their evenings. Spend an hour building a good one, set it to send automatically, and you can reduce a significant share of inbound guest messages before they arrive.
Every June, I do a quiet mental checklist: rainy season is wrapping up, the summer booking rush is coming in — and typhoon season is right behind it. If you operate a short-term rental in Japan, typhoons aren’t a freak event you can ignore. They’re a recurring operational reality, and how you handle them shapes both your guest reviews and your bottom line.
Out of all the operational headaches I didn’t expect when I started managing short-term rental properties in Tokyo, garbage was near the top of the list. Not because it’s complicated — once you know the system, it’s fine — but because guests have absolutely no idea, and the consequences of getting it wrong land on you, not them.
Running a guesthouse in Tokyo means your next guest might be checking in from Seoul, Shanghai, Sydney, or Stuttgart — sometimes on the same day. Japan’s inbound mix is genuinely diverse, and that’s one of the things that makes this business interesting. It’s also one of the biggest operational headaches for small operators who don’t have a multilingual customer service team on payroll.
Running a guesthouse in Tokyo means fielding messages in four languages before breakfast. After a few years of trial and error, I’ve come to believe that which platform you use matters almost as much as what you say — maybe more, because if a guest can’t reach you on their preferred channel, it doesn’t matter how good your reply would have been.
Running a guesthouse in Japan means fielding the same questions over and over, in multiple languages, at all hours. What time is check-in? Where’s the nearest convenience store? How do I get to the property from the station? Can I leave my luggage after checkout? These aren’t complicated questions — but when they arrive at 2 AM in Mandarin and you’re asleep, the guest experience suffers. And in a business built on reviews, a slow reply is a costly one.
We built an AI-powered chatbot for our guesthouse because we were drowning in repetitive messages across too many channels, in too many languages, with too few staff. Here’s what we learned — and what guests actually want to know.