Collect stay requests, send pre-arrival messages, and route guest questions to the right hotel team on WhatsApp. Your staff or connected booking system confirms availability and reservations.
In one line
Use WhatsApp to collect booking enquiries, send reminders, and route guest requests. Reservations confirms availability and rates. Reception and service teams handle requests that need a person.
Industry guide reviewed .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
See how a booking enquiry passes between reservations, reception, and finance. Staff confirm room availability and payment before sending a guest a confirmation.
STAY 1842
Courtyard room
Direct enquiry · Bengaluru
Operating boundary
Treat each stage as an operating contract. Decide what Waaru may collect, what system or person confirms the answer, and what should stop or leave the workflow.
Use the hotel's connected WhatsApp Business number and approved teammate access. Keep service communication and later marketing permission as separate purposes.
Guest replies, structured Flow answers, contact fields, conversation history, and data returned by a connected source within its granted permissions.
Logic Flow can update contact fields, assignment, conversation state, and approved messages. Creating a Razorpay payment link or calendar booking is not exposed as a Logic Flow write; staff or a separate authenticated connected-app action completes that step.
Inbound messages, Flow submissions, human assignment, and verified provider events can move the journey. A copied spreadsheet row is not automatically current availability.
Name the owner for reservations, payments, arrivals, and in-stay requests. Test changes, cancellations, duplicate events, late replies, and after-hours handoff before publishing.
Waaru should not invent a room, rate, upgrade, refund, or service-recovery promise. Keep judgement and exceptions with authorised hotel staff.
Unknown requests and failed actions stay in the shared inbox with the guest's answers and booking reference so a person can continue without restarting the conversation.
The problem
A guest can move through reservations, reception, housekeeping, maintenance, transport, dining, and finance during one stay. When those teams use separate inboxes or copy details manually, the guest repeats dates and room information while staff lose the original promise.
Enquiry
Ask for check-in, checkout, number of guests, property, and room preference with buttons or a WhatsApp Flow. Confirm what was received, then route it to reservations. A Flow can make the intake easier, but availability and final price should still come from a verified source or an authorised person. See how the same structured pattern is built in the visual flow builder.
Operator worksheet
Start with one property and one booking path. Write down the minimum information reservations needs, the person or system allowed to confirm each commercial fact, and the exact point at which the conversation returns to a guest. Use that list to test the workflow before guests use it.
Confirmation
After staff or an integrated property system confirms availability, send the approved rate, cancellation terms, booking reference, and the next payment step. If a deposit is required, authorised staff can create a hosted link through the connected Razorpay action and share it in the thread. The conversational Logic Flow does not create the link. Verify the merchant, amount, expiry, and provider event before offering this path to guests.
Before arrival
Directions, check-in time, identification requirements, parking, transfer options, property rules, and the contact point for changes belong in a concise pre-arrival message. Keep the booking reference attached to the conversation. If the guest changes the arrival time or asks about an exception, reception should see the original stay details before replying.
During the stay
Housekeeping, maintenance, transport, dining, and late-checkout requests have different owners and response expectations. A deterministic workflow can collect the room and request type, then place the thread in the shared inbox for a person to accept. An urgent or unclear request should leave the structured path early instead of waiting behind a routine task.
After the stay
A checkout acknowledgement, invoice notice, or feedback request should state its purpose plainly. A previous stay does not create permanent marketing permission. Store the source and purpose of consent, keep promotional audiences separate from service updates, and suppress future marketing immediately after opt-out.
Operations
Start with the hotel's own baseline rather than an industry conversion promise. Review time to first useful response, requests waiting without an owner, booking enquiries that reach a verified decision, failed payment actions, pre-arrival replies, in-stay acceptance time, and opt-outs by message purpose. These measures reveal workflow gaps without pretending that messaging alone created a booking.
Yes. A WhatsApp Flow or guided conversation can capture dates, guests, property, and room preference. Availability, price, payment, and confirmation should come from a verified system or authorised staff member.
Only when a tested connected source owns current availability. Otherwise the safer workflow collects the request and assigns it to reservations rather than inventing a room or rate.
Yes, but the fields and owners should match the property. A hostel may need bed type and check-in rules, while a serviced apartment may need length of stay, housekeeping cadence, and deposit details.
Yes. The workflow can collect room, request type, and urgency, then assign the conversation to the relevant human queue with the complete thread visible.
Yes, by sharing a hosted link created through the connected Razorpay action. That creation is an authenticated staff action, not a conversational Logic Flow write. Verify the merchant, booking reference, amount, expiry, and payment-event handling before launch.
Only when the guest has an appropriate marketing opt-in and the message follows WhatsApp policy and applicable law. A service interaction or past stay does not automatically create marketing consent.
Research notes
These sources define the messaging and structured-form boundaries. Your property remains responsible for its rates, availability, guest policy, and legal review.
WhatsApp's Business Messaging Policy governs user control, message purpose, acceptable business use, and opt-out handling.
WhatsApp Business Messaging Policy · Accessed 20 August 2026
Meta documents WhatsApp Flows as structured experiences that open inside WhatsApp.
Meta for Developers · Accessed 20 August 2026
WhatsApp workflow template library
Choose a hotel workflow and download a blank planning worksheet.
Hotel booking enquiries and chatbot intake
Collect booking details, check availability and route exceptions to reservations.
Hand over hotel guest requests on WhatsApp
Keep hotel guest requests clear across shifts with an owner, an accurate status and a useful handover note. Avoid treating an acknowledgement as completion.
Hotel pre-arrival WhatsApp messages: useful examples for guests
Prepare helpful hotel pre-arrival WhatsApp messages about directions, check-in, arrival requests, and staff contact. Includes examples and a send checklist.
Test hotel enquiry scenarios
Check unavailable rooms, uncertain answers and staff handoff.
Hotel deposits with Razorpay
Map amount, expiry, payment events, and the unpaid path.
Google Calendar integration
Review booking permissions and failure handling.
Human handoff
Preserve the guest context when staff take over.
Indonesia market guide
Adapt language, ownership, and operating hours for Indonesia.
WhatsApp Business API
WhatsApp opt-in rules
Map one property journey before automating every request.
Bring the current enquiry, booking, arrival, and handoff steps. We will identify the first workflow worth publishing.
