What This Update Actually Is
HubSpot is sunsetting the fallback routing rule inside the "Send to Customer Agent" module in Rule Based Bots (RBB). That specific setting is called a fallbackRoutingRule on the module. After April 27, 2026, HubSpot will remove all remaining fallback rules from affected modules automatically.
Once that happens, every Customer Agent handoff in those bots will follow your portal's global human handoff rules instead. The fallback routing logic will no longer live at the module level.
Two things to know up front. First, you don't need to rebuild your entire bot. Only the one module needs updating. Second, if you don't have this module, or if your module never had a fallback rule configured, this change doesn't touch you at all.
Why HubSpot Shipped This
Here's the honest answer: HubSpot built the Customer Agent AI layer to operate with centralized, global handoff settings. Allowing per-module fallback rules created a split-brain problem. Two places controlled how conversations escalated to a human, and they could contradict each other.
The internal frustration we've seen across portals is real. Admins set up global handoff rules, then couldn't figure out why some escalations behaved differently inside certain bots. The answer was always the hidden fallback rule at the module level. Humans on your support team got routed inconsistently, and no one could easily audit it.
Centralizing handoff logic into one place makes escalation predictable. It also sets the foundation for HubSpot's broader Breeze AI agent architecture, where Customer Agent needs a single source of truth for routing decisions. This isn't just housekeeping; it's a structural requirement for where AI-powered service is heading.
How to Use It Step by Step
If your portal has been showing the in-app deprecation warning banner, follow these steps before April 27, 2026.
- Navigate to your chatflow in the Rule Based Bot builder. Go to Service, then Chatflows, and open the affected chatflow.
- Find the "Send to Customer Agent" module with the deprecation warning banner. It will be visible inline inside the bot flow.
- Click "Update this module" in the warning banner. This calls the module update endpoint automatically and removes the fallback rule. You don't need to touch any other part of the bot.
- Alternatively, delete and manually recreate just that module if you prefer a clean slate over the automatic update.
- Confirm your global human handoff settings are configured correctly. Go to your inbox or chatflow settings and verify that your handoff rules reflect how you actually want conversations routed to human agents.
That last step is the one most portals skip. The "Update this module" button removes the fallback rule, but it doesn't configure your global settings for you. If your global handoff rules are incomplete or stale, this is the moment to fix them.
What It Touches in Your HubSpot Strategy
This change is narrower than it sounds, but the ripple effects are worth mapping out. Here's where it connects to the rest of your portal.
Service Hub Chatflows and Inboxes. Your inbox routing rules are the new authority for all Customer Agent handoffs. If you've got multiple inboxes with different teams, make sure each inbox's handoff settings reflect the right team or individual. An unreviewed global rule could send escalations to the wrong queue.
Breeze Customer Agent Configuration. If you've been exploring or have already deployed HubSpot's AI-powered Customer Agent (the Breeze layer), this change aligns your bot escalation path with the same global logic your AI agent uses. That consistency matters as you scale automation. We've written about the experience of moving AI agents into this environment, and the routing architecture is one of the first things that needs to be solid.
Key Takeaway
Your global handoff settings now control ALL Customer Agent escalations from Rule Based Bots. Review and tighten those settings now, not after April 27.
Workflow Automations Tied to Chatflow Events. If you built workflows that trigger when a conversation is assigned from a bot, test those workflows after updating the module. The trigger event should still fire, but the routing destination changes. A quick test conversation before April 27 is time well spent.
Reporting and Conversation Analytics. Any reports you've built around human handoff rates from bots may shift slightly as routing consolidates. Baseline your current handoff volume before the change, so you have a clean comparison point afterward. If you're newer to Customer Agent as a concept, the deeper context in why Customer Agent deserves a serious strategic look is worth reading before you finalize your handoff settings.
Key Takeaway
Humans on your service team will be routed based on global inbox rules only. If those rules haven't been audited recently, this update is your forcing function to clean them up.
Who Should Care Most
You're directly affected if all three of these are true for your portal:
- You have an active Rule Based Bot in your chatflows
- That bot includes a "Send to Customer Agent" module
- That module has a fallback routing rule configured (you've likely already seen the in-app warning banner for months)
By role, this lands hardest on Service Hub admins and RevOps humans who own chatflow architecture. If you manage multiple portals, check each one independently. The deprecation warning banner is the fastest indicator of which portals need action.
Company profile: any business running Service Hub Professional or Enterprise with a live bot-to-human escalation path. This is common in B2B SaaS, professional services, and e-commerce companies that built early chatflows and haven't touched them since.
If you're not sure whether your portal is affected, log into HubSpot and check your chatflows for any active warning banners before reading further. It takes about 90 seconds.
George's Take
I've been inside enough HubSpot portals to know that chatflow settings are one of the most "set it and forget it" corners of the platform. Teams build a bot, it works well enough, and nobody touches it for two years. That's exactly the scenario this update is designed to shake loose. The good news is that HubSpot made the fix as easy as clicking one button. The real risk isn't the technical change; it's discovering that your global handoff settings were never properly configured in the first place. Use this deadline as a reason to open that section of your portal and actually review it.
“The button removes the fallback rule. But it doesn't fix handoff settings that were incomplete before the rule existed. That part is on us to own.”
Get Your Chatflows and Handoff Settings Audit-Ready
Deprecation deadlines like this one almost always reveal a wider gap. You fix the module, then realize your global routing rules haven't been touched since onboarding. If that sounds familiar, it's one of the patterns we cover in detail when talking about the most expensive HubSpot onboarding mistakes. And if you're building out a more robust AI-powered service layer, the expanding world of Breeze Agents connecting to external tools shows exactly where HubSpot's service architecture is heading next.
If you want a second set of eyes on your chatflows, handoff rules, or broader Service Hub setup before April 27, book a strategy call with the Sidekick team. We'll help you close the gap before the deadline removes the option for you.
Frequently Asked Questions
What is the HubSpot Customer Agent fallback routing sunset?
HubSpot is removing the fallback routing rule (fallbackRoutingRule) from the "Send to Customer Agent" module in Rule Based Bots on April 27, 2026. After that date, all Customer Agent handoffs from bots will follow your portal's global human handoff settings instead of any per-module fallback rule.
How do I know if my HubSpot portal is affected?
Your portal is affected if you have an active Rule Based Bot with a "Send to Customer Agent" module that has a fallback routing rule configured. HubSpot has been showing an in-app deprecation warning banner inside the affected chatflows for several months. If you see that banner, you need to act before April 27, 2026.
Do I need to rebuild my entire Rule Based Bot before April 27?
No. Only the "Send to Customer Agent" module needs to be updated. HubSpot provides an "Update this module" button directly inside the deprecation warning banner. Clicking it automatically removes the fallback rule. The rest of your bot remains intact and does not need to be recreated.
What happens if I don't update the module before April 27, 2026?
HubSpot will automatically remove all remaining fallback routing rules from affected modules after April 27. Your bot will still function, but all Customer Agent handoffs will route according to your global human handoff settings. If those global settings aren't configured correctly, your escalations may route incorrectly.
What are global human handoff settings in HubSpot?
Global human handoff settings control how HubSpot routes a conversation to a live agent when a bot or AI agent can't resolve it. You configure these at the inbox or chatflow settings level in Service Hub. After April 27, these settings become the single source of truth for all Customer Agent escalations from Rule Based Bots.
Which HubSpot plans are affected by this change?
The change affects portals on Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM, all at Professional and Enterprise tiers. HubSpot Credits portals are also included. If you're on Starter or Free, this update doesn't apply to your account.
