Updates blog — Wednesday, May 13, 2026

HubSpot Updates: May 13, 2026

Four updates landed Tuesday and two of them point at the same shift. Both the Marketing Research Agent and Breeze Assistant's new access to campaign data move the conversational layer deeper into the work surfaces marketers and revenue teams already live in. The other two are smaller in scope but worth flagging: a notifications preferences refresh that lands in private beta across every hub and tier, and a quietly useful Help Desk admin update that finally lets nested teams be selected for default email addresses.

If you watched the show today, you already heard the conversation around two of these and a surprise drop-in from the Marketing Research Agent product manager. If you did not, watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Breeze Assistant Can Now Access Campaign Data

Breeze Assistant now answers questions about your campaign's goals, performance metrics, assets, and budget directly within Breeze. The previous workflow involved tabbing between multiple reports and asset views to piece together what a campaign was doing. Now those answers live in one conversation. This is live for Marketing Hub Professional and Enterprise.

Why it matters: Campaigns are not just email blasts anymore. With 28 different asset types associated to a campaign across every hub, Marketing Studio has become closer to a communication strategy canvas than a campaign builder. Bringing Breeze access into the campaign surface lines up with that shift. The bigger signal is the consolidation of conversational entry points across HubSpot. Anywhere you see the Breeze sparkle, you can now ask questions about what is in front of you. The platform is being designed for people who ask questions out loud rather than people who navigate through dashboards.

For more details: Breeze Assistant campaign data access

Marketing Research Agent

The Marketing Research Agent is an experimental agent that analyzes all your marketing reporting data and surfaces recommendations you can act on directly, with task creation as the output. It runs reporting under the hood, reads through the data, and infers next-best actions. Prebuilt prompts include automated email optimization and AEO citation rate improvement, but the agent can reason across any reporting surface, not just marketing-specific ones. This is in private beta for Marketing Hub Professional and Enterprise, with mandatory enrollment calls before access is granted.

Why it matters: Two things are worth flagging. The first is the gating mechanism. Requiring a conversation before granting beta access is the kind of structural choice that produces better feedback loops than a self-serve toggle. It is also a signal that the team building this is actively trying to learn from how it gets used in real portals. The second is the agent's reasoning model. It intrinsically understands the relationships between assets, so if a landing page is linked in an email, the agent treats those two things as connected when it proposes the next action. That asset-aware context is what separates this from “run a report and look at the numbers” tools. The honest take: this is the version of marketing AI that actually has the right inputs to be useful, but only for teams whose data model already supports the questions the agent will ask.

For more details: Marketing Research Agent private beta

Notifications Preferences Page Improvements

The notifications preferences page has been redesigned to reduce noise and give users more control. The new interface surfaces high-volume notifications at a glance, consolidates all channels in one view, and lets you turn entire channels on or off with a single click. A status filter shows exactly what is on and what is off. This is in private beta across all hubs and tiers.

Why it matters: Notifications creep is one of those slow problems that nobody flags as urgent until it is unbearable. The previous page made it hard to see what was actually firing versus what was technically enabled but quiet, which led to a lot of admins disabling everything as a blunt instrument. A status filter and a per-channel kill switch are small in isolation and meaningful for anyone whose Slack or inbox has been getting hammered by HubSpot pings they did not ask for. This is the kind of small efficiency that adds up across a portal's user base.

For more details: Notifications preferences page improvements private beta

Nested Teams Selectable for Default Team Email in Help Desk

Admins can now select nested teams, not just top-level parent teams, when setting a default team email address in Help Desk. Previously, default email assignments were locked to top-level teams, which forced organizations with nested team structures into workarounds. This is available for Service Hub Professional and Enterprise.

Why it matters: This is the kind of update that does not make headlines but quietly removes a real source of confusion for organizations with layered team structures. When a regional support team needs its own default email but lives under a broader Support parent team, the previous limitation forced either an inaccurate assignment or a workaround through routing rules. Letting the nested team own the default email keeps responsibility where it actually belongs and reduces the chance of agents and customers ending up confused about which inbox a message landed in.

For more details: Nested teams selectable for default team email in Help Desk

Key Takeaways and Next Steps

The conversational layer keeps moving deeper into the platform: The Marketing Research Agent and Breeze Assistant's campaign access both point to the same shift. Anywhere there is a work surface, HubSpot is making it possible to ask questions about that surface in natural language instead of navigating to a report. The implication for portal admins: the value of the conversational layer scales with the quality of the data model behind it. The agents and assistants are only as useful as the data they can reason across.

Beta gating is becoming a signal: The Marketing Research Agent requires a call before access. This kind of forcing function is showing up more often in HubSpot betas and it is worth paying attention to. When a team is willing to slow down enrollment to talk to every user, the feature is usually one they expect to evolve quickly based on what they learn. If a beta lands in your hub and the access path requires a conversation, that is a feature worth getting into early.

Small admin updates are still worth tracking: The nested teams update in Help Desk is the kind of fix that does not make a roadmap announcement but materially improves how a Service Hub portal can be structured. The accumulation of these small clarifications is what makes a platform actually usable at scale.