Start with one channel rule
A small hotel does not need every message on every channel. It needs a consistent way to choose.
Use WhatsApp when the guest needs a quick answer or coordination close to the stay: arrival time, directions, a pickup update, a short in-stay request or confirmation that the team received something. It works best when a person is genuinely watching the conversation.
Use email when the message is longer, contains several details, or should remain easy to search later. A full booking summary, policy document, invoice attachment or detailed group itinerary is usually clearer in email. Kiyo's guide to local payment methods also explains why payment instructions should name the method, amount, due point and confirmation step rather than rely on an ambiguous chat message.
Use the booking channel's message thread when the conversation changes a booking made there, concerns the channel's policy, or may be needed to resolve a dispute. Do not move a guest off that thread merely because WhatsApp feels faster. The applicable channel terms and the property's agreement control what must remain on-platform.
Use a phone call for immediate safety, access or welfare issues when chat would create dangerous delay. Follow the call with a short written note in the property record so the next shift knows what happened.
This rule makes templates easier to design. A WhatsApp template should not become a miniature policy document. It should tell the guest what matters now, ask for the next useful detail, and make ownership clear.
Before choosing software, answer the real operating questions: which number is used for guests, who owns it, which message types need email instead, and where the next shift records an unresolved promise.
Put guest conversations and team handover in the right places
Guest messaging becomes difficult when every channel creates a separate private phone, tab or memory. Keep the guest conversation on the appropriate channel and keep internal staff coordination in a separate handover record.
- Keep WhatsApp replies with the guest's WhatsApp conversation.
- Keep OTA booking changes or disputes in the OTA thread when the channel requires it.
- Keep longer records and attachments in an email or system the guest can find again.
- Keep internal ownership, next actions and shift notes out of the guest thread.
- Record which staff member monitors each channel and how urgent issues escalate.
The practical gain comes from one routing rule and one handover habit, not from sending the same message everywhere. A guest conversation stays on its chosen guest channel; the team coordinates the work internally.
Know which WhatsApp rule applies
“WhatsApp” can refer to the consumer app, the WhatsApp Business app, or the WhatsApp Business Platform used through approved business integrations. Their operating rules and capabilities are not identical.
For the WhatsApp Business Platform, the current WhatsApp Business Messaging Policy allows free-form replies during a 24-hour customer-service window after the user's last message. Outside that window, a business can initiate a conversation only with an approved Message Template. If automation is used inside the window, the policy also requires a clear and direct way to escalate to a person.
That is a Platform rule. Do not turn it into a universal claim about every WhatsApp product. Before building a workflow, record which product and number the property actually uses, who owns the Meta business account, and whether the number is connected through an approved provider. Meta's own business-chat update also describes pre-approved templates for business-initiated Platform messages and ongoing controls on business messaging.
Consent and relevance matter even when a message is technically possible. Capture the guest's correct number and communication preference through an appropriate booking or check-in flow. Identify the property in the first message. Do not use a stay-related number for unrelated promotions without a lawful basis and the permissions required by the platform and applicable law.
Build a seven-moment message library
The useful unit is a stay moment, not a pile of clever phrases. Prepare a base message for each recurring moment, then train staff to replace every bracketed field and delete lines that do not apply.
Booking received
English: Hello [guest name], this is [staff name] from [property]. We have received your booking for [dates]. Your booking reference is [reference]. We will confirm [open item] by [time]. Is this the best number for arrival updates?
Bahasa Indonesia: Halo [nama tamu], saya [nama staf] dari [properti]. Kami sudah menerima reservasi Anda untuk [tanggal]. Nomor reservasinya [nomor]. Kami akan mengonfirmasi [hal yang masih terbuka] paling lambat [waktu]. Apakah nomor ini dapat digunakan untuk informasi kedatangan?
Human check: verify the booking, dates, guest consent, open item and promised time. Do not say confirmed when it is not.
Pre-arrival check
English: Hello [guest name], we look forward to welcoming you on [date]. Check-in starts at [time]. What is your estimated arrival time? If you need [pickup/parking/access help], please tell us by [cut-off].
Bahasa Indonesia: Halo [nama tamu], kami menantikan kedatangan Anda pada [tanggal]. Waktu check-in mulai pukul [waktu]. Perkiraan tiba Anda pukul berapa? Jika memerlukan [penjemputan/parkir/bantuan akses], mohon beri tahu sebelum [batas waktu].
Human check: confirm the local time, arrival date, actual service and cut-off.
Directions and access
English: Your destination is [property name]. Map: [verified link]. The entrance is [short landmark instruction]. If you arrive after [time], please [approved late-arrival step]. Reply here if the driver needs help.
Bahasa Indonesia: Tujuan Anda adalah [nama properti]. Peta: [tautan terverifikasi]. Pintu masuk berada [petunjuk patokan singkat]. Jika tiba setelah pukul [waktu], silakan [langkah kedatangan malam yang disetujui]. Balas pesan ini jika pengemudi memerlukan bantuan.
Human check: open the map link on another phone. Send a reusable access code only at the property's approved point.
Room-ready update
English: Hello [guest name], your room is ready. You may check in at [location] from [time]. Please bring [required item]. If your arrival changes, let us know here.
Bahasa Indonesia: Halo [nama tamu], kamar Anda sudah siap. Anda dapat check-in di [lokasi] mulai pukul [waktu]. Mohon membawa [dokumen/barang yang diperlukan]. Jika waktu kedatangan berubah, beri tahu kami melalui chat ini.
Human check: confirm room status in the current record before sending.
In-stay check
English: Good [morning/afternoon], [guest name]. Is everything in the room working as expected? If you need help, reply with the room number and request. For urgent safety help, call [number].
Bahasa Indonesia: Selamat [pagi/siang], [nama tamu]. Apakah semua fasilitas kamar berfungsi dengan baik? Jika memerlukan bantuan, balas dengan nomor kamar dan permintaannya. Untuk bantuan keselamatan yang mendesak, hubungi [nomor].
Human check: confirm that the monitored and emergency numbers are correct, and send at an appropriate time.
Request update
English: Hello [guest name], we have assigned your request for [request] to [team/role]. The next update will be by [time]. If the situation changes before then, reply here or call [number] for urgent help.
Bahasa Indonesia: Halo [nama tamu], permintaan Anda mengenai [permintaan] sudah diteruskan kepada [tim/peran]. Informasi berikutnya akan kami sampaikan paling lambat [waktu]. Jika situasinya berubah, balas di sini atau hubungi [nomor] untuk bantuan mendesak.
Human check: name a real owner and achievable update time. An update is not a promise that the issue will be solved by then.
Checkout and follow-up
English: Thank you for staying with us, [guest name]. Checkout is at [time]. Please [approved checkout step]. If something from your stay still needs attention, reply here and [role] will follow up. We wish you a safe journey.
Bahasa Indonesia: Terima kasih sudah menginap bersama kami, [nama tamu]. Waktu check-out pukul [waktu]. Silakan [langkah check-out yang disetujui]. Jika masih ada hal dari masa menginap yang perlu kami tindak lanjuti, balas di sini dan [peran] akan membantu. Semoga perjalanan Anda lancar.
Human check: confirm the balance, checkout method and open service cases. Ask for honest feedback without pressuring the guest for a positive review.
These are building blocks, not approved WhatsApp Business Platform templates. Platform templates require their own review and approval. A property should submit only the messages it truly needs, use the correct category, and keep variables understandable when read without internal context.
Make every template safe to personalize
The risk in a template is not sounding slightly formal. The risk is sending a confident false statement at scale.
Protect the fields that can change the guest's decision:
- booking status and dates;
- room readiness;
- amount, payment method and due point;
- cancellation or change policy;
- pickup availability and price;
- check-in location and time;
- access instructions; and
- the time of the next human update.
Do not let staff invent these from memory. Pull them from the approved booking record, current rate or policy source, and today's operating status. If a payment was made outside the booking flow, record it through the property's approved process before telling the next shift that the booking is paid.
Keep the language simple enough to translate without changing the promise. “We will update you by 5 p.m.” is safer than “This will definitely be fixed by 5 p.m.” The first commits the team to communication. The second may promise an outcome the team cannot control.
For Bahasa Indonesia, prefer direct hospitality language over literal software language. “Sudah kami terima” is often clearer than a stiff translation of “your ticket has been created.” Use the name of a team or role the guest will recognize, such as front desk or housekeeping, rather than an internal department code.
Give the inbox an operating rhythm
A shared number without a routine can be worse than one well-owned phone. Everyone can see the message, so everyone assumes someone else will answer.
Opening check
At the start of a shift, the assigned inbox owner should:
- Confirm that the device or connection is working.
- Read every unread conversation and every conversation marked for follow-up.
- Match each active guest to the correct booking and stay date.
- Check open requests from the previous shift.
- Assign or accept ownership of each item.
- Escalate safety, access, payment and booking-status issues immediately through the property's approved path.
The owner does not need to answer every question personally. The owner must make sure each question has a responsible person and a next update.
During the shift
Use four simple states: new, waiting on property, waiting on guest, and closed. If the tool does not support labels, use a shift log with the same four states. Do not mark a conversation closed just because someone sent a reply. Close it when the request has an answer, the guest has received the necessary next step, or a manager has accepted the unresolved case.
For a request that takes time, acknowledge it, name the owner and set the next update. A silent search for an answer feels like no action to the guest. A short truthful update keeps the expectation visible.
If several staff use the same conversation, sign with a first name or role when context could be confusing. Do not make the guest repeat the story every time the shift changes.
Shift handover
Handover should include only active or sensitive conversations, not a transcript of every greeting. Record:
- guest and booking reference;
- request or decision needed;
- last promise made to the guest;
- current owner;
- next update time;
- evidence or approval still needed; and
- escalation status.
This is also where messaging meets daily operations. A guest asking for an airport pickup is not merely a chat. It may create a driver task, a cost, an arrival dependency and a handover requirement. The message can close only when the operating task has an owner.
Closing check
Before leaving the shift, review conversations that are waiting on the property. Confirm that the next owner has accepted them. Check for guest messages hidden in archived or filtered views. Record anything that affects room status, access, payment or tomorrow's arrivals in the property's approved operational record.
If your team regularly loses details between chat and the booking calendar, the double-booking prevention guide is a useful companion because it applies the same principle: one current record, one owner and a visible exception path.
Decide what to automate last
Automation is useful after the property can run the manual routine reliably. Start with low-risk reminders whose source fields are trustworthy, such as asking for an arrival time. Keep a person in the loop for room readiness, payment disputes, cancellation decisions, complaints, accessibility needs and safety concerns.
Before enabling a scheduled message, test these cases:
- the guest changed dates;
- the booking was cancelled;
- two guests share a number;
- the arrival occurs after midnight;
- the room is not ready;
- a message field is empty;
- the guest already answered through another channel; and
- the service-window or template requirement changes what can be sent.
The safest fallback is not a vague automated message. It is to stop the send and ask a person to review the booking.
Choose tools only after the routine works
When comparing inbox or messaging tools, test them against the property's real workflow. Confirm which accounts can connect, which staff can see and own a conversation, how the next shift finds open work, how templates are approved, and what happens when a platform or connection is unavailable. A software screen does not remove the property's responsibility to confirm consent, policies, recipients, booking facts and urgent escalation paths.
A 30-minute setup for this week
Do not start by writing twenty templates. Run this short workshop with the people who answer guests:
- List the five questions received most often before arrival.
- Mark which belong in WhatsApp, email, the OTA thread or a call.
- Choose one owner for each shift and one manager escalation route.
- Customize the seven base messages above using verified property details.
- Test map links, numbers, time zones and late-arrival instructions on another phone.
- Role-play one room-not-ready case and one payment dispute.
- Review the shift log after seven days and fix one repeated handover failure.
That gives the property a small working system. Add automation only after the team knows which data is reliable and which exceptions need a person.
Build a guest-message routine your team can hand over
If you want help mapping this routine before choosing or configuring software, bring your current numbers, accounts, top guest questions and shift-handover method. Start with the operation your team actually runs, then decide which tools it needs.
