Hotel room reservation automation: book from messages

A hotel’s most valuable reservation often comes at midnight: "Is there a sea-view room for two for tomorrow?". If the front desk is closed, this message waits until morning and the guest books at another property. The daytime picture is similar: availability and price questions pile up, and while the team works through them one by one, hot requests go cold.

inTusell handles these requests at night too: it takes the date, room type, and party size, replies based on the real availability and rate plans in the Stays module, and opens the reservation if it fits. This article explains hotel room reservation automation: how a hotel automates its availability and reservation flow with inTusell. It is part of the hotel & hospitality section of our sector-by-sector "how to train your AI" series.

Quick answer

Who is it for?

This article is for hospitality businesses that manage availability and price questions from messages: city hotels, boutique hotels, resorts, aparts, and guesthouses. It makes a real difference, especially for properties whose front desk is closed after hours, that do not want to miss requests coming in overnight, and that need to answer foreign guests in their own language.

Availability and reservation flow

When a guest writes a date and party size, the assistant fills in the gaps: room type, board preference (room only, breakfast, half or full board, all inclusive), special notes. This flow runs on the Stays module (beta): your sector must be Hotel & Accommodation and you need to enable the module. In the module you define your properties, room types, rate plans with date ranges and daily availability; the AI speaks only according to them.

The critical point is this: the AI does not invent the price or availability. It does not guess for a date or room type that is not defined; it connects to the front desk. Because allocation happens in one transaction while the availability row is locked, two requests coming through inTusell cannot take the same last room. There is no channel manager connection: rooms you sell on OTAs or by phone you record yourself in the availability calendar by lowering the quota or closing sales (stop sale). When the module is off, the AI never sees the room tools; it gives room information from the knowledge base and, since it cannot confirm availability, makes no booking promise.

Payment, cancellations and no-shows

A stay reservation follows an eleven-state track: quote, option hold, awaiting payment, partially paid, fully paid, confirmed, checked in, checked out, cancelled, refunded and no-show. You collect payment by bank transfer (default) or through an iyzico link; for a transfer, the AI sends the amount, your IBAN and a booking-specific reference code in one message, and you confirm when you see the money. The AI never records a payment itself.

Unlike appointments, there is no automatic reminder before a stay. You record cancellations, refunds and no-shows in the panel; in those cases the rooms go back to availability and those nights can be sold again. An open room is not offered to other guests on its own.

What it isn’t

inTusell is not a simple chatbot: it is an AI sales assistant and CRM that answers messages on WhatsApp, Instagram and web chat, books appointments and opens orders, and follows each customer through the sales pipeline. Nor does it replace a PMS or a channel manager; it does not sync availability or rates with OTAs. It does not invent availability you have not defined, does not record payments on its own, and does not force a change to your existing reservation system. It handles the request accurately and honestly, and hands off to a human when needed.

Frequently asked questions

Where does the AI get the room price and availability from?

With the Stays module on, from the room types, date-range rate plans and daily availability calendar you defined. With the module off, it gives only the general information in the knowledge base and makes no availability promise. It does not invent a price or availability for a date or room type it is unsure about; it hands off to the front desk or the team.

Does it complete the reservation on its own?

With the Stays module on, yes: the AI collects the dates, room type, board, party size and special notes, checks availability, gives a quote and opens the reservation. Payment goes to the property by bank transfer or iyzico; you approve bank-transfer receipts. In unclear or special cases such as groups, it hands off to the team.

What happens if a foreign guest writes in another language?

The AI replies in whatever language the customer writes in. When a guest from abroad writes in English, German or Arabic, the assistant answers 24/7 in the same language.

How does it handle no-shows and cancellations?

There is no automatic reminder for stay reservations. You record cancellations, refunds and no-shows in the panel; in those cases the rooms go back to availability and those nights can be sold again. An open room is not offered to other guests on its own.

Does it replace my existing reservation/PMS system?

No. inTusell is the communication layer that handles the request and opens the reservation; it is not a PMS or a channel manager and does not sync with OTAs. You define availability and prices, and you record rooms sold through other channels in the calendar.

Will I miss requests that come in overnight?

The risk drops: the AI answers even while the front desk is closed and, with the module on, checks availability and gives a quote. When you sit down to operations in the morning, answered requests and receipts awaiting approval are ready.

Next step

To get the assistant ready, see how a hotel trains the inTusell AI and, for daily operations, how a hotel uses inTusell. To see where the requests come from, read Instagram and WhatsApp automation for hotels. For your property, you can explore the hotel & hospitality solution and check out the pricing page.

If you’d like to see it with your own scenario, get a demo or write to hi@intusell.com. For all the guides, see the inTusell blog.