Show recap — Friday, July 31, 2026

Another Orange Morning Recap: July 31, 2026

Friday, July 31, the last morning of the month, and Madelyn Donovan was in the Friday seat with a wall of plants behind her that have finally started cooperating after a lot of grow lights and a lot of patience. Casey Hawkins opened on the pile that had built up: a stack of updates from Thursday that the show had only partly worked through, plus a few more that landed overnight.

Here is what we got into: the marketing email editor getting redesigned again and why that is a good sign rather than a bad one, two sales APIs that matter more for what your AI connector can reach than for anything you will code yourself, associations as lookup properties coming back around with a question nobody had asked yet, a quarterly marketplace roundup with two apps worth stopping on, the new CX Score and the reason you should not trust it out of the box, and Madelyn's Friday horoscopes.

The Email Editor Gets Another Look

The first one on the list was a redesigned marketing email editor. The sidebar collapses down to a strip of icons so the email fills the screen, the editing tools float over the content instead of crowding it, and the actions people actually reach for live in a bar that stays put. A and B testing, preview, test sends, and the desktop and mobile toggles are all one click away rather than buried behind a menu.

What made the room pause is that HubSpot redesigned this editor not that long ago. The read on the show was that this looks like a response to feedback, and that is worth saying out loud because it reads as a good sign, not a stumble.

Madelyn framed the actual problem better than the release note did. It was never really the number of clicks. It was hunting for a setting you already know exists, somewhere behind a panel, in a screen where four things are competing for the same space. A sidebar that gets out of the way and an action bar that stays put are aimed straight at that.

Chris Carolan put the wider pattern around it. Canvas style controls are spreading across HubSpot in general, and once a surface carries this much complexity, cramming everything into one sidebar stops working. When HubSpot finds a layout that lands, it tends to flow out to the rest of the system, so this shape will show up somewhere else before long.

Why it matters: There is nothing to do this week. It is private beta and HubSpot has not published a screenshot yet. If you are in the email editor every day it is worth asking about beta access, and everyone else can wait for it to arrive.

For more details: read our full take on the redesigned email editor.

Two APIs, and a Different Way to Read Them

A sales templates public API and a sequences public API landed on the same day. The first covers listing, creating, retrieving, and updating templates and template folders. The second covers creating, retrieving, updating, and deleting sequences, plus pulling sequence performance data.

Casey named the shift in how she reads these. She skipped API updates for years. Now every one of them gets read as a question about what the AI connectors can do that they could not do yesterday, and on that reading these two land.

There is a naming problem worth flagging first. Sales templates is ambiguous. They have been message templates, then just templates, and the release note does not settle it. The show's read is that these are message templates, and the best evidence is that the sequences API shipped right beside it. Those two have always worked together.

The case that made it concrete came from client work a few weeks back. A team was running their sales motion out of Claude through the HubSpot MCP connector, and hit exactly this wall. There was no way to manage templates from outside HubSpot, so the work fell back to somebody doing it by hand in the portal. This is the endpoint set that closes that gap, and it goes all the way down to Sales Free, which means effectively everyone.

Chris had run into a version of the same thing from the other side, which is worth an asterisk here rather than a section of its own. He has been implementing the HubSpot APIs across an agent team this week, went to check whether the newer endpoints needed anything activated on his tokens, and found that files now has a section of its own with around six endpoints covering read, write, and delete against the file manager. It is the same story these API updates keep telling. The capability is arriving faster than most people are checking for it.

Why it matters: If you are connecting an AI assistant to HubSpot sales work, both of these belong on your list now. The question is not whether you will write the API call. It is what your connector can reach on your behalf.

For more details: read our full take on the sales templates API and the sequences API.

Associations as Lookup Properties, One More Time

This one has been on the show twice already this week, and Madelyn had not been in the room for either pass, so it came back around. What is new since Monday is that HubSpot specified which relationship types are supported at launch: one to one custom labeled associations.

The short version is that lookup properties are a new property field type that points at another CRM record, carrying not just the fact that two records are related but the nature of that relationship through a labeled association. They are meant to show up everywhere properties already do, on record pages, in forms, lists, workflows, reports, and custom views.

Madelyn brought the use case that had not come up yet. A client a few months ago wanted to see associated records of a specific association label in the index view. There were other ways to show them that data, but the index view was where they were ready to look, and anything else was going to slow down adoption. Her second one is reporting, where the workaround has always been building lists off other lists, or automating a tag onto a record just to achieve something you could have looked up directly.

Then she asked the question that got the biggest reaction of the segment. She has a project this week building a workaround for requiring an association at certain deal stages, which HubSpot cannot do today. If associations become properties, can they be required? Nobody knew. It is the right question, and it is the one to watch as this comes out of beta.

Chris added the angle from the build side. Managing associations on a record today means committing screen real estate to a card with a plus button on it. If the relationship is a property instead, it is a dropdown, and the record gets simpler. The timing next to Revenue Hub is not a coincidence either. Orders, invoices, and quotes all depend on things being associated at specific moments, and billing contact is one of the few places HubSpot already ships a purpose built label rather than leaving you with parent and child.

Why it matters: The setup friction is the real target here. Today your team has to know which mental model applies, properties for data and associations for connections, and admins maintain both. Collapsing that into one framework is worth more than it looks on paper, especially for the people on your team who think in properties and have never wanted to learn the rest.

For more details: read our full take on associations as lookup properties.

The Marketplace Quarter, and Two Apps Worth Stopping On

The quarterly marketplace roundup landed with 193 plus new apps and 13 plus featured updates, which put the total well over two thousand. The plus signs next to very specific numbers got their own moment, and Chris admitted he has the same fight with AI when he builds, where it wants to hard code a count onto a page that is going to be wrong by tomorrow.

Casey pulled out the practical one, and it came from this week. Two different sales teams were stuck on the same thing. Leads were scoring, and nobody knew what to do with them or why they had scored at all. The entire solve was opening the record, asking Breeze assistant what the person had done recently, and then asking it to draft an intro email. That was it, for both teams. Slack can now talk to Breeze assistant directly, and both of those teams live in Slack, so that same move now happens where they already are.

That story is also the answer to the complaint that it is impossible to keep up with HubSpot. It is impossible, and Casey reads the updates every day. What actually helps is having the right context at the moment you are stuck, which is a different thing from having read everything.

Chris pulled out the structural one. HubSpot Agent for Microsoft 365 Copilot brings CRM context into Copilot chat and Teams, and lets you act back in HubSpot from there. That is the template, and the blank is going to get filled in over and over. HubSpot agent for wherever your team already works. As that spreads, a lot of integration building stops being necessary at all, and Customer Agent is already doing this. Worth knowing that HubSpot agents carry credits against the work they do.

There is a principle underneath both. The old advice was to find the one place where you do the thing and make everyone go there. That is not how anyone works now. HubSpot is the right hub precisely because it can hold the context in one place and then push it out to whatever surface the work is happening on. As Chris put it, the job is helping people give themselves permission to stop doing it the ways they hate doing it.

A few others got picked out of the list. Shopify now syncs product variants, so different sizes or colors of the same item come across correctly, which closes a gap that has been open a long time. SurveyMonkey's update addresses the thing that always broke third party surveys, matching a response back to the right contact. CallRail added an AI voice assistant that looks up HubSpot contact data, and a lot of teams have fought with CallRail configuration. Granola, Eventbrite, BoldSign, NetSuite, Qualified, and Super all landed updates too.

Why it matters: Do not read the whole list. Skim it against your own stack, and give the Copilot and Slack ones a real look this quarter.

For more details: read our full take on the marketplace roundup.

CX Score, and Why You Should Not Trust It Yet

This is the one the morning kept circling back to, and it had been sitting open in a tab through most of the show waiting for a gap in the conversation.

CX Score puts a unified customer experience number on each support ticket, zero to one hundred, calculated automatically once the ticket closes from the customer and rep message data. It comes with a range category and an explanation that includes quotes from the actual conversation. What has changed since it first appeared is exclusion settings. From Help Desk settings you can now toggle scoring at the portal level and define rules that skip specific ticket types, so spam and auto closed tickets stop dragging through the model.

Madelyn's reframe is what turned the segment around. A post ticket survey only hears from the people motivated enough to answer, and in practice that means the unhappy ones. It is the same reason online reviews cluster at five stars and one star with very little in the middle. A score calculated on every closed ticket reads the whole population instead of the slice that selected itself. That is a real improvement on a health score you configured yourself, and it carries less of your own bias than anything you would have built.

Then the caution, and this is the part to act on. The signal list is lopsided. There are a couple of positive factors against roughly a dozen negative ones. An AI reading tone against a list shaped like that is going to miss positives and over index on negatives, the same way people do. Chris connected it to a conversation earlier in the week about putting agents in a position to succeed, where the ratio that came up was nine positives for every one negative in how people actually communicate. That is close to the inverse of what this scoring model is set up to notice.

There is a second asymmetry underneath it. A good ticket is often just one that got resolved quickly, which shows up as the absence of a negative rather than the presence of a positive. And some of the classifications look strange on their face. Positive future intent and advocacy are sitting in the neutral bucket, which is hard to defend.

So the move is not to take the number and run. Put your own context into the portal first, the terms and the moments that actually signal something for your business, because that kind of transcript management is already available to you and it is what makes a score like this worth having. The risk otherwise is doing what the score tells you without checking whether the score is right.

One more thing worth separating out. This is much easier for support than it will ever be for lead scoring, and the difference is not effort. Tickets are conversations, so there is tone and language to read. Lead scoring exists precisely where no conversation has happened yet, and the whole job is deciding who to start one with. Intent signals and unstructured social data are starting to close that gap, and the interesting part is that the unstructured data about a person has always existed. It lived in inboxes and in people's heads and on sticky notes. It is only now arriving somewhere a system can see it.

Why it matters: If you run support on a Service Hub Professional or Enterprise seat, get into this beta. Then set your exclusions and load your business context before you let a single score drive a decision. The direction is right and the default weighting is not.

For more details: read our full take on CX Score.

The Friday Horoscopes

It had been a heavy scoring week, so the show closed on the other kind of score. Madelyn's Friday segment reads the month's themes back through the zodiac, and this week the themes were a rebuilt home feed, campaign cloning and the rest of the API updates, smarter prospecting, Starter upgrades, dashboard themes, and AI scoring insights.

Aries gets a smarter target for existing momentum. Taurus gets small improvements to daily systems that add up to a better rhythm. Gemini's scattered ideas finally get organized into one sharp feed. Cancer is being asked to build a calmer home base. Leo, in Leo season, has rising visibility and a story worth presenting well. Virgo turns instinct into repeatable results through cleaner structure and smarter scoring. Libra balances aesthetics with utility. Scorpio should trust the signals under the surface. Sagittarius finds expansion easier now the path is mapped. Capricorn should build once and clone wisely. Aquarius gets the reminder that the real breakthrough is usability, not novelty. Pisces gets to stop guessing the vibe, because the right signals are surfacing on their own.

The segment is heading for the Another Orange Morning site, and for an email you will be able to subscribe to. Floating heads of HubSpot people with their zodiac signs attached is apparently also on the table.

The Sign-Off

The bigger thing behind the horoscopes is where the show is heading. Another Orange Morning is turning into a community site and a community content project, built around helping people notice the value already sitting around them in HubSpot. If you have ideas of your own for what belongs there, that invitation is open.

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. Have a good weekend, and we will see you Monday morning.