Move from a metric to its cause
The dashboard goes beyond conversation counts. It links topic, channel, quality and escalation reason, then shows the source material.
Rising evening workload
Over the past four weeks, the number of contacts after 19:00 has risen, and staff have more often taken over conversations started by AI.
Two recurring sources of workload
The dashboard points to incomplete knowledge about night-time access and a high number of questions about parking availability, with a list of conversations to review.
- trend by time, channel and topic
- link to knowledge gaps and quality
- drill down to source conversations
One operational view of all communication
The dashboard supports knowledge, automation and staffing planning. It aggregates contact data while preserving the ability to check what lies behind every important metric.
Connects channels
It shows chat, messaging, email, telephony and portals in a comparable structure of topics and outcomes.
Shows trends
It measures volume, response time, sentiment, quality, gaps and escalations over the selected period.
Leads to the conversation
Every metric can be expanded into a list of contacts that produced the result.
How do conversations become a useful dashboard?
Standardising data
Contacts from different channels receive common topics, statuses, timings and outcomes.
Connecting quality data
The dashboard adds detected knowledge gaps, sentiment analysis, audit results and escalation history.
Aggregating metrics
Data is calculated by period, channel, topic, property and team in line with access rights.
Analysing sources
The user moves from a trend to the conversations and decides whether to change knowledge, processes or staffing.
Shared definitions make channels comparable
Response time, escalation and quality must mean the same thing in every source. The dashboard stores the definitions and data scope used for each metric.
What does AI use?
- standardised conversation histories
- topics, timings and handling statuses
- knowledge gaps and sentiment analysis
- quality control results and escalations
What does the team receive?
- volume and response-time dashboard
- topic, quality and sentiment trends
- conversation lists behind the metrics
A metric without a definition and source should not drive a decision
The user can see the period, filters and calculation method. Access to conversation content is subject to permissions, and reporting can be aggregated to the appropriate level.
The manager selects the scope and filters, verifies source conversations and decides whether to change knowledge, processes, automation or staffing.
The dashboard does not answer guests, change automation rules, assess a staff member based on a single conversation or hide incomplete sources.
Communication becomes a visible operational process
The hotel can see the volume and rhythm of contacts across all connected channels.
Topics, gaps and escalation reasons show what is really driving the team’s workload.
The data helps set priorities for knowledge, automation and staffing.
The analytics layer uses the full communication history
The dashboard connects the central conversation history with quality, sentiment, knowledge-gap and continuity modules. The view depends on permissions.
Related process elements
Frequently asked questions
Which channels can the dashboard cover?
Chat, messaging, email, telephony and portals, provided their data has been connected and standardised.
Can source conversations be opened?
Yes, in line with the user’s permissions. Metrics lead to the contacts that produced the result.
Does the dashboard show data from multiple properties?
It can, if the implementation covers a group and shared categories, permissions and aggregation levels have been defined.
Does the dashboard change processes automatically?
No. It highlights the trend and source material; the team decides whether to make a change.