AI automation for hotels, from the enquiry to the review

Everything around the stay, and the commission it keeps off the booking

AI automation for hotels runs everything around the stay except the stay: answering an enquiry in seconds whatever the hour, recovering bookings that would otherwise arrive through a platform you pay commission on, pre arrival and post stay messaging, coordination between the desk and housekeeping, review handling, and the group and event enquiries that take an afternoon to quote by hand.

It does not run the stay itself. The welcome, the room, the breakfast and the way a complaint is handled at the desk are the product, and none of that is software.

Hotels sit in an unusual position. A large share of demand arrives through platforms that charge for the introduction, and many of those guests looked at your own website first. Everything on this page is either about catching that guest earlier or about giving your team back the hours currently spent answering the same eleven questions.

• Before the stay: enquiries, quotes, direct booking prompts, confirmations, directions and transfers
• During the stay: requests, upgrades, late checkouts, and anything a person must handle escalated fast
• After the stay: thank you, a review request timed properly, and a reason to come back
• Behind the desk: housekeeping status, the morning report, group and event enquiries, repeat guest recognition
• Around the property: reviews monitored and answered, and the same questions answered once rather than daily

The week you actually have

No solutions in this section. Count.

• An enquiry arrives at eleven at night and is answered at nine the next morning, by which time they have booked somewhere else
• A guest books through a platform you pay commission on, having looked at your own website first
• A group enquiry needs three people and two days before anyone can give a price
• The same questions about check in times, parking and airport transfers are answered by hand thirty times a week
• Housekeeping and the front desk disagree about which rooms are ready
• A late checkout is agreed at the desk and never reaches the floor
• A guest complains publicly about something that could have been fixed while they were still in the building
• Reviews sit unanswered for weeks, and the difficult ones get answered defensively
• A guest who has stayed four times is greeted as a stranger
• An event enquiry needs a function quote and the sheet takes an afternoon to write
• The morning report is assembled by hand from three different screens
• One guest messages on WhatsApp, another on Instagram, another through the booking platform, and only some get answers
• Nobody asks for a review at the moment the guest is happiest, which is usually before they leave
• A rate is updated on one channel and not on another

The arithmetic on your own property

No occupancy benchmarks and no borrowed averages. Three sums using numbers you already have.

• Sum one: the commission you paid on platform bookings last month, multiplied by twelve, and then ask what share of those guests had already seen your own website.
• Sum two: your average room rate multiplied by the number of enquiries last month that went unanswered or were answered the following day.
• Sum three: the hours your desk spends each week on repeated questions, housekeeping coordination and the morning report, multiplied by what an hour costs, multiplied by fifty two.

The first sum is the one that changes the conversation. Commission is a line most owners have stopped looking at, because it arrives as a deduction rather than as a bill.

What gets built, and where a property starts

Almost every hotel starts in the same place, which is the enquiry. A property that answers in seconds at midnight, in the guest's own language, with its own booking link attached, changes its own economics before anything else is built.

• One inbox for enquiries from the website, WhatsApp, Instagram, email and the phone, answered in seconds at any hour
• After hours capture and missed call recovery, so a call nobody could take produces a message back
• Direct booking prompts: an answer that carries your own link and your own rate before a platform takes the reservation
• Pre arrival messaging: confirmation, directions, transfer arrangements and offers like early check in or an upgrade
• In stay messaging on the channel guests already use, with anything a person must handle escalated immediately
• Post stay messaging: thank you, a review request timed to the right moment, and a returning guest offer
• Review monitoring, with replies drafted and approved by a person before they are published
• Housekeeping coordination: room status, late checkouts and special requests visible to the desk and the floor together
• Group and event enquiries captured, qualified and quoted from your own price list
• Repeat guest recognition, so preferences and past stays are on the record before arrival
• A morning report: arrivals, departures, occupancy and requests still outstanding
• Rate and availability questions routed to whoever owns them, with the changes still made by a person

What stays human in hospitality

Hospitality is the one trade where the human part is the product, so the line is drawn generously. Anything that carries warmth, judgement or money stays with your team.

Guests are also told plainly that they are messaging a system when they are, and handed to a person the moment they want one. A property that pretends otherwise gets found out, usually in public.

• The welcome, and any conversation where a guest is upset, unwell or unsafe
• Complaints, compensation and anything that would appear in a review
• Rates, discounts, group pricing and contracts with corporate accounts or agents
• Overbooking and relocation decisions, which need a person on the phone and not a template
• Any published review response, prepared by the system and approved before it goes out
• Card and payment details, which never travel through a messaging channel

What changes from one market to the next

A hotel in Karachi, Dubai, Manchester or Toronto has the same week and different rules around it.

• Platform terms differ. Whether you may offer a better rate directly, and how loudly you may say so, depends on rate parity rules that are permitted in some markets and restricted in others. That decides whether direct booking recovery is a price message or a value message.
• Payment differs. Card prepayment, deposit on booking, bank transfer, wallets and cash on arrival each change what the pre arrival message has to do and when the booking is really secure.
• Channel differs. WhatsApp leads in one market, Instagram in another, email in a third. Business messaging on WhatsApp runs on opt in, on approved templates and on a window that closes after the guest's last reply, so a pre arrival sequence has to be designed around that rather than against it.
• Guest registration differs. Some markets require identity documents to be collected and registered with authorities on arrival. Collection can be prepared before the guest arrives, and the submission stays with your staff.
• Seasonality differs. Wedding season, conference calendars, school holidays, Ramadan and Eid all concentrate demand differently, and a messaging system sending one offer all year wastes the peak and misses the trough.

When a property is too small for a system like this

Three cases where the answer is not to buy anything yet.

A fourth, less comfortable. If the rooms are not consistently clean and the beds are not comfortable, faster messaging brings more people to a stay they will complain about, and the reviews get worse rather than better. Fix the stay first.

• An owner run guesthouse with a handful of rooms usually needs a shared inbox and a phone that gets answered, not a system. The build pays once one person can no longer see every message.
• If you are full all year through platforms and content with that mix, direct booking recovery is not your build. Operations and cost are, and that is a different page.
• If nobody on the team will own the system, even for an hour a week, it will drift out of date. Rates change, offers change, and a system answering with last season's information does more damage than no system.

An AI receptionist for a hotel, and the booking it protects

An AI receptionist for a hotel earns its keep on the enquiry that arrives at eleven at night, because a guest who cannot get an answer books the same room through a portal and the property pays commission on a booking it already had.

The property management system is the constraint. Rates, availability and the rules attached to them live there, so the agent quotes from it or it quotes nothing at all. A confirmed rate the system cannot honour is worse than a missed call, because it arrives at the desk as an argument during check-in.

Night coverage, a second language and the request that has to reach a duty manager are the three things worth specifying before anybody quotes. What moves the cost, and what a machine on the line has to declare about itself, is on the AI receptionist page.

What this is competing with, how long it takes, and who is at our end of it

No rate is published on this page, and for a hotel the sensible way to think about the number is the first of the three sums above rather than a software budget. What moves the number is how many channels a guest can arrive on, whether your property management system will let anything read availability, how many languages the enquiry has to be answered in, and who keeps it working in month four. Set that against the commission line for one month multiplied by twelve. That is the figure this is actually competing with, and it is usually the only number in the building nobody has looked at recently.

The audit takes the first week and most of it goes on the channels, because a property that cannot see every enquiry in one place will not answer them in seconds however well the replies are written. One piece is live inside a fortnight and it is the after hours enquiry reply carrying your own booking link, since that is what changes the economics before anything else is built. Pre arrival and post stay messaging follow across month two. Review handling is deliberately later, because a drafted reply is only useful once somebody has agreed who approves it and how quickly.

A property with a capable front office manager can run the pre arrival and post stay messages in-house, and that is often the honest place to start, because writing those messages well matters more than whatever sends them. What is harder to keep on your own team is the enquiry layer across five channels at midnight in more than one language, which is the point at which this stops being a set of templates. Haad, the co-founder who owns growth and client solutions, runs that diagnosis. The nearest published hospitality engagement is Amari Sayulita, a boutique hotel in Mexico, and that work is intent-segmented Google Search rather than front desk automation, which is worth knowing before you weigh it.

Wobble works from Karachi, bills month to month and has 25 engagements across six countries, with no overseas office in any of the markets your guests arrive from. For a hotel that is an argument for building the after hours reply properly rather than a reason to avoid the subject, since the hours nobody is at your desk and the hours nobody is at ours are not the same hours. The property owns the system either way. The guest list, the message history, the templates and the automations sit under your own logins, so if the arrangement ends the midnight reply keeps going out.

Common questions

Will guests know they are talking to a system?

They are told, and they are handed to a person the moment they ask or the moment anything sensitive appears. Guests generally do not mind a fast, accurate answer at midnight. What they mind is a system pretending to be a receptionist and then failing to understand a simple request.

Can this actually reduce what we pay in commission?

It can shift some bookings from a platform to your own channel by getting to the guest earlier, on the channel they were already using, with your own rate and link in the reply. How much room you have to compete on the direct rate depends on your platform agreements, which is a question worth asking before the build rather than after.

Does it connect to our property management system?

Where the system allows an outside connection it does, and room status, arrivals and guest history all become usable. Some systems genuinely do not allow it, whatever the sales page says, and then the design puts a person at the point where the record is committed. That gets checked during the audit.

Can it answer in more than one language?

Yes, and in the markets where guests mix two languages in one message that is the normal case rather than an edge case. Voice notes are handled as well, which matters more than it sounds, because a guest asking for a late checkout by voice at eleven at night is a common request.

Will it reply to our reviews automatically?

It drafts, a person approves. Review replies are published in your name and read by every future guest, and a defensive or clumsy reply damages more than the original review did. The saving is in the drafting and the monitoring, not in removing the approval.

We are a small boutique property. Is this worth it?

The trigger is not the number of rooms, it is whether enquiries are going unanswered outside working hours and whether repeated questions are eating your desk. A property with a dozen rooms and a strong direct following often benefits more than a larger one, because a single missed enquiry is a larger share of the week.