Thursday, October 15, 2026, with Chris Carolan, Casey Hawkins, and Trisha Merriam

Another Orange Morning Recap: Thursday, October 15, 2026

Thursday brought Trisha Merriam back as the Friend, and the first bit of news was secondhand: Zach Hussion, who has told the hosts more than once that the theme song runs too long, admitted on Wednesday that he was jamming to it. Chris Carolan took that as proof that sometimes you do what is best for people before they know they need it. From there the show picked through the board in turns, a system that got confused enough by the half hour mark that Chris promised to work on it.

Here is what we got into: Office Hours, a plain-language definition of unified revenue view, a Thursday LinkedIn series and a hundred Breeze prompts, then five updates: asking Breeze Assistant about your team's use of Breeze Assistant, granular OAuth scopes, external posts on the social calendar, consent email tracking, and higher pipeline object tag limits, before a Will It Breeze that ranked contacts out of an inbox.

Office Hours, a Definition, and a Thursday Series

Chris looked back at Wednesday's Reporting and Dashboards session with Madelyn Donovan and Joshua Oakes, which Zach also joined. Most of that hour was about the different ways to present data to people, including the ways that do not belong in a report at all. Thursday's session is Unified Revenue View with Ryan Ginsberg at 11:00 Central, and Mondays now carry an AI-Native hour with Nico Lafakis and Trisha. Trisha's pitch for that one was that it will be the unintimidating AI-native hour, and if Nico goes over anyone's head she will bring him back down. Chris said the pairing came from the summer boot camp, where Trisha was the one asking what Node is while the rest of the room assumed everyone knew, and that another boot camp is coming at the beginning of December.

Casey Hawkins asked the question she suspects a lot of people have: what does unified revenue view actually mean? Chris put it to Trisha without any frameworks attached, and her answer was the useful one. Wherever you are in the system, you see everything you need to know about revenue, annual recurring revenue, a deal, a product, a line item, without leaving for another tool. Chris added why that is new in HubSpot: it is the first time you can tie marketing intent data to dollars in the bank and forecast forward from one place. The usual RevOps setup keeps the CRM tidy while the revenue numbers the company plans from live in finance's system, so revenue here means forecasting into the bank, not just up to closed won. He would call it a unified value view, and expects to eventually, but not yet.

Trisha and Casey also have a Thursday series on LinkedIn called "You just inherited HubSpot, now what?", a space both of them have lived in for years. Week one was collecting documentation and finding answers; week two, at 12:15 Eastern, is the data model. On the same theme, Chris recorded an episode of the RevOps Loop podcast with Digital Reach titled "Have You Asked Breeze?", published Thursday, and Casey put together a hundred potential Breeze prompts for getting to know an inherited portal, which you can get by messaging her or Trisha. Chris's caveat on prompt lists was the segment's real point: suggested prompts are fine for getting started, but the value is in having the conversation with Breeze, and it is easy to give away your agency when a prompt that worked for someone else does not match your portal. Your contacts are different.

Five Updates Worth Pulling Forward

Ask Breeze Assistant About Your Team's Usage of Breeze Assistant

Live for every hub and tier. A Breeze Assistant skill lets super admins ask the assistant how the team is using it: message counts, adoption rates and team breakdowns, returned inside the assistant rather than on a separate dashboard. Casey guessed correctly that this would be Chris's favorite of the day, and neither Chris nor Trisha could see it on their own boards yet.

Chris's read is that this matches the advice he gives every admin and HubSpot manager: your job is to get people safely using Breeze now, and this is the first tool for checking whether that is happening. The bigger idea for him is what comes after the counts. Watching how people talk to Breeze is the fastest way to understand someone's AI journey, and the natural next step is Breeze itself noticing that a team keeps asking for things in a way that shows they do not understand the data model, and coaching them. Casey tempered expectations for today: it reports message counts and which teams are using it, over a rolling twelve month window, and not much more. Trisha's objection was the practical one. It is limited to super admins, and as a partner she wants to see her clients' usage, where the super admin is often someone who logs in only to add a user. Chris granted she might have a case.

Why it matters: If you are the person responsible for Breeze adoption, you finally have a number to start from, and a reason to look at the conversations behind it. For more details: Ask Breeze Assistant About Your Team's Usage of Breeze Assistant.

New Granular OAuth Scopes and a Self-Service Migration Tool

Live. The new granular OAuth scopes replace the broad files, timeline, tickets and HubDB scopes with permissions split by object and action, and the Granular Scope Migration Tool, in public beta since September, is now generally available in developer accounts for legacy public apps and Projects-based marketplace apps. Trisha picked it, Chris and Casey read it, and the room agreed the reading used up most of its energy.

Chris connected it to the larger transition HubSpot is making away from private and legacy apps: everything in that description is the reason to migrate, because the granular capabilities and the separate grants for sensitive actions are what make the new system safer. If you have ever connected Claude or OpenAI to HubSpot and clicked through every scope box, you know why a developer does not want to do that more than once, which is how scopes go stale on marketplace apps. Trisha's summary stands: this is for people with apps published in the marketplace. And a self-service migration tool, Chris admitted, is a phrase he wants to mean CRM data moving between systems. It does not, and Trisha had not got her hopes up.

Why it matters: If you build or maintain a marketplace app, the migration tool is waiting in your developer account. If you do not, this is the plumbing behind apps asking you for less. For more details: New Granular OAuth Scopes and a Self-Service Migration Tool.

View External Posts on the Social Calendar

A public beta for Marketing Hub Professional and Enterprise, expected October 28. Posts published outside HubSpot show up on the social calendar, so a brand that posts natively or through another tool stops seeing an empty calendar. Chris picked it and then confessed it was a one-line update, which Casey noticed.

Casey's reaction was personal: she posts from HubSpot some days and from LinkedIn directly on others, so this is very nice for her. Chris's hope is consistency. He has been excited before about HubSpot keeping track of things published elsewhere, and whether a post gets caught, and what you have to do for it to be caught, has not always been clear. Trisha wondered how many networks it covers; the connected set is Facebook, Instagram, LinkedIn, Reddit, TikTok, X and YouTube.

Why it matters: If your calendar has never matched what actually went out, this is the fix, with the usual caveat that you should check what it catches. For more details: View External Posts on the Social Calendar.

Consent Email Tracking Capabilities

A public beta for every hub and tier. Email tracking is managed per contact through a new consent record on each email address in the CRM, in response to updated guidance from Italy and France that requires explicit consent before tracking. That consent then governs tracking for marketing and one-to-one email.

Casey had been in a conversation about exactly this earlier in the week, and was glad to see the options expand beyond the email HubSpot sent about the Italy and France requirements a couple of months ago. Trisha wrote it down as something to share with a few people as soon as the show ended. Chris took the long view, and a contrarian one: all the energy that goes into the infrastructure behind email consent is energy he wishes teams would put toward a channel like LinkedIn, because email is getting harder every month and Gmail and Microsoft are getting better at stopping you. Trisha pushed back that this assumes everyone is sending cold email, when plenty of businesses have subscribers who asked to hear from them and still need consent handled properly. Chris's reply was that the opportunity is for businesses that built their whole list on email and never shifted, and that social in HubSpot is underused for that reason.

Why it matters: If you email contacts in Italy or France, this is the practical way to stay inside the rules. If you do not, it is still the cleanest per-address consent model HubSpot has offered. For more details: Consent Email Tracking Capabilities.

Pipeline Object Tags: Increased Limits

Live. Pipeline object tag limits per portal go up: Starter from twenty to thirty, Professional from forty to fifty, Enterprise from eighty to one hundred, with Free staying at zero, and the limit applies across every object type in the portal. Trisha asked whether these are different from deal tags. Casey's answer: they are the evolution of deal tags, which started on deals and now apply to anything with a pipeline.

Chris read the increase as part of the recent move from per-pipeline limits to per-portal ones, and reminded the room that there is more behind a tag than it looks. Setting one up uses a lot of the same machinery as scoring and segmentation, so presenting a Kanban board with tags can get complex fast. Tags are available through the API now too. Building out a new chunk of his data model with AI the night before, the AI suggested tags that did not show up in the system, which he is still investigating. For the deep version, he pointed at the episodes where he and Joshua Oakes, the deal tag guy, work through it.

Why it matters: If you were bumping the old limit, you have room. If you have never used tags past deals, this is a reminder they work across the pipelines you already have. For more details: Pipeline Object Tags: Increased Limits.

Will It Breeze: Rank What Deserves Attention First, From Outlook

The wheel ran under the Sales lens and landed on Contacts, Outlook, and rank what deserves attention first, which built the prompt: as our sales lead using Outlook, can you rank what deserves attention first across contacts? Casey liked it and ran it on her own portal, noting that she does not have Outlook connected. Chris tied it to the historical email import for Outlook from earlier in the week: imagine you have just pulled years of inbox history into HubSpot, and this is the prompt that turns unstructured email into a view of who you actually have relationships with, without asking reps to log anything they never logged.

Breeze searched Casey's connected inboxes, found nothing in Outlook because there is no Outlook, and then did the next best thing: it ranked who she should prioritize anyway and recommended what to do in Outlook, which got a laugh. Chris asked for the prompt in the chat to try with Gmail on his side. Casey's result held up. The two people at the top were the two people she has active sales conversations with, followed by two clients she supports as needed, and the one who had emailed her that morning was exactly where she expected her to be.

Chris's takeaway was the one to keep. You can build this into a fuller process, a context, a step in the system, so nobody has to ask Breeze every time, but the shift is already here: stop forcing reps to do everything for the system when they are already doing it for the relationship. That is the part they will never sacrifice, and it should not be asked of them. The data flow and the context flow now exist, and this is what everyone has been asking for, something that makes it easy to understand what to do next. Will it Breeze? Yes. Watch the episode for the full run.

The Rest of the Week's Updates

The board also carried the Reporting Dashboard header simplification, improved reply recommendations powered by Breeze Assistant, and unit cost mapping for line items between HubSpot and NetSuite, none of which the show got to, plus Wednesday's cloning goals in bulk and redacted email bodies. Everything that shipped is in the HubSpot updates feed.

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 tomorrow morning.