Skip to content

Experience 360

Three addresses. One system.

A guest opens stay., your team works staff., you run admin. — and underneath, all three are the same three systems. Scroll, and watch one become the next.

A club sandwichKitchenExtra towelsHousekeepingA table at eightDiningLate checkoutFront deskTwo sunbeds by the poolPoolThe spa at fourSpaA taxi to VallettaConciergeMore coffee podsHousekeeping
The Wi-Fi passwordFront deskA high chairDiningSomewhere open on a MondayConciergeA cot for the babyHousekeepingThe air conditioningMaintenanceA doctorFront deskBreakfast on the terraceKitchenThe airport transferConcierge

Running at

db Seabank Resort & Spa

500 rooms in Mellieħa, Malta — four restaurants, a pool, and a front desk that stopped taking dinner bookings by phone.

One system, three addresses

It is not three products. It is three ways in.

Room 412

Good evening, Ms Vella

Your order

Room service

Club sandwich · Still water

Cooking

Sent

Seen

Cooking

Delivered

Ravi from the kitchen picked this up at 19:42.

Table at Marea, 20:00

Confirmed · 2 covers

Ask for

Extra towelsIceLate checkoutA taxi

Stay

Dining

Services

Orders

What the guest sees

No app and no account — a card in the room and the surname on the booking. Menus, opening hours, room service and a table at eight, in every language they arrive in.

What is underneath

Three shapes, and the same three things in each.

The hardware changes because the job changes — a hand, a counter, a desk. What does not change is underneath: a content engine, a request router and a message hub. We built those three and stopped.

One catalogue

A price, an opening hour or a photograph is entered once. All three read the same row, so none of them can be out of date with another.

One router

A request finds its department by what it is, not by who tapped it. A sandwich and a towel are two tasks the moment they leave the basket.

One notion of now

Open, closed, full, breaching, checked out. Decided in the database, so the phone, the queue and the console cannot disagree.

All of it, one system

Twenty things a property is asked for. One place they land.

A towel, a table, a taxi and a late checkout are four different jobs for four different teams. They are not four different systems.

  • Key card
  • Concierge bell
  • Room service
  • Dining
  • The pool
  • Housekeeping
  • Spa
  • Scan to enter
  • Arrivals
  • The bar
  • Messaging
  • Reports
  • Do not disturb
  • Wi-Fi
  • Gift vouchers
  • The room
  • Meeting rooms
  • The gym
  • Transfers
  • Late checkout

What you switch on

Start with a page. Add the rest when you want it.

A hotel that wants a directory and a QR code should not be sold an order router it will never open. Each of these switches on a surface that is already built and already tested.

Information page

A page behind one QR code, in your colours. The base, and a real product on its own.

Dining & bookings

Your outlets as content, as a booking engine, and as a page a non-resident can book from.

Facilities

The pool, the spa, the meeting rooms. A sunbed is a seat and a session is a seating.

Teams & access

Who may change a price, who may see a queue. Ticked in the console, enforced in the database.

Reports

What was ordered, what it earned, and which offer earned it — attributed from the first day.

Arrivals & PMS

Tonight’s arrivals imported from your booking system, idempotently, without retyping a name.

A day, end to end

Eight requests, six departments, one system.

  1. 07:40Dining

    Breakfast at Marea

    Booked from the room last night. The restaurant knew the covers before anyone came down.

  2. 09:15Housekeeping

    Extra towels, room 412

    Acknowledged in forty seconds, by the floor that was already on that corridor.

  3. 11:00Pool

    Two sunbeds, by the water

    A sunbed is a seat and a session is a seating. It needed no new idea at all.

  4. 13:30Front desk

    Late checkout, tomorrow

    Answered without a phone call, and without anyone walking down to reception.

  5. 16:00Spa

    A treatment at four

    Offered because there was a gap, to a guest whose stay had three days left in it.

  6. 19:42Kitchen

    Club sandwich, still water

    One basket, two departments, two tickets. She watches it move on her own phone.

  7. 20:00Dining

    A table at Marea, two covers

    Confirmed against the seat count, the table count and the party in the room.

  8. 21:10AI concierge

    Tomorrow, try The Lantern

    Verdala is full and Marea has been done. Nobody is sent to the same room twice.

The part that decides it

A guest uses it for a week.
Your team uses it every shift.

So a guest will forgive a clumsy screen, and a waiter on their ninth hour will not. That is how every one of these systems dies: acknowledging an order takes five taps, the floor quietly stops doing it, and three weeks later the hotel says the software didn’t work.

Don’t take our word for it. Press the button, and watch the guest’s phone change.

Kitchen queue

Oldest first · 3 open

0 taps
412

Club sandwich · Still water

Room service · 2 min ago

New
118

Extra towels ×2

Housekeeping · 4 min ago

507

Late checkout, 14:00

Front desk · 6 min ago

Room 412 sees: Waiting to be picked up

Twenty minutes, and you’ll know.

We’ll put your own property into the demo before the call, so you are looking at your restaurants and your rooms rather than somebody else’s.