Updates blog — Wednesday, June 10, 2026

HubSpot Updates: June 10, 2026

After a quiet Monday, Tuesday brought a full page. Nine updates worth covering, spanning two updates carrying the major-update tag, a run of AI testing and reporting improvements, and a couple of sandbox refinements for Enterprise admins. The throughline, if there is one, is HubSpot working on how people find and trust what the platform already does: a navigation rebuild, better reporting flexibility, and more ways to test AI before you turn it loose.

If you watched the show Thursday, 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

Personalized Navigation

The left navigation is getting personal. Users will get a shortened navigation tailored to their own use cases, with the ability to customize it by adding groupings, reordering items, and adding or removing what they see. CRM objects can sit at the top level, with everything else tucked under a More section you control. This is tagged as a major update and is in development, so treat it as a forward-looking statement rather than a promise, though screenshots are already circulating. It is slated for nearly every hub and tier, from Starter through Enterprise.

Why it matters: The current navigation runs past eighty items, and that is too much for someone who uses five to ten tools on a regular basis. Reducing that to what a given person actually touches is the right call for the majority of users, even if it adds a wrinkle for consultants and admins who bounce between portals and prefer a consistent layout. Two things worth saying out loud: customization per portal means power users will be setting this up more than once, and the search bar is about to become the most reliable way to find anything that is not pinned. This is built for the people who do not live in HubSpot all day, which is most people.

For more details: Personalized navigation in development.

Dashboard PDF Exports Look like Dashboards

Dashboard PDF exports now keep the full dashboard layout, with charts and tables rendered the way they appear on screen, plus titles, dates, and filter context. Scheduled report exports sent by email use the same improved format. This is in public beta across all hubs and tiers.

Why it matters: A PDF that drops the layout drops the context, and context is most of what a dashboard communicates. Matching the on-screen view means the version you hand to a stakeholder looks like the thing you actually built, which cuts down on the explaining you have to do after the fact. The title says exactly what it does, and sometimes that is the whole review.

For more details: Dashboard PDF exports look like dashboards public beta.

Predicted Email Engagement in Segments

You can now see how a segment of contacts is predicted to perform in an email, based on the historical engagement of those contacts. The prediction surfaces as a high, medium, low, or unknown rating, alongside average open and click-through rates for the segment, so you can gauge segment-level performance before you send. This is live across all hubs and tiers.

Why it matters: Email performance is driven by your audience as much as your content, and most teams have been guessing at that or rebuilding past-results reports by hand. A prediction up front helps you put effort where it is likely to land. The caution worth carrying into this one is what engagement actually measures. A high rating reflects open and click history, not whether the message resonated, and a highly engaged audience is not an invitation to email them more. Sometimes the cadence you have is exactly why they are engaged. Use it to focus, not to justify more sends.

For more details: Predicted email engagement in segments.

WhatsApp Home

WhatsApp gets its own dedicated home in HubSpot, sitting alongside the other primary messaging channels. The update brings a WhatsApp messaging management page, a template management experience that pulls Meta templates from your connected WhatsApp Business account, a reporting suite, and a set of day-to-day enhancements. This is tagged as a major update and is live for Service Hub and Marketing Hub Professional and Enterprise.

Why it matters: Giving WhatsApp a first-class home, with templates and reporting that match the rest of HubSpot's messaging tools, is a clear signal that HubSpot is taking global communication channels seriously. For teams in regions where WhatsApp is the primary way customers reach out, this turns a bolt-on integration into a real part of the platform. The Meta template sync is the detail to watch, since it ties your HubSpot messaging to the connected business account.

For more details: WhatsApp Home.

Customer Agent Test as a Contact

Customer Agent testing has had a gap: every test session started as a brand new anonymous visitor, so the agent had no idea who it was talking to. Test as a Contact lets you run a test as a specific customer with real CRM properties and context, so you can confirm how the agent handles lead qualification, audience segments, and other behaviors that depend on knowing the person. You can pick a real contact or set properties manually to simulate any scenario, and test sessions stay clean rather than leaving sample contacts behind. This is in development, expected around June 21, across a broad set of tiers.

Why it matters: Most real customers are not anonymous. They have history and properties that shape what a good answer looks like, and testing against a stranger every time hid the issues that only appear when the agent knows who it is talking to. Closing that gap makes testing trustworthy, and there is a quieter benefit here too: this is a way to learn how the agent behaves, and where your data is weak, without spending credits to find out. That makes Customer Agent a reasonable on-ramp for getting comfortable with AI across your portal.

For more details: Customer Agent test as a contact in development.

Flexible Stages for Journey and Funnel Reports

The journey report builder now supports property-based stage definitions and flexible stage ordering. You can define stages using object properties alone, without requiring a stage-change event, count records that hit stages in any order including skipped stages and backward progression, and count stages separately to see how many records reached a given stage overall during the reporting period. This is in private beta for Sales Hub and Marketing Hub Professional and Enterprise.

Why it matters: Deals and contacts do not move through perfect sequential paths. They skip stages, jump straight to late ones, or get imported with no history of how they progressed. The old reporting either excluded those records or pushed teams to backfill stages with workflows, making up data so the funnel would add up, which then breaks any honest read on time-in-stage or velocity. Defining stages by property and allowing nonlinear movement lets a funnel reflect how the pipeline actually works instead of how a tidy diagram says it should. For anyone who has had the "is it okay if we skip stages" conversation, this is the update to point to.

For more details: Flexible stages for journey and funnel reports private beta.

Updated SDKs for Date-Based Versioning

HubSpot's SDK releases now support date-based API versioning, the new format introduced across HubSpot's APIs. Generated from a single centrally managed API specification, the SDKs cover more endpoints across more languages and release faster, with support for PHP, Java, Ruby, Go, TypeScript, and Python. This is live across all hubs and tiers.

Why it matters: Gaps in SDK endpoint coverage used to mean working around missing methods or dropping to raw HTTP calls where a typed client would have been cleaner. Generating from one managed spec closes most of those gaps and keeps the SDKs in sync with the APIs as they change, which means less documentation drift and fewer surprise breaks for anyone building on HubSpot. Narrow audience, real relief for the developers in it.

For more details: Updated SDKs for date-based versioning.

Playbooks Now Supported in Sandboxes

When you create a new sandbox, playbooks from your production portal now copy over automatically, including their content and recommendation settings. This has moved into public beta. Sandboxes are available across Enterprise tiers, and playbooks themselves require Sales Hub or Service Hub Professional or Enterprise with a seat assignment.

Why it matters: Playbooks shape live sales and service conversations, so changing them blind in production has always carried risk. Carrying playbooks into the sandbox lets teams test configurations before they go live and catch problems early. This is part of a steady run of sandbox work that keeps closing the gap between a test environment and a real mirror of production.

For more details: Playbooks now supported in sandboxes public beta.

Sandbox Support for Multi-Brand Assets

When you create a sandbox, HubSpot now copies assets assigned to all of your brands, not just your default brand. Previously, workflows, emails, and forms tied to non-default brands were missing from the sandbox. This is in public beta across Enterprise tiers.

Why it matters: For teams running multiple brands, a sandbox that only carried default-brand assets was not a true copy of production, which made it hard to test anything touching the full environment. Pulling all brands across makes the sandbox reflect what you actually run. Niche, but for multi-brand Enterprise teams it is the difference between a partial test and a real one.

For more details: Sandbox support for multi-brand assets public beta.

Key Takeaways and Next Steps

HubSpot is working on findability, not just features: Personalized navigation and the dashboard PDF fix are both about reducing the friction between a person and the thing they are looking for. With navigation getting customizable, lean on the search bar and decide which groupings to standardize for your team before everyone builds their own.

Testing AI is getting cheaper and safer: Customer Agent Test as a Contact lets you see how an agent behaves against real CRM context without spending credits. That makes it a low-risk way to learn where your data is strong and where it is not, which is usually the real blocker to deploying AI with confidence.

Reporting is bending toward how work actually happens: Flexible stages for journey and funnel reports is the standout for RevOps. It removes the pressure to fake sequential movement just to make a funnel report, which means cleaner data and more honest velocity numbers. If you have backfill workflows built purely to satisfy old reporting, this is your reason to revisit them.

Sandbox keeps becoming a real mirror of production: Playbooks and multi-brand assets are two more pieces filling in. For Enterprise teams doing serious testing, the gap between sandbox and production is steadily closing.