Show recap — Thursday, October 1, 2026

Another Orange Morning Recap: October 1, 2026

October opened with all three seats filled. Chris Carolan hosted, Trisha Merriam held the Thursday Friend seat, and Casey Hawkins was back at the desk, sharing links before the music had even finished. There were more updates on the board than the day before, and the first one on the screen started with the word human, which is where the show had to start.

Here is what we got into: human handoff routing by channel type in customer agent and the synchronous-versus-asynchronous question, admin navigation customization and where the work actually gets done, Trisha's pick of the new data model overview tab and the pop-up that opened with it, the customer agent weekly coaching digest and who is responsible for one more notification, and Casey's pick of manual sort within board lanes, which turned into the day's Will It Breeze.

Before the Updates: Unboxed Is Done, Office Hours Begin

Wednesday's UNBOUND Unboxed, with George B. Thomas, Joshua Oakes, Ryan Ginsberg and the rest of the Hubsessed crowd, had a little talk of features and mostly talk about how to be human right now, and the recording is on the Unboxed registration page. Hubsessed Office Hours start officially today, with the Unified Revenue View session led by Chris and Ryan on their favorite topic, Revenue Hub. Reporting and dashboards follow on Wednesday with Joshua and Madelyn Donovan, more experts are joining, and Chris is hoping his own name appears on that schedule a lot less soon, unless the one he lands on is Loop Marketing and AEO, which he insists could happen.

The First Word Was Human

Human Handoff Routing by Channel Type in Customer Agent

Human handoff routing by channel type is in public beta for customer agent. Handoffs to a person can now be configured and handled separately for messaging and for email conversations, where before one routing setup had to serve both. The room wondered aloud how much of that word choice came from George B. Thomas and Chris, and decided the answer was yes, because it is the only way to talk about human agents and AI agents clearly. You cannot say rep handoff anymore.

Most customer agent conversations are about setting up the agent's chat or email experience. This one is about what happens when the conversation needs a person, and letting chat and email behave differently when it does, since chat is instantaneous and email can carry a longer delay.

Why it matters: synchronous conversation versus asynchronous conversation, as Chris likes to put it. Put the humans in when a synchronous conversation is wanted on the other side. Teams try to force synchronous conversations through email all the time, which is not what email is built for, and chat already exists, so the optionality makes sense. Most folks still have to think those two motions through before they can ask AI to pick between them, and if you are excited about customer agent, that thinking is the setup. It may also leave your communication processes better documented than they were.

Admin Navigation, Finally Customizable

Admin Navigation Customization

A major update, in private beta for Professional and Enterprise. Admin navigation customization lets admins build custom navigation menus and assign them to users and teams, so a user sees only the tools that matter to them, with the full menu behind More. Trisha had been flicking through every portal she supports at Casey's DMV HUG earlier in the week, and every left nav was the same overwhelming list, until she reached one client whose admin had put real thought into the layout, and it felt really nice.

Bookmarks have been the workaround Casey points people to. Chris went further and wiped his menu entirely, forcing himself to add tools back only when he actually needed to click them, which he offered to show on screen later in the day.

Why it matters: the question underneath this is where the work is being done. Admins doing most of their work outside HubSpot, and users leaning on search more than navigation, change what a menu is for. There are also new icons to learn, and how people navigate by pictures is a dynamic most teams are not paying attention to. Nobody wants that nav expanded across their screen all day; it is too much real estate. Also, a shout-out to Frank the dog for the applause as soon as the update was read, even if he had demanded a trip outside minutes earlier.

Trisha's Pick: The Data Model Overview Tab

New Data Model Overview Tab

Trisha chose the data model overview tab, now in public beta, and her first question was whether the show had seen it before. It had, on September 8, when it was private. The tab is a single place to review data health issues, see personalized suggestions, and do the common data model actions, creating properties, custom objects and pipelines, for people who find the full data modeling interface overwhelming. Casey pulled it up in the Value-First Team portal. It looks nice, and the recommendations are the part worth watching.

Chris's hesitation was about process. Most admins touch the data model in the flow of doing something else, so a dedicated workspace only pays off if you set aside time for documenting and understanding data, asking whether the property you created last month is being used, and the muscles for that are not well conditioned across most HubSpot teams. Trisha noted how much this area has moved: it used to drop you straight into the map, then into the manage table, which she can see confusing people. Chris hopes it is done being a moving target; it did have to move out of settings.

Why it matters: opening the tab popped Breeze Assistant open, unannounced, and both Casey and Chris closed it on instinct, the way you close any pop-up, before reading that the empty screen wanted them to use Breeze. Assume positive intent: HubSpot is testing every way to get Breeze into every user's life, and everywhere else that would have been an entry box in the white space. Trisha's take was that this may be the chatbot arc all over again. She did not use chatbots when they first appeared, and now they are often the first place she goes on a website, so maybe she will stop clicking out of this too. Chris's wish: if this is the first time someone opens it, start the conversation that needs to be had, like mapping the business model, which is probably instant value for almost every HubSpot admin and does not cost credits. Those mappings are always on every admin's list and never get done, and it went on the list for Office Hours later that day.

Agents Sending Newsletters

Customer Agent Weekly Newsletter

The customer agent weekly coaching digest, in private beta, is an email every Tuesday at 9 AM local time with your customer agent's performance stats and its top coaching recommendations, so you do not have to log in to see them. Trisha's reaction was honest: it is interesting, and she is feeling notification overwhelm with HubSpot, partly because she lives in many portals and gets every notice many times over. The conversation that matters is who should be reading these and who is responsible for them, because if no one knows who is responsible, no one is.

Chris brought a counterexample from Nico Lafakis, who has started using the new always-on assistant from OpenAI, which Chris described as Breeze Assistant as one continuous conversation that always has your context. Unprompted, it asked who handles Breeze enriched data deletion requests for Value-First, because a HubSpot notice that morning reported two pending ones. His read: humans are already overwhelmed and that cannot be solved, so the email channel is becoming something agents watch, which is why he leans on email more than he used to. Casey's read was more pessimistic. Agents will generate even more email, the pool she never looks at just gets bigger, and she already has agents sorting her inbox into categories she mostly does not open.

Why it matters: coaching is like the data model, always on the list and never actioned, because it is hard, undocumented, and it makes you feel bad when the same thing comes up before you have coached it. Whoever actions it first will do it with an agent that says here are the top three, ready to go, instead of a fifteen-minute research exercise through transcripts. That was the second paradigm shift in a single morning: first that pop-ups may be worth not dismissing out of hand, and now new approaches to what happens in your inbox.

Casey's Pick, Reluctantly: Manual Sort Within Lanes

Manual Sort for Board View Within Lanes

Casey did not want to be up, but she was. Manual sort for board view within lanes is live for all tiers: drag and reorder cards inside a lane, not just between lanes, with the order shared with everyone on the view and kept over time. On the show it did not work, allegedly, until the board stopped sorting by a property and switched to manual sorting. Then, ta-da.

Why it matters: pipeline review meetings. The companies with better sales results had sales leadership meeting regularly on exactly what was in the pipeline and its likelihood to close, and where many teams fall down is running that review from a spreadsheet. If this lets the review happen inside HubSpot and lets you direct the team to the narrative you want them to take away, it is great.

Will It Breeze: Where Does the Order Live?

Chris turned the same update into the day's Will It Breeze, because the question has come up on his tickets board: small, medium and large pieces of work, and a need to prioritize within the planned and in-progress lanes for a client's Compass portal. One of his favorite uses of Breeze is asking how to apply a new update in your specific portal, so he pasted the update in and asked how it related to the tickets board view. Breeze listed his boards, backlog, client app feedback, office hours questions, collective feedback and surface feedback, and proposed a use for each, from arranging work by the next valuable action to setting a discussion order before a session without changing a question's status.

The distinction it drew was the useful part. Status is where the work stands, priority is how important or urgent it is, position is what to address next within the lane, and position should not become hidden business logic. Those words cause real problems for every admin deciding between a pipeline and a dropdown. Chris then asked where the order is stored when you drag a card, since his team had already created a numeric priority property to show the same thing on the external portal. Breeze found a position-in-stage property on the ticket object, but its definition had no description tying it to this update, so it would not responsibly claim the drag writes to it. Help us out a little, HubSpot: if you are going to put it there, describe it. It turned out the team had created that property itself, which leaves the real question open, and Chris would rather use HubSpot's native storage than maintain his own version.

Why it matters: Trisha uses Claude and Breeze every day, and for very HubSpot-specific questions she finds Breeze's answer is often better. Working alongside Breeze on an update in your own portal is exactly that kind of question.

The Rest of the Updates

One more customer agent update shipped and did not make it to air: CRM action details in message insights, now live, shows which records the agent created or updated during a conversation, linked by object type. From Wednesday's board, row-level filtering and data preview for data warehouse integrations is in public beta for Data Hub Enterprise, contracts with a retroactive effective date is in development, and the customer success space in the customer portal is in private beta. Everything else that shipped is in the HubSpot updates feed.

The Sign-Off

Hubsessed Office Hours start today at 11 AM Central with the Unified Revenue View. Chris's air conditioning is getting fixed, so the background noise was real.

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.