A booking comes in
It calls the guest to confirm the reservation, gives them arrival details, and collects anything you still need — an ID, an arrival time, a card for the deposit. The reservation is confirmed before anyone on your team has read it.
The AI agent
An employee who never
stops picking up.
Think of it as someone who sits behind your BookingHQ with access to exactly the data you permit — your rates, your availability, your policies, your reservations — and uses the phone, WhatsApp, SMS and email the way a good front-desk manager would.
Twelve minutes, no human involved, and a room that would have gone empty is sold at your own rate rather than an OTA's.
What it does
Four moments where a booking is won or lost.
A booking is abandoned
This is the one that pays for itself. The cart stalls; it calls, works out what stopped them, answers it against your real rates and policy, sends an invoice payment link, and confirms the booking on the same call.
An arrival is due
Nobody checked in by six? It calls to check they are on their way, so a late arrival is a late arrival rather than a room written off as a no-show at midnight.
A bad review lands
It calls the guest, hears the actual problem, and gets you the chance to resolve it — while the review is still a conversation and not a permanent one-star.
It only sees what you permit.
The agent is not a chatbot bolted onto your website with a copy of your FAQ. It reads the same database your console does — which is what lets it quote a real price and honour a real cancellation window — and every category of data is a switch you control.
- Rates, availability and your booking policy
- The reservation it is calling about, and that guest's history with you
- Your FAQs, house rules and property details
- Nothing else — not your ledger, not your staff, not other guests
What it will not do.
The limits are the product. An agent that oversteps once, at scale, under your property's name, costs more than it ever earned.
It will not pretend to be human
It identifies itself when asked, every time. Misleading a guest about who they are speaking to is a line we do not let it cross.
It will not call someone who said no
Do-not-contact is absolute and immediate, and a guest can set it on the call itself.
It will not act beyond your setting
Every action can run in draft — it writes, you press send — until you have watched it for a week and agreed with it.
It will not invent an answer
If it does not have the fact, it says so and hands the guest to a person with the whole thread attached.
It uses whichever channel the guest actually answers.
Phone first when it matters, WhatsApp when it does not, SMS when there is no data, email for anything that needs a record. One conversation, on your timeline, whichever route it took.