Home Reports
๐Ÿ“Š

Reports

Understand your helpdesk performance with reports on tickets, agents, AI, and customer satisfaction.
8 articles

Understanding reports

Reports show ticket volume, response times, agent performance, and customer satisfaction. Finding reports Click Reports in the left sidebar. You'll see the available report tabs listed below the Reports header. Available reports - ๐Ÿ“Š Overview โ€” Ticket volume and response times across your helpdesk - ๐Ÿ‘ค Agents โ€” Individual agent workload and performance - ๐Ÿค– AI agent โ€” Resolution rates and handovers for your AI agent - ๐Ÿ“ฅ Inboxes โ€” Performance by channel (email, chat, social) - ๐Ÿ‘ฅ Teams โ€” Team-level metrics - ๐Ÿท๏ธ Labels โ€” Conversation counts by label - โญ CSAT โ€” Customer satisfaction scores Who can access reports Administrators and Managers can access all reports and see data for all agents, teams, and inboxes. Agents can only access the Agents report. They see only their own performance data โ€” not other team members. Selecting a date range 1. Click the date picker in the top right 2. Choose a preset (Last 7 days, Last 30 days) or select custom dates 3. Click Apply Comparing periods 1. Click the comparison dropdown below the date picker 2. Choose a comparison type: - Previous period โ€” Same duration, immediately before your selected range - Previous year โ€” Same dates, one year earlier 3. Trends appear as percentage changes on each metric Business hours toggle When enabled, time-based metrics only count hours during your configured business hours. You'll need to set up business hours in Settings first.

Last updated on Jan 27, 2026

Overview report

The Overview report shows high-level metrics for your helpdesk. Opening the Overview report 1. Go to Reports in the sidebar 2. Click Overview Overview metrics - New tickets: Conversations created during the selected period. Excludes imported tickets. - Resolved tickets: Conversations closed during the selected period. - First response time: Average time from when a customer opens a conversation to when an agent sends the first reply. - Resolution time: Average time from the first message to ticket closure. Productivity metrics - Average response time: Average time from customer message to agent reply for follow-up responses only. The first reply in a conversation is excluded โ€” that's tracked under First response time. - Messages sent: Total outbound messages from your team during the period. - One-touch tickets: Percentage of resolved tickets where an agent sent exactly one reply. - Zero-touch tickets: Percentage of resolved tickets with no agent replies. Typically AI-resolved or auto-closed tickets. Business hours If your inbox has business hours configured, time metrics can be calculated using business hours only. Toggle this in the report settings. Using the chart Click any metric to graph it over time. Hover over the chart to see daily values. If you've set a comparison period, a dashed line shows the previous period's data. Reading trends Each metric shows a percentage change compared to your comparison period: - Green arrow up = improvement - Red arrow down = decline Common questions Why is Average response time different from First response time? First response time measures how quickly you respond to new conversations. Average response time measures ongoing responsiveness โ€” how fast you reply when customers follow up. A ticket was replied in 50 minutes, resolved, then reopened and replied in 70 minutes. What's the Average response time? 70 minutes. The first reply (50 minutes) counts toward First response time only. Average response time tracks follow-up replies โ€” in this case, the 70-minute response after the customer reopened the ticket. Why does Overview use averages while other reports use medians? Overview gives you a quick pulse check with averages. The Agents, Inboxes, and Teams reports use medians to reduce the impact of outliers when comparing individual performance.

Last updated on Jan 29, 2026

Agents report

The Agents report shows performance metrics for each team member. Opening the Agents report 1. Go to Reports in the sidebar 2. Click Agents Metrics explained - Closed tickets: Conversations this agent resolved during the period. - % of closed: This agent's share of all resolved tickets. - Tickets replied: Conversations where this agent sent at least one message. - Messages sent: Total outbound messages from this agent. - Messages received: Inbound messages in conversations assigned to this agent. - First response time: Median time from customer message to this agent's first reply. - Average response time: Average time from customer follow-up to this agent's reply. Excludes first responses. - Resolution time: Median time from first message to resolution for tickets this agent closed. - One-touch %: Percentage of tickets this agent resolved with exactly one reply. - Handle time: Median time from when this agent sent their first reply to when the ticket was resolved. Measures how long conversations stay active after the agent engages. Business hours If your inbox has business hours configured, time metrics can use business hours only. Toggle this in the report settings. Using this data High first response time usually points to assignment delays. Check if tickets are sitting unassigned. Low one-touch percentage? Consider adding more canned responses or enabling AI assist. Compare handle time across agents to identify coaching opportunities. Common questions Why doesn't my first reply count toward Average response time? First responses are tracked separately under First response time. Average response time only includes follow-up replies, when a customer messages again and the agent responds. What's the difference between Resolution time and Handle time? Resolution time is the full duration from the customer's first message to ticket closure. Handle time starts when the agent sends their first reply, measuring how long the agent actively worked on the conversation. Why are daily totals different from the date range total for Tickets replied? "Tickets replied" counts unique conversations where an agent sent at least one message. When viewing daily breakdowns, a ticket appears on each day the agent replied to it. The date range total counts each ticket once, even if the agent replied on multiple days. Example: An agent replies to the same ticket on Monday and Tuesday. The daily view counts it twice (once per day). The date range view counts it once, because it's one unique ticket.

Last updated on Feb 03, 2026

AI agent report

The AI agent report shows how your AI agent performs. Requirements You need AI agent enabled on at least one inbox to see this report. Opening the AI agent report 1. Go to Reports in the sidebar 2. Click AI agent Performance metrics - New tickets: Conversations the AI agent handled or was involved in during the period. Includes tickets currently assigned to AI and tickets handed over from AI. - Resolved tickets: Conversations the AI resolved without human help. - First response time: Median time from customer message to AI's first reply. - Resolution time: Median time from first message to resolution for AI-resolved tickets. Rate metrics - Involvement rate: Percentage of all new tickets where the AI participated. - Success rate: Percentage of AI-involved conversations that were resolved without human help. - Handover rate: Percentage of AI conversations that were escalated to a human agent. - Pending rate: Percentage of AI conversations that are still open (snoozed or waiting). Guidance breakdown Shows performance for each guidance rule: - Tickets: Conversations that matched this guidance. - Success rate: Resolved without handover. - Handover rate: Needed human help. - Pending rate: Still open. High handover rate on specific guidance means it needs clearer instructions or more knowledge sources. Action breakdown Shows how many times each custom action triggered and its success rate. Common questions How is Success rate calculated? Success rate = Resolved tickets รท Total AI-involved tickets. A ticket counts as AI-involved if the AI responded, handed it over, or resolved it. Why might Involvement rate be higher than expected? Involvement rate includes any ticket where the AI participated, even briefly. If AI sends an initial response before handing over, that ticket counts as AI-involved.

Last updated on Jan 29, 2026

Teams report

The Teams report shows metrics grouped by team. Requirements You need teams configured in Settings โ†’ Teams to see data here. Opening the Teams report 1. Go to Reports in the sidebar 2. Click Teams Metrics explained - Created tickets: Conversations created and assigned to this team during the period. - % of created: This team's share of total created tickets. - Closed tickets: Conversations resolved by team members during the period. - % of closed: This team's share of total resolved tickets. - Tickets replied: Conversations where at least one team member sent a reply. - Messages sent: Total outbound messages from team members. - Messages received: Inbound messages in conversations assigned to this team. - First response time: Median time to first reply across all team members. - Average response time: Average of each team member's average response time. Excludes first responses. - Resolution time: Median time from first message to resolution for tickets assigned to this team. - One-touch %: Percentage of tickets the team resolved with exactly one reply. - Handle time: Median time from first team member reply to resolution. - Avg CSAT: Average satisfaction score for conversations handled by this team (if CSAT is enabled). Business hours If inboxes have business hours configured, time metrics can use business hours only. Toggle this in the report settings. Common questions How is team CSAT calculated? Team CSAT is the average rating from all CSAT responses on conversations where team members participated. Why is Average response time an "average of averages"? To give equal weight to each team member regardless of ticket volume. An agent handling 10 tickets contributes the same as one handling 100.

Last updated on Jan 29, 2026

CSAT report

The CSAT report shows customer satisfaction scores. Requirements You need CSAT surveys enabled. Go to Settings โ†’ CSAT to configure. Opening the CSAT report 1. Go to Reports in the sidebar 2. Click CSAT Summary metrics - Total responses: Number of customers who completed the survey during the period. - Satisfied: Responses rated 4 or 5. - Dissatisfied: Responses rated 1, 2, or 3. - Average rating: Mean score across all responses (1-5 scale). - Satisfaction score: Percentage of responses rated 4 or 5. - Response rate: Percentage of resolved conversations where the customer completed the survey. By agent Satisfaction scores broken down by the agent who handled the conversation. Shows each agent's total responses, satisfied count, and satisfaction score. Distribution Count and percentage for each rating value (1 through 5). Helps identify if dissatisfaction clusters at specific ratings. Trend Daily satisfaction scores over your selected period. Useful for spotting patterns or the impact of changes. Common questions How is Satisfaction score different from Average rating? Average rating is the mean of all scores (e.g., 4.2 out of 5). Satisfaction score is the percentage of responses that were positive (4 or 5). Both are useful โ€” average rating shows overall sentiment, satisfaction score shows what percentage of customers are happy. Why might Response rate be low? Customers may not see the survey (email goes to spam), may ignore it, or may not feel strongly enough to respond. Response rates between 10-30% are common.

Last updated on Jan 29, 2026