Analytics

Analytics brings the organization’s operational metrics together at /admin/analytics. Access to Overview, Agents, Users, Models, Credits, and SLA requires the analytics.view permission. Logs uses the independent audit_log.view permission and can also be opened directly at /admin/analytics/logs.

The Analytics item may disappear from the sidebar while the organization has no messages. This does not change route permissions: the menu is only a navigation hint, while direct access remains protected by the permissions above.

Understand the time ranges before comparing numbers

The tabs do not share one global filter:

• the four Overview cards, the Agents and Users rankings, and Models data are cumulative, with no 30-day cutoff;
• only the Overview Conversations per Day chart covers the last 30 days;
• Credits has its own agent, channel, and date filters;
• SLA has its own 7-, 30-, or 90-day selector plus a custom range;
• Logs starts at 7 days and offers 24 hours, 7 days, or 30 days.

Do not compare two cards only because they appear on the same page. First confirm the period and population represented by each one.

The seven tabs

• Overview: cumulative totals and a chart of conversations started in the last 30 days.
• Agents: up to 10 non-archived agents, ordered by cumulative conversation count.
• Users: up to 10 non-removed members, ordered by cumulative conversation count.
• Models: AI responses, tokens, and credits grouped by the recorded model.
• Credits: credit-ledger entries within the selected period and filters.
• SLA: current queue and historical first-human-response performance.
• Logs: audit trail for actions involving agents and knowledge bases.

Overview

The cards show:

• Total Conversations: every conversation in the organization; the caption says how many currently have active status.
• Total Users: organization memberships that have not been removed. The current count also includes members without an active plan seat; confirm seats under Settings → Users.
• Credits Consumed: the cumulative sum of credits_used on conversations, not only the current month.
• Active Agents: agents with at least one conversation among the 10 agents returned by the ranking. This card can undercount organizations with more than 10 used agents and should not be treated as a complete inventory.

The Conversations per Day chart is the only part of this tab limited to the last 30 days. It counts conversations by their UTC creation date and fills days without new conversations with zero.

Agents

The list shows up to 10 non-archived agents, ordered by cumulative conversation count. If the organization has fewer than 10 agents, agents with zero conversations may appear. Each row’s bar is proportional to the first-ranked agent.

Select Details to open /admin/analytics/agents/:agentId. The detail page starts at 30 days and lets you select 7, 30, or 90 days or a custom range. It includes:

• conversation, message, credit, and tool-execution cards;
• daily activity;
• tool usage and errors;
• model and channel distributions;
• satisfaction average, coverage, distribution, and low-satisfaction conversations.

An archived agent can still be opened by URL and receives an Archived badge on the detail page, although it is absent from the main ranking.

Users

This tab shows up to 10 non-removed members, ordered by cumulative conversation count. Each row includes name, email, conversations, and credits associated with conversations whose user_id belongs to that member. If there are fewer than 10 members, people with no conversations may also appear.

Because the current query does not exclude plan_restricted_at, a member without an active plan seat may remain in this list. Use Settings → Users to verify who actually occupies an active seat.

Models

This tab considers only assistant messages with a recorded model. Its data is cumulative and does not follow the Overview chart’s 30-day window.

It contains:

• Total Messages, Models Used, and Most Used Model;
• Distribution by Model, showing each model’s percentage;
• Usage by Model, showing response counts;
• a Model, Messages, Tokens (In/Out), Credits, and Credits per Message table.

Messages without a model identifier are excluded from this distribution.

Credits

The Agent, Channel, Start Date, and End Date filters update the tab immediately. The initial range runs from the date 30 days ago through today, inclusive. There is no Apply button.

The channel selector offers Web, Telegram, WhatsApp, and Public. All channels keeps other channels in the result, but the current selector cannot isolate them. Entries without a conversation are grouped as Web by the query.

The tab shows:

• Total Credits: the absolute sum of credit_usage entries in the filter;
• Total Messages: despite its name and caption, it counts every credit entry in the period, including non-message operations such as crawl, automation, context research, and meeting transcription;
• Average per Day: total credits divided by the calendar days in the range, including days with no consumption;
• Usage per Day: entry count and credits by date;
• Top Agents by Consumption: up to 10 agents associated with entries, including entry count, credits, and main channel. Main channel means the channel with the most entries, not necessarily the highest cost.

The overall totals may include consumption without an agent. The ranking excludes entries without an agent_id, so its rows do not have to add up to the Total Credits card.

SLA

The Human support SLA tab separates current state from history:

• Current queue ignores the selected period and counts cycles still waiting for a first human response. At risk, Overdue, and Unassigned are subsets of Total waiting. An item becomes at risk when no more than 25% of its target remains, with a minimum five-minute risk window.
• Human responses, Within SLA, Average response time, and Violations use completed cycles whose first human response occurred within the selected period;
• Performance by attendant uses the same period and sorts people with the most violations first. The table shows responded, on target, violations, compliance, and average time, and identifies former members or responses without a recognized attendant.

Choose 7, 30, or 90 days or Custom. A custom range only takes effect after you select both dates and click Apply.

Logs

Logs requires audit_log.view, independently of analytics.view. A person who only has this permission opens /admin/analytics/logs directly and sees only the Logs tab.

Available filters are:

• Period: last 24 hours, 7 days, or 30 days;
• User: the action’s author;
• Action: creation, update, removal, and relationship changes for agents, tools, categories, and bases;
• Search by name: searches only the entity name, not the complete change text.

The table shows When, User, Action, and Entity in batches of 50 records. Select a row to view its author, timestamp, before and after values, and available metadata. Load more currently replaces the visible batch with the next one instead of appending it; record any details you need before moving forward.

How to investigate a discrepancy

1. Identify whether the question concerns cumulative data, the Credits range, the SLA range, or Overview’s last 30 days.
2. For costs, filter Credits by date first and then by agent. Remember that “messages” on this tab means credit-ledger entries.
3. For one agent’s performance, open Agents → Details and select the appropriate range.
4. For human-response delays, compare Current queue with historical SLA data; changing the period does not change the queue.
5. To discover who changed an agent or a base, use Logs and open the row details.