Sample · Hospitality
Sample: a guest assistant that creates a real task
This sample shows a guest assistant for a single hotel that answers a short list of questions and turns everything else into a task the right department can see. It is a concept, not a hotel we have delivered.
- One property, not a group rollout
- WhatsApp or web, not both, until the task path is trusted
- No unsupervised changes to the folio
- A daily review of transcripts for the first two weeks
Sample solution. This describes a concept we use to show the shape of a build. It is not a client engagement and it is not a result from a completed customer project.
The problem the concept takes seriously
Guests write on WhatsApp and the website about late checkout, extra towels, and airport pickup. Those messages sit with whoever is near a phone. Housekeeping never sees the towel. The desk promises a checkout the manager has not approved.
The shape of the first release
The assistant knows the property facts you publish: hours, wifi, dining times. A request for housekeeping or maintenance becomes a task with the room number taken from the reservation system, not typed from memory. Billing arguments and complaints go straight to a person, with the transcript.
- One property, not a group rollout
- WhatsApp or web, not both, until the task path is trusted
- No unsupervised changes to the folio
- A daily review of transcripts for the first two weeks
What would make this a real project
A reservation system we are allowed to read, a named owner on the desk, and Arabic and English examples of the questions guests already send. Without those, the concept stays a concept.
A guest assistant that stops
The sample includes
- Answers for hours and requests
- A task for the department
- A handover when the guest is unhappy
A real hotel would still need
- The actual property system
- The night staff who will own the queue
- A decision on what the bot must never say
What would make this real
The source
Answers have to come from that hotel’s content, not from a generic model.
The desk
If the night manager will not open the queue, the bot should not be launched.
The bill
Charges stay with a person. The sample does not pretend otherwise.
If this shape fits a hotel
- 01
Your content
Hours and requests in your words, not a generic model.
- 02
The night queue
A person who will open the handover.
- 03
The property system
Where the stay already lives.
- 04
The bill
Confirm charges stay with staff.
Marks this hotel sample keeps its boundary
- 01
It is a sample
No hotel is named and no occupancy result is claimed.
- 02
The assistant hands over
A request the bot cannot finish reaches the desk with the room.
- 03
The folio is the record
The lesson is that guest messages meet the stay, not a separate chat log.
- 04
No metric is added
Response time and savings are not invented.
