Why the group chat breaks down
- Nobody owns the message. Five people read “Room 204 needs towels”; each assumes one of the others went.
- A message has no state. It cannot be open, in progress or done. The only way to find out is to ask again — in the same group.
- There is no clock. You cannot tell whether requests take ten minutes or an hour, or at what time of day they pile up.
- It buries itself. By evening the morning’s unanswered request is two hundred messages up, and staff mute busy groups.
- Shift changes lose it. The night shift joins a conversation with no idea what is still pending from the day.
- Guest details end up on personal phones. Names, room numbers and phone numbers sit in chats on staff members’ own phones — including after those people have left. Guests gave those details to the hotel, not to everyone who was ever in the group; they belong where only the staff who need them can see them.
None of this is the staff’s fault. A chat is designed for talking, and a hotel needs something designed for jobs.
What a request system has to do
| It needs | Because |
|---|---|
| One owner per request | “Somebody will go” means nobody goes |
| A clock with a target | Acknowledge within so many minutes, resolve within so many, per category |
| Categories that route | Towels to housekeeping, the AC to maintenance, food to the kitchen |
| Escalation | When a target is missed, the request moves to the next person up |
| A record | Who did it, when, and how long it took |
| No app for the guest | Phones read a QR code with the camera or the browser they already have; very few guests will install your app |
| A way for the desk to log calls | Phone calls and walk-ups belong in the same queue |
How QR requests work in practice
- Print a QR code for each room and put it where a guest looks: the bedside, the desk card, the back of the door. Print the room number on it too.
- The guest scans it with the phone camera and picks what they need — housekeeping, water, towels, a maintenance problem, food. A short note or a photo helps.
- The request becomes a ticket for that room, routed to whoever is on duty for that category.
- That person acknowledges it — the first clock stops — and then resolves it.
- If a target is missed, the ticket goes up the chain: the supervisor, then the manager.
- The owner sees what is open, response and resolution times, and which rooms and categories keep coming back.
One evening, two requests
An illustration of how the clock works — the times are made up for the example, not measured:
| Time | What happens |
|---|---|
| 21:04 | Room 204 scans the QR code and asks for an extra blanket. A ticket opens for housekeeping. |
| 21:05 | The housekeeper on duty gets it on her phone and taps acknowledge — one minute to respond. |
| 21:13 | The blanket is in the room and the ticket is resolved — nine minutes, start to finish. |
| 23:10 | Room 311 reports that the AC is not cooling. A ticket opens for maintenance. |
| 23:20 | Nobody has acknowledged it within the ten-minute target, so it escalates to the duty manager. |
| 23:24 | The duty manager acknowledges it, sends the electrician on call and offers the guest a fan. |
| 23:55 | The AC is fixed; the ticket is resolved, with the breach on record. |
The next morning the owner does not need anyone’s version of the night. The first request met its targets; the second missed one, and the record shows where — which is a question about the on-call arrangement, not about the electrician who eventually came.
What to print on the QR card
- The room number, large enough to read from the bed.
- One line that says what the code is for: “Scan for towels, water, housekeeping or a repair — no app needed.”
- The same line in Hindi, or in the language most of your guests read.
- The desk’s phone number, for a guest without a smartphone or a data connection.
- Nothing else. A card crowded with Wi-Fi passwords, menus and offers is a card nobody reads.
Setting response targets
Targets are what make the clock mean something. Start with a short list and adjust it after a month of real numbers. The figures below are a starting point you would set for yourself — not a standard, and not a promise any hotel makes:
| Category | Acknowledge within | Resolve within |
|---|---|---|
| Towels, water, toiletries | 5 minutes | 15 minutes |
| Room cleaning | 10 minutes | 45 minutes |
| AC, fan, lights, power | 10 minutes | 60 minutes |
| Plumbing, hot water | 10 minutes | 60 minutes |
| Food and room service | 5 minutes | 30 minutes |
| Complaint | 5 minutes | 30 minutes |
Two rules keep targets honest. The clock starts when the guest asked, not when somebody noticed. And a request marked resolved should actually be resolved: a “done” that the guest disputes does more harm than a ticket left open.
Rolling it out without upsetting the staff
- Start with one floor, or one category, for two weeks.
- Keep the WhatsApp group for talking. Move only the jobs out of it.
- Have the desk log phone calls and walk-up requests as tickets too, so the queue is the whole picture.
- Look at the numbers with the team every week. For the first month use them to find problems — a room whose AC fails every few days — not to blame people.
- Then set the targets the numbers say are realistic, and hold to them.
What to measure, and how to measure it honestly
- Median time to resolve, not the average. One request forgotten overnight drags an average up by hours; the median shows what a typical guest experienced.
- Share acknowledged within target. The first thing a guest notices is whether anybody responded.
- Requests per room and per category. The same room asking for maintenance every week needs a repair, not faster service.
- Requests closed without a resolve time. If staff close tickets without marking them resolved, your timings will flatter you. Count those separately and say so, rather than quietly leaving them out.