Requests turned into services sold
Record the amount after a service is completed and the sale is checked. The report adds up recorded sales; open requests never count as revenue.
FOR MULTI-ASSET PROPERTIES — HOTEL, RESTAURANT, POOL, BEACH CLUB, SPA
More services sold.
Less high-season chaos.
Give every guest request an owner, protect the guest experience and see the value of the services your team records as sold. Built for hotels and beach clubs, from a phone.
Authenticated pilot workspace · public demo with synthetic data · no PMS integration required.
Real bookings, payments, employment intermediation, payroll, credit, external orders and real-time destination data are not active. Configuration and demonstration remain under human control.
THE OWNER’S VIEW
What did the week deliver?
Three questions to bring to the weekly meeting.
Look after the guest experience
Find requests still waiting for ownership before they turn into complaints. Reviews and reputation matter; no rating improvement or financial saving is guaranteed.
Give the team lead time back
Ownership and progress stay visible at handover. Compare minutes spent reconstructing requests before and during the pilot, using your own measurements.
HOTEL
A guest should not have to ask twice.
Reception, restaurant, spa and partner beach: one clear handover for dinner, a massage or a cabana request. Your team stays responsible for confirming availability.
Try the hotel flow →BEACH CLUB
Service at the sunbed. Order behind the scenes.
Record sunbed requests on a phone: lunch, extra towels, cabanas and boat transfers. The till, floor team and boat staff see the same progress.
Try the beach club flow →01 · THE PROBLEM
Every day, a multi-asset property loses something between one team and the next.
You do not need another management system to notice it. You need one place where requests stop living in notes, chats and verbal handovers.
- A guest asks reception for a cabana. The person who took the request finishes their shift.
- The restaurant prepares for eight people; three have already left on a transfer.
- The beach club does not know that a family asked for two sunbeds and a step-free route.
- At the end of the week nobody knows how many recorded requests received no follow-up.
The cost is not theoretical: it is the review about disorganisation, the service that was not sold and the team lead’s time spent reconstructing what was promised to whom.
02 · HOW IT WORKS
One request. One owner. One visible status.
The flow stays readable from the moment a request is created until it is closed.
Record it where it starts
Reception, bar, beach or spa: the person receiving the request enters the team, time window and need from a phone.
Route it to the right team
The request enters the relevant queue with its priority and open questions. A person takes ownership.
Keep it readable
Who owns it, when it was taken and what changed remain in the register. Open requests and ownership stay visible at handover.
THE QUESTION EVERYONE ASKS
“Who enters the data?”
It is the right first question. The answer starts with work that already exists.
The person receiving the request
No new role is created: the person speaking with the guest records the request while handling it.
From a phone
The form is designed around a few operational fields. Practise the three core actions with the 15-minute staff guide in the demo.
No initial migration
There is no need to import PMS history: the pilot starts with new requests and keeps existing systems separate.
03 · ALONGSIDE EXISTING SYSTEMS
The PMS remains the PMS. Ekonuro covers the handover between teams.
No connector needs to be configured to begin the pilot.
| System | What it continues to do |
|---|---|
| PMS | Rooms, reservations, rates and guest records. It remains the authoritative source. |
| POS | Payments, receipts and tills. It is not replaced. |
| ERP / accountant | Invoices, payroll and accounting. They remain separate. |
| Ekonuro | Operational requests, handovers and ownership that currently live outside those systems. |
No connector is promised before it has been tested at the property. The pilot begins without changing the PMS, POS or accounting stack.
04 · MULTI-DESTINATION
The property remains the starting point. Every place changes the voice.
Qemuro adapts its editorial profile to the destination without changing the guest’s action: open one link and understand the place better.
Capri
Island rhythm, sea and local stories
Ischia
Wellbeing, villages and nature
Procida
Maritime identity and slower rhythms
Naples
Neighbourhoods, culture and local life
Sorrento
Coast, traditions and orientation
Amalfi Coast
Trails, villages and journey timing
Capri is the complete profile. The other profiles are opening; operational information and local content are published only with defined sources and ownership.
05 · THE GUEST LAYER
Inside the property, Ekonuro coordinates. Outside, the guest has Qemuro.
The pilot can generate a QR card locally with the property name and logo; the public link opens Qemuro with destination and language preset. Only destination and language travel in the link: no guest or operating data. Ekonuro does not publish a separate guest portal.
SPRING 2027 PILOT
Start before the season gets busy.
Meet in autumn, prepare in winter, aim for an April start. Dates follow your property’s opening calendar.
We help you set up
Plan one afternoon together for teams, services and ownership, plus a 15-minute staff session. These are the proposed onboarding format, not measured speed claims.
Agree one measurable target
For example, zero requests without ownership at handover, or a target number of extra services sold. Record the baseline, period and target before starting.
One page. A clear decision.
Review the report together. The proposed pilot is free; duration and a fixed follow-on price are agreed in writing before it starts. Continuing requires an explicit decision.
Show us one busy shift.
Use the Italian or English demo and staff guide on a phone. Requests received on WhatsApp can be entered manually; automatic WhatsApp intake is not connected. The current workspace remains a test-data pilot until operational readiness checks are completed.
Already have a PMS? Will seasonal staff use it?
Your PMS and till stay in place. Start with one team and one service, practise intake, ownership and closure together, then measure actual use before expanding.
07 · BOUNDARIES
What remains outside the current scope.
A clear scope makes the pilot easier to assess without replacing the legal and privacy checks it requires.
- It does not decide or execute. Orders, prices, shifts, confirmations and guest messages come from an authorised person.
- It does not touch money. No collection, custody or tax transmission on behalf of the property.
- The public demo collects no identity documents or health data.
- It makes no workforce decisions. No recruiting, scoring or automated evaluation.
- It sends no guest data to Qemuro. Only destination and language travel in the link.
- It declares no integration before testing. PMS, POS and ERP stay separate until a connector is verified.