Tourism and hospitality
Enquiries, occupancy and reviews: what holds in hotels and restaurants and where dynamic pricing and guest data touch the limit.
What this is about
| Task | Classification |
|---|---|
| Answering enquiries in several languages | limited, disclosure duty |
| Forecasting occupancy and cancellations | unproblematic |
| Planning staff and supplies | unproblematic |
| Analysing and answering reviews | limited |
| Writing descriptions and images for listings | limited, labelling |
| Steering prices by occupancy | limited |
| Treating guests differently by characteristics | high to inadmissible |
The tasks that hold
- 01
Answer enquiries
Availability, arrival, house rules, special requests. In the language of the enquiry, handing over to a person for anything that is a commitment.
- 02
Forecast occupancy
From booking curve, calendar, weather and events. A time series model, not a language model.
- 03
Plan demand
Align staff and supplies to the forecast. The benefit arises in the kitchen, not in the model.
- 04
Analyse reviews
Themes and trends rather than individual opinions. Answers always as drafts.
What has to be settled first
- Which commitments a system may make. A price quoted in chat binds, and the tool does not know that.
- What the handover to a person looks like and when it happens automatically.
- Which guest data is processed and for how long. Registration data carries its own retention rules.
- Who samples the answers, and at what rate.
Pricing
| Method | Classification |
|---|---|
| Price by date, occupancy, lead time | common and lawful |
| Price by channel or booking route | lawful, keep it transparent |
| Price by device or location | legally contestable, transparency duty |
| Price by personal characteristics | inadmissible, discrimination risk |
| Personalised price from a profile | information duty under consumer law |
The second-to-last row is the one an optimisation model finds by itself if you give it the characteristics. Which is why the choice of input variables is itself a legal decision.
Guest data
- Registration data has its own statutory basis and its own retention periods. It is not a marketing list.
- Special categories arise incidentally in hospitality: dietary notes can be health or religious data.
- Marketing needs its own basis, usually consent, separate from the booking.
- Review platforms are third parties. Exporting guest data to them is a transfer with its own basis.
Metrics
| Metric | Why it counts |
|---|---|
| Share of enquiries answered without human involvement | The relief effect |
| Share of handovers to a person, with the reason | Shows where the system reaches its limit |
| Occupancy forecast error | The plannable benefit |
| Cost of goods per guest | Effect of demand planning |
| Response rate to reviews and time to answer | Effect on the outside |
Entry sheet: tourism and hospitality
FREE ACCOUNT
Entry sheet for tourism and hospitality
This sector's tasks by risk class, the points to settle beforehand, and the metrics the benefit shows up in.
Checklist3 items