Read Dashboard and SLO reports

Use Dashboard for the current workspace overview. Use SLO for the operational report and its 7d or 30d period. Check the selected period before comparing values.

Read the source of each measure

Dashboard cards summarize the activity represented by their labels. Open the relevant conversation, campaign, number or workflow when you need the underlying record. A headline total is not a substitute for the individual message state.

The SLO page reports operational measures such as:

• Promotion lag: the delay between scheduled and promoted Logic Flow work. It is not the time a customer waited for a support reply.
• Flow completion: recorded completion of workflow activity. A completed path is not automatically a resolved customer request or a sale.
• Node dropoff: where recorded flow activity stops progressing. Investigate the node and its inputs before attributing the result to customer intent.

These are not agent-response SLA, revenue-attribution or conversion guarantees. Use Chat history and Automation run history to investigate the relevant operation.

Handle empty or unavailable data

An empty report can mean the selected period has no qualifying activity. Confirm the workspace, permissions and period before treating it as a failure. Missing data is not proof that no customer work occurred.

If a section cannot load, use its retry action and preserve any existing context. Do not launch duplicate broadcasts or flows merely to make a chart populate.

Compare like with like

Use the same period and definition when comparing a change. Record what was changed and verify actual task outcomes alongside activity counts. The automation measurement guide provides a manual worksheet for those outcomes; it does not imply that every suggested metric is a built-in dashboard report.