Read your first analytics baseline
Use the first Analytics pass to understand demand, activity, and where the workspace is healthy versus merely configured.
Treat analytics as an operational baseline
Your first Analytics pass is not a full business report. It is a readiness signal: are conversations arriving, are tools being used, and is the workspace beginning to show stable activity?
Focus on three early signals
- Conversation volume is non-zero and moving through the intended routes.
- Token and tool activity suggest the agent is actually doing work, not idling.
- The workspace health summary aligns with what you see in Connections, Knowledge, and Inbox.
Use the data to choose the next fix
If traffic exists but answers are weak, improve persona guidance or Knowledge coverage. If there is no traffic, return to Connections health and test delivery first. The baseline tells you where to focus next.
Why does Analytics still look empty?
Analytics is usage-driven. You need actual conversations or token activity before the baseline becomes useful. If Inbox is active, give the charts a short time to populate and then refresh.
What should I review during the first week after launch?
Review real conversations, escalation patterns, unanswered questions, tool activity, and early analytics trends. The goal is to tighten answer quality before volume compounds mistakes.
Review your first conversations in Inbox
Use the first live transcripts in Inbox to confirm routing, answer quality, and the places where the rollout still needs guardrails.
Manage workspace settings and access
Keep the workspace operable by confirming who owns rollout decisions, who can change configuration, and where tenant settings affect the live experience.
Understand billing and usage basics
Read plan posture, capacity, and early usage signals in Billing without turning the first pass into a finance project.