Updates blog — Thursday, June 25, 2026

HubSpot Updates: June 25, 2026

Ten updates posted on June 25, and a few of them are graduations more than debuts: features that moved from private to public beta, or got a round of refinement. Live chat picked up two changes, service routing got more deliberate, and a couple of releases are about seeing cross-object context without leaving the page you are already on.

If you watched the show today, you already heard the conversation around several of these. If you did not: watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Inline Association Table

The inline association table lets you see and act on associated record data directly from any CRM index page, without clicking into individual records or building a workaround. You can also apply quick filters inside the table to narrow the associated records on the fly. It is in public beta across all hubs and tiers.

Why it matters: The questions that used to require a detour now answer themselves on the page you already live in: which contacts have a deal closing next month, which companies have an open ticket. One clarification worth keeping straight is that this surfaces and filters the associated records, not the index itself, so it is not yet a way to filter your index by association. The quieter benefit is that when this data is visible to you on a single surface, it tends to be visible to Breeze Assistant too. For an earlier look at this one, see our June 25 recap.

For more details: the inline association table public beta.

Personalized Product Updates

The product updates page has been redesigned to highlight what is most relevant to your team, with a personalized For You view, simplified navigation, and search from every tab. The page has been in private beta for a while; what is new in this release is the ability to customize the order of sections in the For You view and a new Save tab where starred updates collect, with notifications as their status changes. It is rolling out in private beta across all hubs and tiers.

Why it matters: When every update looks the same, the changes that actually affect your portal get lost in the noise. A page that learns what your team uses and lets you save the rest for later is a small efficiency that compounds across a year of releases. The reorder and save additions are the kind of refinement that turns a feed you skim into one you work from.

For more details: the personalized product updates page private beta.

Track Key Stakeholders and Stated Pain Points with New Intent Signals

Two new unstructured engagement intent signals are now live. Key Stakeholder Identified fires when a decision maker, champion, economic buyer, or influencer is recognized in a conversation, and Pain Point Mention fires when a contact explicitly shares a business challenge. These are company-level insights pulled directly from deal-associated engagements such as emails, notes, and call transcripts, and they capture buying roles as distinct, filterable properties rather than a comma-separated list. The signals are eligible across workflows, scoring, and list segmentation. This runs on HubSpot credits, and the portal must meet the standard deal dependency criteria first: at least one monitored company in intent signals or an active prospecting agent play, with engagements tied to a deal that is tied to a company.

Why it matters: Intent data is not new. What is changing is how close the signal sits to the person who can act on it, and how much context arrives without anyone combing through a thread. The honest caveat is that this is only as good as the conversations you actually keep in HubSpot. Emails alone will fire signals, but the fuller picture depends on call transcripts being in the platform, which is still a gap in plenty of portals.

For more details: intent signals for key stakeholders and pain points.

AI-powered Filing Assistant for Workflows

An AI-powered filing assistant in account cleanup analyzes your unfiled workflows, reads their names and descriptions, groups them into suggested folders, and lets you review, adjust, and apply the changes in a few clicks. This one was in private beta earlier in June and has now moved to public beta across the Enterprise tiers.

Why it matters: Every mature portal carries a backlog of unfiled workflows that is easy to ignore and tedious to fix by hand, so it compounds. Having AI do the analysis and propose the structure turns an afternoon of sorting into a few minutes of review. It is also part of a pattern worth watching: account cleanup keeps absorbing the governance work admins know they should do and rarely get to. The move to public beta means you no longer need to wait for enrollment approval to try it.

For more details: the AI-powered filing assistant for workflows public beta.

Site Visitors Can Now Resize the Live Chat Widget

Visitors can now resize the live chat widget to fit what they are doing. They can drag the edges to any size or use quick-toggle buttons in the header to switch between compact and expanded views, and the widget remembers each visitor's preferred size for the next visit. It is in public beta across all hubs and tiers.

Why it matters: Rich responses like detailed AI answers, source citations, meeting links, and embedded content get cramped in a small window, and constant scrolling is how people disengage. Handing size control to the visitor is a small comfort change that keeps them reading rather than giving up halfway through an answer.

For more details: resize the live chat widget public beta.

Allow Visitors to Leave Live Chat Messages When Your Team Is Unavailable

Your live chat chatflow can now capture visitor messages when your team is away, at capacity, or outside business hours. When enabled, visitors can reach out at any time, and reps can view and respond from the inbox or help desk once they are back. This has moved from private to public beta, available across all hubs and tiers.

Why it matters: Plenty of teams treat live chat as an async channel, not a strictly real-time one, and a chat input that locks after hours throws those conversations away. Giving admins control over when visitors can still reach out restores a behavior teams had built processes around. The setting is a choice, not a default, so decide deliberately. If your team can keep up with overnight messages, turn it on and route them; if response expectations would suffer, point the off-hours experience to another channel. For prior context, see our June 23 recap.

For more details: leave live chat messages when your team is unavailable public beta.

FileUpload and FileViewer for UI Extensions

FileUpload and FileViewer are new UI extension components that let developers add file upload and display to app cards. Files are stored in a per-app folder in HubSpot's file manager, and uploaded files can optionally be attached to CRM records. This is in public beta across all hubs and tiers.

Why it matters: Until now there was no native way to handle files inside a UI extension, which forced workarounds or pushed file interactions out of HubSpot entirely. For teams building app cards, this keeps file-dependent apps in context on the record, with real drag-and-drop upload and a proper viewer instead of the file-property approaches people improvised before. It is developer-facing, but the experiences it makes possible show up for everyday users on the record. For an earlier look, see our June 25 recap.

For more details: FileUpload and FileViewer for UI extensions public beta.

New Workflow Action: Rotate Record by Skill

Rotate Record by Skill is now available as a workflow action, letting you assign tickets to users based on their skills inside ticket-based workflows. It brings the same skill-based routing logic used in Help Desk routing rules into workflows, so assignment, automation, and decision-making can live in one place, and tickets can be re-enrolled into skill-based routing actions. It is in public beta for Service Hub Enterprise.

Why it matters: Skill-based assignment used to be locked to routing rules, separate from the rest of your business logic. Putting it inside workflows means a team can combine the routing decision with everything else a workflow already handles, which is where more flexible and scalable routing comes from. This is part of a steady move toward letting workflows own more of the assignment layer.

For more details: the Rotate Record by Skill workflow action public beta.

More Predictable Routing Between Customer Agent and Skill-Based Routing

Help Desk routing has been made clearer by introducing a single primary assignment method for each channel. Customer Agent and skill-based routing can still work together, but through explicit, intentional handoffs rather than overlapping behavior. It is live for Service Hub Enterprise.

Why it matters: Previously, when Customer Agent and skill-based routing were both enabled on a channel, the outcome depended on timing rather than intent, which led to tickets bouncing between agents, unexpected reassignments after a successful handoff, and tickets briefly showing as unassigned. Naming one primary method per channel removes that ambiguity. If you run both on the same channel, this is the kind of fix that quietly stops a category of confusing tickets.

For more details: more predictable routing between Customer Agent and skill-based routing.

See What's on the Sandboxes Roadmap

You can view the sandboxes roadmap, including upcoming betas and additional asset support, and share feedback on which asset types you would like to see supported next. The roadmap lives under Settings and then Sandboxes. This release is a set of clarifications to that live feature: clearer language on how feedback informs the roadmap, a better explanation of planning sandbox creation around upcoming asset support, and minor wording fixes. It is available across the Enterprise tiers.

Why it matters: Sandbox planning is a quiet pain point for anyone running a complex portal, and knowing what is and is not testable before you start a build saves the rebuild later. The feature itself is not new, but the clarifications make the roadmap easier to read and act on, and the feedback path is a real opening to tell the team which asset types matter most to your work.

For more details: see what is on the sandboxes roadmap.

Key Takeaways and Next Steps

The public beta wave is worth acting on: The filing assistant and the after-hours live chat messages both moved from private to public beta in this batch, which means no more waiting on enrollment approval to try them. If either was on your list, this is the week to turn it on in a test and see how it behaves before it becomes a default expectation.

Live chat is maturing as an async channel: Two of these updates, resizing the widget and capturing messages after hours, point in the same direction. HubSpot is treating live chat less as a strictly real-time tool and more as a flexible channel that respects how visitors and teams actually use it. If you run chat, both are small comfort changes that reduce the number of conversations you lose.

The platform keeps making cross-object context actionable: The inline association table and the new intent signals are different features with the same underlying idea: surface what is happening across related records where the person can act on it, rather than burying it a click or a thread away. The thing that makes either one pay off is the data behind it. Visible associations and in-platform conversations are what turn these from a nice demo into something your team uses every day.