Guests keep chasing requests. How can hotels see each one through?
AI-generated hotel operations concept; not a customer installation or a measured service result.
A guest asks for a firmer pillow, calls again after dinner, then explains the request to someone starting the evening shift. Several employees have spoken to the guest. The pillow still has not arrived.
A hotel can improve this experience with a simple request record and clear responsibility. Use the team's existing paper log or shared document, provided the duty team can find the same current record.
Write down the request the guest actually made
Record the item or service, quantity, room and preferred arrangement. “Two bath towels after we return” gives an attendant more useful information than “guest needs towels.” Repeat the details back before ending the conversation.
This follows a basic point in TESDA's housekeeping training: clarify the need and record the details, including an agreed delivery time. Add an owner, progress states and shift handover to keep unfinished requests visible.
Ask only what the task requires. Record access preferences without adding personal explanations that other employees do not need. Keep the record within the hotel's approved staff channels; room details and guest names do not belong in public messages.
Name an owner and agree the next contact
The person accepting a request should remain responsible for following it through until another named employee accepts responsibility. Sending a message to housekeeping is a handoff attempt. Check that someone has accepted it.
Before promising delivery, check availability and the team's workload. Agree a realistic service window with the guest. If that cannot yet be confirmed, agree when someone will provide an update. An honest callback arrangement is more useful than repeating “soon.”
Record the promised time separately from the actual completion time. If the window will be missed, the owner contacts the guest before it expires where possible, explains the delay and agrees the next step. An unavailable item needs an alternative the guest accepts.
Use one shared request record
Copy these fields into the team's existing log. Give each request a reference so calls, messages and departmental notes can point to the same task.
| Field | What staff enter |
|---|---|
| Reference and received time | One request reference; when it first arrived |
| Room and exact need | Room identifier, item or service, quantity and relevant detail |
| Guest's agreed arrangement | Delivery window or callback time; preferred contact method |
| Access instructions | Knock and deliver, agreed appointment, or another permitted arrangement |
| Owner and accepting employee | Who follows up; who accepted the operational task |
| Current status | Received, accepted, in progress, awaiting guest, or completed |
| Delay and next action | Blocker, next action, person responsible and next update due |
| Completion evidence | What happened, when, and any necessary guest confirmation |
The log needs an end state for a declined or cancelled request too. Record the outcome accurately so a cancellation does not appear as successful delivery.
Close the task when the guest can use the service
An acknowledgement means the hotel has received the request. An attendant collecting the item means work has started. Completion means the agreed service has been delivered in a usable condition.
For a borrowed appliance, that may include the agreed setup and a brief explanation. For a repair, the employee should check that the fault is resolved. A guest who asked for delivery while present still needs that agreed appointment respected.
Follow the property's room-entry and do-not-disturb procedures. If access is unavailable, record the task as awaiting access and follow the agreed contact arrangement. Never count a blocked door visit as completed service.
Carry open requests across the shift
At handover, review every unresolved request with the incoming owner. Include the guest's last update, the obstacle and the next action due. The incoming employee explicitly accepts the task before the outgoing employee leaves it.
Consider a hypothetical evening request for a firmer pillow. The first employee confirms the preference, finds that the floor stock is empty and contacts the supervisor. The guest agrees to an update once availability has been checked. At shift change, the incoming owner sees that the update remains due and follows it through, even if the pillow comes from another department.
Escalate when the agreed window is at risk, an item cannot be sourced, the guest has already chased, or the issue needs a supervisor's authority. Urgent safety or security concerns follow the hotel's immediate response procedure.
Check failures per 100 requests
Review a sample of completed and unresolved records together each week. Use the same denominator so a busy week can be compared fairly with a quiet one.
- Repeat contacts about the same unresolved need per 100 requests.
- Requests that missed their agreed service window per 100 requests.
- Requests reopened after being marked complete per 100 requests.
- Requests left without an accepted owner at shift change per 100 requests.
Read failed records before changing targets. Stock shortages need supply changes; missed handovers need a clearer handover routine. Preserve the original received time when a guest calls again to show their actual wait.