Most support teams have a vague sense that response times are "pretty good."
They're usually wrong.
Not because the team is slow. But because averages hide the real problem. Your median response time might look fine while a handful of tickets are sitting for 18 hours. Or Mondays are quietly destroying your SLA while Friday looks great. You don't see it because HubSpot's built-in reporting doesn't surface it without custom reports you've probably never built.
Here's a five-minute fix.
First-response time is one of the biggest drivers of customer satisfaction in support, and it's one of the easiest things to quietly let slip. The issue is never usually the team. It's patterns: a specific day of the week, a ticket category nobody has a template for, or a ticket type that keeps getting routed to the wrong person.
Once you can see the pattern, fixing it is usually straightforward. Until you can see it, you're guessing.
This audit also sets you up to make a real call on whether Breeze Customer Agent is worth turning on. HubSpot's AI support agent now charges $0.50 per resolved conversation (not per conversation, only when it actually resolves the issue, as of April 14, 2026). If you can quantify how many of your tickets could be templated responses, you can run the numbers yourself.
Go to CRM > Tickets in your HubSpot account.
Filter the view by Create Date: last 30 days. If you want to scope it further, open tickets only, a specific pipeline. Apply those filters now.
Make sure you're in the list (table) view. In the top right, click Export. Choose CSV as your file format, and select which properties to include. At minimum, you want:
Click Export. HubSpot will send you a download link via email. It usually arrives within a couple of minutes.
Open the CSV. Open Claude or ChatGPT. Upload the file and use this prompt exactly:
"Here are my support tickets as a CSV. For each ticket, calculate the time between creation and first reply. Give me: (1) Average first-response time, (2) The 10 slowest tickets with what caused the delay, (3) Which day of the week has the worst response times, and (4) What percentage could be answered with a templated response. Show me the numbers, not your opinions."
That last line matters. Without it, you'll get a paragraph of hedged observations. With it, you get a table.
The AI will work through the data and return actual figures: average hours to first reply, the outliers, day-of-week breakdowns, and a rough categorisation of ticket types by complexity. The "templated response" estimate is especially useful, it gives you a data-backed number to anchor any conversation about automation or AI.
A few things to look for in the output:
The gap between average and worst. If your average first-response is two hours but your 10 slowest tickets took 20+ hours each, the average is masking a real problem. Those outliers are the ones your customers remember.
Day-of-week patterns. Monday morning backlogs are common. Weekend tickets pile up and the team is slow to triage. If that's your pattern, it's fixable with a queuing or routing rule, not more headcount.
The templated response percentage. If 40% of your tickets are variations of the same three questions, that's a concrete case for either a knowledge base, canned responses, or a Breeze Customer Agent trial. If it's 10%, it's probably not worth the setup.
Breeze Customer Agent is worth considering if this audit shows a significant volume of repetitive, low-complexity tickets. As of April 2026, it's priced at $0.50 per resolved conversation, and the key word is resolved. HubSpot only charges you when the AI actually closes the ticket without human escalation. If it can't resolve it, you don't pay.
But whether it makes sense for your portal depends on your ticket mix, which is exactly what this audit tells you.
If 50% of your tickets are password resets and policy questions, Breeze is probably worth a 28-day free trial (which HubSpot now includes for Pro and Enterprise customers). If your support is mostly complex, bespoke queries that need a human, it's probably not the right fit yet.
Run the numbers. Then decide.
The audit output is most useful if it goes to someone who can act on it. That might mean:
This is the kind of thing that takes five minutes to run and three weeks to get around to. Run it now, while you're thinking about it.
If the audit surfaces something bigger, a routing problem, a support ops gap, a Breeze setup you want to do properly, that's the kind of thing we help with.
Neighbourhood is a Diamond HubSpot Partner. We spend a lot of time inside Service Hub setups that have grown faster than they were designed. If yours is one of them, drop a message and we'll take a look.
For more HubSpot AI hacks and technical deep-dives, subscribe to our Ops Intelligence newsletter below. Come join us over on our Facebook page and YouTube channel to be part of the conversation.
Happy HubSpotting!