WhatsApp for restaurants and hotels: what an AI agent handles before the front desk

A hotel or a restaurant gets the same questions on WhatsApp a hundred times a week: a table for two tonight, breakfast hours, the gluten-free menu, parking, a late arrival. Each one is simple. Together they occupy the front desk all day, and nobody answers after closing.

This guide describes what an AI agent settles alone on WhatsApp Business in a venue, what it leaves to a person, how it books, and the order to set it up in.

What guests actually write

Over a month, a venue's messages fall almost entirely into five families.

• Booking: a table, a room, a treatment, an activity.
• Asking: hours, menu, allergens, amenities, pets, access.
• Warning: a late arrival, a delay, a change in numbers.
• Requesting a gesture: an upgrade, a cake, a quiet room.
• Complaining: a room, a bill, a wait.

The first three families are settled from data you already hold. The last two need a person, and the agent has to know it.

What an AI agent settles alone

• Availability and hours, read from your booking system through its API or from a NocoDB base kept current.
• The menu, allergens and treatment prices, from a file or a page of your site.
• House rules, from a document written once: cancellation, children, pets, late check-in.
• The booking itself, confirmed in the thread, with a note to the front desk when the guest arrives late.
• The reply in the guest's own language, whatever it is, without configuring an agent per language.

A guest writing at 11 pm for a table tomorrow does not want an away message. They want "yes, 8:30 pm, noted". That is the only reply worth anything.

What it must hand off

• A complaint, whatever its size: tone matters more than the answer.
• A refund, a disputed bill, anything touching money already paid.
• A group, a wedding, a seminar: terms that get negotiated.
• A guest who asks for a person.

The handoff goes into the same thread, to the front desk or a named person, with the context: the request, what was answered, the existing booking. The agent pauses and resumes when handed back.

The 24-hour window and templates

On WhatsApp you reply freely for 24 hours after the guest's last message. Beyond that, only a template approved by Meta can reopen the conversation. For a venue this mostly concerns confirmations and reminders: the day before arrival, the morning of a booking. The agent sends those templates at the planned time, and the conversation that follows continues normally.

Setup, in the order that works

• Connect the WhatsApp Business number through Meta's login. Several people can then answer on the same number.
• Link availability and hours first, then the menu and the house rules.
• Write what gets handed off, and to whom, before writing anything else.
• Test in the sandbox with last week's messages, in your guests' languages.
• Publish on WhatsApp, then add Instagram and email on the same agent.

What to measure after two weeks

• The share of messages settled without the front desk, day and night.
• The median first reply time.
• Bookings confirmed in the thread, and late arrivals noted without a phone call.
• Handoffs: too many handoffs is a missing rule, not a failing agent.

To go further, the hospitality page shows the agent on a full booking, and the WhatsApp Business page details what it settles on that channel.