Skip to main content

Dashboard Analytics

The analytics area now covers much more than session counts. It ties conversation activity, leads, handoffs, ROI assumptions, CRM outcomes, and shared reporting into one workspace view.

What you can measure​

  • sessions and message volume
  • leads captured
  • human handoffs
  • high-intent or outcome-tagged activity
  • ROI assumptions applied to operational events
  • influenced pipeline and influenced closed-won revenue
  • report snapshots shared with stakeholders

Core analytics surfaces​

Overview dashboard​

The main dashboard highlights current performance, recent sessions, notifications, and operating tasks that still need attention.

Sessions​

Use the sessions area to review:

  • full transcripts
  • flags and review status
  • per-session timing and message counts
  • exported CSV or JSON history

Leads​

Track captured leads and connect them back to the session that created them. Lead analytics are especially useful when paired with ROI assumptions and CRM attribution.

Handoffs​

Measure:

  • queue volume
  • first-response pressure
  • resolution timing
  • the topics most likely to require human takeover

ROI modeling​

Per website, you can assign expected values for events such as:

  • leads
  • meetings booked
  • support resolutions
  • high-intent sessions
  • handoffs

Those assumptions power outcome summaries inside analytics.

CRM attribution​

If CRM attribution is configured, analytics also show:

  • open pipeline
  • influenced pipeline
  • closed won revenue
  • influenced closed won revenue
  • synced opportunities and top influenced deals

See Revenue Attribution.

Shared reports​

You can freeze the current analytics view into a shareable report link. Each shared report stores the exact snapshot at the moment it was created instead of changing underneath the recipient later.

Using analytics to improve the system​

Use the analytics surface to:

  1. Find the questions and flows that cause handoffs.
  2. Add or improve knowledge sources for recurring gaps.
  3. Run retrieval evals before publishing high-risk changes.
  4. Compare rollout candidates before moving traffic.
  5. Tie operational activity back to influenced revenue.

Accessing Analytics​

Navigate to Analytics from the dashboard sidebar.

Related docs: