No room sold with a broken AC.
The moment something that matters breaks, the room comes off sale and reception knows why. No apologies at check-in.
LivionLivion Flow
Livion Flow · Hotel automationsBuilt into LivionEvery hand-off between departments, done without a message.
A housekeeper reports a broken AC. Before the next room is made up, maintenance has the ticket, reception knows the room is off sale and purchasing has the part on its list. Livion Flow moves the work between your departments, and stops to ask whenever a decision belongs to a person.
What changes
Less falls between departments.
No chasing in group chats.
Checkouts reach housekeeping, tickets reach the technician on shift, deliveries reach the department waiting for them. Nobody has to remember to pass it on.
No order sent without a yes.
Livion drafts the supplier order from your stock levels. Your purchaser approves it in one tap, or changes a quantity first.
Ready-made
Switch it on. Don’t build it.
Livion ships automations for the hand-offs every hotel has. Turn one on, answer two or three questions about your hotel, like who gets the ticket or whether the room should be blocked, and it runs. Most properties never need more.
Every ready-made automation can be adjusted, and reset to the original at any time.
Written in plain words
If your team can say it, Livion can do it.
Every automation reads like a sentence someone on your team would say. Anyone can check what it does without a manual, and change it without calling a developer.
When
a guest checks out
Only if
the room has an arrival today
Then
put it first on the housekeeping list and tell the floor supervisor
And every step says who does it.
- Automatic
The routine work. Livion does it straight away and notes it in the activity.
Checkout → room on the housekeeping list - Asks first
Anything with a cost or a guest impact. Livion prepares it, and a named person says yes before it happens.
Supplier order → the purchaser approves - Task for staff
When a hand or an eye is needed. Livion assigns it to a person and follows up until it is done.
Minibar checked before the room is resold
Across departments
One problem. Every department. In the right order.
Point tools automate inside their own box. Livion runs housekeeping, maintenance, front office and purchasing on one platform, so a single automation carries a problem from the first report to the last hand-off. Each lane is a team, so you see who does what, and when.
Automatic Asks first Task for staff Livion also links the ticket to the AC’s record, so its repair history stays complete.
You stay in charge
Decisions reach the person who makes them.
When a step needs a yes, the request lands on the right phone with the story so far. One tap to approve, decline or change a quantity. Nobody has to open a settings page to keep the hotel moving.
- Name a person, a department or a role to approve
- Decide what happens if nobody answers in time
- Every answer is recorded, with who and when
Build your own
Describe it. Nebbia drafts it.
For the hand-off only your hotel has, write it the way you would tell a colleague. Nebbia, the AI assistant in Livion, turns it into steps you can read. Nothing runs until you check it and press Create.
- Every trigger and step your modules offer
- Messages filled with the facts: room, guest, priority
- Waits, reminders and questions that split the path
Try it first
See what it would have done last month.
Before an automation goes live, replay your own recent events through it. Livion shows every time it would have run, every time it would have skipped and why. Nothing is carried out.
- Your hotel’s real events, not sample data
- Every occurrence listed, so you can check the edge cases
- Skips explained in plain words
Activity
Every run reads like a note from a colleague.
No logs, no error codes. Each run says what happened, what Livion did and who said yes or no. When something can’t be finished, it tells you why and what you can do about it.
Grows with you
Nobody starts on a blank canvas.
Start with what Livion ships. Adjust the steps when your hotel works differently. Lay them out by department when one problem needs two paths.
Level 1Every hotel
Ready-made
Pick an outcome, answer at most three questions, switch it on.
Level 2Department managers
Steps
Add a condition or a step and choose who does it. Still reads top to bottom.
Level 3When paths split
Map
Steps laid out in department lanes, so the hand-offs between teams are visible at a glance.
Safe by design
Automation you can leave running.
Flow was built for a hotel that runs around the clock, where a mistake repeated a hundred times is worse than no automation at all.
One run per event. Nothing is done twice
Approvals with a default if nobody answers
Pauses itself after repeated failures
Every change recorded, compare and reset any time
Only administrators change automations
Paused, never deleted, when a module is switched off
What it reaches
Every Livion module, and the systems around it.
Flow uses the modules your property runs. Whatever is not in your plan is shown, never hidden, so you see what becomes possible.
Livion modules
Rooms and housekeeping, room assets, maintenance, warehouse and purchasing, restaurant, staffing, checklists, concierge and the bulletin board.
Your PMS
Checkouts and room status from the PMS can start an automation, so housekeeping and maintenance follow the stays.
Other systems, in and out
Another system can start an automation with a simple web call, and a step can send the details to another system, signed so the other side knows it came from Livion.
Nebbia
Nebbia drafts automations from your description, and a step can let Nebbia choose between options you define.
FAQ
Questions about Livion Flow
What is Livion Flow?
Livion Flow is the automation layer of Livion. It connects events in one department to the work that follows in another: a checkout to housekeeping, a broken asset to maintenance, rooms and purchasing, a declined shift to the next person on the list. Every automation is a trigger, optional conditions and steps.
Do we need to build automations ourselves?
No. Livion includes ready-made automations for the hand-offs hotels have every day, grouped by area. You can switch them on, adjust them and reset them. When you need something specific, you build your own from a trigger, conditions and steps, or describe it in words and let Nebbia draft it.
Can an automation do things without asking anyone?
Only the steps you mark as automatic. For each step you choose: Livion does it, Livion asks a named person first, or Livion files it as a task for someone on the team. For approvals you also set what happens if nobody answers in time, by default the step is skipped.
How do we know an automation does what we expect?
Before switching it on, you can try it on your hotel's recent events. Livion shows how often it would have run, how often it would have skipped and why, without carrying anything out. Once it is live, every run appears in Activity as a short story.
What happens when something goes wrong?
The run says what happened, why, what Livion did and what you can do. Each event runs once, so nothing is done twice. A failed step is retried, and an automation that keeps failing pauses itself and tells you.
Does Flow work with our other systems?
Yes. Another system can start an automation by calling a secure address, and every field it sends can be used in the steps. A step can also send details to another system. PMS events such as checkouts can start automations where a PMS is connected.
Who can create and change automations?
Administrators. Approvals go to the people, department or permission holders you name. Every change is recorded, can be compared with the original and reset.
Is Livion Flow a separate product?
No. Flow is part of Livion and works through the modules your property uses. Automations whose module is not in your plan are shown but not active.
Hand the hand-offs to Livion.
In 30 minutes we show you the automations that fit your departments, running on situations from a hotel like yours.
Continue evaluating Livion