Hoteliers wanted AI in their data and across every tool, without it leaving the EU
Apaleo has always been open: every capability published as an API, a store of 250+ apps around it, and the first MCP server in hospitality. When AI arrived, hoteliers on Apaleo had the data to use it. What they didn't have was a way to use it that worked for a hotel.
Guest data can't leave Europe.
ChatGPT and Claude process data on US servers, with no say over what's kept. For a European hotel, that ended the conversation before it started.
The answers are spread across a dozen tools.
“Why was last Tuesday soft?” needs the PMS, the rate shopper and the events calendar. Each has its own login, and none of them talk to each other.
Groups ask about the portfolio, not one property.
A PMS works property by property, so one group-level question means thirty separate checks.
Most work starts with an event, not a question.
A cancellation, an enquiry or a check-out — the day is full of them, and none of them start with someone typing a question.
One day at a 30-property group: five jobs the team no longer does by hand
One day at a group running thirty properties on Apaleo, with a team of Sidenet assistants inside Apaleo. Different assistants handle different moments — one on reports, one on the inbox, one listening to the PMS — and the hotelier never picks. They just get the result.
- 06:5506:55
Reports on schedule: every property, one email, before the shift starts
The GM opens Gmail on the way in. The morning report is already there: last night's pickup, today's arrivals and departures, ADR and RevPAR against the same day last year, out-of-order rooms — every property, one email, the two that need attention at the top. Nobody asked for it this morning. It was asked for once.
- 09:1209:12Proactive · seconds after the event
A cancelled room offered to the next guest within seconds, without anyone asking
A reservation is cancelled at one property for Saturday night, which was full. Apaleo sends the event. Within seconds the assistants have checked the enquiries that property declined this week for those dates, picked the best fit, and drafted the “a room just opened up” email — waiting for one click from the front desk, before anyone has read the cancellation notification.
- 01Apaleo sends the cancellation event
- 02The enquiries declined for those dates are checked
- 03Best fit picked, email drafted
- 04Front desk approves with one click
“ The PMS said a room had opened up. The assistants had already found who wanted it.”
- 11:3011:30
One answer across the PMS, the rate shopper and the events calendar
The revenue manager asks, in Apaleo: “Why was last Tuesday soft when the comp set was full?” The answer needs Apaleo's occupancy and rates, the rate shopper's view of the comp set, and the local events calendar — in one reply. It comes back as a chart, with the rate gap on the two nights that mattered. She saves it as a dashboard that refreshes itself.
- 14:0514:05
A group enquiry from the inbox, checked against every property and answered
A company writes to the group's shared inbox: forty rooms and a meeting room in November, which properties could take it? The assistants read the email, check availability across the portfolio, tag the thread, and draft a reply listing the three properties that can take it — for a human to send.
- 16:4016:40
Thirty properties in one question, and changes made in Apaleo with approval
The director asks for weekend occupancy across every property, ranked, with the two lowest flagged. One question, one answer, the whole group — not thirty properties checked one by one. Then: “Block 204 and 206 at the Frankfurt property out of order until Thursday.” An assistant proposes the change, the director approves, Apaleo is updated.
Nobody on the team exported a report, rebuilt a spreadsheet or chased an inbox today. That time went to the guests.
On request, on a schedule, or the moment something happens in Apaleo
Here's more of what the assistants do, grouped by what starts it. Two of the three columns run without anyone typing.
When you ask
- “Which guests arriving this week are returning, and what did they book last time?”
- Upsell candidates among tomorrow's arrivals, from guest history
- “No-show rate by channel this quarter, per property”
- A reply drafted to a guest, in their language
On a schedule
- Monday's revenue summary in the revenue manager's inbox
- Weekly pickup by channel, against the same week last year
- End-of-month out-of-order and maintenance summary to operations
When something happens in Apaleo
- New booking → upsell offer drafted before the guest checks in
- Check-out → housekeeping task created in the tool the team actually uses
- Folio balance change → alert to the right person, in Slack or by email
From eleven logins to one: every tool connected, all run from Apaleo
A hotelier on Apaleo runs eleven tools around the PMS, and every one is another login. Sidenet's assistants connect to all of them — store apps, Gmail, HubSpot, WhatsApp, the group's own spreadsheet — answer what no single tool knows, and push each change back to the right one. Eleven tabs become one.
The team does the joining up.
The assistants do the joining up.
rates · folios · arrivals · enquiries — and out of every tool around it
out-of-order rooms · tasks · draft replies · tags · alerts — and into any of the eleven
One team of assistants. One tab. Eleven tools handled — and the time goes back to the guests.