Updates blog — Monday, June 8, 2026

HubSpot Updates: June 8, 2026

Ten updates landed Monday, and most of them are about the same thing: making the everyday CRM surface faster, where you actually work, click by click. There is also a meaningful Customer Agent expansion, a few admin and reporting wins, and one migration notice with a date attached that you will want on the calendar.

If you watched the show, you already heard us work through six of these, plus a first live look at the universal record page beta. If you did not: watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

In-Person Meeting Notetaker Update

Starting July 31, 2026, HubSpot is changing how recorded meetings get logged. Meetings recorded through Notetaker, Zoom, Google Meet, or Microsoft Teams will create a single Meeting record instead of both a Meeting record and a duplicate Call record, and new properties for transcript, transcript ID, and duration are moving onto the Meeting record directly. This is a public beta change that enrolls the entire account, for Sales Hub Professional and Enterprise.

Why it matters: The duplicate call record has been a quiet source of confusion in reporting and automation for anyone working with recorded meetings, so cleaning it up is the right call. The catch is that the cleanup can break things you already built. If you have workflows that trigger on call creation, properties that read from the call record, or dashboards that count calls for what were really meetings, audit those before July 31 rather than after. We talked through this one on the June 5 show; for the on-air discussion of what it means for call-based setups, see that recap: Another Orange Morning recap, June 5.

For more details: In-Person Meeting Notetaker iOS public beta update.

Streamlined Index Page and Updates to Board View

The CRM index page, the central home for contacts, companies, deals, and every other object, got a cleaner layout, a simpler toolbar, and an improved board view. The change you will notice first is edit columns, which now lives in a one-click button on a persistent right rail that stays visible as you scroll instead of hiding inside nested settings menus. This is in public beta across all hubs and tiers.

Why it matters: The index page is where most HubSpot work happens, so small reductions in friction add up fast across a team and a day. The edit columns move is the standout, and it reads like a direct response to how often people lost that control. One thing to flag for your team before they find it the hard way: the save action sits at the bottom of the panel now, which is easy to miss the first few times.

For more details: Streamlined Index Page and Board View public beta.

Property Context Menu on Records

You can now hover over any property on a record, click the three-dot icon, and reach a quick-action menu that copies the value, opens property history, or takes an action tied to the field, like calling a number, visiting a URL, or starting an email. This is in public beta across all hubs and tiers.

Why it matters: Copying a property value used to mean clicking into the field, highlighting, and copying. Collapsing that to one action is a real efficiency, and it matters more now that so much of the workday involves moving a value out of HubSpot and into an AI tool or a document. Two things to know going in: the email action opens your default mail app rather than a HubSpot email, and copy value only shows up when the field actually has a value, so grabbing an internal name from an empty property is not there yet.

For more details: Property Context Menu on Records public beta.

Updated Add to Dashboard Panel

The Add to Dashboard panel has a new layout that surfaces report recommendations at the top and organizes the rest of your report options more clearly. This is in public beta across all hubs and tiers.

Why it matters: Building a dashboard used to mean scrolling an undifferentiated list of reports trying to remember what each one was. Putting recommendations first and giving the rest some structure is a modest change that mostly helps newer admins and anyone who builds dashboards rarely enough to forget where things live. It belongs to the same theme as the index page work: less time navigating, more time on the data.

For more details: Updated Add to Dashboard panel public beta.

Customer Agent Now Responds to Forms

Customer Agent can now reply to inbound form submissions in Help Desk or Inbox workspaces by sending a response email to the person who submitted the form. You can scope when it runs, across all hours, specific hours, outside specific hours, or based on conversation coverage. This is in private beta for the Professional and Enterprise tiers across Content, Marketing, Data, Sales, Service, and Smart CRM hubs, and it consumes HubSpot credits.

Why it matters: Form submissions carry an expectation of a quick reply, and the gap between submission and first response is where tickets pile up. Letting Customer Agent cover that closes a real hole. The piece to plan around is cost. It runs on Customer Agent, so a response is in the range of a single conversation, and the charge is per conversation rather than per message, so a back and forth stays inside one cost. The open question worth watching is whether a one-time personalized confirmation should ever cost the same as a full conversation. For now, treat it as a credit decision, not a free add-on.

For more details: Customer Agent responds to Forms private beta.

Configure Audiences Customer Agent Responds to on Email

Coming soon and in development, admins will be able to define which contacts Customer Agent responds to on an email channel by selecting from existing HubSpot Lists. This is slated across hubs and tiers, including Starter, Professional, and Enterprise.

Why it matters: This is the update that makes the form-response feature above something you can scope rather than something you flip on for everyone. The smart way to adopt an agent on a credit budget is to point it at a narrow, high-volume, low-risk audience your frontline team can name, and keep the sensitive or high-touch contacts on a human. Doing that with existing lists means the control lives in segmentation you already maintain, which is one more reason to get your segments in order. It is not live yet, but it is the half of the story that controls cost and risk.

For more details: configure audiences Customer Agent responds to on email.

Date and Datetime Properties in Conditional Property Logic

Date and datetime properties can now serve as the controlling property in conditional property logic, so a date value can make a dependent property appear or become required. This is in public beta for the Professional and Enterprise tiers across Commerce, Content, Marketing, Data, Sales, and Service hubs, plus Smart CRM.

Why it matters: A lot of rep workflows are timing-driven, but properties had no native way to react to a date, which left people managing the timing by hand. Letting a record surface the right field at the right moment based on a date closes a gap that conditional logic should have covered all along. If date-based conditions have been a limitation in any of your property setups, this is the one to revisit.

For more details: date and datetime properties in conditional property logic public beta.

Control How Custom Events Appear on the Record Timeline

When you set up a custom event, you can now control how it shows on the activity timeline of linked records, including the header, the subheader, which properties appear, and the order they appear in. This is live for users with custom event edit access on the Professional and Enterprise tiers of Marketing, Sales, Service, Content, and Data hubs.

Why it matters: Custom events can capture anything from a video view to an abandoned cart, but a bare timeline card rarely tells the story on its own. Giving each event a clear header and the right properties means anyone reviewing a record can read what happened without digging into raw event data. It is a small lever with a real payoff for support and sales teams who live in the timeline.

For more details: control how custom events appear on the record timeline.

User Import Supports a Wider Range of Fields

User import now handles more than the basics, including teams, seats, managers, job titles, and custom user properties, so you can configure users in bulk instead of cleaning up by hand afterward. Core fields like name, job title, and manager are available on all accounts, team assignment and permission sets are Professional and above, and custom user properties are Enterprise only. This update is live. Worth noting that this is for importing HubSpot users, not contacts.

Why it matters: For admins onboarding a large or distributed team, the old import covered name and email and left teams, permissions, and custom properties as manual follow-up, which was slow and error-prone at scale. Handling the full user setup in a single import is squarely an admin quality-of-life win, and a welcome one for anyone who has built out a team the long way.

For more details: user import supports a wider range of fields.

Connected CPQ, Billing, and Payments

A new connected quote-to-cash experience ties CPQ, billing, and payments into one flow: fewer restrictions on billing schedules, automation of the operational work between quote acceptance and payment, and buyers guided to set up payment directly when they accept a quote. This is in private beta for Commerce Hub Professional and Enterprise, with seats required to participate.

Why it matters: The space between a signed quote and money in the bank is where revenue operations spends its least visible and most expensive hours: manual billing setup, chased payments, hand-built documentation for revenue recognition. Connecting those steps shortens collection cycles and makes revenue more predictable, and prompting the buyer to set up payment at the moment of acceptance is the detail most likely to move the number. Paired with the quoting work Commerce Hub has shipped recently, the direction is a real quote-to-cash story rather than a set of separate tools.

For more details: Connected CPQ, Billing, and Payments private beta.

Key Takeaways and Next Steps

The everyday CRM surface keeps getting faster: The index page right rail, the property context menu, and the rebuilt Add to Dashboard panel are all small fixes aimed at the places you click most. None of them is a headline on its own, but together they signal that HubSpot is paying attention to the minute-by-minute experience, not just the big features. The index page edit columns change alone will save your team a surprising number of small annoyances.

Customer Agent is becoming something you scope, not just switch on: Responding to forms and, soon, choosing which audiences get email responses are two halves of the same idea. The agent is moving from an all-or-nothing toggle to a tool you point at specific, named audiences. That is the right way to adopt it, both for cost and for customer experience, and it puts the value back on having clean lists and a frontline team that can tell you where automation actually helps.

One date to put on the calendar: The July 31 change to how recorded meetings get logged is the only item here with a deadline and a real chance of breaking something. If you rely on call-based workflows, properties, or reports for meetings recorded through Notetaker, Zoom, Meet, or Teams, audit that setup now while you have runway, not after the duplicate call records stop appearing.