Hotel and hospitality bookings on WhatsApp in Kenya

A corporate traveler messages from the airport taxi line: "Single room tonight? Rate with breakfast? Airport pickup?" — while front desk is down to one night auditor juggling check-ins. Hotels in Nairobi lose direct bookings to Booking.com when WhatsApp sits silent until morning. OTAs take commission; WhatsApp keeps margin if someone answers rates, availability, and payment policy while the guest is still deciding.

For vertical overview see hotels and hospitality on WhatsApp.

What guests ask before they book

Hotel enquiries cluster around the same facts:

• Availability — tonight vs weekend, room type
• Rate — rack, corporate, bed and breakfast vs room only
• Location and amenities — WiFi, parking, generator, pool
• Payment — M-Pesa, card at desk, deposit for hold

Timi answers from pasted rate sheet. You confirm reservation when guest sends deposit, company LPO question, or needs group block pricing.

Rate sheet in business context

Keep room types and policies where night staff can paste updates:

• Room type: "Standard double — city view"
• Rate KES: "8,500 B&B weekday / 9,500 weekend"
• Availability: "3 rooms tonight — updated 6pm"
• Extras: "Airport pickup KES 3,500 — book 2h ahead"
• Policy: "50% deposit holds room; free cancel 24h"

Refresh availability after each check-in wave — stale "room iko" causes front-desk arguments at midnight.

24/7 replies without burning front desk

Hotels cannot staff chat like a salon — but silence costs direct revenue. Split responsibility:

• Timi overnight — rates, availability snapshot, deposit instructions
• Human confirm — when deposit lands or guest asks negotiated corporate rate
• Morning handoff — night chats flagged in Feed for reservations team

See when to use AI vs reply yourself. Automation handles facts; complaints and upgrades need empathy.

Use business hours auto-reply only for non-urgent marketing — operational chat should stay on for "room tonight".

Reservation flow from enquiry to folio

• Rate + availability — Timi. "Standard B&B 8,500, 2 rooms left"
• Dates + guest name — Timi prompt. Collect check-in/out
• Deposit / guarantee — You or night auditor. M-Pesa till screenshot
• Confirmation — You. Booking ref, check-in time, ID needed
• Special requests — You. Late checkout, extra bed

Timi never promises complimentary upgrade — route VIP and complaint threads to duty manager.

A worked night booking

A guest messages at 11:10pm from JKIA arrivals: "Standard room tonight, B&B? Any pickup?" Timi answers from the rate sheet: "Standard double B&B — KES 9,500 tonight, 3 rooms left. Airport pickup KES 3,500, booked 2 hours ahead." The guest asks "can you hold it?" Timi replies with the deposit step: "A KES 4,750 deposit holds the room — Till 123456, send the M-Pesa screenshot here." When the screenshot lands, Timi flags the chat for the night auditor, who confirms the booking and sends the reference. The guest is checked in by midnight without the front desk touching a keyboard.

The OTA math

A Booking.com guest paying KES 9,500 costs you roughly KES 1,400–1,900 in commission plus the OTA owning the guest email. The same guest booking direct on WhatsApp keeps the margin and the contact. That difference is why a fast, accurate WhatsApp reply on "rate with breakfast?" is a revenue decision, not a nicety. Keep the direct rate equal to or better than OTA (where rate parity allows) and say so in the first reply.

Corporate and event blocks

Conference season brings "20 rooms Mon–Wed" and "rate with conference package". Timi states from-rate and "sales responds within 24h" — then notify sales immediately. Group contracts and credit terms stay human.

Direct booking vs OTA

OTAs own guest email; WhatsApp on hotel official line builds repeat corporate and wedding block business. Paste "Best direct rate — mention WhatsApp booking" only if policy allows parity with Booking.com — rate parity mistakes anger OTAs and guests.

Deposit and no-show policy

State the hold rule in the first reply, not at checkout: "50% deposit holds the room; free cancel up to 24 hours before." Guests who book on WhatsApp and see the policy before paying rarely argue the no-show charge later — the ones who do are the ones who never saw a number. Paste the policy once in context so night staff and Timi say the same thing.

Guest communication after booking

Confirmation template reduces no-shows. See message templates:

• Booking reference and check-in time
• Pin to hotel and parking note
• Deposit received amount
• Contact for airport pickup

Timi can send template skeleton; you personalize when guest asks safari extension or late flight.

Safari and airport packages as chat upsells

Many Nairobi hotels sell JKIA transfer + city hotel + safari extension in one conversation. Timi can list package from-price and hand off to reservations — automation should not confirm lodge availability without your partner callback. Paste one line per package in context so night staff does not invent rates under pressure.

Guests comparing three hotels on WhatsApp often pick whoever answered breakfast, WiFi, and pickup fee in one message — not the property with the nicest pool photos and silence until morning.

Common mistakes

• Weekend rate quoted on weekday inquiry without dates
• No deposit policy — guest no-show leaves empty room
• Timi off overnight — JKIA arrivals book competitor on OTA app
• Breakfast ambiguity — review hit after checkout
• Automation promises upgrade — front desk cannot deliver

FAQ

Can Timi integrate with PMS? Paste manual availability snapshot until integrated; update at shift change.

Walk-in vs WhatsApp rate? State policy — many hotels match if guest messages before arrival.

Long-stay discounts? Hand off weekly and monthly rates; paste "7+ nights — ask reservations".

Restaurant and spa upsell? Add optional lines in context — Timi mentions once, not hard sell.

Swahili and Sheng guests? Timi handles multilingual FAQs; see AI replies in local language mix.