What This Update Actually Is
HubSpot shipped four new automatic values for the Customer Agent Status property on tickets. These statuses are read-only and set entirely by the system. You can't manually edit them, which is exactly the point.
Here's what each value means in plain terms:
- Pending: Customer Agent owns the ticket and is actively handling it. No human rep is needed yet.
- Awaiting Human Assignment: Customer Agent triggered a handoff, but no human rep has been assigned yet. This is the danger zone.
- Handed Off: A human rep is now assigned and owns the ticket. The AI's job is done.
- None: Customer Agent was never involved with this ticket at all.
The property updates automatically as ticket ownership and handoff events occur. No workflow. No manual update. Just accurate, real-time signal.
Why HubSpot Shipped This
If you've been running Customer Agent in your help desk, you've probably felt this pain already. The AI handles a conversation, decides a human needs to step in, and then nothing. There's no obvious flag on the ticket. A rep might not notice. A manager has no queue view that separates AI-stalled tickets from everything else.
That gap between AI handoff and human pickup is where SLAs break and customers get frustrated. Humans waiting on hold don't care whether it was a bot or a person who dropped the ball.
The internal frustration runs deeper, too. Support managers told HubSpot they couldn't build meaningful reports on AI performance because they had no clean way to filter for which tickets Customer Agent actually touched. This property solves both problems at once.
How to Use It Step by Step
The status is automatic, but you still need to do the work of surfacing it where your team will actually see it. Here's how to make it useful from day one.
- Confirm Customer Agent is active in your portal. Go to Service > Help Desk > Settings and verify Customer Agent is enabled. If it isn't, this property will show None on all tickets.
- Add the property to your ticket views. In Help Desk, edit your saved views to include Customer Agent Status as a column. Filter for 'Awaiting Human Assignment' to create a dedicated queue for tickets stuck in the gap.
- Build a workflow to flag stuck handoffs. Create a ticket-based workflow triggered when Customer Agent Status equals 'Awaiting Human Assignment' for more than a set number of minutes. Send a Slack message or internal email to your support lead so no handoff goes cold.
- Add it to ticket record sidebars. Edit the ticket properties panel to include Customer Agent Status so reps see the AI's involvement the moment they open a ticket.
- Report on CA performance with real data. Create a custom report using Customer Agent Status as a breakdown dimension alongside first response time and CSAT. You'll finally be able to measure how AI handling affects ticket outcomes.
What It Touches in Your HubSpot Strategy
This isn't just a help desk quality-of-life fix. It's a foundational data layer for anyone running AI-assisted support at scale.
On the reporting side, Customer Agent Status becomes a segmentation property for every ticket-based report you run. You can now split your SLA compliance, resolution time, and CSAT scores by whether CA was involved. That's a completely new lens on support performance.
Key Takeaway
The 'Awaiting Human Assignment' status is your most important new signal. Any ticket stuck in this state is a live SLA risk. Build a workflow or view around it before anything else.
On the automation side, this property unlocks workflow triggers that weren't possible before. You can now route, escalate, or notify based on exactly where the AI-to-human handoff stands. Pair this with HubSpot's conversation routing fallback to Customer Agent and you have a complete picture of how tickets enter and exit AI handling.
On the CRM data side, this is a native ticket property, which means it works everywhere properties work: list filters, custom reports, workflow enrollment criteria, and the API. If you're building integrations that pull ticket data, this status travels with the record.
There's also a broader strategic ripple worth naming. If you're thinking about the full arc of your AI investment in HubSpot, our deep dive on the HubSpot agentic platform explains how properties like this one are part of HubSpot's larger play to make AI activity measurable and accountable inside the CRM.
Key Takeaway
Customer Agent Status works alongside CX Score to give managers a full picture of AI-assisted tickets. Use both properties together in reports to see not just what happened, but how well it went.
Speaking of CX Score: if you haven't set that up yet, the CX Score update breakdown pairs directly with this one. Together, these two properties give you AI involvement and outcome quality on every ticket.
Who Should Care Most
Not every portal on Service Hub will feel this update the same way. Here's who should act on it immediately.
- Support managers running Customer Agent at volume. If CA handles more than 20% of your incoming tickets, you have handoff gaps happening right now that you can't see. This property makes them visible immediately.
- RevOps and HubSpot admins. You'll want to build the workflow escalation and the reporting structure before the support team even knows this property exists. Be proactive here.
- Growing companies with lean support teams. When every rep is stretched, the last thing you need is ambiguity about who owns a ticket. This property removes that ambiguity at the system level.
- Humans in customer-facing roles who rely on context. A rep picking up a handed-off ticket needs to know the AI already tried to resolve it. This property tells that story instantly, without reading the whole conversation thread.
If your portal is on Service Hub Starter or Free, this update doesn't apply yet. You'll need Service Hub Professional or Enterprise with a Service Seat assigned.
George's Take
I've been in more portals than I can count where teams were running Customer Agent but flying completely blind on the handoff. The AI would do its job, flag a ticket for a human, and then that ticket would just sit there because nobody had a view that surfaced it. The frustration wasn't with the AI. It was with the invisible gap between what the AI did and what the human needed to do next. This property fills that gap with a signal that's automatic, clean, and reportable. It's the kind of foundational data layer that should have shipped the moment Customer Agent went GA. The good news is it's here now, and the teams who wire it into their workflows and dashboards this week are going to see faster handoffs, fewer stalled tickets, and a real ability to measure whether their AI investment is actually paying off.
“The AI did its job. The property proves it. Now your workflows just need to catch up.”
If you want help wiring Customer Agent Status into your support workflows, building the right reports, or auditing how AI is performing across your help desk, the Sidekick team is ready. Book a strategy call at sidekickstrategies.com and let's make sure your AI-to-human handoffs are running the way they should be.
Frequently Asked Questions
What is the HubSpot Customer Agent Status property?
It's a read-only ticket property that automatically tracks where a ticket stands in the Customer Agent to human handoff process. It sets one of four values: Pending, Awaiting Human Assignment, Handed Off, or None. It updates automatically based on ticket ownership and handoff events, with no manual editing required.
Can I manually change the Customer Agent Status on a ticket?
No. The Customer Agent Status property is set and updated entirely by HubSpot based on ticket ownership and handoff events. It's read-only by design so the data stays accurate. You can filter, report on, and trigger workflows from it, but you can't edit the value directly.
What does 'Awaiting Human Assignment' mean on a HubSpot ticket?
It means Customer Agent triggered a handoff to a human rep, but no rep has been assigned to the ticket yet. This is the status most likely to cause SLA gaps. Teams should create a workflow or saved view that surfaces these tickets immediately so they don't go cold after the AI handoff.
Which HubSpot plans include the Customer Agent Status property?
Customer Agent Status is available on Service Hub Professional and Service Hub Enterprise. A Service Seat is also required. It's not available on Service Hub Starter or Free plans.
How do I build a report using Customer Agent Status in HubSpot?
Go to Reports and create a custom ticket report. Add Customer Agent Status as a breakdown or filter dimension. You can combine it with first response time, resolution time, or CSAT to measure how AI involvement affects support outcomes. This is especially useful for comparing Pending versus Handed Off ticket performance.
How does Customer Agent Status work with HubSpot workflows?
Customer Agent Status can be used as an enrollment trigger or condition in ticket-based workflows. A common use case is triggering a Slack alert or task creation when a ticket enters the Awaiting Human Assignment status for more than a set number of minutes, so support leads catch stalled handoffs before they breach SLA.
