What This Update Actually Is
HubSpot added a fallback option inside each channel's routing settings in Chatflows. When all human agents are unavailable or at capacity, the routing engine can now automatically assign the incoming conversation to Customer Agent instead of leaving it unassigned.
Before this update, that gap had one outcome: the conversation sat in a queue. Now there's a configured safety net. Customer Agent steps in, begins the conversation, and starts triaging the contact's needs until a human is ready.
The setting lives below the existing user and team assignment selector inside each channel's routing configuration. It's opt-in, backwards compatible, and requires zero changes to your existing routing types or logic. If you don't configure it, nothing changes from how your portal works today.
Why HubSpot Shipped This
The external problem is obvious: conversations that sit unassigned break SLAs and frustrate the humans waiting on the other end of the chat. The internal frustration for most admins is harder to name but just as real.
Deploying Customer Agent at all felt like a risk. If it fired at the wrong time or replaced humans who were actually available, you'd erode trust. There was no clean boundary between "AI handles this" and "human handles this." Admins wanted a safer on-ramp.
This update answers that directly. Customer Agent doesn't compete with your team. It activates only when your team can't respond. That's a meaningful shift in how you can position AI assistance inside your support operation without worrying about it overstepping.
How to Use It Step by Step
- Opt into the public beta inside your HubSpot portal if you haven't already. As of August 26, 2026, the gate is unlocked and you can join immediately.
- Navigate to Conversations, then Chatflows in your left nav. Open the Chatflow tied to the channel where you want the fallback active.
- Go to the routing settings for that channel. Look for the new Customer Agent fallback option below your existing user and team assignment selector.
- Select your configured Customer Agent as the fallback. Save the routing rule.
- Test it by simulating an off-hours or capacity scenario. Confirm that the conversation routes to Customer Agent and that handoff behavior matches your team's expectations.
- Repeat the configuration for each channel where you want the fallback active. The setting is channel-specific, not global.
One important note: if you don't configure a fallback, conversations continue to behave exactly as they did before. Unassigned or waitlisted, depending on your current setup. This change is fully additive.
What It Touches in Your HubSpot Strategy
This update lives at the intersection of Service Hub and Breeze AI, but its ripple effects move through your whole support operation.
On the routing side, every Chatflow you've built now has a new decision branch available. If you've been careful about mapping out when and how conversations get assigned, this is a new node to document in your routing logic. Don't skip that documentation step.
Key Takeaway
Customer Agent as a fallback works best when you've already configured its guidelines and trained it on your knowledge base. A well-prepped Customer Agent triages. A poorly prepped one frustrates. Set it up right before you set it as a fallback.
On the reporting side, you'll want to track how often the fallback fires. High frequency means your human coverage has a gap worth addressing. Low frequency means it's working as a safety net. Either way, that data is useful.
If you haven't set up Customer Agent yet, HubSpot's Customer Agent Auto-Setup feature can build and configure it from your existing portal data in minutes. And once it's live, the redesigned Customer Agent guidelines interface gives you card-based targeting and templates to control exactly how it responds, which matters a lot when it's your first line of defense.
On the workflow side, think about what happens after Customer Agent handles the initial triage. Does a ticket get created automatically? Does a human get notified when they're back online? Those downstream automations should be in place before you turn on the fallback.
Key Takeaway
Configure your post-triage workflows before enabling the fallback. Customer Agent starting a conversation is step one. What happens when your team logs back in is step two. Both steps need a clear owner.
If your Help Desk operation is getting a broader overhaul, this update pairs well with recent Help Desk improvements like the ability to bulk unmark spam conversations. Cleaner queues and smarter routing work together.
Who Should Care Most
This update is most immediately valuable for specific roles and company profiles. Here's who should move on it first:
- Service operations admins who manage Chatflows and routing rules and are responsible for SLA performance across live chat and messaging channels.
- Small and mid-sized support teams where overnight or weekend coverage is limited and conversations regularly pile up unassigned during off-hours.
- RevOps leaders who've been cautious about deploying Customer Agent broadly and want a lower-risk entry point that doesn't touch primary routing logic.
- Businesses in time-zone-heavy markets where a significant share of inbound conversations arrive outside business hours and response time is a competitive differentiator.
- HubSpot admins managing high-volume chat who've already seen Customer Agent in action and are ready to extend its role without replacing human judgment during peak hours.
If your team is small, globally distributed, or supporting customers across multiple time zones, this is one of the most practical AI updates HubSpot has shipped for your specific situation.
George's Take
We've seen this pattern play out across a lot of portals: admins want to use AI in their support operation but they don't want to hand over the wheel entirely. Customer Agent as a fallback is exactly the kind of guardrailed deployment that makes it safe to say yes. The AI doesn't jump in front of your humans. It catches what your humans can't catch. That's not a threat to your team. That's your team getting a backup that never sleeps. The key is doing the prep work first: solid guidelines, a trained knowledge base, and clear downstream automations. When those pieces are in place, flipping on this fallback is one of the lowest-risk, highest-value moves a service team can make in their HubSpot portal right now.
“Customer Agent as a fallback isn't AI replacing your team. It's AI showing up when your team physically can't, and that's a very different conversation.”
If you want help configuring this fallback correctly, auditing your existing Chatflow routing logic, or building the downstream automations that make Customer Agent handoffs clean, let's talk. Book a strategy call with the Sidekick team and we'll walk through your portal together.
Frequently Asked Questions
What is the HubSpot Conversation Routing Fallback to Customer Agent?
It's a new setting inside HubSpot Chatflows that lets admins designate Customer Agent as an automatic fallback when no human agents are available or at capacity. Instead of leaving conversations unassigned, the routing engine sends them to Customer Agent to begin triage. It's available in public beta now and rolling out fully on September 29, 2026.
Does the Customer Agent fallback replace my human agents?
No. The fallback only activates when all human agents are unavailable or at capacity. When humans are available, the routing engine assigns conversations to them first as usual. Customer Agent steps in only when your team can't respond, making it a safety net rather than a replacement for your human support operation.
How do I configure the Customer Agent fallback in HubSpot?
Go to Conversations, then Chatflows, and open the Chatflow for the channel you want to configure. Inside the routing settings, you'll find a new Customer Agent fallback option below the existing user and team assignment selector. Select your Customer Agent, save the rule, and test it. The setting is channel-specific, so configure it for each channel separately.
Which HubSpot hubs and tiers include the Customer Agent routing fallback?
HubSpot has made this update available across all hubs and all tiers, including Free and Starter. You don't need a Service Hub Professional or Enterprise subscription to access it. You do need to have Customer Agent configured in your portal before you can set it as a fallback in your routing rules.
Will enabling this fallback break my existing routing rules?
No. The Customer Agent fallback is fully backwards compatible. HubSpot implemented it as an optional field on the existing routing rule definition. If you don't configure it, your routing behaves exactly as it did before. Existing rules, waitlists, and assignment logic are all unaffected unless you actively add the fallback setting.
What should I do before enabling the Customer Agent fallback?
Make sure Customer Agent is already set up with clear guidelines and a trained knowledge base. Then build or review the downstream automations that handle conversations after Customer Agent's initial triage, such as ticket creation and team notifications. A well-prepped Customer Agent creates better handoffs. A poorly configured one creates more work for your humans when they log back in.
