SofIA runs the channel.
WhatsApp, Instagram, and Messenger. Today it connects to the Hotelisimo PMS or to Cloudbeds.
Where it shows up
- Messenger
What it does on a turn
Sell the stay
Availability, room options, hold, changes, cancellation, and the payment link. Payment is confirmed with the PMS.
During the stay
Room photos, hotel facts, the menu, an order, and a task. If a room fact is missing, it reads the adapter before stating it.
With the team
If staff take the conversation, SofIA stops on that thread. Taking a single task pauses SofIA on that ticket, not on the whole chat.
Which PMS it uses
Hotelisimo PMS
The native adapter reads and writes the stay in Hotelisimo: availability, hold, changes, cancellation, and the payment link.
Cloudbeds
The adapter talks to Cloudbeds. The reservation stays there. The conversation, the order, and the task stay in Hotelisimo.
A PMS that is not connected yet
Tools do not call Cloudbeds directly. They go through the adapter. A new PMS would use that door. No third PMS is connected today.
How a hotel goes live
The PMS first. Then SofIA on the guest channel.
Hotelisimo PMS
The calendar, reservations, housekeeping, and rates live in this panel. The stay is stored here.
Cloudbeds
The reservation stays in Cloudbeds. Hotelisimo keeps the conversation, the order, and the task. Casa Mädi runs this way.
SofIA
It connects to WhatsApp, Instagram, and Messenger. It checks availability, places the hold, and sends the payment link. The charge is confirmed in the PMS.
Who opens the panel
Each role sees its own work. The guest does not open the panel. They write on WhatsApp, Instagram, or Messenger.
Owner and manager
Reservations, rates, stop-sell, the menu, inventory, and the team. They can sell over a stop-sell.
Front desk
The stay file, walk-ins, orders, and tasks. Front desk cannot sell over a stop-sell.
Kitchen
Sees orders and turns a dish on or off. Kitchen does not edit the menu.
Housekeeping
Works tasks. The native PMS Housekeeping board is separate: checklist, photo, and blocks.