Use these four Analytics Dashboard templates to start monitoring support activity, team performance, AI impact, and Knowledge Base efficiency in Crisp.

Crisp Analytics includes many reports, metrics, views, and filters. Templates give your team a ready-made starting point, so you can understand what is happening in support without building every Dashboard from scratch.

This guide covers:

• Why use Dashboard templates? → when templates are useful
• How to import a Dashboard → where to upload a template file
• Four templates you can use → activity, team, AI, and Knowledge Base views
• How to customize your Dashboards → filters and segments to adapt each template
• Where to go next → companion Analytics articles

Why use Dashboard templates

Templates help you avoid starting from a blank page. They group useful reports into a clear structure, then automatically use your real workspace data once imported.

A good Analytics setup usually looks at four layers: what is happening, how your team handles it, how much AI helps, and whether your Knowledge Base reduces repetitive questions.

How to import a Dashboard

Open Crisp, then go to Analytics → Dashboards. Click Create a new dashboard, choose Import from a file, and upload the .json file for the Dashboard you want to reuse.

Once imported, the Dashboard appears in your list and can be renamed, edited, filtered, or exported again.

4 Dashboard templates you can use inside Crisp

Each template answers a different operational question. You can use them as they are, or edit them to match your team structure, support channels, customer segments, and reporting habits.

Conversation Overview

This Dashboard gives you a global view of support activity: conversation volume, peaks, channels, and first response origin.

Included metrics

This template usually includes:

• Conversations Over Time → volume trend across the selected period
• Conversations Per Period → heatmap of daily and hourly activity patterns
• Most Used Conversation Channels → where conversations come from
• Conversations Per First Response Origin → human, automation, AI, or other first response sources

How to interpret it

Start with conversation peaks. If volume spikes on specific days or hours, adjust staffing, routing, or automation coverage around those periods. Then compare channels to understand where customers actually contact you, and review first response origin to see whether automations are helping with the initial load.

Useful resources: how Crisp Analytics work and improve customer service response time.

Team Performance Dashboard

This Dashboard helps team leads review how agents handle conversations, where workload is concentrated, and whether response targets are being met.

Included metrics

This template usually includes:

• Human Conversations → conversations handled by human agents
• First Response Time → how quickly users receive the first reply
• Global Resolution Time → average time to resolve conversations
• Operator Rating → customer satisfaction per operator
• Operators Table → operator-level volume, response time, resolution time, and ratings
• Conversations Per Operator → workload distribution across the team
• Conversations Breaching SLA → conversations that exceed your response target

How to interpret it

Start with workload distribution. If a few operators handle a disproportionate share of conversations, review routing, shifts, and assignment rules. Then compare response and resolution times with the team median to identify coaching opportunities or process gaps.

If SLA breaches spike at specific times, align staffing or strengthen automation during those periods. If breaches rise across the board, the team may need better shortcuts, clearer triage, or more AI coverage for repetitive requests.

Useful resources: Routing and Assign and keyboard shortcuts for the Crisp Inbox.

AI Performance Dashboard

This Dashboard focuses on how Crisp automation and Hugo reduce workload, speed up resolution, and affect customer satisfaction.

Included metrics

This template usually includes:

• Conversations → total conversation volume
• Automated Conversations → conversations initially handled by AI or automation
• Fully Automated Conversations → conversations resolved without human intervention
• Human Resolution Time → average resolution time for human-handled conversations
• AI Resolution Time → average resolution time for AI-handled conversations
• Overall Rating / Automation Rating → customer satisfaction across human and automated interactions
• Saved Time → estimated time saved by fully automated conversations

How to interpret it

Compare human and AI resolution times to understand where automation is creating value. Fully automated conversations are the clearest signal that Hugo is removing repetitive work from the team.

If automation performance is lower than expected, review missing knowledge, weak instructions, unclear routing prompts, or edge cases where Hugo escalates too often. Those gaps usually show where training resources or workflows should be improved next.

Useful resources: Getting started with Hugo AI Agent and How to measure AI Chatbot ROI with Crisp?.

Knowledge Base Performance Dashboard

This Dashboard shows how effectively your documentation supports self-service and reduces repetitive questions.

Included metrics

This template usually includes:

• Website Visits / Knowledge Base Visits → traffic to your site and documentation
• Knowledge Base Visits Over Time → article consumption trend
• Visits by Language → views by Knowledge Base locale
• Articles Table → visits, reactions, usefulness, and article-level details
• Top Search Queries → most searched terms inside the Knowledge Base

How to interpret it

Start with search queries. They reveal what customers tried to solve before contacting support. If high-volume searches have poor article coverage or low usefulness scores, prioritize those topics.

Then compare article visits with support trends. If an article receives traffic but does not reduce conversations, it may need clearer steps, better examples, stronger internal links, or a better title. Use the language breakdown to prioritize translation work when multiple locales are active.

Useful resources: use the Knowledge Base and format Knowledge Base articles.

How to customize your Dashboards

Once a template is imported, the easiest way to make it relevant is to use segments and filters. This lets the same Dashboard answer different operational questions without duplicating every chart.

Segments can help you compare:

• Teams or inboxes → Support, Sales, Billing, VIP support, or language-specific teams
• Customer types → free users, paid users, enterprise accounts, new customers, or high-value customers
• Conversation topics → bug reports, onboarding, refunds, pricing, or product questions
• Channels → chat, email, WhatsApp, Instagram, Messenger, or other connected channels
• Regions or languages → country, locale, or market-specific views

For example, apply an Enterprise segment to review high-value customers, a Bug reports segment to monitor engineering-related workload, or a WhatsApp segment to understand channel-specific performance.

Useful resource: What is a segment and how can it help your team?.

Where to go next

These four templates give you a practical starting point for customer support reporting. Import them, review the default charts, remove anything your team does not use, and add custom charts as your reporting needs become clearer.

Useful companion articles:

• How do Crisp Analytics work? → understand reports, filters, and metric calculations
• How to build a custom dashboard in Crisp Analytics? → create your own reporting view from scratch
• How to import / export a dashboard in Analytics? → reuse templates across teammates or workspaces

Updated on: 03/05/2026