Skip to main content
The Analytics section in the left sidebar contains four dashboards. Each answers a different question: Access requires the Manage Analytics permission, which only admins have by default. See Roles and Permissions if the section is missing from your sidebar.

Overview

The Overview page (titled Agent Productivity) gives you a live snapshot of your operations. It is the only dashboard that auto-refreshes — the Operations Overview section carries an “Auto-refreshes every 5m” pill — and you can click Refresh for the latest data at any time. Analytics overview dashboard

Real-Time Status

Four cards show your current operational state:

Today’s Performance (vs Yesterday)

Summary cards compare today’s numbers to yesterday, each with the current value and the percentage change:

Distribution charts (Last 7 Days)

Below the cards, three groups of charts break down the past week:
  • Conversation distribution — a pie chart of conversation volume by channel (Website, SMS, WhatsApp, Messenger, Email, Zalo, Zalo OA) and a line chart of daily volume per channel.
  • Ticket distribution — daily tickets by status (Open, In Progress, Closed) and daily ticket volume by channel.
  • Escalation trends — escalations per day, and a breakdown of which channels generate the most escalations.
Check the Overview at the start of each shift. Queue Depth and Agents Online together tell you immediately whether you are staffed for the current load — before any customer feels the wait.

Chat Agents

The Chat Agents page measures engagement and conversion for website chat agents — how many visitors see your pages, how many start a chat, and how many become leads. It covers website agents only; if you have none, the page prompts you to create one. The Chat Agents analytics page controls — chatbot selector, date range, refresh, and export — showing the No data available message for a period with no report data

Controls

Summary cards

Four cards, each showing a trend against the prior period of equal length: Read the two conversion percentages as a funnel: page views → chats → leads. If page views are healthy but chats are low, your widget or conversation starters need work; if chats are high but leads are low, the agent isn’t collecting contact details effectively.

Engagement and conversion charts

  • Engagement chart — Page Views as a toggleable line, Chats as a line, and Leads as bars, over time.
  • Conversion Performance — chat conversion % and lead conversion % over time, with averages.
  • Why People Chat — a donut of the top contact reasons.
  • How Chats Begin — Manual (visitor typed) vs Preset (clicked a conversation starter).
  • Conversation Starter Distribution — which preset buttons get used most. Retire starters nobody clicks and promote the ones that convert.
  • Top Chat URLs — the 10 pages generating the most chats, with its own Export CSV.
  • URL Categories — chats by website section (top 5, plus Other).

Exports

Two CSVs are available: a daily report (Date, Page Views, Chats, Leads, Meetings, Successful Resolutions, Chat Conversion, Lead Conversion, Resolution Rate) and a URL data file (URL, Chat Count). Use the daily report to build your own week-over-week comparisons, or subscribe to Daily Reports for a scheduled summary instead.

AI Agents

The AI Agents page (titled AI Agent Performance) monitors AI effectiveness, response performance, and escalation patterns. Use the date range selector to choose a period (defaults to the last 7 days). Refresh is manual; there is no export. The AI Agent Performance dashboard with the Containment Rate and AI Fail Rate KPI cards, the Performance comparison section, and the response time and messages-per-conversation charts

KPI cards

Two cards summarize AI performance: The two come from different systems: Containment Rate, volume, and response times come from conversation analysis, while AI Fail Rate is produced by the evaluation system — see Evaluations Overview for how conversations get scored.
Read the two cards together. High containment with a high fail rate means the AI is closing conversations it shouldn’t — customers aren’t escalating, but they aren’t getting good answers either. Aim for containment rising while fail rate holds or falls.

Agent Performance table

A sortable per-agent table with these columns: Sort by Fail % to find the agent that most needs prompt or knowledge base work; sort by Volume to see where a fix pays off fastest.

Response and escalation charts

  • Response time histogram — the distribution of AI response times, with the average.
  • Messages per conversation — how long a typical AI conversation runs, with the average.
  • Conversations by day — daily volume broken down per agent.
  • Conversation heatmap — conversation volume by date and hour of day. Use it to see when visitors are most active.
  • Escalation heatmap — when handoffs to humans happen, by time of day.
If containment starts falling, check the escalation heatmap first: escalations concentrated in specific hours usually point to a traffic pattern (a topic your agent can’t handle that spikes at certain times, or after-hours questions it defers) rather than a general quality regression. Escalations spread evenly across days point back to the agent itself — review recent prompt or knowledge base changes. For what happens after a handoff, see Human Takeover.

Human Agents

The Human Agents page (titled Human Agent Performance) tracks team productivity, workload distribution, and response times. Use the date range selector to choose a period (defaults to the last 7 days). Refresh is manual; there is no export. The Human Agent Performance dashboard with the FRT, AHT, TTR, Resolution Rate, and CSAT summary cards above the Agent Leaderboard and workload charts

Team summary cards

Five cards summarize the team: CSAT comes from conversation feedback ratings — customers must be asked to rate. Enable feedback in the Feedback section of Chat Agent Advanced Settings, or this card stays empty.

Agent leaderboard

A sortable per-agent table: Agent, Active (open conversations), Total (conversations), Tickets Assigned, Tickets Resolved, FRT, Handle Time, Resolution Time, Resolution %, CSAT. Use it to compare like with like: an agent with a slow FRT but the highest ticket load isn’t underperforming — they’re overloaded. Ticket columns reflect the workflows described in Working with Tickets.

Workload and response charts

  • Workload distribution — conversations per agent and peak hours.
  • Ticket trend — ticket creation and resolution over the period.
  • Response time analysis — human response times, including first response time by hour.
If FRT is rising, check the workload distribution chart before blaming individuals: a lopsided distribution means routing is funneling too much to too few people. Review your routing rules and per-agent concurrency caps in Conversation Routing, then confirm with first response time by hour whether the slowdown tracks specific shifts.

What’s Next

  • Daily Reports — get a scheduled summary of these metrics delivered instead of checking dashboards.
  • Evaluations Overview — how the quality checks behind AI Fail Rate work, and how to tune them.