What This Update Actually Is
HubSpot shipped a redesigned analytics experience for the Customer Agent, which is the AI-powered support agent inside Service Hub. You'll find it under the Analyze tab by clicking Reports.
The Performance section got two meaningful changes. First, the handoff rate formula changed. It now counts conversations with a handoff divided by all conversations where the Customer Agent was the assigned owner, not total conversations. Second, the deflection rate formula changed. It now excludes any conversation that started with a human owner. The updated formula only measures conversations where the Customer Agent started as the owner and remained the owner without pulling in a human.
Both changes are about accuracy, not aesthetics. The numbers you see now reflect what your agent actually did, not a blended average that masked real performance.
Why HubSpot Shipped This
The old reporting view crammed too much into one screen. Service leaders were left staring at charts that felt incomplete at best and misleading at worst.
Here's a specific problem we've seen across portals: a support team routes some conversations directly to human agents and others to the Customer Agent. The old deflection rate mixed both pools together. That dragged the rate down even when the AI agent was actually handling its assigned conversations well. Humans responsible for reporting had no clean way to explain that gap to leadership.
The same confusion hit handoff rate. If the agent was only assigned to half your conversations but the formula divided by all conversations, the metric looked better than it was. Or worse. Depending on routing logic, it could swing either direction.
HubSpot fixed both formulas to scope each metric to the conversations that actually belong to the agent. That's the right baseline for any AI performance conversation.
How to Use It Step by Step
- Navigate to your HubSpot portal and open the Service workspace.
- Click the Analyze tab in the top navigation.
- Select Reports. You'll land on the refreshed Performance section automatically.
- Review your Handoff Rate. Remember the new formula: handoffs divided by conversations where the Customer Agent was the assigned owner. A rising rate here means more escalations from your AI agent's assigned conversations.
- Review your Deflection Rate. This number now only counts conversations where the Customer Agent started as the owner. A higher rate means the agent is resolving more issues without needing a human. A lower rate is a signal to look at your knowledge base content or agent configuration.
- Compare current numbers to your historical benchmarks. Because the formulas changed, your new numbers may look different from last month's. Don't panic. Set a new baseline from today's data going forward.
- Share the updated view with your service leadership team and walk them through the formula changes before they compare new numbers to old ones.
What It Touches in Your HubSpot Strategy
This update lives inside Service Hub, but it ripples into your broader RevOps reporting stack. If you're using the Customer Agent as part of an omnichannel service motion, these numbers feed leadership dashboards and QBR decks. Getting them right matters.
Key Takeaway
Your deflection rate and handoff rate are now scoped to the conversations the Customer Agent actually owned. Historical comparisons will look different. Set a clean baseline from the update date and build your benchmarks forward from there.
Conversation Routing and Inbox Configuration
The deflection rate formula now excludes conversations that started with a human owner. That means your inbox routing rules directly affect this metric. If you've set up routing that sends certain conversation types straight to a human agent, those conversations are invisible to the deflection rate calculation. Review your routing logic to make sure you're measuring the full scope of what the Customer Agent is actually handling.
AI Agent Configuration and Knowledge Base
A low deflection rate after this update is a diagnostic signal, not just a bad number. It likely points to gaps in your knowledge base content or agent instructions. The Customer Agent can only deflect what it has the knowledge to handle. Use the updated report to identify which conversation types result in handoffs, then work backward to fill the content gap.
Cross-Hub Data and Reporting
This update is one piece of a larger agentic platform story HubSpot has been building. If you want the full picture of where AI agents are headed inside HubSpot, our deep dive on the HubSpot agentic platform covers what's live today and where it's heading.
Key Takeaway
Handoff rate and deflection rate are now your two clearest levers for evaluating AI agent ROI. Track them week over week and tie changes directly to knowledge base updates or routing rule adjustments.
Custom Dashboards and Leadership Reporting
If you've pulled Customer Agent metrics into a custom dashboard, revisit those reports after this update. The underlying data has changed. This is similar to the kind of recalibration work that comes with any HubSpot data layer update, like what teams had to do after the HubSpot Merge Rules update shifted how winning records are determined. When the formula changes, your dashboards need a review.
Who Should Care Most
Not every update demands action from every role. Here's who needs to pay attention to this one:
- Service Hub admins who configure the Customer Agent and own performance reporting. You'll need to set a new baseline and re-educate your leadership team on what the numbers mean now.
- Service operations leaders and RevOps professionals who track AI agent effectiveness as part of a broader automation ROI story. These cleaner metrics give you the data credibility you need for executive conversations.
- Mid-market and enterprise companies running the Customer Agent at volume. The higher your conversation count, the more a flawed formula distorts your read on agent effectiveness.
- Humans in support management roles who report on agent performance to a VP or C-suite. You'll want to brief your audience on the formula change before presenting the first updated report.
- Companies evaluating whether to expand their Customer Agent usage. Accurate deflection and handoff data makes the ROI case much easier to build.
George's Take
I've sat in enough portal reviews to know that bad metric definitions quietly erode trust in good tools. When the humans responsible for a support team look at a deflection rate that includes conversations the AI agent never even touched, they start doubting the agent before they've given it a fair shot. That's a real cost. HubSpot fixing the formula here isn't a flashy release, but it's exactly the kind of foundational work that makes AI adoption stick. Accurate data builds the case for expanding what the Customer Agent handles. Inaccurate data kills momentum before it starts.
“You can't coach what you can't measure accurately. These formula fixes don't just clean up a report. They give service leaders a honest starting point for growing what their AI agent can do.”
If you're running a Customer Agent and want to pressure-test your current configuration, or if you're thinking about turning one on for the first time, our team has done this across dozens of service portals. We know where the routing gaps hide and which knowledge base structures actually drive deflection. Read our full breakdown of the HubSpot agentic platform to get oriented, then book a strategy call with Sidekick Strategies and we'll walk through your specific setup together.
Frequently Asked Questions
What changed in HubSpot's Customer Agent performance reporting?
HubSpot redesigned the Performance section of Customer Agent analytics and updated how handoff rate and deflection rate are calculated. Handoff rate is now scoped to conversations where the Customer Agent was the assigned owner. Deflection rate now excludes conversations that started with a human owner, making both metrics more accurate and trustworthy.
How is the new HubSpot Customer Agent deflection rate calculated?
The updated deflection rate only counts conversations where the Customer Agent started as the owner. It measures the percentage of those conversations where the agent handled the issue without involving a human. Conversations routed directly to a human agent from the start are excluded from this calculation entirely.
How is the new HubSpot Customer Agent handoff rate calculated?
Handoff rate is now calculated as the number of conversations with a handoff divided by all conversations where the Customer Agent was the assigned owner. Previously, the denominator included conversations the agent was never assigned to, which skewed the metric. The new formula gives a clearer picture of how often the agent escalates its own conversations.
Will my historical Customer Agent performance numbers look different after this update?
Yes. Because the formulas for handoff rate and deflection rate have changed, your numbers will likely look different compared to pre-update data. HubSpot recommends treating the update date as a new baseline. Don't compare new numbers to old ones without first explaining the formula change to your team and leadership.
Which HubSpot plans include the updated Customer Agent performance reporting?
The updated reporting is available on Professional and Enterprise tiers across Content Hub, Smart CRM, Data Hub, Sales Hub, Marketing Hub, and Service Hub. It's also available to HubSpot Credits customers. Starter and Free tier plans are not included.
What should I do if my deflection rate drops after the Customer Agent reporting update?
A lower deflection rate after the update likely signals a real performance gap, not a bug. Review which conversation types result in handoffs and audit your knowledge base content and agent instructions for those topics. The new formula is more accurate, so a lower number is a diagnostic signal worth acting on rather than ignoring.
