From the show
Chapters
- 02:04Good morning: Tuesday, November thirdTopic
- 02:41Today: the Marketing Studio admin HUG, then Office Hours on loop marketing and AEOTopic
- 04:26A LinkedIn Live on whether AI is making work more fun or busierTopic
- 05:47The events page, and a daily sync that last ran October 29Topic
- 07:24CRM Gantt view: more objects, more configuration and an hours time scaleTopic
- 10:13How do work management and Gantt charts connect?Question
- 11:29A company record on top, its projects underneath, and deal stages that really happen on other systemsTopic
- 14:44Improved permissions visibility on the user recordTopic
- 15:57A client asks to add three people to HubSpot and send them getting-started tipsTopic
- 18:10Permissions as a job description, documented with BreezeTopic
- 20:30Round robin routing for callingTopic
- 22:37Confirming a caller's identity: typed in, or already on the screen?Topic
- 24:56Presentation templates in context within Agent HubTopic
- 27:07A weekly client slide deck that used to take a full dayTopic
- 28:02How does sales know they can use Breeze to do the templates?Question
- 30:08Marketing teams that can't get out of the identity of sales supportTopic
- 33:02Manage app secrets automatically with the new Developer Secrets APITopic
- 34:39Opportunity and risk: secrets when a UI extension deploysTopic
- 36:33What is the risk of implementing this?Question
- 39:26Breeze with direct data access to any third-party toolTopic
- 40:42Naming your secrets matters when an agent manages themTopic
- 42:16Will It Breeze: "As our head of marketing using buyer intent, can you explain this to someone brand new across leads?"Question
- 43:06Buyer intent is a signal, not certaintyTopic
- 44:59IP address matching: Breeze said problematic, corrected on air to probabilisticTopic
- 46:15Why the model calls it an interest objectTopic
- 47:10Intent signals that name the person are probabilistic tooTopic
Another Orange Morning Recap: Tuesday, November 3, 2026
Ryan Ginsberg joined Chris Carolan and me for a Tuesday that was already full before we started: the Marketing Studio admin HUG, then Office Hours on loop marketing and AEO, then my LinkedIn Live with Sarah Lane-Hawn on whether AI is making work more fun or busier. Across five updates the same question kept coming back: what does a person, a team or an agent get to see and do, and who decides?
Here is what we got into: the day's schedule and the events page, then five updates in a row. CRM Gantt view, permissions on the user record, round robin routing for calling, presentation templates in Context Home, and the Developer Secrets API. We finished with a Will It Breeze on buyer intent from a marketing lens.
Before the Updates: A Full Calendar and a Sync That Went Quiet
The Marketing Studio admin HUG runs 10 to 11 Central, and Office Hours follows right after it. I haven't played around a lot with the new Marketing Studio yet, so my hope is that we use that hour to dig in together. Chris is double booked for the first half hour of the HUG and will be there for the second, since it's a good lead-in to Office Hours.
The poll behind my LinkedIn Live asked whether AI makes work feel more fun or busier: 50 percent said more fun and 41 percent said busier. I'm in the busier camp and have said so. Ryan has worked with Sarah on leveling up her AI, so she will be talking through some of what she has built with him, and he said he might pop in and listen. You can find the day's shows on the events page. Looking at it, we noticed the daily sync that fills the calendar last ran October 29, so it is on Nectar's list.
Five Updates, One Thread: What You Can See, and Who Decides
CRM Gantt View Usability Enhancements
Chris picked this one. The Gantt view now supports custom objects, events, orders, courses, listings, appointments and meetings. You can choose the start and end date properties that power it, add task properties as columns, view it at an hours time scale, and select rows for bulk actions. It is live, not a beta you opt into, so if it's available in your portal you can go look. Chris noticed that the tier list now mixes Smart CRM and Revenue Hub in with the Professional and Enterprise tiers of the individual hubs.
It sent Chris straight to Unified Revenue View, which is the topic for Thursday. Ryan's question was how this connects work management to Gantt charts. Chris's picture is a company record at the top with project records underneath it, covering marketing, technical review, executive review and delivery, the pieces that happen in other systems and that a sales team shouldn't have to chase. Orders and custom objects sit in the same view, so you can see what happened before activation and what came after. On the hours scale, he said "Not that I advocate for measuring hours at all, but visually just to understand what the day needs, that can be super helpful."
Why it matters: a company's whole journey, from the first marketing touch through renewal, is hard to see in one place. Chris called this "another place that can give… an operational unified revenue view to really understand the journey." Ryan liked "the whole premise that you'd be able to look at a company and see all the connected pieces."
For more details: CRM Gantt view usability enhancements.
Improved Permissions Visibility on the User Record
Admins used to open the permissions editor just to see what a user already had enabled. That information now shows directly on the user record. I do that all the time, and it has a built-in risk: once you're in edit permissions, you might start editing permissions when you only needed to look. Fewer clicks is the headline for me.
I was especially happy to see it because a client emailed me yesterday asking me to add three people to HubSpot and send them some getting-started tips, with very little else to go on. This update didn't solve that one, but I said "any help with permissions is so needed." Understanding what permissions exist, and what people already have, is a big piece of onboarding.
Chris sees it as a requirement for getting real help from AI: all the information on the same page at the same time. On an HR project he is working on right now, he said this view is getting close to a job description, built from the access you have and the objects you are supposed to own. You can pull up Breeze next to it and ask it to document the permission set. Ryan pointed at the Routing and Preferences tabs in the screenshot and said "It really exposes the complexity and the power of what HubSpot is capable of." As a person who oversees accounts, he has never had to touch those tabs, and he wasn't sure what was being routed.
Why it matters: a permission set you can read at a glance is one you can document, explain to a new user and hand to Breeze. Admins just have to get comfortable talking to Breeze first.
For more details: Improved permissions visibility on user record.
Round Robin Routing for Calling
Ryan's routing question had a timely answer: "Funny you should ask about routing specifically, Ryan," Chris said, since it was update number three. Round robin routing rotates incoming calls among available team members, ringing one person at a time. Calls no longer ring every rep at once or default to the same person. The point is to spread inbound call volume evenly so a few reps aren't carrying most of it, which reduces the risk of burnout.
I thought about the two kinds of callers on a team: "there's probably two types of people, the people who are answering on the first ring and the people who are like, I'll just let it ring a couple times." Chris will pick up every time if he knows a HubSpot question is on the other end. Election Day texts have taken over his phone, so testing this means putting a number on the website.
Ryan took it to a use case: when you call your bank, "you have to always confirm your identity." In HubSpot terms, a call comes in and you want to confirm who it is before you open the record. Chris has noticed that when an agent rattles off your address, it is usually on their screen already. Ryan's read was that the verification is the recorded call itself.
Why it matters: service and sales teams get an even share of inbound calls, and callers reach a person without every phone ringing at once. The identity question is worth a design pass before you turn it on.
For more details: Round robin routing for calling.
Presentation Templates in Context Home
Chris saw this one for the first time at the Houston HUG last week. Customers can upload their existing presentation templates in Agent Hub and give Breeze Assistant instructions for when and how to use them when it creates presentations. That means on-brand slides with less manual restyling.
I said "I love this update." I use way more slides than I did three or four months ago, and the ability to make slides that don't look like text thrown on a blank deck has been a real benefit. I have one client where I now make a deck every week for our call. A year ago that would have taken a full day, and now I do it while I'm prepping for the call.
Ryan sees an effect on the whole flow: "there's just so many new capabilities that just change how you even think about the problem you're trying to solve." He has a client with a UI extension that builds a PowerPoint deck from the line items on a deal record, and he wondered what this would replace, how sales learns the templates exist and who writes the prompt. Chris said we will likely see both approaches. He pointed at marketers who can't get out of the identity of sales support only: "this is your chance to get really good at supporting the sales team and open up the space for you to do all the other marketing stuff that's been on your plate forever." Drifting decks saved on local drives have been a brand problem since digital was a thing, and a shared template in the flow of work addresses it. His bottom line: "none of it matters if you can't get people talking to Breeze."
Why it matters: a template with instructions attached gives a team consistent decks and gives marketing a visible way to support sales. Show a couple of conversations that get most of the way there, then take it to your admin.
For more details: Presentation templates in Context Home.
Developer Secrets API
The last pick was mine, partly because of what I said: "I get the notification all the time to rotate my things and I'm like, I don't know. I don't know what that means." The Developer Secrets API, in beta, lets agents and custom automation manage app secrets end to end: list the keys, create new secrets, update values (for example, to rotate an expiring credential) and delete ones you no longer need. Secret values are write only, so the API never returns them.
Ryan gave us the opportunity and the risk. "I build a lot of UI extensions," he said, and those need a token from a third party like Snowflake to authenticate. When a deployment fails because a secret is missing, an agent with permission to write secrets can read the error, create the secret and retry the deployment. The risk is on the read side: if your app can read secrets and you aren't careful with the token, "all the secrets that go there become readable via an agent." Chris noted that the update allows "create and change without the read," which closes that door. He thinks Breeze managing some of this is not far away.
Ryan added a practical one for anyone with agents in their portal. "Naming your secrets now becomes more important," he said, because "key one is not going to be very helpful to an agent."
Why it matters: credentials are one more thing agents can help you document and keep current. Write access without read access is the shape to look for, and descriptive names are how an agent knows what each secret is for.
For more details: Developer Secrets API.
Will It Breeze: Buyer Intent for Someone Brand New
I drove this one on my screen, in our own portal, and Chris called the lens: it sounded like a marketing kind of day. The spin came up with Buyer Intent across Leads, with the outcome of explaining it to someone brand new. The prompt read: "As our head of marketing, using Buyer Intent, can you explain this to someone brand new across Leads?"
Breeze opened with "Buyer intent helps us recognize which companies may be interested so we can decide where a helpful conversation makes sense. It does not prove someone is ready to buy." For someone brand new, it said, "It gives us a signal, not certainty," and "A company showing interest is not the same as a person asking for help." It laid out a sequence: recognize interest, check relevance, review the relationship, choose a useful response and confirm readiness through conversation.
Chris added a correction on the IP matching Breeze described. It is "the IP address matching, which is probabilistic": the service surveys the land and makes educated guesses about which company an address belongs to. The same goes for intent signals that name a person, such as someone engaging on social. Chris has seen that be wrong, so he looks for a link to the post or article that confirms the contact record, which a prospecting agent can now do and verify.
The lesson he took from it: "Our lead object is called an interest object in our model for that reason." Recognizing an Interest is separate from readiness to buy, because "you can be interested in something, but have no need for a call or no need for next steps." Ryan asked where the record lands, and since it shows up on the company as long as they're associated, it connected back to yesterday's theme. You can try the same kind of spin yourself on the Will It Breeze page.
The Rest of the Updates
We did not get to everything on the board. Also on the list: Job Change Signals powered by UserGems, now live; team approvers for content approvals; property comparisons in segments and workflows; the Table artifact in Breeze Assistant, in private beta; streamlined integrations with Azure Synapse and Microsoft Fabric; and Turning Off Sensitive Data Protection. Everything else 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.
Produced by Value-First Media
