Show recap — Wednesday, June 3, 2026

Another Orange Morning Recap: June 3, 2026

Casey is back. Two days in Cannon Beach, two days in Oregon wine country, Portland on either side, and a firm ruling that the Oregon coastline and the Maryland coastline are not the same genre of coastline. She returned to a Wednesday show with Chris Carolan and the Orange Wednesday guy himself, Zach Hussion, who confirmed that orange is now a load-bearing part of his wardrobe, complete with a story about a client's chief revenue officer failing to recognize him without his hat at a RevOps workshop. The hat went back on for day two. Branding matters.

It also turned out that taking a vacation during this stretch of HubSpot releases means returning to a pile: roughly seventeen updates since Monday, heavily themed around Customer Agent and commerce. Here is what they got into: Customer Agent learning to take payments and find invoices, the Salesforce selective sync release that Casey called a personal passion, Price Books getting the full treatment from the manufacturing angle, and a Will It Breeze segment built around a branded image Chris has spent a week failing to recreate.

Customer Agent Can Take Your Money Now

The headliner cluster: Customer Agent can now send payment links directly inside a conversation. When a buyer signals they are ready, asking for product details, a price, or saying they want to buy, the agent picks the right payment link from your library and sends it in the same chat, email, or WhatsApp thread. You control which links the agent can send, which get actively offered, and which stay off limits.

Zach's first question was the right one: how do the guardrails work, and how do you make sure the right link answers the right ask? The answer lives in the setup, where each payment link gets its own trigger conditions, and the show's advice was to design the conversation so the buyer naturally says the thing that fires the trigger, because high-intent phrasing is the match. Part numbers and SKUs are the extreme version: when a customer says I have your part number, I have ordered this a hundred times, just get me the thing, there is no cleaner intent signal in commerce.

The reframe of the segment came from Chris: the release note talks about friction stalling deals, but do not focus on deals. Focus on post-sale, where you already know the person, their history, and their products, and where picking the right payment link is easy because the relationship data already exists. Zach grounded it in his world: nobody is closing a six-figure deal through a chat payment link, and plenty of teams cannot use payment links at all because of downstream ERP and billing systems. But a service team selling consumables and replacement parts to existing customers, the five hundred dollar part someone needs because their system is down and they do not want the rigmarole, that is the perfect starting lane. From there the conversation reached cross-sell at the payment moment, the recently released payment links API for creating links dynamically, and the open question Zach raised about customer-specific discount structures: if a customer has negotiated pricing, does the payment link know? Probably not today, was the honest answer. Betas do not solve everything at once, and the team is looking for exactly that feedback.

For more details: Get paid through Customer Agent with payment links.

Find Invoices, and the Identity Question

The companion release lets Customer Agent find invoices for customers who ask, which the show framed as the start of something bigger: connecting Customer Agent to the rest of your CRM data, order status, tracking information, copies of documents, the whole portal-style self-service experience buyers actually want. If you are using HubSpot invoices, the data is already there and this is close to free value.

The pitch worth stealing: show this to an accounting team focused on collections. Not because every customer will suddenly pay through an agent, but because improvement projects work in increments, and an invoice paid or accessed through Customer Agent is a measurably better outcome metric than time saved. Zach shared the encouraging version of the adoption story: he ran a Customer Agent demo that one of the reps managed to break immediately, and the room did not care, because the direction was still that compelling.

The practical thread was identity. The screenshots show the agent answering what was my most recent invoice, which only works if the agent knows who is asking. The show walked the logic: a logged-in or cookied visitor gets recognized, and otherwise there is a setting to ask for an email address, after which the agent can both update data related to that contact and pull their related objects into the conversation. Verification is the unglamorous hinge the whole experience swings on. Also noted: Customer Agent can make and receive calls now, on top of chat, email, and WhatsApp, and Casey is planning a fresh round of updates to the famous Wonka demo portal to put all of this through its paces.

For more details: Find invoices in Customer Agent.

Selective Sync for Salesforce: The End of a Workaround

Asked what she had to talk about today, Casey did not pretend to be neutral: the selective sync for Salesforce objects release is a personal passion, and Chris admitted he was going to bring it up if she did not. You can now set filters that control which Salesforce objects sync with HubSpot, working like inclusion lists but applied to the Salesforce side, giving you the control there that you have always had on the HubSpot side.

Casey double-clicked on the sentence in the release note that deserves it: customers no longer strictly need to set up integration users in Salesforce to control what data is shared. For anyone who has not lived it, that was the workaround, a dedicated Salesforce user existing purely so its permissions could act as the sync filter. It worked, and it was tech debt in its purest form: creating a user just to manage a sync. The supporting riff was a moment of gratitude: the more time you spend in the back end of Salesforce, Sugar, or Dynamics, fighting CSV exports just to see your own data, the more you appreciate what HubSpot makes ordinary. People have jumped out of chairs watching it.

Why it matters: The scope notes tell you where this is going: available now for custom objects and tickets, coming for companies and deals as the integration moves to the upgraded version, with contacts later this year. Casey named the deeper reason she loves updates like this one: they are a peek behind the curtain, and for anyone who builds workarounds for a living, knowing what is coming changes decisions you make today. If you run a HubSpot and Salesforce stack, start planning the retirement party for your integration user.

For more details: Selective sync for Salesforce objects.

Price Books, From the Manufacturing Floor

Invited to pick from the list, Zach took Price Books for eight hundred dollars. Price Books give RevOps teams a centralized way to define, manage, and apply product pricing across deals and quotes, with this first private beta release focused on structured pricing setup and basic end-to-end use.

Zach brought the scar tissue. A B2B SaaS client once rebuilt their entire pricing structure to launch in India, where pricing had to reflect a different cost of living, and the implementation was held together with workarounds. Under Price Books, that becomes a condition: if country equals India, apply price book India. His manufacturing clients live the harder versions daily, volume pricing, annual spend tiers, negotiated rates, and the flexibility to encode those is the part he called huge. Chris painted the before picture everyone recognizes: the price list thumbtacked to the cubicle wall, the tribal knowledge that makes veteran quote processors fast and new hires untrainable, the fat-fingered price that nobody catches, and the version control problem where pricing updates ship but half the team still quotes from the old printout on their desktop. That mess is one of the hardest-to-debate reasons teams refuse to quote in HubSpot at all.

The governance read rounded it out: loose price lists leak outside organizations, and the better model is one or two people controlling products and pricing while everyone else consumes it, with quote and deal approvals handling the exceptions. One real limitation to plan around: single currency accounts only in this release, so no quoting in dollars and rupees yet. And no, per the show's official ruling, nobody is advocating for Bitcoin acceptance. Yet.

For more details: Price Books private beta.

The Rapid-Fire Customer Agent Roundup

Zach flagged a few more from the pile worth knowing about. The new Customer Agent status property adds statuses representing exactly where a ticket stands in the agent-to-human handoff process, paired with default view updates in help desk. The segments release, letting one agent serve different audiences with different knowledge, got a pretty cool from the room. And the multi-brand support hit closest to home for Zach, who is working with more and more clients running four or five brands in a single HubSpot portal, for whom a brand-aware Customer Agent is a real decision factor.

Will It Breeze: The Image Chris Could Not Recreate

The segment formerly known as Will It Workflow is officially mid-transformation into Will It Breeze, news delivered alongside reports that Chris has put restrictions on wheel spins and that scolding messages have been received and cheerfully ignored. The reason for the change is the same one driving every show lately: Breeze Assistant is too interesting not to demo.

This week's mystery: before vacation, Casey ran a prompt asking Breeze for a visual based on what it knows, and got back a fully branded image. Chris has spent the week since running the same prompt and getting the portal-audit-style visual every single time. Casey pulled hers up live, and the AI lesson wrote itself: same prompt, different outputs, and the branded image only happened because enough brand settings existed for Breeze to draw on. The frame being right is the win; once you trust the context frame, you iterate toward the visual you actually wanted. The Breeze team already has the obvious feature request from all of this: let users share conversations with each other.

Chris then showed his current daily practice: pasting a product update into Breeze and asking what it thinks, in this case the payment links release, getting back a strategic take, and then asking for a visual to explain it to sales and finance teams specifically. Those audiences were chosen on purpose, because they are where adoption goes to die: sales gatekeeping prices, finance withholding payment link approval, the team spending hours quoting a five hundred dollar item while insisting they cannot try the new thing. Every HubSpot manager needs help communicating what HubSpot can be to each stakeholder type, and this is now a conversation you can have with the system itself, transcripts included. The first mermaid diagram came back unreadable, the fix was five words, can you make it vertical, and the corrected version rendered in under ten seconds, which Chris read as evidence that HubSpot is building skills into the assistant, diagram means mermaid, and here is how mermaid works.

Zach asked the question many people are wondering, whether Breeze improving at images is HubSpot inheriting upstream model gains, and the working theory on the show was probably, with the recent clarifying-questions upgrade reading like a reasoning step. His sharper observation was about speed: HubSpot has always had the context advantage, all the data connected in one place, but historically lagged the point-solution chat tools on responsiveness. It is a lot faster now, and faster plus more accurate is the adoption flywheel. Then he proved the point live, running the same tell-me-about-this-business prompt in his own portal mid-show and getting back ICP and market position, operational philosophy, a process map of how the portal appears to operate today, lead management, qualification, pipeline, and revenue process. His verdict: good stuff, and exactly the head start he wants when walking into a brand-new portal to map current state for a client.

Why it matters: Chris closed with his favorite moment of the week. On the way to producing a data model report, Breeze observed unprompted that this was not just a sales and CRM implementation of HubSpot, it was using everything. A month ago that recognition was impossible, and its absence was exactly why he could not trust the assistant. Now it can see the whole portal and think a little before answering. The homework has not changed: get in there, have the conversations, and let it learn your business while your team learns what it can do.

The Rest of the Pile

The show could not get to everything seventeen updates deep. Full breakdowns of the June 2 batch, including the Instagram API migration, smarter AEO prompt suggestions, help desk folders, and the workflow enrollment fix for merged records, are on the updates blog: HubSpot Updates: June 2, 2026.

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.