In short
A small hotel team can handle guest requests reliably in five steps: put every request on one list, give each one a named owner, set a response time, keep the guest informed, and check the result before closing it. Most requests don't fail because they're hard. They fail in the gaps between the person who hears them and the person who does them.
The hotel and its people are fictional. The situations are ones every hotel team will recognise.
Three requests, three channels
The next Friday, Meera stayed late and followed every request that came in. Three were enough to show her the problem.
9:40 PM, at the desk. Room 205 asked Arjun for a phone charger. He said he'd bring one up. Then the phone rang, a taxi arrived, and the charger reached Room 205 forty minutes later, after the guest had come down to ask again.
9:55 PM, on WhatsApp. Room 118 messaged for extra towels. The hotel's WhatsApp lives on a phone in the back office. Nobody opened it until morning.
10:20 PM, in the corridor. Ms. Iyer in Room 312 stopped a housekeeper to say her air conditioner was rattling. The housekeeper promised to tell maintenance. Maintenance had gone home at ten, so the promise became a sticky note on the housekeeping trolley.
Ms. Iyer slept badly. At checkout she was polite, and she wrote one line on the feedback card: "Nobody came about the AC."
Three requests. Three channels. Three people who each meant well. And not one place where anyone could see all three.
Why guest requests go missing in small hotel teams
Good guest request management is one of the quiet foundations of hotel operations, and it's hardest in a small team. A request can arrive at the desk, by phone, on WhatsApp, or in passing in a corridor. Whoever hears it usually means to handle it themselves. Then something else comes up, and the request quietly disappears.
Shift changes make it worse. What the evening team knew doesn't always reach the night team. And a request that belongs to "front office" belongs, in practice, to nobody.
Meera didn't need her team to try harder. She needed a little structure that everyone follows every time, however busy the night gets. It came down to five steps.
Step 1: Put every request on one list
Every request goes on one shared list, whichever way it arrived. The tool matters less than the habit: a shared spreadsheet, a logbook at the desk or a group chat with a strict format can all work, as long as there's only one.
The rule is simple: whoever hears a request writes it down within a minute, even if they plan to handle it themselves. Each line needs six things:
- The guest's name and room.
- What they asked for, in their words.
- When they asked.
- Who owns it.
- When the guest was told to expect it.
- Where it stands: open, in progress, done or checked.
Step 2: Give each request one owner
Every request gets a named owner: a person, not a department. The owner can pass the work to someone else, but stays responsible until it's closed.
This one change fixed most of Meera's lost requests. "Someone will do it" became "Arjun is doing it".
Step 3: Set a response time for each kind of request
Decide in advance how quickly each kind of request should be handled, and write it down. The right times depend on your building and your team. What matters is that they exist and everyone knows them. Four groups cover most requests:
- Items to the room, like towels, toiletries, an iron or a charger. Most housekeeping requests sit here.
- Fixes, like the air conditioning, the TV, Wi-Fi or plumbing.
- Information, like directions, timings or recommendations.
- Bookings, like a table, a taxi, the spa or a wake-up call.
Items and information are usually quick. Fixes may need an engineer, so the promise is an honest estimate. Bookings depend on someone else, so the promise is to confirm, not to complete.
Step 4: Tell the guest what's happening
Guests forgive a short wait. What they remember is silence. Three short messages cover almost everything:
- Acknowledge straight away. "Thank you, extra towels are on their way to Room 118."
- Give an honest time. "Our engineer will be with you in about twenty minutes."
- Update if it slips. "I'm sorry, this is taking longer than we said. It will be with you by 9:40."
Meera wrote these out in the hotel's voice and taped them beside the desk phone, so nobody had to find the words at the end of a long shift.
Step 5: Close the loop
A request isn't finished when the towels leave the store room. It's finished when the guest has what they needed. For fixes, and anything that went wrong, a quick check ("Is the air conditioning working properly now?") catches the times it didn't.
Closing the loop also tells you things. The same fix asked for twice in one room, or the same item missing from several rooms, points to a problem no workflow can solve alone. Room 312's air conditioner, it turned out, had been reported three times that month.
The fifteen-minute weekly review
Every Monday, Meera and the head of housekeeping spend fifteen minutes on the list. Three questions are enough:
- Which requests missed their promised time, and why?
- Which rooms or items keep coming back?
- Did anything get lost at a shift change?
Everything above can run on paper. Software helps when it gathers requests from every channel into one list automatically and warns the team before a promised time slips. The numbers this list produces turn out to matter a great deal. We come back to them in Chapter 4.
The owner's office
The list worked. Chargers arrived when promised. WhatsApp requests reached the desk. The air conditioner in Room 312 was finally replaced.
Then came a wedding weekend. By Saturday night the list ran to four pages, and Arjun was typing requests with one hand while answering the phone with the other.
On Monday, Mr. Sethi, the hotel's owner, read all four pages over his coffee and asked the question Meera had been expecting. "Isn't this what AI is for? A company called me last week. They have a chatbot."
Meera wasn't against the idea. She just wasn't sure a chatbot was the answer. Working out where AI really belongs is Chapter 3.
What Meera took away
- Every request goes on one list, whichever way the guest asked.
- Each request needs one named owner and a promised time before work starts.
- Guests forgive waiting far more easily than silence. Acknowledge first, then deliver.
- A request is done when the guest is happy, not when the item leaves the store room.
Frequently asked questions
What is the best way to manage guest requests in a small hotel?
Put every request on one list, give each one a single named owner, agree a response time for each type of request, keep the guest informed, and check the result before closing it.
How fast should hotels respond to guest requests?
Acknowledge every request straight away, then complete it within the time you have set for that kind of request. The right time depends on the property. What matters is that it is written down and kept.
Should hotels handle guest requests on WhatsApp?
WhatsApp suits many guests, but requests that arrive there must go on the same list, with the same owner and response time, as requests from every other channel.
