The Analytics dashboard
What the dashboard shows
Eight panels arranged in a single scrollable view. The KPI cards and query-volume chart are on every paid plan; the other six panels require Growth or above Growth+ :
- KPI cards. Total queries, conversations, satisfaction, average response time.
- Query volume over time. Area chart of daily query counts.
- Top questions. Most-asked questions with answer count. Growth+
- Unanswered queries. Questions where retrieval came back weak. Growth+
- Channel breakdown. Pie chart of conversation volume per channel. Growth+
- Satisfaction trend. Thumbs up/down ratio over time. Growth+
- Peak hours heatmap. Day-of-week + hour-of-day grid. Growth+
- Sources usage. Which documents drove the most retrievals. Growth+
One date-range picker at the top controls every panel. The whole dashboard exports as a single CSV on Business and above (see CSV export).
KPI cards
Four cards at the top show this period's headline metrics:
- Total queries. Count of AI-generated responses across all channels.
- Total conversations. Unique conversation threads. Multiple queries per conversation count once.
- Satisfaction. Percentage of thumbs-up votes among responses that received feedback.
- Average response time. Mean latency from customer message to bot reply.
Each card shows the value plus a percentage change vs the previous period (e.g., last 7 days vs the 7 days before). Green for improvement, red for regression.
Date range
The date-range picker at the top controls all panels:
- Last 7 days. Useful for spotting this week's issues.
- Last 30 days (default). Most common view.
- Last 90 days. Longer-trend visibility.
- Custom range. Pick any start and end date.
Up to 365 days in one request, limited to the conversation history your plan keeps (see Limits below).
Top questions
Lists the 25 most-asked questions in the date range. Each row:
- Question text (de-duplicated across paraphrases).
- Count. How many times asked.
- Average satisfaction for responses to this question.
- Top source the bot cited.
Useful for spotting:
- High-volume questions to add to your FAQ. If "what's your refund policy?" comes up 200 times a month, it deserves a dedicated FAQ entry.
- Underperforming responses. A high-volume question with low satisfaction signals the bot's answer isn't good. Investigate.
Click any row to see the conversations behind it.
Unanswered queries
Lists the 25 most common questions where the bot's confidence was low or it refused to answer. Each row:
- Question text.
- Count. How many times asked.
- Top retrieval source the bot found (even though it wasn't confident enough).
This is the most actionable panel. Unanswered queries are knowledge gaps. Plug them by:
- Adding a Q&A pair with the canonical answer.
- Adding a snippet with the relevant info.
- Adding the page with Exact Links if your documentation has the answer but the page isn't indexed, or resyncing it if it changed since it was indexed (small edits can be missed by Resync; see why).
Review weekly. Reduce the unanswered list by 5 to 10 entries per week and the bot's coverage compounds.
To go further, the AI Insights panel clusters these failures into topics, diagnoses why each one failed (content missing, unclear, contradictory, or out of scope), and drafts a fix you can apply as a Q&A pair in one click.
Channel breakdown
A pie chart of conversation volume per channel. Helps you see which channels are getting traction.
The mix depends entirely on where your customers already are. Stores with mobile-first shoppers often see more WhatsApp traffic; software companies often see more website and email traffic.
Track the breakdown over time to spot channel shifts (e.g., WhatsApp adoption growing) and budget your channel investments.
Satisfaction trend
A line chart of thumbs-up percentage over time. Daily granularity by default.
Three things to watch:
- Baseline. Note where your score settles in the first few weeks and treat that as your normal.
- Spikes down. A bad day correlates with a content update gone wrong, a model provider issue, or a sudden volume spike.
- Long-term drift. Slowly declining satisfaction signals content rot. Resync the affected pages.
The chart excludes responses without feedback (most). Only thumb-voted responses count toward satisfaction.
Peak hours heatmap
A 7x24 grid showing conversation volume per day-of-week and hour-of-day. Useful for:
- Staffing decisions. When is your team busiest? Match coverage.
- SLA configuration. Set tighter SLAs during peak hours.
- Campaign timing. Launch outbound at low-volume hours to avoid drowning the inbox.
Heatmap cells deepen in color with higher volume. Hover for exact count.
Which clock the charts use
Today every day and hour on this page is counted in UTC, so a team in New York sees a 9am peak drawn at 13:00 and a late-Monday spike drawn on Tuesday. We are rolling out a workspace time zone (not yet switched on): once it is on, the daily charts, the peak-hours heatmap, custom date ranges and the CSV export all follow your workspace's time zone, including the days when clocks change for daylight saving. Each chart then says which clock it uses ("Times in America/New_York (EDT)"), and the heatmap title names the period you picked. Set it in Settings → General.
Sources usage
Lists the 25 most-cited documents in the date range. Each row:
- Document name.
- Citation count.
- Average satisfaction for responses citing this document.
Useful for content decisions: a small set of sources usually carries most citations, so keep those pages accurate first.
CSV export
For deeper analysis (BI tools, custom reports):
- Export. Click Export on the dashboard toolbar. AskVault generates one CSV covering the current date range. An overview summary, daily query volume, your top 20 questions, and the channel breakdown. And downloads it.
- Dates and times. Daily rows are UTC calendar days today. With the workspace time zone on
(rolling out), they are calendar days in your time zone and the file starts with a "Time Zone"
row. Conversation exports then write each timestamp with its UTC offset
(
2026-03-09T00:30:00-04:00), so spreadsheets read it unambiguously.
Export available on Business and above. Business+
Real-time vs cached
Every panel queries live conversation data: there's no overnight batch step. Data is cached for 60 seconds per date range, so switching tabs and back within that window shows the same numbers; after 60 seconds, or on a fresh page load, the panels refetch.
For a live view of an individual conversation as it happens, use the Live Chat inbox directly.
Limits
- Conversation history kept. 30 days on Starter, 90 days on Growth, 365 days on Business and Enterprise (7 days on Free).
- Date range per request. Up to 365 days.
- Plan availability. KPI cards and query volume on every paid plan (Starter+). The other six panels (top questions, unanswered queries, channel breakdown, satisfaction trend, peak hours, sources usage) require Growth+. CSV export requires Business+.
Common pitfalls
Satisfaction looks low. Customers only vote on responses they care strongly about (positive or negative).
Unanswered list grows over time. New questions arrive faster than you backfill content. Schedule a regular review and close the most frequent gaps first.
Channel breakdown skewed by one customer. A high-traffic enterprise customer dominates the chart. There is no dashboard-wide filter for that today; put very different audiences in separate workspaces if you need separate numbers.
Peak hours don't match your assumptions. Often the inbox is busier in evenings than during business hours, depending on your customer mix. Trust the data, not your assumptions.
FAQ
Can I see analytics per channel?
The Channel Breakdown panel shows the per-channel split for the selected date range. There isn't a dashboard-wide channel filter that applies to every other panel today.
Can I pick a custom date range?
Yes. The date-range picker at the top applies to every panel, including a custom start and end date up to 365 days. There isn't a dedicated side-by-side range-comparison view today.
Are agent metrics included?
Per-agent response times and resolution counts are available in the Help Desk's agent reports.
We're rolling out a change to how that report gives credit. Each reply will count for the teammate who wrote it, and each resolve for the teammate who resolved it, including bulk resolves. Reassigning a conversation later won't move that credit. "Handled" will mean the teammate replied to or resolved the conversation in the selected period. Until the change reaches your workspace, a conversation counts for whoever it's assigned to when you open the report.
How accurate is the data?
Counts are exact: every panel queries live conversation data, not an overnight batch. Latency is real-time measured. Satisfaction is opt-in from customer feedback.
Related guides
- AI Insights, the improvement loop
- Live Chat inbox
- Knowledge
- AI Agents page
- Conversation lifecycle
- Q&A pairs