A useful dashboard separates immediate operating signals, weekly diagnosis, and monthly decisions. Every view should answer a question and name who acts.
Three horizons for three kinds of decision
The daily view protects the operation: arrivals, resolutions, backlog, oldest conversation, unowned work, and commitments approaching breach. It should trigger an action in the same shift, such as moving capacity or taking ownership of a risk case.
The weekly view explains variation through contact reasons, reopens, transfers, SLA by queue, and a quality sample. The monthly view examines trends, seasonality, capacity, cost per resolution, and the effect of implemented changes. Mixing horizons creates a crowded screen and a meeting with no decision.
A minimum dashboard architecture
Put inflow, outflow, and stock in the first band. Use the second for time and risk: first reply, resolution, backlog age, and percentiles as well as averages. Connect quality and effort in the third: repeat contact, transfer, available satisfaction evidence, audits, and capacity.
GOV.UK advises teams to choose a few KPIs that answer whether a service works and retain other measures for diagnosis. Google SRE defines a dashboard as a summary of a service’s core indicators and warns that averages can hide the tail of a distribution. Apply the principle carefully without treating human service as technical infrastructure.
| Cadence | Main question | Useful signals |
|---|---|---|
| Daily | Where is risk now? | Arrivals, resolutions, backlog, age, unowned work, SLA |
| Weekly | Why did it change? | Reasons, reopens, transfers, segments, quality sample |
| Monthly | Is the system improving? | Trend, capacity, cost, seasonality, implemented changes |
Every visual needs context
Show a comparison period, baseline, internal target when one exists, sample volume, and useful segments. A faster average may result from fewer complex cases; higher CSAT may come from fewer survey responses. Do not colour an indicator green or red without documenting the rule.
Record the hypothesis, action, owner, and review date beside the number. The dashboard then supports a cycle: observe, inspect conversations, test a change, and verify the same segment afterwards.
Write the metric contract before comparing results
Record the name, management question, numerator, denominator, start event, end event, observation window, calendar, exclusions, and owner. If two people cannot reproduce the same result from the same cases, the definition is not ready.
Keep the formula version with the report. A change in status, channel, business hours, or reopen policy can break historical comparability. Preserve the previous series or mark the break clearly whenever the rule changes.
- A management question written in one sentence
- An explicit numerator and denominator
- Documented eligible population and exclusions
- An observation window long enough for the measure to mature
- Segments for channel, queue, reason, and period
- A conversation sample that explains the change
- A named owner, expected action, and next review date
How to apply this with Signaldesk without claiming more than the data proves
In Signaldesk, use queues, owners, history, states, and conversation context as the operating record. Consistent fields let a manager trace a number back to the conversations behind it. AI can suggest reasons, summarise history, and flag review candidates, but people should validate classifications and decisions that affect customers or staff.
Confirm which events, reports, and exports are available in your workspace before making a formula depend on them. If a calculation needs financial cost, cohorts, or an external rule, combine the operating record with the right source and document the reconciliation. The aim is traceability, not artificial precision.
A four-week pilot
In week one, freeze definitions and establish a baseline. In week two, inspect a conversation sample and correct events or states. In week three, choose one priority cause and test a small change. In week four, compare the same segment, record side effects, and decide whether to keep, adjust, or remove the change. Four weeks is not a promised outcome; it is a practical period for validating the method and the team’s ability to act.