What This Update Actually Is
HubSpot is sunsetting legacy channel-level handoff routing inside Customer Agent. The old system let portals define different routing rules for each inbox channel separately. The new system, Global Handoff, works at the agent level instead.
On April 27, 2026, HubSpot will auto-migrate any portal still using the legacy setup to Global Handoff. The migration is automatic. The configuration is not.
Two groups are affected. First: portals using the Rule Based Bot with a "Send to Customer Agent" module that still has a fallbackRoutingRule configured. Second: portals using multiple inbox channels where each channel had its own routing rule. Per-channel rules do not carry over to Global Handoff automatically.
If your portal uses a single channel, or doesn't use the "Send to Customer Agent" module at all, this change doesn't touch you.
Why HubSpot Shipped This
Channel-level routing was built before Customer Agent existed as a unified AI layer. It solved a real problem at the time: different channels needed different teams. But it created fragmented configuration that was hard to maintain and impossible to reason about at scale.
Global Handoff centralizes that logic. Instead of configuring routing on each channel, you configure it once at the agent level and then use conversation-based routing workflows to handle the nuance. It's a cleaner architecture that gives more control, not less.
The humans managing service operations in HubSpot deserve a routing setup they can actually understand when something breaks at 2pm on a Tuesday. Global Handoff is that setup. The legacy system was not.
How to Use It Step by Step
Your path depends on which group you're in. Start by identifying which one applies to your portal.
If you're a Rule Based Bot (RBB) user:
- Open the affected chatflow inside your Rule Based Bot settings.
- Look for the deprecation warning banner on the "Send to Customer Agent" module. Click "Update this module." This automatically removes the fallback routing rule. You don't need to rebuild the whole bot.
- If you prefer doing it manually, delete and recreate only that module inside the chatflow.
- Confirm your Global Handoff settings are configured correctly before saving.
If you're an inbox user with multiple channels:
- Navigate to Customer Agent handoff settings in your portal.
- Map out every per-channel routing rule you currently have. Write them down. You'll rebuild them as conversation-based routing workflows.
- Use the new conversation-based routing option inside Global Handoff to create workflow-based rules per inbox channel. Match your existing logic.
- Test routing behavior on each channel before April 27. Don't assume it's right. Verify it.
What It Touches in Your HubSpot Strategy
This change lives in Service Hub, but its ripple effects reach further than most service updates do.
Conversation routing directly affects ticket creation, team assignment, and SLA tracking. If conversations land in the wrong inbox after April 27, tickets get created with the wrong owner, SLAs start on the wrong clock, and reporting gets noisy fast.
If you've been tracking the broader Customer Agent changes, this update connects directly to the Customer Agent fallback routing sunset in Rule Based Bots that HubSpot has been warning about for months. These are two sides of the same architectural shift.
Key Takeaway
Per-channel routing rules do not migrate automatically. If your portal routes live chat differently than email or Facebook Messenger, you must manually recreate that logic inside Global Handoff using conversation-based routing workflows before April 27.
On the automation side, any workflows that rely on conversation or ticket properties set during the handoff step need a review. If those properties depend on which channel triggered the handoff, your workflow enrollment logic may behave differently after migration.
Reporting is also at risk. Conversation volume by channel, first response time, and team assignment accuracy are all downstream of routing. Bad routing means bad data in your service dashboards.
Key Takeaway
Don't treat this as a bot update. Treat it as a service operations audit. Review your routing logic, your ticket workflows, and your service reporting filters before the migration date.
If you're newer to Customer Agent as a tool, it's worth reading about what makes HubSpot Customer Agent worth building in properly before you invest time in restructuring your handoff configuration.
Who Should Care Most
This update is urgent for a specific set of portals. Here's who needs to act now.
- Service Hub administrators managing multiple inbox channels with different routing rules per channel. This is the highest-risk group.
- Marketing or ops professionals who built Rule Based Bot chatflows that hand off to Customer Agent. If you see a deprecation warning banner in your chatflow, you're in this group.
- RevOps leaders at companies using Service Hub Professional or Enterprise with structured support tiers or regional team assignments that depend on channel-level routing to stay accurate.
- Business owners and operators who built their initial HubSpot setup years ago and haven't audited their chatflow configuration recently. Legacy setups are the most likely to break quietly.
Portals with a single inbox channel and no Rule Based Bot handoff don't need to do anything. But if there's any doubt, log in and check.
George's Take
I've been inside hundreds of HubSpot portals over the years, and the ones that get hurt by updates like this are almost never the ones with the most complex setups. They're the ones where nobody checked the deprecation banner for six months. HubSpot gave plenty of warning here. The in-app banner has been live for months. But warnings only help the humans who are actively looking at their portals. If your service ops setup was built and then mostly left alone, April 27 is your wake-up call. Global Handoff is genuinely better than the legacy system. It's just not going to configure itself.
“Warnings only help the humans who are actively looking at their portals. If your service ops setup was built and mostly left alone, April 27 is your wake-up call.”
This pattern shows up again and again: portals get configured at launch and then drift. It's one of the most expensive HubSpot mistakes we see across onboarding audits. A proactive portal review before a forced migration like this one is always cheaper than cleaning up broken routing after the fact.
If you're not sure whether your portal is affected, or you want a second set of eyes on your Customer Agent configuration before April 27, the Sidekick team is ready to help. Book a strategy call and we'll walk through your handoff setup together before the migration window closes.
Frequently Asked Questions
What is HubSpot's Global Handoff and how is it different from legacy channel routing?
Global Handoff is HubSpot's current agent-level handoff configuration for Customer Agent. Unlike the legacy system, which let you set different routing rules per inbox channel, Global Handoff applies one configuration across all channels. You can still replicate per-channel logic using conversation-based routing workflows inside Global Handoff.
Will HubSpot automatically fix my routing when it migrates me to Global Handoff?
Partially. HubSpot will auto-migrate your portal to Global Handoff on April 27, 2026, but per-channel routing rules do not carry over. If your portal routes conversations differently per channel, you must manually recreate that logic using conversation-based routing workflows before the migration date or conversations may route incorrectly.
How do I know if my portal is affected by this Customer Agent routing change?
Check two things. First, look for a deprecation warning banner on the "Send to Customer Agent" module inside any Rule Based Bot chatflow. Second, review your inbox settings to see if you have multiple channels with different routing rules configured. If either applies, you need to act before April 27, 2026.
Do I need to rebuild my entire Rule Based Bot chatflow?
No. For Rule Based Bot users, only the "Send to Customer Agent" module needs to be updated. Click the "Update this module" button inside the deprecation warning banner, or manually delete and recreate just that module. The rest of your chatflow stays intact.
What happens if I don't update before April 27, 2026?
HubSpot will auto-migrate your portal to Global Handoff. For portals with complex per-channel routing, this means conversations may route to the wrong team or inbox. Ticket assignments, SLA tracking, and service reporting can all be affected. Proactive configuration before the deadline is the only way to avoid disruption.
Which HubSpot plans are affected by the legacy channel routing sunset?
This change affects portals on HubSpot Credits, Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM at the Professional and Enterprise tiers. The key factor isn't the plan, it's whether your portal uses the "Send to Customer Agent" module in a Rule Based Bot or has multiple inbox channels with different routing rules.
