WhatsApp is the fastest way to say something.And the fastest way to lose it.

Azulo is the Virtual Desk for hotels, and it runs inside WhatsApp. The desk you never see, the one your team runs on memory and goodwill, gets an owner, a status, a handover and proof. And nobody moves off WhatsApp to get them.

14 days free. Unlimited staff on every plan. We don't charge by the head.

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.

Two desks and the bridge between them. That is the whole product.

Properties and operators we have worked with

  • Mövenpick
  • Marchica Lagoon Resort
  • Michlifen Resort & Golf
  • Kenzi Hotels Group
  • RATP Dev

Hospitality and transport, single properties and groups. Different industries, the same problem: work that arrives as a message and leaves without a trace.

The problem you already have

WhatsApp is fast. It just has no memory.

Nobody compiles them. They fall out of the work.

Hotel · Staff group

Recepción

412 says the AC isn't working

21:06

Mantenimiento

👍

21:44

Recepción

Anyone got 412?

22:31

Turno noche

just came on, what's 412?

22:33

Recepción

?

07:15

Nobody is at fault here. There is simply nothing in this thread that owns anything.

  • The guest asks twice.
  • The answer was sent, but nobody owns the request.
  • The next shift cannot see the story.
  • Reception rings housekeeping. Again.
  • The complaint was acknowledged, never closed.
  • The manager finds out from the review.

What a lost message costs

The group chat is free. The way it fails is not.

Three costs. None of them appear on an invoice.

  1. 01

    You are paying trained people to be a search engine

    40 repeat questions a day, three minutes each, is two hours of payroll gone before lunch. Count yours tomorrow morning.

    Breakfast hours. The wifi password. Where to park. Every one of those pulls a receptionist away from the person standing in front of them, and every one of them has the same answer it had yesterday.

  2. 02

    An unread message is an uncaptured request

    Take the requests you'd have said yes to last month and multiply by what each was worth. That number is not on any report you currently receive.

    A late checkout, a table for two, a spa slot. The guest asks once, it scrolls past three other messages, and they quietly stop asking. Nobody logged a loss, because nobody logged anything.

  3. 03

    The complaint you never closed is now public

    One review moves your rating for months. You already know roughly what a tenth of a point does to your rate.

    A fault fixed inside the stay costs you a repair. The same fault, unclosed and unmentioned again, becomes a paragraph about unresponsive service read by everyone deciding whether to book you.

We publish no ROI figure and no case-study percentage, because we have not measured yours. Run one workflow for thirty days and the number will be yours, not ours.

Count it for yourself

Put your own numbers in.

Ours are guesses. Yours are not. Move the sliders.

Assumptions you can change

60
78%
3

Assumes 0.8 messages per occupied room per day, and that 60% of them are questions with the same answer as yesterday. Both are our starting points, not measurements. If they are wrong for you, the result is wrong by the same amount.

8

Hours a week answering the same questions

Front desk time, at your occupancy

51

Staff days a year

The same hours, annualised

This is multiplication, not a study. It is worth exactly as much as the numbers you typed into it, which is the point.

Two desks

One faces the guest. One faces the hotel.

The same desk, seen from either side.

Guest Desk

The front of the desk

Repeat questions answered in the guest's own language, at 23:40, without waking anybody. Real requests captured with an owner. Anything sensitive held for a person, because a complaint is not a job for a machine.

Reception · Front office · Guest experience · Reservations

Team Desk

The back of the desk

Readiness work with a name on it. Rooms, incidents, planned jobs and shift handovers across housekeeping, maintenance, F&B and the gobernanta's team. Owned, routed, escalated, closed.

Housekeeping · Maintenance · F&B · Operations · GM

There is no third desk. When a guest request needs another team, the request, the owner, the status and the guest follow-up simply stay attached to each other. That bridge is the part every other tool drops.

What changes on the floor

You will know it worked when you hear these four sentences.

Not from a report. From the people on shift.

I know who owns this.
The next shift can see what happened.
The guest did not have to ask again.
We saw it was stuck before it became a complaint.

What you can finally prove

The numbers arrive on their own.

Nobody compiles them. They fall out of the work, which is the only reason they are still true on a Tuesday morning.

Requests captured

312

A typical week, 60-room hotel

Answered by the Desk

64%

Reception handled the rest

Median first response

14 min

Their own target was 20

Closed inside target, by team

Front office91%9 min
Maintenance82%18 min
Housekeeping64%24 min

Same thing breaking twice

Room 412 · Split unit3
Room 1104 · Door lock3
Room 305 · Basin tap2

Nobody spotted this in the group chat. It was there the whole time.

The panel above is a typical week on the Desk. It is modelled, not measured, because we told you we don't publish figures we haven't earned. The thirty-day pilot is how the numbers become yours, with your name on them.

  • Staff stay in control

    The Desk answers what repeats. Your people keep the part a guest is actually paying for.

  • Nobody moves off WhatsApp

    Same app for the guest. Same habit for your team. The request just stops disappearing.

  • The data is yours

    Cancel tomorrow and we delete nothing. Bring your own number and it leaves with you.

Pick one Desk Workflow. Run it for thirty days.

Not a full rollout and not every channel on day one. One workflow your reception already dreads, one owner, one number to watch. If it doesn't move, we'll have found that out cheaply and so will you.

or WhatsApp us