Updates blog — Monday, June 29, 2026

HubSpot Updates: June 29, 2026

Nine updates carry a June 29 release date, and they spread across the platform rather than clustering: cleaner email routing, a smarter Microsoft Teams integration, two notification improvements, sandbox parity for sequences, more flexible ticket messaging, the Claude connector reaching into quotes, an AI filing agent, and a higher approver limit for deals. The loose through-line is control, most of these hand an admin a sharper tool than the blunt one they had.

Today's show stayed on the June 30 releases, but the recap is worth a watch for where the platform is heading: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Respect Reply-To Header in Email and Help Desk

HubSpot now uses the Reply-To email header to decide the sender for contact creation and outbound replies in Help Desk and the Conversations Inbox, so replies reach the intended recipient and CRM records stay accurate. This is in public beta across all hubs and tiers.

Why it matters: Support teams often get email where the From address is not the real sender, which sends replies bouncing, creates the wrong contact records, and breaks conversation threads. Honoring Reply-To fixes a quiet source of bad data and, per the release note, unblocks Customer Agent adoption for thousands of portals by bringing HubSpot in line with how other tools already behave. If your inbound support runs through a forwarding address or a ticketing relay, this is the one to test first.

For more details: respect reply-to header in Email and Help Desk public beta.

Microsoft Teams Integration Updates

The Microsoft Teams integration picks up a batch of improvements to notifications, call logging, and setup. You can target workflow notifications to individual Teams users rather than only channels, trigger those notifications from any HubSpot object type, log multi-participant Teams calls in HubSpot, and upgrade from a user-level to an admin-level install for more stable, org-wide connectivity. This is live, with specific capabilities available across a range of Professional and Enterprise tiers.

Why it matters: Teams is where a lot of companies actually work, and until now the integration was thin on exactly the things that make an integration useful: precise routing, complete call records, and a clean install. Notifications to a person instead of a channel is the change most admins will feel first, because channel noise is why people mute notifications in the first place.

For more details: Microsoft Teams integration updates.

Improved CRM Notifications in Email

Notification emails now carry the full contents of a notification, so you can get caught up without leaving your inbox. The format covers six types: mentioned on a record, assigned a record, and stage, status, activity, or association updates on a record you follow. When you do want to dig in, a clear button and a clickable card take you straight to the record. This is in private beta for all hubs and tiers.

Why it matters: A notification email used to tell you something happened without telling you enough to decide whether to act, which meant clicking through to HubSpot for context every time. Putting the full notification in the email lets you catch up from email alone on the road and reply to mentions without leaving it. Read alongside the wider push to meet people where they work, it is HubSpot accepting that not everyone needs to live inside the product all day.

For more details: improved CRM notifications in email private beta. Full background is in our earlier coverage of improved CRM notifications in email.

Notifications That Take You to the Right Record Across All CRM Objects

Improved mention notifications now link directly to the exact record where the mention happened, and notification support is expanding to more object types, including appointments, carts, contracts, courses, listings, marketing events, orders, services, and subscriptions, which now support mention, follow, and assigned notifications. This is in private beta for all hubs and tiers.

Why it matters: When someone mentions you, you expect the notification to drop you into that conversation, not a different associated record that costs you extra clicks to escape. Routing straight to the record where the mention occurred keeps you in flow, and extending notifications to the newer object types means the parts of your data model built on those objects stop being second-class for collaboration.

For more details: notifications that take you to the right record across all CRM objects private beta. This one has an earlier home in our earlier coverage of notifications across CRM objects.

Sandbox Support for Copying Sequences

When you create a sandbox, sequences now copy over from your production portal, so you can build, test, and refine outreach flows without confusing the reps working in production. This is in public beta across Smart CRM, Marketing Hub, Sales Hub, Service Hub, Content Hub, Data Hub, and Revenue Hub.

Why it matters: Sequences are core to how sales and service teams run one-to-one outreach, and until now any new or tweaked sequence had to be tested live in production with no safe environment to confirm it. This is one more piece of the steady, worthwhile project of bringing sandboxes to parity with production. If you test in sandboxes, it is worth keeping a running sense of what copies over now versus what does not, because the answer keeps changing.

For more details: sandbox support for copying sequences public beta.

Create Your Own Ticket Automation Messages

You can now build additional ticket automation messages for ticket-based workflows, beyond the default Ticket Received and Ticket Closed messages HubSpot provides. These can go to any recipient, including non-marketing contacts and contacts not subscribed to any marketing list. This is in public beta for Service Hub Professional and Enterprise, included with the subscription.

Why it matters: Two stock messages were never enough for real support operations. This opens up alternate versions per workflow branch, messages for statuses like Waiting on Customer, and messages in other languages, all without burning marketing sends or fighting subscription status. If your team has been building workarounds to message ticket contacts mid-lifecycle, this is the cleanup release.

For more details: create your own ticket automation messages public beta. It first appeared in our earlier coverage of custom ticket automation messages.

Create Quotes and Analyze Revenue via the Claude Connector

The HubSpot connector for Claude can now create and manage quotes and quote templates through a revenue-aware tool. It builds quotes, pulls line items from your deal, applies your branded templates, and follows your product rules, approval rules, and permissions, and Claude gains read access to core revenue objects so you can analyze revenue data in the same conversation. This is in private beta for Revenue Hub Professional and Enterprise, turned on by reconnecting your HubSpot account and enabling the revenue objects tool in the connector settings.

Why it matters: The earlier version produced a basic quote with none of the CPQ logic, approval flows, or branding that makes a quote sendable, and it asked for details already set automatically. This version validates against CPQ rules and handles recall, line-item edits, and publish as single steps. The capability is real; the harder part is trust, because a lot happens behind the scenes, and the work is putting both your people and your AI in a position to succeed before you ask a team to quote this way.

For more details: create quotes and analyze revenue via the Claude connector private beta. We dug into this one on air when it launched: our earlier coverage of the Claude connector for quotes and revenue.

AI-Powered Filing Agent for Workflows

An AI-powered filing agent 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 is in 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. Handing the analysis to an agent 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.

For more details: AI-powered filing agent for workflows public beta. The earlier stage of this one is in our earlier coverage of the AI filing agent for workflows.

Deal Approvals: Increased Approver Limit

You can now add up to ten approvers to a deal pipeline approval process, up from the previous limit of three. This is live for Sales Hub Enterprise.

Why it matters: When an approval process spans legal, finance, management, and sales leadership, a cap of three forces you to consolidate approval responsibility onto fewer people, which creates bottlenecks the moment someone is out of office. Ten approvers per pipeline lets the flow reflect how your team actually signs off, which is the point of building the approval in the first place.

For more details: deal approvals increased approver limit.

Key Takeaways and Next Steps

Notifications are getting a real overhaul: Three of these touch how HubSpot tells you something happened, from full-content emails to mention routing that lands on the right record. If your team has quietly tuned out HubSpot notifications, this is the moment to turn a few back on and see whether they are worth paying attention to again.

Support and inbox accuracy is the quiet theme: The Reply-To fix and the custom ticket messages both sharpen how support communication actually reaches people. For any team running Help Desk or a shared inbox, the Reply-To change is worth confirming early, because it affects data accuracy, not just convenience.

The AI surface keeps widening, tier by tier: The Claude connector reaching into quotes and the filing agent cleaning up workflows are both about pushing AI into work admins already own. Both sit behind higher tiers, so the practical step is knowing which of these your subscription actually includes before you plan around them.