What This Update Actually Is
HubSpot's Customer Agent now has a native action called Collect Ticket Properties. When a conversation reaches the handoff threshold, the agent doesn't just transfer the chat. It first asks the visitor targeted questions to gather the properties you've configured.
Those answers get written directly to the ticket as properties. Then HubSpot's native workflow engine reads those properties and routes the ticket to the right team. Billing goes to billing. Retention goes to retention. Fulfillment goes to fulfillment.
There's no limit on how many properties you can configure the agent to collect. You can set this up through Customer Agent > Human Handoff or through the action library, where you'll find the writeable property configuration and the option to enable the action directly.
Why HubSpot Shipped This
Here's the pattern we see constantly across support portals: a customer contacts support, the bot hands off to a human, and the human inherits a ticket with almost no useful context. No category. No priority. No reason for contact.
The internal frustration is real. Support reps re-ask questions the customer already answered. Tickets land in the wrong queue. Managers build fragile multi-step workarounds to compensate, usually involving extra workflows, form redirects, or manual triage. None of that scales.
HubSpot shipped this to close the gap between what AI agents can do and what human agents actually need when they pick up a ticket. Collection, writing, and routing now happen in one native flow, with no duct tape required.
How to Use It Step by Step
- Navigate to Customer Agent in your Service Hub settings, then open the Human Handoff section.
- Select Collect Ticket Properties. Alternatively, go to the action library and find the writeable property configuration option to enable it from there.
- Add the ticket or contact properties you want the agent to collect. Think about what your routing logic actually needs: category, issue type, cancellation reason, priority level, account tier. Add as many as your workflow requires.
- When a handoff is triggered, the Customer Agent asks the visitor clarifying questions to capture the configured properties. The questions are conversational, not form-like.
- The agent writes the collected values directly to the ticket as properties. No manual entry. No delay.
- HubSpot's native workflow engine reads those properties and routes the ticket to the correct team. Configure the routing logic inside your existing workflow setup. No separate system required.
One caveat worth naming: this update is marked as a current development plan and is subject to change. HubSpot's own release note flags that availability, tier access, and feature scope may shift. Set it up, test it in a sandbox if you have one, and confirm behavior before rolling it out to your live support queue.
What It Touches in Your HubSpot Strategy
This update sits at the intersection of Service Hub, your CRM data model, and your automation layer. Each one of those areas is affected in a meaningful way.
On the CRM and property side: the properties the agent collects and writes are live CRM data. That means they're available for segmentation, reporting, and any downstream automation you've already built. A ticket property written by the agent behaves exactly like one entered manually. Your existing views, custom reports, and pipeline logic will see it.
On the workflow side: routing is handled by HubSpot's native workflow solution. That means you're not learning a new tool. You're adding a data source (the agent-collected properties) to logic you've probably already built or can build using the same workflow editor you already know.
Key Takeaway
Properties collected by the Customer Agent are written as real CRM data. Every downstream workflow, report, or view that reads those properties will have access to them immediately after handoff.
On the support operations side: team routing accuracy is a direct output of this feature. If your support org has three or more queues, the math on mis-routed tickets adds up fast. Each ticket that lands in the wrong queue costs a re-assignment, a delay, and an extra touchpoint with a frustrated human on the other end.
This also pairs well with the broader push HubSpot is making toward AI that actually prepares context for humans rather than just deflecting. If you've been following how Breeze agents are evolving, the mobile notetaker and AI post-meeting experience now live in Service Hub is another good example of that pattern: AI doing the prep work so your humans can focus on the conversation.
Key Takeaway
If you've built any routing logic using ticket properties today, you can extend it immediately. The agent-collected values drop into the same property fields your workflows already reference.
On the property configuration side: this is a good moment to audit which ticket properties your routing logic actually depends on. If those properties aren't consistently filled, your routing is inconsistent. The agent can solve that, but only if your property design is intentional. Garbage in, garbage out still applies.
Who Should Care Most
This update is most valuable for specific roles and company profiles. Here's who should move fast on it.
- Support operations managers running multiple queues who currently rely on manual triage or multi-step workarounds to get tickets to the right team.
- RevOps leaders who own the CRM data model and want ticket property data to be complete and consistent without depending on human agents to fill it in.
- Service Hub Pro and Enterprise admins who've already deployed Customer Agent for deflection and now want to extend it into the handoff experience.
- Growing companies with 3 or more support teams (billing, retention, fulfillment, technical support) where mis-routing creates measurable delays and re-work.
- HubSpot practitioners on Sales Hub Pro/Enterprise and Marketing Hub Pro/Enterprise who also have Customer Agent enabled, since the feature is available across those hubs as well.
If your support volume is low and you run a single queue, this update won't move the needle much yet. But if you're building toward more specialized teams, it's worth getting your property structure right now so the routing logic is ready when you need it.
George's Take
What I love about this update is that it's honest about where AI should sit in a support workflow. It's not replacing the humans doing the work. It's doing the prep so those humans can actually do their best work when they show up. We've audited enough portals to know that incomplete ticket data is one of the most consistent sources of friction in support operations. The fact that an AI agent can now handle collection and writing natively, without a separate form or a bolt-on workflow, is a real quality-of-life improvement for every support team running more than one queue. The key is making sure your property design is intentional before you turn this on. The agent can collect whatever you configure, so take the time to get that configuration right.
“AI should do the prep work so your humans can show up to the conversation ready to actually help. That's what this feature does.”
If you're curious how other AI-driven features are changing the way HubSpot handles context and data, it's worth reading what HubSpot's Breeze Assistant can really do for a fuller picture of where the platform is headed.
Ready to get your support workflows and property structure set up correctly before you flip this on? That's exactly the kind of work we do with growing teams at Sidekick Strategies. Book a strategy call and we'll map out what needs to be in place for this feature to actually flourish in your portal.
Frequently Asked Questions
What is the HubSpot Customer Agent Collect Ticket Properties feature?
It's a native action inside HubSpot's Customer Agent that lets the AI ask clarifying questions during a support conversation, collect ticket and contact properties, write those values directly to the ticket, and route the handoff to the correct team using HubSpot's workflow engine. No separate tools or manual data entry required.
Which HubSpot hubs and tiers include the Customer Agent property collection feature?
The feature is available on Service Hub Professional and Enterprise, Sales Hub Professional and Enterprise, Marketing Hub Professional and Enterprise, and HubSpot Smart CRM Professional and Enterprise. It's not available on Starter or Free tiers.
How do I set up Customer Agent to collect ticket properties before handoff?
Go to Customer Agent in your HubSpot settings, open the Human Handoff section, and select Collect Ticket Properties. You can also configure this through the action library. Add the properties you want collected, then configure your routing logic in HubSpot's native workflow editor.
Can HubSpot's Customer Agent collect contact properties as well as ticket properties?
Yes. The feature supports both ticket and contact properties. You can configure the agent to collect whichever combination your routing and reporting logic requires. There's no documented limit on the number of properties you can add to the collection configuration.
How does Customer Agent route tickets to the right team after collecting properties?
Routing is handled by HubSpot's native workflow solution. Once the agent writes the collected property values to the ticket, your existing workflow logic reads those values and routes the ticket to the appropriate team, such as billing, retention, or fulfillment. No separate routing system is needed.
Will the properties collected by Customer Agent appear in HubSpot reports and workflows?
Yes. Properties written by the Customer Agent are standard CRM data. They appear in your ticket records, are available for segmentation and reporting, and trigger any workflow enrollment criteria that reference those properties, exactly the same as manually entered properties.
