Why we are building TripCorpus
Every ryokan operator I've spoken with has shared the same exhaustion:
“We get the same question 20 times a day.” “An English inquiry comes in, we run it through DeepL, write back, run it through DeepL again. Daily.” “Every time someone asks for the Wi-Fi password we replace the lobby sign.”
The pure volume of human-handled information transfer is too high. This is not “polite hospitality” — it's operational waste accumulating.
What TripCorpus solves
TripCorpus lets ryokans and hotels offload 80%+ (empirically) of the inquiries they handle daily.
Concretely:
- Drop in your URL — our AI reads your site and drafts a structured FAQ
- Public FAQ pages in JA / EN / ZH / KO / VI / TH go live immediately
- Guest questions on web chat and LINE Official Account get instant answers
- Questions the AI doesn't know get queued for owner approval
The most important design choice: AI cannot lie before a human approves it
The biggest failure mode for AI chatbots is confidently wrong answers. A guest asking about check-in time, getting a fabricated “3 PM”, and arriving at noon to find the lobby empty.
TripCorpus does not allow the AI to generate answers it “guesses might be true.” It only ever responds from owner-approved FAQs or owner-approved drafts.
This may feel restrictive, but hospitality guests value accuracy above all. A wrong check-in time ruins a day.
Next
We're currently recruiting pilot ryokans in Kyoto, Nara, Okinawa, and Hakone. Six months free.
Get in touch if interested.