From the show
Another Orange Morning Recap: September 28, 2026
Monday's show had all three seats filled. Chris Carolan was back from Moonshot, Joshua Oakes held the Monday Friend seat, and Casey Hawkins joined from her car, which the room is now calling a web series. Ten updates landed on the list, and a lot of them had moved from public beta to live in the afterglow of UNBOUND.
Here is what we got into: notifications for form automations and the case for choosing your alerts carefully, the Knowledge Base API and why you do not need a data pipeline to get value from it, the health score side card finally showing its math, conversational editing for AEO-generated blog posts and the credit question underneath it, the NetSuite connector for Breeze Assistant and what cross-system friction does to a team, email templates for workflow tasks, and a round of Will It Breeze on explaining product updates to a head of sales.
Before the Updates: UNBOUND Unboxed and Hubsessed Office Hours
Two dates to hold this week. UNBOUND Unboxed is Wednesday, September 30, at 10 AM Central, where the Hubsessed team gets together to share what they are thinking coming out of UNBOUND. Sharing Kyle Jepson's slides on Friday's show set a good precedent for the kind of thing that fills that hour.
Then Hubsessed office hours start on October 1, free in October for Hubsessed subscribers. The sessions run at 11 AM Central and cover Loop marketing and AEO, reporting and dashboards, the unified revenue view, and HubSpot super admin work, wrapping up on Fridays. Nobody expects you to make every one, and registering gets you the recordings. The pitch from the room was simple: bring a real question, even a small one, because somebody else probably has it too, and saying it out loud tends to produce the most useful two minutes of the week.
The Afterglow of UNBOUND: Notifications for Form Automations
Notifications for Form Automations
The first pick off the list was one of the updates that went from public beta to live. Notifications for form automations let you set your preferred method, email or in-app, for hearing about issues with automations built in the forms app and about out-of-range changes in form submission rate. It is Enterprise only. For anyone who could not opt into the beta, or had no time during beta season to try something unfinished, this is the moment to go look at what is now done.
Enterprise portals already have a fair amount of control over workflow notifications: which members or teams get notified, and whether a workflow triggered too much or too little. Form automations have mostly had one move, emailing a person when a form is submitted. Bringing the same control to forms is a real win for admins, particularly for the edge-case forms a customer only fills out in an unusual situation.
Why it matters: an alert is only useful if someone reads it. Plenty of people love email notifications and run their inbox like a to-do list, right up until they miss the important one because it arrived with two hundred others. The room also flagged two ways out-of-range alerts go sideways: a low-volume automation will trigger constantly, since one or two extra people is a big percentage change, and anything tied to closing deals has a built-in end-of-month spike and start-of-month dip. Below Enterprise, the read is that most portals do not have enough volume for these swings to be meaningful, and you will become aware when you need to be.
The Knowledge Base API Is Here
Knowledge Base API
Speaking of more control, the Knowledge Base API is in public beta for Service Hub Professional and Enterprise, one of those updates that is surprising only because it did not already exist. Fifteen new endpoints let developers create, retrieve, update and publish articles, with read access to settings, categories and tags. Until now there was no programmatic path at all; every article went through the HubSpot UI.
The first reaction was that this is a very big deal, and the second was a caution against overthinking it. You do not need to build an automated pipeline for this to be valuable. Being in an AI conversation, realizing something would make a good knowledge base article, and shipping it into HubSpot is going to matter to a lot of people. The knowledge base and customer portal are usually the part of Service Hub teams plan to get to after tickets and help desk, and then never do, so anything that lowers that bar for people and for the agents working around HubSpot is welcome.
Why it matters: the use case that keeps coming up with clients is syncing from somewhere else. Training programs, LMS material and PDFs often live outside HubSpot, and until they are in, the answer has been a one-time export or accepting that Breeze does not know that information. Waiting for HubSpot to build a migrator for your particular system gets complicated the moment your setup is customized. Now an AI tool can read that source and write it into the knowledge base the way HubSpot needs it. The easiest beta test is to have an AI tool find a gap in your existing knowledge base, or turn a good Q&A thread from your inbox into an article. It is also one of the lower-risk places to start using AI on the context already in your systems, since it does not carry the lead and sales KPIs that tend to get in the way, and it opens up with one Service Hub seat.
Casey's Pick: The Health Score Shows Its Math
Improved Health Score Side Card Score Breakdown
When it was Casey's turn, she went with the health score side card score breakdown, partly because she was not sure what all of the words in the title meant. It turns out to be a very practical update. The side card now shows the signals behind a customer's health score, grouped the way you set up your health score configuration. HubSpot's example is a score of 55 that includes a minus six for low meeting frequency, called out right on the card so you know to increase contact with that customer, if that is what you want to do with that score.
Why it matters: why a score is what it is comes up constantly, and lead scoring already shows its breakdown. The card itself is the best place to answer that question, because users should not have to dig into the configuration settings behind a score to understand it, which is what they have had to do until now. It is live for Service Hub Professional and Enterprise. The one thing the room wanted and did not get was a screenshot on the update.
AEO Blog Posts, Conversational Editing, and the Credit Math
Conversational Editing for AEO-Generated Blog Posts
Conversational editing for AEO-generated blog posts is in private beta for Marketing Hub Professional and Enterprise. You can refine a blog post the AEO tool generated by telling Breeze Assistant what to change: tone, structure, messaging, or a specific section. HubSpot's framing is that AI-generated content sometimes needs a final round of refinement, and the room's response was that sometimes is doing a lot of work in that sentence.
The update is really about the path around it. Creating an article from an AEO recommendation runs through Content Agent, which the room understood to cost around a thousand credits, and most portals start with three or five thousand. The best recollection on the show was that the credits are consumed when the post is generated, not when it is published, which makes this a place where credits are not outcome-based, while the conversation with Breeze afterward appeared to be free. That leads to the question worth testing: with the recommendation on screen, could you open Breeze Assistant and build the article there instead, and skip the thousand credits?
Why it matters: the AEO tool has a lot of power on one surface, including social post recommendations that are not the same thing as a blog post, and HubSpot adds more every day. Build SOPs around it before it gets overwhelming, and use a Breeze conversation to decide how to approach each recommendation, including whether you need the article at all. The recommendations themselves got good marks. They are prioritized and carry an estimated citation lift that is most useful for comparing recommendations to each other, and where they have missed, it has usually been the prompts or product configuration in the portal rather than the tool. None of this means you should not spend the credits; it may be the best way to spend them. There are just a lot of variables in that decision.
The NetSuite Connector and the Cost of Cross-System Friction
NetSuite Connector for Breeze Assistant
The NetSuite connector for Breeze Assistant is in private beta for all hubs and tiers. Once it is connected, you can ask Breeze Assistant to look up NetSuite records, run reports, execute saved searches, and create or update NetSuite records without leaving HubSpot, and it respects NetSuite's existing role-based permissions. The room's summary: to the extent that NetSuite has to be in your life, the less you have to use NetSuite to interact with NetSuite, the better.
This one could change the scope of real client conversations. The common request goes like this: the team needs access to post-sale information, NetSuite is the source of truth, leadership does not want everything brought into HubSpot, and nobody wants to buy sales reps NetSuite licenses because they are expensive. The fix has been an integration that can cost tens of thousands of dollars and take three to six months, followed by the change management to get anyone to check the new orders view. Now the rep can ask Breeze. It runs the other direction too, for the person on a separate team getting HubSpot data forwarded by email because they do not have a seat.
Why it matters: the bigger cost of cross-system friction is not the missing information, it is what it does to people. When a rep has to file a request and wait three days to see billing terms before building a quote, they give up, and the lesson they learn is that the machine is impossible, so why try anything meaningful to improve it. That is what learned helplessness looks like, especially with a sales manager asking for faster quotes on things outside the rep's control. HubSpot built the complex connector so you do not have to, and it starts to chip away at that resistance. Every admin should be getting their team used to talking to Breeze, because updates like this keep making that conversation the best way to answer most questions. Building a capability is one thing; getting people to adopt it is another.
Email Templates, Now in Workflow Tasks
Email Template for Workflows
Sequences have always loaded a template when a manual email task is assigned. With email templates for workflows, now live for Service Hub Professional and Enterprise, workflows can do the same, and template support works everywhere tasks are created. Some teams had been routing email tasks through sequences purely to get a templated starting point, but sequences cap you at one per contact at a time, which creates operational issues and puts deliverability at risk for everyone on the account.
Why it matters: this makes one of the first steps in any onboarding process more valuable: get the team's email templates out of Word docs and wherever else they live and into HubSpot. Even the room was surprised to find out how long templates had worked on sequence tasks. There was also a small request for the product team: when an update is named with a word as broad as email, a qualifier helps anyone trying to find it again later.
Will It Breeze: Explaining Product Updates to a Head of Sales
The show closed with Breeze Assistant on HubSpot's own product updates page. The first ask was to explain the page to someone brand new. Breeze pulled company and brand context first, then wrote an explanation formatted for Microsoft Teams, which is where its suggestions kept pointing. The content was solid: this is where HubSpot announces what is new, updated or changed, usually first. Most admins have never written anything like that for their teams, and a note like this from a leader to a frontline user goes a long way toward explaining why it is so hard to keep up with HubSpot.
Then the asks got harder. A version for the head of sales came back long, and one with a stronger sales leadership angle was better. A kid-simple infographic version produced a soccer coach analogy, where a team that misses a rule change keeps running old plays, which was pretty good, along with an instruction to be less explicit about the eleven-year-old part before anything went to a sales leader. Breeze's ability to borrow an analogy from anywhere keeps impressing people, and none of this required building out your own AI first. Explaining and documenting are on the table for every portal right now.
Why it matters: the real lever is context. If your CRM holds relationship details, like how someone prefers to communicate or that Sam loves camping, Breeze could shape a document for that specific person, and that was the next experiment the room wanted to run. Audience profiles make it faster still, because a contact on a profile carries what you know about their situation. The room's ranking: agents are the fastest path for bounded problems you have seen before and materials you reproduce every time, and Breeze is a close second for the one-off, like a business case in someone's own board format. Agents can feel out of sight and out of mind at the level of trust most teams have with these systems, so teaching people what to expect from Breeze conversations, with an admin and an SOP behind them, looks like the right path to agents later. Get your context into HubSpot, and Breeze can be useful.
The Rest of the Updates
Seven more updates shipped between September 25 and 28 and did not make it to air. Work on tasks with Breeze Assistant puts a button on every task that starts a Breeze thread to help you finish it, in private beta. Managing spend between seats and HubSpot Credits will let Super Admins swap unassigned seats for credits or a different seat type without going through the account team, expected October 16. Cross-object filtering on CRM index pages, which Casey called out on Friday, is now live for all paid subscriptions. Spam visibility and management in forms is live, with a Spam tab on each form and spam across all forms in the Analyze tab. Conversational enrichment for email is in public beta, capturing contact and sales data from email conversations. The Knowledge Base Agent is in public beta for Service Hub Professional and Enterprise, suggesting new articles and edits from your tickets. And map visualization for CRM index pages is in private beta for Enterprise customers. Everything else that shipped is in the HubSpot updates feed.
The Sign-Off
Casey is running a prospecting agent HUG workshop tomorrow, UNBOUND Unboxed is Wednesday at 10 AM Central, and Hubsessed office hours start Thursday at 11 AM Central. We hope to see you there.
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