Help Desk Chapter 3: Reporting
Your manager asks how the team’s doing. You know the answer. Mostly good, a few rough days, a couple of great days, nothing catastrophic. But now you need to prove it.
Cue the spreadsheet gymnastics. Export this, cross reference that, calculate averages manually because the numbers don’t quite line up. An hour later, you’ve got something that sort of answers the question.
Or flip the scenario: you’re the manager who needs to make a decision right now. Should you reassign tickets? Pull someone into coverage? You don’t have time to dig through data, so you guess. Sometimes you’re right. Sometimes you’re not.
Here’s what changes with Help Desk reporting: the answers are just there. No hunting, no exporting, no math homework. You look, you know, you act.
The Two Ways You’ll Actually Use Reporting
Most reporting tools give you everything and overwhelm you with nothing useful. Help Desk splits it into two modes: what’s happening right now, and what’s been happening over time. That’s it. Simple.
Summary: Your “Right Now” Dashboard
Open Help Desk, click Summary, and you see today. A real-time, high-level overview of your team’s performance.
Team availability shows who’s online, who’s at max capacity, who’s about to be. Ticket counts break down by channel and priority. SLA progress tells you what’s overdue, what’s due soon, what’s on track. Customer wait times, response times, calling metrics—all updating as things happen.
Why this matters: you can actually intervene before problems compound. You see three reps hit max capacity at 2pm, you don’t wait until 4pm when tickets are piling up. You act when you still have options.
Having clickable numbers is huge here. Every metric links directly to the actual tickets behind it. “Time to first reply” isn’t just a number—click it, see which tickets missed the SLA, categorize them to see exactly where the team is hitting and missing the mark. Done. Those linked results take you straight into the Help Desk with filters already applied, so you’re looking at exactly what needs attention.
One thing to know about those delta changes you’re seeing: they compare to the same time of day for your chosen period. If it’s 10am today and you’re comparing to yesterday, you’re seeing the change from 10am yesterday to 10am today. It’s an apples-to-apples comparison that actually makes sense.
Analyze: Your “What’s the Pattern” Tool
When you need to look beyond today, that’s Analyze. Same core metrics, but over time. Filter by rep, team, channel, category, whatever cut you need to understand what’s actually happening.
The built in reports cover what most teams need: tickets created over time, average response times, SLA completion rates, message volume patterns, time to close trends. You’re not building everything from scratch.
Here’s the part that saves you time: AI assisted insights. Click the Breeze icon on any report, and Copilot summarizes what the data’s showing. “First reply times increased 18% this week, driven primarily by email channel volume doubling.” Now you know what to investigate instead of squinting at graphs trying to figure out what changed.
And yeah, everything’s still clickable. Numbers always connect back to actual tickets. You’re never wondering “which tickets does this metric include?”, just click and see them.
Pro tip: Turn on category identification to be able to automatically set the reason the customer reached out using AI. This analyzes the first message of the ticket and is based on both default and custom options. If you need to manually change the value, the AI model learns to categorize it better next time.
Please note: this setting is turned off by default. To turn on Category identification:
- In your HubSpot account, click the settings settings icon in the top navigation bar.
- In left sidebar, navigate to Inbox & Help Desk, then select Help Desk.
- Click AI tools.
- Toggle on the Category identification switch.
When You Need a Deeper View: Service Analytics
Sometimes you need to go beyond Help Desk’s daily and trend reporting. That’s when you head to Service Analytics (Service > Service Analytics). It pulls from Help Desk data and gives you more specialized analysis for the niche questions that come up in support operations.
Here’s what makes Service Analytics worth the extra click:
Average time to close in SLA hours: Not just calendar time—actual working hours against your SLA. See which ticket types consistently disrupt your service commitments.
Hour of day patterns: When do tickets hit the “waiting on us” stage? When are the most reps available? Staff your team based on actual demand, not assumptions.
AI handoff analysis: Track when your chatbot and Customer Agent escalate to humans. Pattern recognition here helps you improve autonomous resolution rates.
Revenue impact: Connect ticket data to revenue. Which support issues are affecting your highest-value customers?
The beauty of Service Analytics is specificity. You’re not looking at these reports every day—you’re pulling them when you need to understand a specific pattern or make a specific decision. Think quarterly reviews, process improvements, or investigating why something changed.
How This Actually Plays Out
Daily routine: Check Summary when you start your day. See what’s urgent. Throughout the day, glance back if something feels off or to make sure the team is on track. The real-time updates mean you’re working with current information, not yesterday’s snapshot.
Weekly reviews: Pull up Analyze. Look at trends from the past week. Use AI insights to quickly spot what changed. Click through to see specific tickets when numbers need context. Adjust processes based on patterns, not one-off incidents.
Coaching conversations: Stop having vague “try to respond faster” talks. Pull the specific data. Show your rep the percent of their tickets that met SLAs with SLA adherence. See how many tickets they resolved by a single answer with one-touch tickets. Understand what’s happening, and give targeted guidance.
Leadership updates: They ask how the team’s performing? Screenshot the Summary tab. It’s current, comprehensive, and shows you’re on top of things. Need to go deeper? Pull an Analyze report with AI insights already summarizing the story.
Process improvements: When you’re questioning why something keeps happening, dig into Service Analytics. Maybe those high-message tickets correlate with a specific product issue. Or your KB articles about billing generate more tickets than they resolve. Now you know what to fix.
The system works because everything connects. Real-time visibility for immediate decisions. Trend analysis for pattern spotting. Clickable metrics for context. AI insights when you need the data translated. Service Analytics when you need specialized views.
What You Actually Get
Help Desk reporting isn’t about having more data. It’s about having the right data when you need it, in a format that helps you make decisions instead of doing math.
Because it’s all built on the same data powering the rest of Help Desk, you’re not reconciling numbers across tools or wondering if your reports are accurate. The data’s consistent because the foundation is solid.
Questions about specific reports you should set up? Want to know which metrics actually matter for your team? Curious how other teams are using this stuff? Bring them to the upcoming AMA December 8-12 where our product team can walk through your specific scenarios.
What’s next in the series: Operations: Team Spaces, Advanced Ticket Operations, Unified Channel Management, and Advanced Routing. Coming soon.
Catch up on the series: