Two matters concerning one guest do not get lost in separate channels
The dashboard brings together information related to the same stay and shows its sequence, so staff can start with the context instead of searching for it.
Maintenance request and low rating
The guest reported an air-conditioning problem and later mentioned noise in a survey. Their breakfast order has already been accepted for the following day.
One story and clear next steps
The dashboard shows the status, owner, timing and source of each interaction, placing the matter requiring attention at the top of the list.
- complete event timeline for the active stay
- matters without an owner or response
- links to original requests and responses
An operational view of the stay, not another fragmented report
The dashboard aggregates existing events from the guest guide and highlights service gaps. It does not take action itself, resolve complaints or replace source systems.
Connects events
Puts check-ins, requests, orders and surveys on a shared timeline for the relevant stay.
Highlights exceptions
Highlights matters without an owner, past their deadline or with a signal requiring review.
Preserves sources
Links to the original form, order or response and shows the history of status changes.
How is a shared stay view created?
Identifying the stay
The dashboard connects events marked with the same guest-guide identifier and booking context.
Normalising statuses
It brings different sources into shared categories such as new, in progress, completed and requiring attention.
Setting priorities
It displays matters according to approved rules for timing, ownership and signal type.
Working with the source
Staff open the details, move to the relevant process and update the status in the authorised place.
One identifier links interactions to the right stay
The dashboard needs consistent links between events and clear statuses. It should not copy complete data unnecessarily — it shows a summary and leads to the source.
What does AI use?
- remote check-in status
- requests and their statuses
- service orders
- surveys, ratings and service history
What does the team receive?
- shared timeline for the active stay
- list of matters requiring attention
- owners, deadlines and links to sources
The dashboard highlights work but does not decide for the team
View rules help organise matters, but staff assess the situation, contact the guest and confirm the resolution in the appropriate process.
The team assigns owners, verifies priorities, takes action and is responsible for changing the status of each matter.
The dashboard does not send messages independently, order services, award compensation, close requests or replace the PMS or task management system.
The team identifies what guests need faster
Key interactions are available together, with their timing and source preserved.
Issues without a response or owner do not get lost between inboxes and forms.
The next person can take over without asking the guest to repeat the entire history.
The dashboard brings together events from the guest guide and stay processes
The foundations are the guest guide, remote check-in, requests, surveys and orders. Notifications and location analysis can extend the view, but are not required.
Related process elements
Frequently asked questions
Does the dashboard replace the PMS?
No. It brings together digital service events and can display PMS context, but the source system remains authoritative for reservations.
Can I see the full history of an issue?
Yes. The dashboard shows an event timeline and links to the source requests, orders and responses.
Does the module prioritise issues automatically?
It can highlight issues according to approved rules, but a person verifies their significance and the order of response.
Can messages be sent from the dashboard?
Not as part of the core scope. The dashboard points to the relevant process or source where the team takes action.