When a guest from Shanghai books a ryokan in Hakone six months before their stay, the booking itself goes through an OTA. Every question they have between booking confirmation and check-in day, however, tends to land on WhatsApp. This is not an assumption. Among inbound travelers from China, Southeast Asia, and much of Europe and South America, WhatsApp is the primary personal messaging channel. It is where they expect to reach businesses directly.
Most small Japanese hotels and ryokan are not yet on WhatsApp in any organized way. Some owners use a personal WhatsApp number informally. Some rely entirely on the OTA messaging system, which adds latency and removes the direct relationship. The properties that have set up WhatsApp Business correctly, with a verified account and a trained response layer, have a genuine communication advantage during peak season when their competitors are buried in unanswered messages.
This guide covers the actual setup sequence, the decisions that matter, and the points where most properties run into trouble.
WhatsApp Business vs the WhatsApp Business API: knowing which one you need
There are two versions of WhatsApp for businesses. The WhatsApp Business App is a free mobile app similar to the consumer version, designed for very small operations. It allows one user at a time, works from a single phone number, and has basic auto-reply capability. For a single-staff guesthouse handling a modest volume of foreign messages, it works. For anything with more than a few hundred monthly conversations, or with multiple staff who need access, it runs into limits quickly.
The WhatsApp Business API is a different product. It connects to WhatsApp's infrastructure through an approved API provider, allows multiple agents or systems to access the same number, supports bulk messaging (for confirmations and pre-arrival messages), and integrates with automation tools. This is the route for any property that wants to handle multilingual messages at scale, or connect WhatsApp responses to a FAQ-based AI concierge.
The tradeoff is cost and setup complexity. The API requires a Meta Business account, a phone number that is not already connected to a personal WhatsApp, verification of the business, and an API provider or integration layer. The approval process is not instant. Allow two to three weeks minimum before a planned peak season, not two to three days.
The phone number decision
This is where most properties make a mistake they later have to undo. WhatsApp links a channel identity to a phone number. Once a number is used for personal WhatsApp, it cannot simultaneously be used for WhatsApp Business API without migration, and migration removes the existing chat history.
The clean approach: obtain a dedicated business SIM or use a VoIP number for the WhatsApp Business API line. Keep personal numbers separate. If you are inheriting an existing WhatsApp Business App setup that used a front desk number informally, the migration path exists but requires carefully timing it before you go live with the API so no conversations are lost.
Document the number you register and who has access credentials. In a small operation, this sounds obvious, but staff turnover at the front desk creates access problems when the only person who knows the verification code is no longer working at the property.
Setting up a multilingual response layer
WhatsApp itself is language-agnostic. The channel carries whatever language the guest sends. The challenge is on the response side: your property can only respond accurately if it can understand the incoming message and generate a reply in the guest's language.
The bare minimum approach is to use a human translator service or rely on Google Translate for outgoing messages. This works for low volume but breaks down during peak season when messages arrive in four or five languages simultaneously and need responses within a few minutes to meet guest expectations.
The more sustainable approach is to connect your WhatsApp Business API number to an automated concierge that handles incoming messages in any language. The key distinction here is between generic machine translation (which converts text but does not apply your property's specific knowledge) and a trained concierge that answers from your FAQ library. When a Korean guest asks whether the private onsen requires advance reservation, the correct answer involves your specific booking rules, not a translation of a generic hospitality phrase.
Building this layer takes some preparation. You need to define which question categories the automated system handles on its own, which ones trigger a flag for staff review, and what the escalation threshold is for messages that need immediate human response. The preparation time is roughly the same as writing a thorough FAQ for your booking page, because that is essentially what you are building.
Message template requirements for outbound communication
If you plan to use WhatsApp to send outbound messages to guests (confirmation reminders, pre-arrival instructions, checkout follow-ups), Meta requires that these be sent using approved message templates. Templates must be submitted and approved before use. They cannot contain promotional content in the initial message. Approval typically takes 24 to 48 hours.
This means the pre-arrival sequence you want to send three days before check-in needs to be planned and approved well in advance of peak season, not drafted the week before Golden Week. The template process is a Meta compliance requirement, not a tool limitation. Properties that have their templates approved and their pre-arrival sequence ready send cleaner, more professional pre-arrival messages than those scrambling to draft them mid-season.
What WhatsApp does not replace
Setting up WhatsApp correctly solves the foreign-guest channel problem for inbound travelers from regions where WhatsApp is dominant. It does not solve it for guests from Japan (who use LINE) or from Korea and Taiwan (where KakaoTalk and LINE are more common than WhatsApp). A complete multilingual channel strategy for a Japan inbound property typically combines WhatsApp for guests from China, Southeast Asia, Europe, and the Americas with LINE for domestic and Northeast Asian guests.
WhatsApp also does not replace the PMS or OTA messaging systems for booking management. The channel handles direct guest communication before and during the stay. Reservation changes and cancellations typically still flow through the OTA or your booking system. The cleaner the handoff between these systems, the less confusion your front desk team has about which conversation is authoritative for a given guest interaction.
A realistic timeline for first setup
Allow four weeks from starting the Meta Business verification process to having a functioning WhatsApp Business API line with a basic automated response layer in place. Week one: Meta Business Manager setup and phone number registration. Week two: API provider connection and business verification completion. Week three: FAQ library drafting and training the automated concierge. Week four: test conversations in target languages, escalation threshold calibration, template approval for pre-arrival messages.
The properties that set up in a rush before peak season miss the testing phase and go live with a FAQ library that has gaps or tone issues in certain languages. Testing with native speakers in Chinese, Korean, and English before you go live is not optional if you want the guest experience to match the quality of the physical hospitality you provide.