Inbox-native
Lives inside Outlook / email.
Runs as a side panel next to the original mail. The team works in the inbox they have used for years. Nothing replaced, nothing migrated.
The shared front-office mailbox handles everything — guest inquiries, FAQ, internal handoff. The engine classifies, structures, and prepares drafts in the inbox your team already opens. Nothing leaves the hotel without a human sending it.
The engine works where the team already works. No new tool, no new login, no migration. Original mail untouched — structure, draft, and availability appear alongside.
Runs as a side panel next to the original mail. The team works in the inbox they have used for years. Nothing replaced, nothing migrated.
Each message is classified automatically — reservation inquiry, FAQ, internal forward, complaint, request follow-up — and labelled at glance speed.
Guest name, dates, room type, party size, language, special requests — all extracted, structured, and shown in the side panel. The original mail stays untouched beside it.
Before drafting a reply, the engine checks live availability against the PMS or booking engine — so quoted rates and rooms reflect what is actually sellable, not what was sellable yesterday.
The team requests a draft. The engine prepares a complete reply in the guest's language, with correct rates and a booking link already filled in. Edit freely, then send. Never auto-send.
Classification, structure, drafts — all of it stops at the team. No auto-reply, no autonomous outbound. The judgement of the front desk stays the final step.
The engine adds a side panel and a draft button. Everything else stays where the team expects it to be.
A new message hits the shared inbox. The engine classifies it, extracts the data, and prepares the structured view in the side panel. Nothing in Outlook changes — same folders, same threads, same view the team is used to.
Side panel shows the structured data — guest, dates, room type, language, party size, special requests — plus live availability for the requested stay and any relevant FAQ. The original mail sits unchanged next to it.
One click prepares a complete reply in the guest's language — with correct rates and a booking link already inserted. The agent reviews, edits if needed, and sends. The engine never sends on its own.
The engine runs on European infrastructure under a signed data processing agreement. Hotel data is not used to train AI models.
All processing and storage happen on European infrastructure. No transatlantic data transfer. Built on platforms hotels already trust.
A signed data processing agreement (Auftragsverarbeitungsvertrag, GDPR Article 28) governs every engagement. Controller and processor roles, retention, and sub-processors defined in writing.
Classification and draft generation run through commercial AI APIs under terms that exclude training use. No inputs, no outputs, no hotel data is used to train models.
Compatible with Apaleo and Mews out of the box. Further property management systems available on request.
The Mail Intelligence Engine is for general managers and operations managers of small to mid-sized hotels who want to relieve the front-office inbox without asking the team to learn a new tool. The system shows up where the work already happens — and stays out of the way the rest of the time.
Write a few sentences about your setup — the inbox, the PMS, the daily volume, the kinds of inquiries that take the most time — and we will take it from there.
renato@relevo-lab.com →