Skip to content
Vyrobel Example scenario · 96 keys · city hotel
Illustrative scenario, composed from onboarding conversations · vyrobel.com
Hotel · city centre· 9 min read

The floor stopped phoning reception

⚠️ An illustrative scenario, not a customer. Vyrobel is new and has no published customer stories yet. This describes how the product is used by an operation of this shape, composed from onboarding conversations. Nothing here is a claim about a real business, and no figure is a measured result.

Ninety-six keys, a legacy PMS only the front desk could use, and a housekeeping team working from a sheet printed at seven in the morning.

Property
96 keys
independent, one building
Housekeeping
14
across two shifts
Peak turnover
40+ rooms
on a summer Saturday
Live in
7 weeks
February, deliberately

Before: a system with one door into it

The old PMS worked, in the sense that the front desk could check a guest in and take a payment. Nobody else could get into it. Housekeeping had a printed sheet, maintenance had a notebook behind the desk, and the only connection between those two and the reservation system was a person walking between them.

On a forty-room turnover day this produced a specific kind of chaos. Reception could not see which rooms were ready, so they phoned the floor. Every call interrupted somebody cleaning, which made the room later, which produced another call. Guests waited in the lobby with their luggage while two departments who both wanted to help them were unable to see each other's work.

The switch: February, and one department at a time

Seven weeks in the quietest month of the year, and the sequence mattered more than the speed. Housekeeping went first, on its own, for a fortnight before anything else changed: the board on phones, the four states, the old printed sheet still coming out in parallel. By the time it was the front desk's turn, the floor already trusted the thing they were being asked to depend on.

Front desk was the real test, and it was where the fortnight of parallel running earned its cost. Two receptionists worked both systems for a full week, and the exercise surfaced a group-booking pattern the import had flattened into individual reservations. That was fixed before cutover rather than discovered in July.

Channels moved on a Tuesday morning in the seventh week, with fourteen arrivals on the board and both teams watching.

After: the loop closed

Reception can see room state without asking, so the calls stopped. A room marked guest-ready appears at the desk in the same second, which means the guest in the lobby is handed a key by someone who already knew rather than someone who has just been told.

Rooms with a guest waiting pin themselves to the top of the board, which changed the shape of the turnover day more than any single feature. The cleaner is not guessing at priority; the priority is on the screen.

Maintenance was the quiet win. A cleaner photographs a broken shower screen and raises a ticket from the room in fifteen seconds, and if that ticket takes the room out of service the room stops selling immediately — including on the channels. The category of problem where a known-broken room kept being sold has simply gone.

Desk-to-floor calls
Effectively eliminated on turnover days. Room state is visible to both.
Broken rooms off sale
A maintenance ticket blocks the room across every channel, automatically.

What was harder than expected

Two long-serving receptionists genuinely did not want to change, and said so. Both were right that the old system was faster for them personally, because fifteen years of muscle memory is worth a lot. The honest answer was that the hotel was optimising for the whole floor rather than for the desk, and that took a difficult conversation rather than a training session. One of them is now the person who trains new starters.

The group booking import also had to be redone by hand. Fourteen group reservations that the export represented as blocks came across as individual stays, and rebuilding them correctly took a day nobody had planned for.

Illustrative scenario

Composed from onboarding conversations with independent hotels of this size. Named customers and verified figures replace it at launch.

Vyrobel for hotels Read: housekeeping at scale
Vyrobel · Property management for hotels, apartments and villas · contact@vyrobel.com · vyrobel.com
Figures in this story are illustrative. Named customers and verified numbers replace them at launch.

An ordinary visit sets 2 cookies — vyrobel-session and XSRF-TOKEN. 2 more appear only if you ask for them. All 4 are strictly necessary, and there are no analytics, no marketing and no third-party cookies at all — nothing here tracks you across other sites. So there is nothing on this notice to switch off today. We record your answer anyway, because it binds us if that ever changes.

What each one is for
Every cookie this site sets
Cookie What it does How long When it is set
vyrobel-session Keeps your session — the sign-in that follows you between pages, and the basket of a booking in progress. 2 hours On your first page view.
XSRF-TOKEN Protects every form on the site from cross-site request forgery. Without it a form you submit here could be forged from another site. 2 hours On your first page view.
vy_td Remembers a device you chose to trust, so two-factor authentication does not ask again on it. 30 days Only if you tick “trust this device” at a two-factor prompt. Never otherwise.
vy_cookie_choice Remembers the answer you gave on this notice, so it is not shown again and so the answer can be honoured. 365 days Only when you answer this notice.
Privacy notice