Updates blog — Tuesday, June 2, 2026

HubSpot Updates: June 2, 2026

Fourteen updates landed June 2, and the batch has a clear center of gravity: Customer Agent is learning to handle money. Payment links in conversation, invoice lookups, and handoff statuses all shipped together, alongside the Price Books private beta, a connected quote-to-cash experience, and a Salesforce sync release that retires one of the oldest workarounds in the integration playbook. There is also a quiet workflow fix in here that every data team will appreciate.

If you watched Wednesday's show, you already heard the conversation around the biggest of these. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Get Paid Through Customer Agent with Payment Links

Customer Agent can now send payment links directly inside a conversation. When a buyer signals they are ready to purchase, 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 decide which links the agent can send, which get actively offered, and which stay off limits, so the agent runs a meaningful slice of your go-to-market motion while keeping the guardrails. This is in private beta and free across all hubs and tiers.

Why it matters: The release note frames this around deals stalling to friction, but the sharper opportunity is post-sale, where you already know the person, their history, and their products, and picking the right link is easy. Think service teams selling consumables and replacement parts to existing customers: the five hundred dollar part someone needs today without the rigmarole of a quote cycle. Nobody is closing six-figure deals through a chat link, and teams with downstream ERP and billing constraints may not be able to use payment links at all, but for the right repeatable purchase, this closes the gap between answered question and completed sale. One open question worth feeding back to the beta team: customer-specific discount structures do not flow into payment links yet.

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

Find Invoices Action in Customer Agent

Customer Agent can now find and send invoices directly inside a conversation. When a customer asks about a past or upcoming invoice, the agent queries the right invoice, explains what is on it, and sends a copy along with its secure checkout in the same chat, email, or WhatsApp thread. This is in private beta and free across all hubs and tiers, with the obvious prerequisite that the invoices live in HubSpot.

Why it matters: Invoice lookup and explanation are two of the most common requests billing teams handle, and every one of them is triage work a human does not need to do. The identity layer is the hinge, since the agent recognizes logged-in or known visitors and can ask for an email address otherwise, after which it can pull that contact's related records into the conversation. The pitch worth making internally: show this to an accounting team focused on collections, framed as incremental improvement. An invoice paid or accessed through the agent is a concrete outcome metric, which is rarer in AI rollouts than it should be.

For more details: Find invoices action in Customer Agent private beta.

Selective Sync for Salesforce Objects

You can now set filters that control which Salesforce objects sync with HubSpot, working like inclusion lists but applied to the Salesforce side. Set your filters, and Salesforce objects that match will sync while everything else gets skipped, giving you the control on the Salesforce side that you have always had on the HubSpot side. This is in public beta for Professional and Enterprise tiers across Content, Marketing, Sales, Service, and Smart CRM, available now for custom objects and tickets, with companies and deals coming as the integration upgrades and contacts later this year.

Why it matters: The sentence in the release note worth reading twice: customers no longer strictly need to set up integration users in Salesforce to control what data is shared. That dedicated integration user, existing purely so its permissions could act as a sync filter, was the workaround, and it was tech debt in its purest form. Native filters mean cleaner control, less Salesforce admin overhead, and one less fragile dependency in the stack. The phased object rollout is also a useful peek behind the curtain: if you run a HubSpot and Salesforce stack, you can plan the integration user's retirement now instead of discovering the option later.

For more details: Selective sync for Salesforce objects public beta.

Price Books

Price Books give RevOps teams a centralized way to define, manage, and apply product pricing across deals and quotes, with this first release focused on structured pricing setup and basic end-to-end usage. Set named pricing sets against your product catalog, then apply them with conditions, so country equals India can mean apply price book India automatically. This is in private beta for Commerce Hub Professional and Enterprise, and supports single currency accounts only in this release.

Why it matters: As pricing grows more complex across segments, geographies, and deal types, the current state at most companies is a spreadsheet, a printout thumbtacked to a cubicle wall, and tribal knowledge that makes veterans fast and new hires untrainable. That mess is one of the hardest-to-debate reasons teams refuse to quote in HubSpot at all. Price Books move pricing under governance: one or two owners set it, everyone else consumes it, and exceptions route through quote and deal approvals. Volume tiers, negotiated rates, and market-specific pricing all become conditions instead of folklore. The single-currency limitation is the one to plan around if you sell internationally.

For more details: Price Books private beta.

Connected CPQ, Billing, and Payments

A new connected quote-to-cash experience ties CPQ, billing, and payments into one end-to-end revenue lifecycle: fewer billing schedule restrictions, automated operational tasks, and buyers guided to set up payment directly upon quote acceptance. This is in private beta for Commerce Hub Professional and Enterprise.

Why it matters: The space between quote accepted and cash collected is where revenue operations does its least glamorous and most expensive work: manual billing setup, chased payments, hand-built financial documentation. Connecting the pieces shortens collection cycles and makes revenue more predictable, and paired with Price Books in the same release batch, it sketches HubSpot's ambition plainly: the whole quote-to-cash motion living in one system. If Commerce Hub has felt like a collection of parts, this beta is the connective tissue to watch.

For more details: Connected CPQ, billing, and payments private beta.

Workflow Enrollments Preserve Objects When Merging

When you merge two records, the record you keep now stays enrolled in its active workflows instead of being unenrolled alongside its duplicate. Only the record being merged away gets unenrolled. This is in private beta for Marketing Hub, Sales Hub, and Service Hub Professional and Enterprise.

Why it matters: This fixes one of the nastiest silent side effects in HubSpot: cleaning up duplicates used to quietly pull contacts out of in-flight nurtures, onboarding sequences, and renewal workflows, which meant data hygiene and automation were actively working against each other. You should never have to choose between fixing your data and keeping your automation running, and now you do not. Paired with the custom duplicate rules and merge preview from last week, the whole merge experience just became something admins can run confidently at scale.

For more details: Workflow enrollments preserved when merging private beta.

Instagram API Requirements Now Reflected in Social Tool

HubSpot's Social tool has been updated to reflect Instagram's latest publishing requirements for video, images, and captions, so the limits enforced when you build a post now mirror what Instagram's API actually accepts. This is live for Marketing Hub Professional and Enterprise.

Why it matters: A post that fails after you hit publish is the worst kind of failure, since you find out late and the fix means rebuilding. Matching Instagram's real limits in the composer means fewer failed posts and problems flagged before publish instead of after. Unglamorous, and exactly the kind of reliability work social teams feel every week.

For more details: Instagram API requirements in the Social tool.

Content Recommendations for Emails

Content recommendations analyzes your past email sends and peer benchmarks, then surfaces tactical, ready-to-implement suggestions for improving email performance. This is in private beta for Marketing Hub Professional and Enterprise.

Why it matters: Email best practices have a way of living in one person's head and leaving when they do. A system that reviews what worked in your own sends, not generic industry advice, and hands back specific actions keeps that institutional knowledge in the tool where it belongs. The peer benchmark layer is the interesting part to watch: knowing what worked for you is good, knowing how that compares is better.

For more details: Content recommendations for emails private beta.

Smarter Prompt Suggestions for HubSpot AEO

Prompt Suggestions recommend the best prompts to track in the AEO tool by studying what people search about your category, products, and ideal customers, then suggesting prompts you are not yet tracking, each backed by real search volume data. This is in private beta for Marketing Hub Professional and Enterprise customers with HubSpot AEO.

Why it matters: AEO already tracks how your brand shows up in answer engines. The new piece is making sure you are tracking the right questions, because a Brand Visibility score built on prompts nobody actually asks is a vanity metric. Suggestions grounded in search volume turn prompt selection from guesswork into coverage analysis, which is the difference between an AEO score you report and one you act on.

For more details: Smarter prompt suggestions for HubSpot AEO private beta.

Omnichannel Waitlist

Omnichannel Waitlist automatically holds and prioritizes tickets when your team is at capacity, then assigns them the moment agents free up. Instead of new tickets landing in Unassigned, help desk places them in a dedicated Waitlist view where they are ordered, monitored, and automatically assigned by priority and availability. This is in private beta for Service Hub Professional and Enterprise.

Why it matters: Unassigned is where response times go to die, because it depends on someone noticing. A waitlist that holds order, respects priority, and assigns automatically means peak-hour spikes degrade gracefully instead of chaotically, and your SLA risk becomes visible in one view instead of scattered across an unowned queue. For support leaders, this is the difference between managing capacity and hoping about it.

For more details: Omnichannel Waitlist private beta.

Introducing Folders for Help Desk Views

Folders bring structure to the help desk sidebar, letting teams group related views into named folders instead of one long scroll. This is in public beta for Service Hub Professional and Enterprise, with a Service Seat required.

Why it matters: View sprawl is the natural consequence of a team using help desk well, and the cost shows up at the worst time: hunting for the right view mid-rush. Folders are simple organizational hygiene, and the busiest desks will feel the difference fastest. Worth pairing with a quick audit of which views your team has stopped using.

For more details: Folders for help desk views public beta.

Customer Agent Status Property and Default View Updates in Help Desk

New structured statuses represent exactly where a ticket stands in the Customer Agent to human handoff: Pending while the agent is actively handling, Escalated when handoff has triggered but no human is assigned, Handed Off once a rep owns it, and None when the agent is not involved. The updated default view shows all agent-involved tickets, open or closed, sorted by urgency. This is in private beta for Service Hub Professional and Enterprise.

Why it matters: The old status values were limited and unclear, and a ticket somewhere between agent and human is a ticket nobody owns. Escalated is the status that earns its keep, since handoff-triggered-but-unassigned is precisely the state where customers fall through cracks. Together with last week's handoff summaries, the agent-to-human boundary is becoming reportable, routable, and accountable.

For more details: Customer Agent status property and help desk view updates private beta.

Default Brand Selection at Login

If you manage multiple brands in HubSpot, you can now set a default brand to land in automatically at every login, instead of manually switching to your preferred brand each time. This is live for Marketing Hub Enterprise customers with the Brands Add-on.

Why it matters: For anyone living primarily in one brand of a multi-brand portal, this deletes a small daily chore. It also signals continued investment in multi-brand operations, which matters more every quarter as more teams consolidate four or five brands into a single portal.

For more details: Default brand selection at login.

Personalization Token Support in Rules-Based Chatflow Welcome Messages

You can now customize a live chat bot's welcome message with CRM data, inserting personalization tokens like first name, company name, or recent activity directly into the greeting. When a visitor is recognized via tracking cookies, the token renders with their information automatically. This is in public beta for Marketing Hub and Service Hub Professional and Enterprise.

Why it matters: First impressions shape the whole conversation, and a generic "hi there" ignores everything you already know about a returning visitor. A welcome that reflects who they are makes the experience feel intentional from the first message, and it costs nothing but a token to configure.

For more details: Personalization tokens in chatflow welcome messages public beta.

Key Takeaways and Next Steps

Customer Agent is becoming a revenue surface: Payment links, invoice lookup, and explicit handoff statuses shipped in one batch, and notably, the two money features are free across every hub and tier. That moves Customer Agent from answering questions to completing transactions, and the right first lane is post-sale and repeatable purchases, where identity and history already exist. Start the conversation with your accounting and service teams now, framed around incremental wins, not a storefront replacement.

Quote-to-cash is becoming one motion: Price Books and the Connected CPQ, Billing, and Payments beta landed together, and together they read as a statement of intent: pricing governed in the system, billing automated from quote acceptance, cash collected without manual chase. Commerce Hub teams should evaluate these as a pair, not as separate features.

The data quality loop closed quietly: Selective Salesforce sync ends the integration-user era, and workflow enrollment preservation removes the last reason to fear running merges. Combined with last week's custom duplicate rules and merge preview, dedup work no longer fights your automation. If your sync architecture leans on a dedicated Salesforce user, document what it controls today so the migration is a checklist instead of an archaeology project.

Help desk operations are maturing: A capacity-aware waitlist, sidebar folders, and handoff statuses are all answers to the same question: what happens to the desk when volume is high and attention is scarce? The common thread is removing the dependence on someone noticing. Support leaders should look at the waitlist beta first; it is the one with SLA numbers attached.