The conversation ends with a complete order, not a vague question
The assistant guides the guest through the details required for a specific service and shows a clear summary before passing it on.
We’d like breakfast in our room tomorrow
The guest requests breakfast for two. Concierge AI asks for the time, menu option and any allergies required by the service rules.
Details ready for fulfilment
Once confirmed by the guest, the order, including its time, option and note, is linked to the room and passed to the team.
- details required for the specific service
- clear guest confirmation
- owner and status of the next fulfilment stage
From intent to an organised request
The module handles selected services described in the approved catalogue and scenario. It does not improvise beyond the offering, guarantee fulfilment without operational confirmation or take payments independently.
Collects the details
It asks only for the information required for the service, such as the time, number of people, option or notes.
Confirms with the guest
Before passing it on, it shows a complete summary and requires clear acceptance of the order.
Passes it on for fulfilment
It creates an organised request linked to the stay and directs it to the relevant team or system.
How does a conversation become an order?
Identifying the service
Concierge AI matches the request to an item available in the approved catalogue.
Collecting the details
It asks for all required details and explains the conditions provided in the source.
Guest confirmation
It shows the service, time, option and any known conditions, then waits for acceptance.
Passing on the request
After confirmation, it links the order to the stay and sends it through the agreed fulfilment route.
The service catalogue defines every required field
For each supported service, the hotel defines the scope, available options, fields, restrictions and fulfilment location. The PMS provides the context for the relevant stay.
What does AI use?
- guest request in Concierge AI
- approved catalogue and service rules
- stay context from the PMS
- details and guest confirmation
What does the team receive?
- complete order linked to the stay
- summary accepted by the guest
- request sent to the relevant queue
The hotel decides which services can be ordered in conversation
The team defines the catalogue, conditions, limits and handover method. Unusual requests or uncertain availability are passed to a person.
A staff member approves the scope of automated order taking, handles exceptions and remains responsible for the actual service fulfilment.
The module does not invent services, guarantee availability without a reliable source, take payments or mark an order as completed without feedback from the fulfilment process.
A shorter route from guest need to fulfilment
The team receives the required details without having to ask again for basic information.
Guests can place standard orders without waiting to connect with reception.
Every request is clearly linked to the stay and the guest’s confirmation.
Concierge collects the details; the PMS links them to the stay
The foundations are the guest guide, Concierge AI, the PMS and the agreed fulfilment channel. Additional systems may later confirm availability, price or completion.
Related process elements
Frequently asked questions
Does the guest see a summary before placing the order?
Yes. The order is passed on only after the guest clearly confirms the details.
Does AI confirm service availability?
Only when it receives that information from a reliable source. Otherwise, it passes the request to the team for verification.
Can every service be ordered?
No. The hotel specifies a defined catalogue of services and scenarios covered by the module.
Does the module take payments?
Not within the described scope. Payment requires a separate, secure integration and process.