Your best guests, booking direct — in 10 seconds.
Returning guests tap once and the bot already knows their party, plan and check-in time. A multilingual concierge answers “is late check-in ok?” at one in the morning.
from ¥6,800/mo excl. tax · 30-day free trial · no minimum term · no commission on a stay
The trial clock starts when you connect LINE, not when you sign up. Importing your plans and room types costs no trial days.
Dotted figures are placeholders: they are not claims until the numbers are ours to make.
What one rebooking is worth
Not a slogan — your own numbers. A guest who already stayed with you costs an OTA nothing to find, and costs you commission every time they go back through one.
Arithmetic, not a forecast. It assumes the stay happens either way and only the channel changes — which is exactly the case for a guest who already knows your name. It does not assume you leave the OTAs; you should not.
What it is like now
Six things every property with repeat guests recognises.
- Your repeat guests book through an OTA out of habit, and you pay commission to reach someone who already knows the room.
- The newsletter goes out to everyone and about 8% of it is opened, so last autumn’s guests never hear that the maples are turning.
- The front desk answers the same twenty questions every week — parking, late check-in, allergies, whether the bath is private, whether a two-year-old is welcome.
- There is no way to reach only the guests who came last November on the kaiseki plan, because nobody kept the stay history anywhere you can query.
- Inbound guests message in five languages, at hours when the only person on site is the night porter.
- The post-stay survey is a paper sheet in a drawer, so what a guest told you about the pillow never reaches next year’s offer.
Friend-add once, rebook forever.
A guest adds your LINE Official Account at check-out. From that moment they have a direct channel that needs no app, no account and no password — and you have a guest you can write to again.
Behind the friendship sits a guest profile: party size, the room type and plan they chose, their check-in habits, dietary notes, language, and the labels their post-stay survey produced. It is what makes ten-second rebooking possible, and it is what makes a seasonal message land — you write to the forty guests who came last November, not to the whole friend list.
Availability and rates come from your site controller through the engine, so the bot sells the same room at the same price your OTA listings show. And when the question is not about a stay at all — the last bus, the bath rules, whether a two-year-old is welcome — the concierge answers it from your knowledge base, in the guest’s language, at whatever hour it was asked.
Availability, rates and plan definitions, synced through the engine so the bot never quotes a room you have already sold. Connect it here and the status is honest either way.
One QR on the check-out folder, the room card and the confirmation email. No app to install, no password to reset, and the guest keeps the thread — so next November your message arrives in a conversation they already recognise.
Twelve things it does
Each one is an outcome and the mechanism that produces it. Nothing here is “powerful”.
A returning guest taps the rich menu and the bot has already filled in the party size, the room type, the plan and the usual check-in time from their last stay. Two taps and the stay is held — no card, no form, no account.
Plans render as a LINE Flex carousel with a photo, the per-person price, what the meal is, and what the cancellation policy actually says. The guest compares two room types in the chat instead of leaving for a comparison site.
Availability and rates come from your site controller through the engine, so the bot quotes the same room and the same price your OTA listings show. Connect it below; until it is connected the bot quotes from the plan table you type in and says so.
Access and parking, the last bus, whether late check-in is possible, allergies, cots, whether children are welcome in the bath. Answered from your own knowledge base, at 1 am, in the guest’s language, with a handoff when the answer is genuinely a judgement call.
Towels, an extra futon, a later dinner, a taxi for the morning. The guest picks from a request list, it lands on the right staff channel with the room number attached, and the acknowledgement comes back into the guest’s chat — so nobody has to ring the desk to check.
Twelve places you would actually send a guest, with walking times, opening hours and the note about which one closes on Tuesdays. Written by you once, offered by the bot at the moment a guest asks what to do before dinner.
The bot answers in the language the guest wrote in — Japanese, English, Chinese or Korean — and records the preference on the guest profile so the pre-arrival message goes out in the same language. Staff always see the conversation in Japanese alongside.
Season, plan, room type, party size and survey labels are stored on the guest profile, so “last November, kaiseki, party of two” is a segment you can send to. It feeds Segment Campaigns rather than duplicating it.
Five questions the morning after check-out. Each answer maps to a label on the guest profile — firm pillow, no shellfish, prefers the ground floor — and the bot uses them next time instead of asking again.
One message on the date the guest gave you, with a plan that fits the party they usually travel with. Sent as a single push per guest per year, so it costs one message and reads as a note rather than a broadcast.
Names, passport details for inbound guests and an arrival time, filled in a LIFF form on the way here and waiting at the desk. The paper still gets signed; the typing does not happen while the guest stands in the entrance with their shoes off.
When the answer is a judgement — is the open-air bath safe for a toddler, can we hold a room for a funeral — the bot stops, says it will not guess, and passes the thread to staff with a one-paragraph summary and the guest’s profile attached.
How to start
Four steps. The long one is importing your plans, and the site controller does most of that for you.
Elsewhere this is a six-week onboarding, because someone retypes a rate table. Two weeks is normal here for exactly one reason: plans and room types import.
Play it as a guest
Four real conversations at Yumoto Kagetsu, a 24-room onsen ryokan. The left pane is the guest’s LINE screen; the right is what the property sees while it happens.
Type anything off-script and the bot will say it would rather not guess and hand you to a person. That is the real behaviour, not a demo limitation. Open the full-height demo.
What the guest actually sees
Seven screens, from the QR on the check-out folder to the survey the morning after.
Pricing
By room count, because a 9-room ryokan and a 200-room hotel are not the same product. Every price excludes consumption tax.
| Property size | Monthly | Included |
|---|---|---|
| 1–9 rooms | ¥6,800/mo | 1 property, 10,000 AI replies/mo, stay-history segments, post-stay surveys, all five LIFF pages |
| 10–29 rooms | ¥9,800/mo | Everything above, plus request routing to up to 5 staff channels |
| 30–49 rooms | ¥13,800/mo | Everything above, plus unlimited staff channels and per-floor routing |
| 50 rooms and above | Custom | Quoted on room count and the number of properties. Talk to us. |
All prices excl. tax, in Japanese yen. No minimum term — monthly, cancel from the account page, service runs to the end of the month you have paid for. No commission on any stay the bot books, at any tier.
One flat plan at ¥8,800/mo covers any property up to 49 rooms. Worth taking if your room count sits near a tier boundary or you would rather not re-tier when you convert an annexe.
- Site-controller sync — ¥3,000/mo
- Additional property — ¥5,000/mo
- +1,000 AI replies — ¥1,000/mo
- Done-for-you setup — ¥29,800 once, waived on the launch offer — confirm the end date before quoting it
Separately, and never through us. Almost everything the concierge does happens inside the free 24-hour reply window. The pre-arrival note is one push per stay; a seasonal campaign is one push per guest in the segment. At 24 rooms that sits inside LINE’s free or Light plan — check yours with the calculator.
Built for these
The default template is the onsen ryokan. The others change the vocabulary, the plan table and the four demo conversations.
Case studies
Three shapes of property. The metrics are placeholders until a property lets us publish theirs.
Rebooking moved out of the OTA funnel for guests who had already stayed once. The rich menu Book cell did most of it; the concierge answered the parking question that used to arrive by phone at 07:30.
Property name and figures pending the property’s written consent.
A seasonal message to last year’s autumn guests, sent to a stay-history segment rather than the whole friend list. One push per guest, and the plan in the card was the one they had actually booked before.
Property name and figures pending the property’s written consent.
Weather, what to bring, whether dogs are allowed and what time the fire pit lights. All answered by the concierge from a knowledge base written once, in four languages, out of hours.
Property name and figures pending the property’s written consent.
Questions
Thirty days. Your own guests. Your own numbers.
Import your plans, connect LINE, and put the QR on the check-out folder. If the guests who already know you do not come back through it, cancel — there is no term to run out.
Scanning it will add the demo account as a LINE friend and drop you into the ryokan concierge. Until the channel is provisioned the browser demo above is the same script.