Friday, October 16, 2026, with Chris Carolan and Casey Hawkins

Another Orange Morning Recap: Friday, October 16, 2026

Friday was a two-person show. Madelyn Donovan, the usual Friday Friend, was traveling, so the horoscopes stayed on the shelf and Chris Carolan and Casey Hawkins took the hour themselves. Casey opened with official notice that she flies out Wednesday for a vacation and has not yet worked out when a person is supposed to pack for a Wednesday departure. Chris's advice was pack when you need to, which is right before, if no other time.

Here is what we got into: a week of Office Hours that kept landing on the data model, the two updates HubSpot posted overnight, a dashboard header Casey had been curious about since Thursday, a September update that turned out to be the fix for a client problem years in the making, and a Will It Breeze under the Finance lens that asked CPQ for the next best move.

Office Hours Keep Landing on the Data Model

Chris recapped Thursday's Hubsessed Office Hours on Unified Revenue View, where Ryan Ginsberg brought an open question about contracts and the NetSuite situation he is working through. The conversation was about how hard it is to fit real customer behavior into systems built for payment, delivery and invoicing, which want an audit trail and a linear order of events, when a client wants the invoice for four months from now, post-dated, today. The humans have carried that gap for years because the systems will not. HubSpot, built around the contact record and communication with people, is more flexible about it, though it is still a complex thing to think through when another system is supposed to be the source of truth. Friday's session is HubSpot Super Admin with George B. Thomas, and Chris planned to bring him the seats and credits question on behalf of everyone staring at that screen.

Casey connected it to the Thursday series she and Trisha Merriam are running on inheriting a HubSpot portal. Two or three years ago she would have heard data model and thought that was Chris's thing; she says all the time that the two of them do very different work in the same platform. The data model has become a bigger and bigger part of her world as the platform has evolved. Chris's version is that getting the data model right was a bet made as AI approached, a bet that it would not be a fleeting thing, and it is turning out to be true. There are plenty of shiny objects and credits right now, but the data model comes with whichever form of HubSpot you pay for, including free, and a relational place to put data helps any business further than importing lists and sending email.

The counterexample was fresh: a half hour spent Thursday watching someone get ten event contacts into Salesforce by way of VLOOKUPs and ZoomInfo, work that exists only because of a missing integration and a missing understanding of the data model. At some point the next step is telling leadership that nobody should be spending time on this. Contracts, which came up again from last week's session with Alexia, are the umbrella object HubSpot now offers for keeping track of everything after the sale, and you do not need a revenue seat to use them. Office Hours recordings and clips live on hubsessed.io behind a free membership.

Two Updates Worth Pulling Forward

Manage Spend between Seats and HubSpot Credits

This one went live Friday, and the hosts had figured it would be the update of the day, the kind you could spend the hour on alone. Super Admins can now swap unassigned seats for HubSpot Credits, or for a different seat type, from Account and Billing or the Seats page, without going through the account team. Casey translated: if you have a sales seat nobody is using, you can convert it to credits for buyer intent, an agent or data enrichment. The unsaid part is that assigned seats not everyone needs are a flexibility question too.

Casey had already put it to work. She pasted the update into Breeze from her partner portal and asked whether it was immediately relevant to any of her clients. It flagged two with unassigned seats, she emailed both, and one came straight back asking her to assign the seat to a person they had not known was unseated. A good opportunity to reevaluate, she said, and the bigger question is whether all the assigned seats are on the right people.

Chris's concern is the catch-22. Salesforce and NetSuite shops have strict IT admin structures, not user friendly or even manager friendly, but changes like this come with due diligence. HubSpot land is more accustomed to what do I need right now. As more things start to cost credits, that becomes the trigger: your boss wants intent signals on another list of companies, the seats are idle, so you convert them. Next week you hire somebody. Can you get it back? No. Casey had asked HubSpot that exact question, and the understanding is that credits do not turn back into seats. If the trigger was needing credits right now, you will also have spent them, and you are waiting a month at least before you can reconsider.

Why it matters: The self-serve swap is real flexibility, and it is one way only. Think it through before you convert, and treat this as a stepping stone toward a simpler seat model, something like a front office seat and an operations seat, rather than the final shape. Our take and the FAQ are on the Manage Spend between Seats and HubSpot Credits page.

Customer Agent Understands WhatsApp Voice Notes

Customer Agent came up next because it is a lot like a seat, the kind of thing that might actually use the credits a converted seat frees up. Customer Agent now transcribes WhatsApp voice notes and answers them as it would a typed message. Previously a voice note went unanswered or the agent asked the customer to type instead, and Casey's reaction covered the customer experience case: she would be so annoyed to record a long voice note and get can you type that instead.

Chris's rule of thumb is that whenever an update says previously and then why does it matter, it is usually describing something that was not okay from a customer experience perspective. The fix is obvious and welcome. The more useful idea is the framing: if you are struggling to connect seats and credits, thinking of Customer Agent as a seat on the team helps the dynamic make sense, and there is a big opportunity for teams that have used HubSpot heavily and have real data and context in it to start using Customer Agent.

Why it matters: Here is what nobody should do: have empty seats, not know what to do with the credits, turn the seats into credits, and then not use those either. The update itself needs nothing from you. The full write-up is on the Customer Agent understands WhatsApp voice notes page.

The Dashboard Header, Revisited

The hosts had been curious about the Reporting Dashboard header simplification since it slipped off Thursday's show. HubSpot says the header now shows only the most important actions with cleaner action and settings menus. Casey is not in the beta yet, so the hosts pulled up a live dashboard and worked out what they think is changing: the very top bar, the dashboard name, the refreshed three minutes ago, the three dots, share, link and add content, with everything collapsing into drop downs and the share link becoming one button. A little cleanup, and a nice one.

Chris is more interested in what is happening below the header, the ability to highlight metrics on the page in a new way, custom metrics built just for the dashboard that are not really reports. His suggestion is to pull up Breeze Assistant on the dashboard and ask how to highlight specific metrics so that when you share it, someone sees the story without reading ten pages.

Why it matters: The header change arrives on its own. The highlighted metrics are the part that changes what the people you share with actually see. More on the Reporting Dashboard Header Simplification page.

A Special Update Announcement: Customer Mapping for QBO and Xero

Casey asked for a special update announcement, and it was an update from September that she did not realize the meaning of until she ran into it last week. Improved Customer Mapping for QuickBooks Online and Xero creates a lasting connection between HubSpot contacts and companies and the customers in the accounting system, on stable record IDs rather than email or name, so invoices and payments keep syncing to the right customer when details change. The public beta covers inbound, outbound and bidirectional syncs, B2B and B2C billing, and once mapping is set up, contact sync is turned off because it no longer decides where anything goes.

Casey's client is the case study. Invoices kept arriving in QuickBooks without the billing contact, because the contact was not sent over until it was associated with an invoice, and the invoice got created first. The alternative, sending every contact, runs into QuickBooks having one billing contact field and no way to know which of ten people it should be. For that customer, this was the solve that has been months in the making. Chris's correction was years.

Chris then asked Casey to search the Another Orange Morning site for QuickBooks, which turned up a 2024 conversation with Joe Warren, the product owner on the integration since then, and the same problem. HubSpot exists to communicate with humans who can be identified by an email address, so email is its unique ID and every import and integration dedupes on it. No other system works like that. They all run on record IDs that mean nothing outside the system, and they are built around accounts, opportunities and invoices, not people. QuickBooks taught the market that there is one billing contact, from a world where invoices went in the mail and the PO box mattered more than the email. Ten associated contacts who all need the invoice does not integrate with a data model that does not care about contacts, which is why you find notes fields full of names and someone copying everyone in by hand.

Underneath it is language. HubSpot has contact and company. Everything else has customer, and the customer could be either. An email address cannot resolve that; record IDs can, and that flexibility is why a unified customer view and a unified revenue view are easier to build in HubSpot than in systems that start from an ambiguous word. When you integrate, what is a customer is almost always the first point of friction, and everyone thinks it should be obvious. Talk it through first and you do not run into it later. Even if you never touch QuickBooks or Xero, Chris's read is that the data sync settings for other systems are turning into this kind of mapping, and you will be defining the rules yourself.

Why it matters: If invoices keep landing on the wrong customer or missing the billing contact, this is the fix, and it is in public beta now. Casey has a lot of thoughts on the current project this touches and is saving them for another day. The page is Improved Customer Mapping for QBO and Xero.

Will It Breeze: Finance, CPQ, and the Last 90 Days

With QuickBooks fresh, the hosts took the Finance lens on the Will It Breeze wheel, and the reels landed on the last 90 days, Configure, Price, Quote (CPQ), and name the next best move. The composed prompt: as our finance lead, using Configure, Price, Quote (CPQ), can you name the next best move across the last 90 days? There is a lot of nuance in those words, and Casey's reading was based on the last 90 days, what should we be doing next, from a finance perspective.

Chris ran it in his demo portal, which is not set up around CPQ at all, and Breeze still came back with a finance and sales reconciliation of CPQ activity before changing pricing or discount policy. Casey called that great advice. CPQ gets implemented from the configuration side, approvals and rules because margins are suffering and sales is making decisions it should not, and it does not come with the CRM because it is not relationship driven. Finance asks whether margin was lost in the last 90 days and whether the discount policy should change; sales may not hit its number without the discounts. That push and pull is often the reason two teams cannot even integrate their systems, and the point of the segment was that inside HubSpot, with CPQ used as designed and Breeze used as designed, you can get the answer to that question easier than ever. Casey ran it in her portal too and got essentially the same answer.

Her takeaway was practical: a lot of finance people do not go into HubSpot, so when she is walking into a meeting with finance about the CPQ process, this is a great prompt to prepare with. Chris's was the lesson of the day. You can be the admin and ask a question like this. If you are getting called into a meeting and finance is going to be there, be ready to show the value of what you are doing in HubSpot, because you will almost certainly be asked, and even if you have never heard the word finance before, you can prepare by talking to AI, which has. Casey does a version of this almost daily with a client whose leadership has changed: work through the problem, then ask the AI to pretend it is the C-suite and say what it cares about. Will it Breeze? Yes, it can. Watch the episode for the full run.

The Rest of Friday's Updates

Friday's drop was the two updates above, and the hosts noted the cadence slowing after a bigger Thursday. The Thursday updates that did not come back around on Friday, granular OAuth scopes and the self-service migration tool, improved reply recommendations powered by Breeze Assistant, external posts on the social calendar and consent email tracking, were covered on Thursday's show and are in the HubSpot updates feed with everything else that shipped.

The Sign-Off

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