Operational reports
Read workspace activity and operational reports for the selected period.
Reviewed
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.
Read support performance
Open Support performance at /analytics/support to inspect human response,
resolution and waiting conversations. Access requires reporting permission and
retains your workspace, number and conversation visibility restrictions.
Choose a range of up to 31 UTC calendar days and, when needed, filter by team, assignee or number. Response and resolution use different cohorts; current waiting backlog includes open waiting sessions regardless of the selected dates. Switch the cohort before comparing rows, and group by team, agent or number to inspect the available session details. Missing measurements display as unavailable, not as zero-duration responses. If the report is too large, narrow its filters.
These measurements describe recorded conversation activity. They do not establish an SLA guarantee or measure the speed of Waaru Care's own support service.
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.
Consent and safety settings
Set opt-out keywords and STOP/START replies, and understand how active marketing warnings differ from the safety checks on new sends.
Billing and plan interest
Review free platform access and the dashboard’s provisional plan-interest controls without confusing them with checkout or AI usage billing.