An Aivell answers the reservations inbox in the guest's language — check-in times, parking, pets, availability — hands real bookings to a human, alerts the duty manager to complaints, and delivers the arrivals list every morning. It also collects the week's reviews into one digest, with replies drafted for approval.
The reservations inbox wakes up in German, English, French and Italian. Half the messages ask things the website already says; all of them expect an answer before they book somewhere else.
Check-in time, early check-in, parking, pets, breakfast hours, city tax, cot in the room. Reception answers each one dozens of times a week, between check-ins, from memory.
Reviews scatter across three portals. Someone is supposed to read them, reply to each in the right tone, and notice that "the shower again" has now come up four times. Usually that someone is the owner, on Sunday.
Someone cross-reads today's bookings for the allergy note, the anniversary, the late arrival, the unpaid balance — and briefs the shift. When it's skipped, the guest tells you at the desk.
Hospitality admin has no back office — it happens at the front desk, between a check-in and a phone call. The inquiry from Hamburg waits while room 12 gets keys; the review reply waits until Sunday; the arrivals briefing depends on who opened that morning. Email alone eats 28% of the average workweek, and a hotel inbox is worse: it’s seasonal, multilingual, and every unanswered message is a room sold by a competitor.
The knowledge to answer it all exists — in the head of whoever has worked reception longest. That’s the fragility: the answers walk out the door with the shift.
An Aivell puts that knowledge in a box in your office and lets it answer. You write the house procedure in plain language — what we say about pets, when Sofia handles a group, who hears about a complaint at 2 AM — and the Aivell follows it in the guest’s language, at the guest’s hour. Reception starts the day with the arrivals list already annotated; the owner gets one weekly review digest instead of three portal logins.
On-premise matters in few industries like this one. A hotel knows who slept where, with whom, and how they paid — data no guest ever agreed to share with an AI vendor. On an Aivell, inference runs onboard: the reading, drafting and digesting happen behind your firewall, with a complete audit trail and nothing sent to the cloud. The hospitality stays personal, in every sense.
read every message to reservations@, whatever language it arrives in
routine questions — check-in, parking, pets, city tax — answer from the knowledge base, in the guest's language
availability requests, check the calendar, propose free dates, and say a colleague will confirm
groups of eight or more, weddings, and full-buyout requests go to Sofia untouched
complaints get an apology within the hour and the duty manager alerted, day or night
at 7:00 send the front desk the arrivals list with special requests highlighted
log every inquiry and what was done in the reservations sheet
Customers write in any language; your Aivell replies in theirs and briefs the team in yours. Translation runs onboard, so mail never leaves the office.
Evening and weekend inquiries answered on the spot by an on-premise AI colleague. Mornings start with qualified, pre-handled requests — not a backlog.
Visitors pick a real free slot in your site chat and get a real calendar invite — booked by an AI colleague on your box, not a scheduling cloud.
Recurring customer questions answered by email within minutes, from your own documents — on a box behind your firewall. The rest goes to a human.
Your Aivell re-reads tender portals, regulations and terms pages on schedule, and emails a plain-words summary when something actually changed.
One morning email: what arrived overnight, what needs a decision, what was already handled. Read and written on a box in your office, not in a cloud.
Reminder emails before every appointment, reschedules handled by reply — run by an AI colleague on a box in your office, not in someone's cloud.
It never leaves the hotel. The Aivell processes mail on a box behind your firewall, with onboard inference and encryption at rest — no guest identity, stay history or payment correspondence goes to a cloud AI. Under GDPR that's privacy by design, not a policy promise.
Not unless you want it to. The usual chore lets it answer questions and propose dates, while confirming a reservation stays with a human — a guardrail, not a habit. Some properties later allow direct bookings for simple cases; that's one sentence in the chore.
Portal messages that reach you as email get read and answered like any other inquiry, and the Browser Agent can work a portal's message page where needed — within guardrails that let it reply but never touch rates or availability.
Every week the Aivell collects new reviews from the pages you list, summarizes what changed — score, themes, that recurring shower complaint — and drafts a reply for each in your tone. You approve or edit; nothing is posted without you.
An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.
You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.
onboard inference · air-gapped · fixed monthly fee