Forty-eight hours before arrival, your guest gets a WhatsApp from the hotel. They confirm an evening flight, ask for a late check-in, pick a high floor, and say they need a baby cot.
Your front desk never sees it.
The chat lives on someone's phone. The reservation in the PMS still shows a blank special-requests field. Housekeeping makes up a standard room. At 11 p.m. the guest arrives tired, and the night team rebuilds the stay from scratch.
That is not a messaging problem. It is a write-back problem.
Pre-arrival WhatsApp only pays for itself when what the guest says becomes what the property prepares. This post is a practical map: what to collect before arrival, what must land in the PMS, how opt-in and templates keep you compliant, and how to tell a real ops loop from a pretty chat that dies in a thread.
Why does pre-arrival WhatsApp fail in most hotels?
Most properties already "do WhatsApp." Guests message the reservations number. Someone replies when they can. A few teams paste a welcome paragraph from a notes app.
The failure modes are predictable:
| What happens | What breaks on arrival |
|---|---|
| Message sits on one phone | Next shift cannot see preferences |
| No link to the reservation ID | Front desk cannot find which booking the chat belongs to |
| Preferences typed in chat only | Housekeeping, F&B, and engineering never get the ask |
| Manual copy into PMS "when free" | Free never comes on a busy day |
| Marketing blast with no reply path | Guest replies; nobody owns the answer |
Email pre-arrival packs suffer the same fate. WhatsApp at least reaches guests on the channel they already use to message the hotel. That reach is wasted if the answer never becomes a PMS note, a room block flag, or a task for the right department.
What should a hotel collect before the guest arrives?
Keep the ask short. Guests will finish a five-minute thread. They will abandon a form that feels like immigration.
Collect only what changes prep or service:
| Field | Why it matters | Where it should land |
|---|---|---|
| Estimated arrival time | Night desk, room assignment, late check-in readiness | Reservation note + arrival-time field if your PMS has one |
| Early / late check-in ask | Inventory, rate, and housekeeping sequence | Special request + optional charge flag |
| Room preferences (floor, quiet, connecting) | Assignment and upgrades | Profile / reservation preferences |
| Occasion (anniversary, birthday, honeymoon) | Soft touch and F&B upsell | Special request + F&B task |
| Airport transfer / parking | Ops roster and revenue | Package or add-on on the folio path |
| Dietary or accessibility needs | Safety and dignity, not a nice-to-have | Hard-coded note visible to all shifts |
| Payment or deposit status | No-show risk and front-desk friction | Folio / payment state, never only in chat |
Do not collect government ID over an unsecured free-app chat as a casual habit. If you run digital pre-check or Aadhaar-style verification, do it through a controlled flow with clear consent, not a photo dump into a shared handset.
What does "writes back to the PMS" actually mean?
Write-back means the guest's answer becomes structured data on the reservation (and ideally the guest profile), not a screenshot in a WhatsApp gallery.
A working loop looks like this:
- Reservation is confirmed in the PMS (direct, OTA, or voice agent).
- At a set time (usually T-72h or T-48h), an approved WhatsApp template fires from your hotel's Business API number.
- Guest replies inside the service window (or taps buttons on an interactive template).
- The platform maps each answer to reservation fields and notes.
- Front office, housekeeping, and F&B see the same truth in the PMS on the morning of arrival.
- Exceptions (VIP, complaint, complex group) escalate to a human with the reservation context attached.
If step 4 is "someone will update the PMS later," you do not have pre-arrival automation. You have a chatbot with amnesia.
How do opt-in and templates keep this legal and deliverable?
In India, and under Meta's WhatsApp Business rules, outbound hotel WhatsApp is not "blast whoever booked."
Practical rules of thumb for operators:
| Rule | Ops meaning |
|---|---|
| Clear opt-in | Capture consent at booking (website checkbox, voice agent disclosure, OTA follow-up that invites the guest to message you first) |
| Approved templates | Pre-arrival utility messages need Meta-approved templates before you can open the conversation outside the customer-care window |
| Utility vs marketing | Arrival time, check-in info, and reservation updates are utility. Upsell bundles are marketing and cost more, with tighter consent |
| Verified business number | Guests trust a named hotel profile, not a personal mobile that changes every season |
| DPDP-aware handling | Store only what you need; restrict who can export chat and ID images; define retention |
The free WhatsApp Business app cannot run this loop cleanly across shifts. Shared ownership, template automation, and PMS hooks need the Business API (Cloud API via an approved provider or a hospitality agent that already speaks hotel ops). If you are still deciding which WhatsApp product you run, treat that as a separate checklist before you promise pre-arrival magic.
What does a good T-48 hour thread look like?
Tone stays short, warm, and operational. No novel. No emojis that look like a travel influencer.
Example skeleton (adapt to your brand and approved templates):
- Confirm name, dates, and room type already on the reservation.
- Ask estimated arrival time (button choices beat free text when you can).
- Offer one clear preference question (floor / quiet / early check-in).
- Offer one optional add-on (transfer, late checkout, celebration setup).
- Confirm that answers are saved to their booking and the front desk will see them.
- Give a human escape hatch ("Reply HELP to talk to the desk").
When the guest finishes, the PMS note should read like a colleague left it: arrival ~21:30, high floor preferred, baby cot required, transfer declined. Not "see WhatsApp."
How does this connect to voice, payments, and the front desk?
Pre-arrival is one chapter of the same guest file.
Hotels that close the loop usually run four moments on one stack:
| Moment | Guest action | System action |
|---|---|---|
| Booking | Calls or messages to reserve | Live availability check, rate quote, reservation create |
| Pay | Confirms hold with UPI / card link | Payment status on folio; room blocked on success |
| Pre-arrival | Answers WhatsApp preferences | Write-back to reservation notes and tasks |
| Arrival | Walks in or late check-in | Desk sees the same record night and morning shifts use |
HeyKoala is built for that loop, for hotels only: voice and WhatsApp against live PMS inventory, UPI and card payment links inside the conversation, automatic write-back, and workflows trained on your SOP. Independent hotels can go live in about 10 minutes, integrated properties in days, and enterprise groups in weeks. The point is not another inbox. It is one reservation record that stays true from the first inquiry to the first morning coffee.
Across HeyKoala hotels, 95% of guest calls get answered, about 80% of routine front desk work is automated, and a property recovers around $126K a year that used to leak to missed calls and OTAs. Pre-arrival write-back is where that shows up as a calmer lobby, not only a fuller reservations log.
FAQ
Do OTA guests get pre-arrival WhatsApp too?
Yes, if you have a reachable mobile number and a lawful way to open the thread (guest messages you first, or you use an approved template with proper consent). Many hotels use pre-arrival as the moment to invite a direct relationship for the next stay. Do not bait-and-switch rates in that first utility message.
What if the guest never replies?
Your default PMS reservation still stands. Send one reminder inside policy, then stop. Silence is not consent for marketing follow-ups.
Can housekeeping see WhatsApp?
They should not have to. They should see a clean task or reservation note in the PMS or your task board. Chat is for the guest. The PMS is for the building.
Is this only for big hotel chains?
No. Mid-market and independent hotels on cloud PMS platforms often ship faster because APIs and onboarding are simpler. Chains need tighter brand templates and multi-property governance, which takes longer, not different physics.
What should we measure in the first 30 days?
Template delivery rate, reply rate, percentage of arrivals with a non-empty preference or arrival-time note, early/late check-in requests captured before desk contact, and front-desk time spent re-asking questions you already asked on WhatsApp.
CTA
If your pre-arrival WhatsApp still dies in a personal chat history, fix the write-back before you buy another template pack.
Free tool · no signup
What is your front desk missing each month.
Missed calls and unanswered WhatsApp never reach your PMS, so they never make the morning report. Move five sliders and see what they cost your property, per month and per year.
