The booking that used to go to the OTA rings you first.
Kaigen is the AI operating system for a hotel's front desk. It answers the call or the message, holds the room, confirms on WhatsApp, and runs the stay through to the review after checkout, in the guest's language.
Cove House, Goa
Front desk · replies in seconds
Guests call at eleven at night, and the desk is on a wake up call.
A ring that goes to voicemail is a booking that goes to a portal at commission. The agent picks up on the first ring, every hour of the night.
It answers what the desk answers a hundred times a day.
Parking, breakfast, airport distance, early check in, whether the pool is open in December. All of it on the first ring, no hold music.
The guest asks
Is there parking, and is breakfast included?
The agent has all of it
- Parking
- Breakfast
- Airport distance
- Early check in
- Pool hours
- Late checkout
Answered on the same call, and sent in writing afterwards.
One agent for the whole stay, not one for the booking.
It books the room, confirms the arrival, takes the room service order, arranges the late checkout and asks for the review. The guest has one number for all of it. Open a line to see each step.
What the agent knows before it says hello
What the agent knows before it says hello
The enquiry worth twenty rooms does not wait for Monday.
A wedding, a conference, a corporate block. The agent takes the dates, the headcount and the budget, and the sales manager wakes up to a brief instead of a voicemail.
The call, 23:40
What the caller said
- A wedding in March
- About twenty rooms, two nights
- Dinner for eighty on the Saturday
- Wants a price by the weekend
The brief, 07:00
What your sales manager opens
- Dates, rooms and headcount on one page
- Budget bracket, and who decides
- The call, transcribed
- A reply drafted for their approval
The returning guest is greeted like one.
The room they liked, the pillow they asked for, the early breakfast. It is on the record from the last stay, and the agent has it when they call back.
First stay
Second stay
Third stay
Each stay adds a line. Nothing is asked for twice.
Old leads are still leads.
Every business has a list of people who asked once, went quiet and never heard back. Give us the list. The agent reaches each of them, remembers what they asked about, and hands back the ones who are ready now.
Leads from last year
- Two nights, booked
Opt-outs and calling hours are checked before anything is sent. Every reply, and every silence, goes on the record.
Watch one call go from a ring at night to a booked room.
A call lands after eleven. Watch it get answered, quoted, booked and confirmed without the night desk touching it.
What changes for your front desk.
No new system to learn, and nothing changes about how they greet a guest. What changes is how many rooms are booked direct.
Every night,
the phone is answered.
- Arrivals confirmed the day before.
- Group enquiries briefed by morning.
- Every call written up before the morning shift.
- Monday starts with the numbers already in front of you.
You ask
Which source sent guests who checked in?
It answers
Counted from the calls themselves, not from a form someone filled in.
Ask your own data a question, in plain English.
Every call and message is in one place. Ask which source books guests who arrive, which dates guests ask about and do not book, or who cancelled after a rate question. It answers from the calls themselves.
It grades every call it makes, and gets better.
Every conversation with a guest is scored against what you signed off: what it must say, what it must never say, what it was there to do. Judges are calibrated against human grading, so the score means something. What fails is fixed before it happens again.
It writes to the system you already run.
Mews, Cloudbeds, Opera and SiteMinder sync both ways. Everything else reaches you through a webhook.
If your desk does it, we can build it.
The rate sheet for travel agents in their format. The upsell rules for the suite. The review request in the guest's language. We build around how your property already runs, then we run it. You approve every script before a guest hears it.
Your dashboard
- Outbound calling
- Inbound, all channels
- Reminders, the day before
- Follow up after the visit
Done. Two workflows paused, resuming Monday 09:00. Reminders unchanged.
Yours to run, at any hour.
Every agent, workflow and channel has a switch in your dashboard. Turn it on, turn it off, change the script, watch the calls. Or ask the Kaigen agent to do it: it builds workflows, changes prompts, provisions numbers and answers questions about your data, from the dashboard or from Claude and any AI tool through our MCP server.
The phone numbers, the paperwork and the compliance are ours to handle.
We buy the numbers in your name, file the paperwork, connect them and attach the agent. Before any outbound call, the number is checked: the country, the legal calling hours, the registration it needs. Anything missing, the call does not go.
- NumberBought in your name
- PaperworkFiled by us
- NetworkTrunk and routing
- AgentAttached, recording on
- LiveMonitored by us
We run it. You keep the keys.
Our team builds your agent, listens to the calls and tunes it every week. Everything it does is in your dashboard, your workflows are yours to edit, and your own AI tools can read the whole record through our MCP server. Change as much or as little as you want.
Will guests know they are talking to an AI?
It says so when asked, and we recommend saying so up front. Anyone who wants a person is transferred to the desk.
Does it quote our rates?
It quotes the rates you set, for those dates, with the taxes. Nothing is invented, and the rate sheet stays yours.
Will it speak to guests in their language?
Any major language, and it switches mid conversation without being asked.
How long until it is live?
Two to three weeks for most properties. We learn how your desk quotes and books, agree the plan with you, then build and tune against it.
More at the full FAQ.