The Virtual Desk

One desk. Two faces.

Guest Desk faces the person who wants something. Team Desk faces the people who can do it. One product, not two bolted together. That is why a message becomes somebody's job and comes back as an answer without being retyped.

Desk on

Marta Ferreira

WhatsApp · Room 412 · Arrives 22:40

Hola, our train gets in late. Is there parking, and can we still check in?

Reception is open all night, so a late arrival is no problem. Parking is in the square behind the hotel, 18 EUR a night. Shall I hold a space?

Answered by the Desk

Yes please. Also the air conditioning in 412 is not cooling.

Held for Elena to answer. The Desk does not improvise on a complaint.

Waiting on reception, 40 seconds

Two requests, captured, nobody typed them

Hold a parking space

#4820Square lot · Arrival 22:40
AssignedFront officeRouted by the Desk
ELElena, front office

Air-conditioning not cooling

Urgent
#4821Room 412 · Split unit
AssignedMaintenanceRouted by the Desk

3rd fault on this unit since April

YMYusuf, maintenance

The Desk answered the parking question in the guest's own language, held the complaint for a person, and turned both into work with an owner.

Desk Workflow

Six things a WhatsApp message never has.

A Desk Workflow is the six things that turn a message into work you can trust. It is the unit we sell, prove and expand: one workflow at a time, never the whole hotel at once.

01

Owner

Somebody's name, not a group chat.

02

Route

To the team whose job it actually is.

03

Status

Which the next shift can read without ringing anyone.

04

Escalation

A clock, so silence is not the same as handled.

05

Closure

With what was done, in the words of whoever did it.

06

Proof

Kept, so the pattern shows up later on its own.

What sits behind each face

Six parts. Still one desk.

Guest Desk

Guest contact

One place for WhatsApp, email, the OTA inbox and the booking form. The Desk answers what you have taught it, drafts a reply for the rest, and holds anything sensitive for a person. The thread stays attached to the guest, the room, and whatever work came out of it.

Guest Desk

Requests and recovery

A parking hold, an early check-in, a late checkout, a complaint. Each becomes a real request with an owner and a clock instead of a promise somebody has to remember. Service offers get followed up rather than mentioned once and forgotten.

Team Desk

Readiness work

Four kinds of work, kept apart on purpose: routine jobs, faults, guest complaints, and things people reserve. Each asks for different information, goes to a different person, and runs on a different clock. Flattening them into one generic list is exactly how the urgency gets lost.

Team Desk

Rooms and equipment

Your rooms, floors, restaurants, plant rooms and the kit inside each one. Every job hangs off a real place and a real machine. That is the whole trick behind knowing 412's split unit has failed three times since April, instead of vaguely feeling that it has.

Team Desk

Teams and shifts

Housekeeping, maintenance, front office, security and IT each get their own view. A gobernanta sees her floor. The GM sees the property. Everyone else gets My Shift: the short list of what is theirs, right now, on the phone in their pocket.

Team Desk

Schedules and escalation

Weekly deep cleans, monthly equipment checks, the daily opening round. They write themselves and turn up on the right phone. Anything that goes quiet escalates on its own, against a response time that is enforced rather than aspirational.

What the Desk is not

It is not a chatbot, and it is not there to replace your reception.

A chatbot stops at the moment a real hotel job begins. And replacing reception is not the idea: the judgement, the tone and the awkward conversations are what your guests are paying for. The Desk takes what repeats so your people keep what doesn't.

Not an inbox

Putting five channels in one window is tidier. It still leaves the work unowned.

Not a report

Numbers are the by-product. A manager's report your staff never feed is a prettier guess.

Not a hotel OS

Your PMS stays your PMS. We take the coordination nobody's system was holding.

How you start

Three steps between interested and running.

No project plan, no rollout committee. This is the whole of it.

01

Bring your WhatsApp number

Your own WhatsApp Business number, connected. If you don't have one yet, we help you get it. The channel stays yours, whoever you pay later.

02

Pick one workflow

The one your reception already dreads. We map how it runs today and the Desk arrives set up around it. You adjust; you don't build.

03

Run it for thirty days

One owner, one number to watch. If it moves, switch on the next workflow. If it doesn't, we found that out cheaply, and we'll say so.

It arrives configured

Say what kind of operation you run and the Desk turns up with the categories, place types, equipment and departments that fit it. You adjust. You do not build.

Made for a corridor

The staff screens are drawn for a phone held in one hand by somebody carrying linen in the other. Not a desktop in a back office.

Thirteen languages

A guest writes German. Your gobernanta reads Spanish. A seasonal hire reads Arabic. Nobody is translating on their phone between rooms.

The questions you're not typing into the form

Asked before you have to ask.

How long does setup take?
A working session, not a project. The Desk arrives configured for your kind of operation; you rename what your team already calls things and connect the number. Most properties run their first workflow the same week.
Do you integrate with our PMS?
The first workflow doesn't need your PMS at all. It runs on WhatsApp and the Desk itself. Your PMS stays your PMS; we take the coordination no system was holding.
Is this allowed on WhatsApp?
Yes. The Desk runs on the official WhatsApp Business Platform, on your own number, under Meta's business messaging rules. No grey-market gateways, nothing that puts your number at risk.
How much training does the team need?
If someone can use WhatsApp, they can close a job. My Shift shows each person the short list of what's theirs, and the first shift is usually the training.
What if the team doesn't use it?
Then the pilot fails, cheaply, and we'll tell you so. That is exactly why we start with one workflow and one owner instead of a rollout: adoption gets measured, not assumed.