Human handoff routing by channel type in Customer Agent

Thursday, October 1, 2026

Service HubHubSpot AIProfessionalEnterprisePublic beta

What it is

Customer agent human handoffs now support routing by channel type, with separate configuration and handling for messaging and email conversations. Public beta for Customer Agent, which is available on Professional and Enterprise tiers of every hub and through HubSpot Credits.

Why it matters

Before this, handoff routing was configured the same way for every channel, which did not fit the different needs of live messaging and asynchronous email support. Routing by channel type makes handoffs more predictable and sends email conversations to the right team on the first try.

The Take

Chris Carolan

The first word on the screen was human, which is where we had to start, and it is the only way to talk about human agents and AI agents in any kind of clear way; you cannot say rep handoff anymore. The update is not about setting up the agent's chat or email experience, which is what most customer agent conversations are about. It is about what happens when a conversation needs to go to a person, and letting chat and email behave differently when it does.

Or, as I like to say, synchronous conversation versus asynchronous conversation. Put the humans in when there is a synchronous conversation wanted on the other side. So often we try to force synchronous conversations through email, which is not what it is built for, and we have chat, so the optionality here makes a ton of sense. Most folks have to think through those two motions more carefully before they can ask AI to know which way to go, and if you are excited about getting customer agent involved, that thinking is the work. It might also leave you with your communication processes documented better than they were.

Watch Us Discuss This

The full segment from the show, us working through this update start to finish.

Human handoff by channel: synchronous versus asynchronous3:38

Produced by Value-First Media