Skip to main content

Analytics

What You Will Find on the Page​

Analytics provides a quick overview of usage, costs, data activity, workflow activity, and recordings. The current application splits analytics into tabs:

  • Usage: usage and activity trends.
  • Cost: token and model cost overview.
  • Data: data-source and collection activity.
  • Workflows: workflow runs and related trends.
  • Recordings: recording activity and processing trends.

At the top of each view, you will usually see KPIs relevant to the selected tab:

  • Conversations: the number of completed conversations and daily change.
  • Messages: the total number of messages from the last few days.
  • Data Sources: how many sources you have connected (e.g., files, databases, APIs).
  • Agents: the number of active agents.

Consider these numbers as a “health check” – if any indicator unexpectedly drops, it is a signal to verify the configuration or content.

Usage​

Use Usage to understand overall activity in the platform. This tab is the first place to check when you want to know whether users are actively working with agents and conversations.

The Usage screenshot shows headline KPIs for conversations, messages, connected data sources, and active agents. Below the KPIs, the monthly conversations chart makes adoption trends visible across the calendar year. The side panel lists recent negative feedback so admins can jump from an analytics signal into the conversations or agents that need follow-up.

Usage analytics

Typical questions:

  • Are conversations and messages increasing or decreasing?
  • Did activity change after a rollout, workflow update, or agent configuration change?
  • Are users engaging with the expected assistants?

Cost​

Use Cost to track token and model spend. This tab helps admins understand how AI usage translates into consumption and where limits or optimization may be needed.

The Cost screenshot focuses on token consumption. The KPI cards separate input, output, reasoning, and total token counts for the selected period, while the stacked chart shows how those token categories change day by day. Use this view when investigating cost spikes, model changes, or unusually long conversations.

Cost analytics

Typical questions:

  • Which period has the highest AI cost?
  • Did a newly deployed agent or workflow increase usage?
  • Should model connections receive stricter token limits?

Data​

Use Data to monitor data-source and collection activity. This is useful when agents rely on uploaded files, synced sources, or knowledge collections.

The Data screenshot summarizes the current data inventory: total storage, number of data collections, source types, and files. The donut charts break storage down by collection and source connection, and show document counts by file type. This helps admins verify whether the expected data sources are present and whether one collection or connection dominates storage usage.

Use this tab together with Data Collections when a collection exists but answer quality is low. Analytics tells you whether the data footprint looks healthy; the collection detail tells you whether the expected documents, chunks, and sync runs are actually present.

Data analytics

Typical questions:

  • Are data collections being used and updated?
  • Are new sources being added as expected?
  • Does low agent quality correlate with missing or stale data?

Workflows​

Use Workflows to monitor workflow usage and outcomes. This view is useful after publishing a workflow to a pilot team or after making a workflow available more broadly.

The Workflows screenshot shows workflow executions, operation volume, operation categories, and active periods for the selected range. The bar chart tracks workflow runs over time, while the donut chart groups operations by workflow or operation type. Use this view to identify high-volume automations and confirm whether workflow activity matches the expected business process.

This tab is especially useful after releasing a new workflow to production or after changing triggers, conditions, or external connections. Compare expected operational volume with the real run pattern before assuming a workflow is healthy.

Workflow analytics

Typical questions:

  • Which workflows are being run most often?
  • Are workflow runs completing successfully?
  • Did a workflow change affect usage or failure patterns?

Recordings​

Use Recordings to review recording activity and processing trends. This helps teams understand whether recordings are being captured, processed, and reused as expected.

The Recordings screenshot shows the total number of recordings, peak recording volume, and active recording periods. The time-series chart groups created recordings by week for the selected range, making it easier to spot adoption spikes, quiet periods, or irregular recording behavior.

If recordings are used as a source for follow-up chat, analytics, or operational review, use this tab to confirm that uploads and processing continue at the expected pace after a rollout.

Recording analytics

Typical questions:

  • Are recordings being created regularly?
  • Are there periods with unusual recording activity?
  • Does recording usage support the intended team workflow?

Chart Interpretation​

Below the KPIs, analytics views use charts to show trends over time. For quick diagnostics:

  • Sharp drop = check the availability of agents, connected channels, or recent changes in prompts or workflows.
  • Growth = verify whether capacity (rate limits, resources) is keeping up.

Feedback and Follow-up​

When analytics points to quality or adoption problems, follow the signal into the related operational page:

  • Open Conversations to inspect the conversation that created the signal.
  • Open Agents to adjust instructions, tools, prompts, or model settings.
  • Open Data to check whether the agent has the right data collection.
  • Open Workflows when the signal may come from automation volume or failed orchestration behavior.
  • Open Recordings when the issue is tied to transcript availability or uneven recording intake.
  • Open Logs to inspect audit events or tool executions.

Tips for Working with Data​

  • Monitor daily changes in KPIs to quickly identify fluctuations.
  • If the number of messages is increasing without a rise in conversations, check the quality of responses (feedback) and possibly adjust the instructions.
  • With zero data sources, verify that agents have the correct datasets and access assigned.