What This Update Actually Is
HubSpot shipped two distinct improvements in this update. They're related, but worth separating so you know exactly what changed.
First, @mention notifications now link directly to the specific CRM record where the mention occurred. Before this fix, HubSpot would sometimes route you to an associated record instead. If someone mentioned you in a note on a Deal, you might land on the Contact. That's gone.
Second, notification support has expanded to nine additional CRM object types: Appointments, Carts, Contracts, Courses, Listings, Marketing Events, Orders, Services, and Subscriptions. These objects now support three notification types:
- @mention notifications when someone tags you in an activity on that record
- Follow notifications when activity happens on a record you're watching
- Assigned notifications when a record of that type gets assigned to you
Both improvements are enabled by default for everyone across all hubs and tiers. This is a private beta rolling out in late July 2026, per the official HubSpot product update.
Why HubSpot Shipped This
Here's the external problem: notification routing in HubSpot was inconsistent. The system didn't always respect the object type where the mention happened. It would sometimes follow an association and land you on a related record instead.
The internal frustration is real. Humans in busy portals rely on notifications to jump in fast. When you click a mention and land on the wrong record, you lose the thread. You start hunting. You click back, you search, you waste thirty seconds minimum. Multiply that across a team of ten over a week and you've burned real time.
The expanded object support addresses a different gap. As HubSpot has grown its CRM to include commerce-related objects like Orders, Carts, and Subscriptions, those records were silent. No one got notified when activity happened there. That's a problem for any team using HubSpot to manage post-sale workflows.
How to Use It Step by Step
The routing fix requires no setup. It works automatically once your portal is included in the rollout. Here's what to expect and what to review:
- Wait for the rollout. HubSpot is targeting late July 2026. If your portal is in the private beta, the change will apply automatically.
- Test the fix. Go to any CRM record, add a note, and @mention a colleague. Ask them to click the notification. Confirm they land on the correct record, not an associated one.
- Review your notification settings. Go to your profile icon, then Notifications. You'll see the expanded object types listed. Because these are enabled by default, every human on your team may start receiving more notifications than before.
- Audit per object type. If your team doesn't actively work Orders or Appointments in HubSpot, turn off those notification types to prevent noise. Do this per user, not just at the admin level.
- Check existing notification rules. If someone had previously turned off @mention notifications for a specific object type, they won't receive mentions on that object. Remind your team to confirm their preferences still match their intent.
- Communicate the change to your team. The volume of notifications going up is the most likely friction point. A quick Slack message or team email sets expectations before inboxes start filling up.
What It Touches in Your HubSpot Strategy
This update looks small. It isn't. Notification reliability is the connective tissue of any collaborative CRM workflow. When it works, humans move fast. When it doesn't, they stop trusting the tool and find workarounds.
Here's where the ripple effect lands in your portal:
- Sales workflows: Deal notes and task mentions now route correctly. Reps don't lose context mid-conversation.
- Service workflows: Ticket mentions route to the right ticket. Support teams can respond faster without hunting for the thread.
- Commerce and post-sale: Orders, Subscriptions, and Contracts now surface activity to assigned humans. This is critical for renewal workflows and order fulfillment coordination.
- Automation handoffs: If your workflows assign records to humans, those humans now get notified on object types that were previously silent. This closes a gap in automated handoff sequences.
- Notification settings governance: Admins now have a reason to audit and document notification preferences across the team. What's on by default may not match what each role actually needs.
Key Takeaway
The expanded object support matters most for teams using HubSpot Commerce Hub features. If you're managing Orders, Subscriptions, or Contracts in HubSpot, your team was previously flying blind on activity notifications. That changes now.
This update pairs naturally with HubSpot's broader push to make CRM notifications more useful. If you haven't already, check out what shipped for improved CRM notifications in email, which adds full context and reply-to-mention support directly in your inbox. Together, these two updates make the notification layer of HubSpot significantly more reliable.
Key Takeaway
If your team uses @mentions as a handoff signal inside deals or tickets, this fix directly reduces the time it takes to act on those handoffs. Fewer wrong-record landings means fewer follow-up messages asking 'where exactly did you mean?'
On the automation side, this update also connects to how records get created and assigned mid-workflow. If you're building sequences that create new CRM records and assign them in the same flow, the assigned notification improvement now means the right human gets pinged immediately. See how that fits with using records created in a workflow later in the same workflow for a stronger end-to-end automation pattern.
Who Should Care Most
This update is relevant to anyone using HubSpot collaboratively. But some roles and company profiles will feel the impact more than others.
- Sales reps and managers who use @mentions to flag deals for review or escalation. The routing fix is an immediate quality-of-life improvement.
- Service and support teams who rely on ticket mentions to coordinate internally. Correct routing means faster response times.
- RevOps and portal admins who need to audit notification preferences across the team now that defaults have expanded. This is a prompt to do that work.
- Companies using HubSpot Commerce Hub. If you're managing Orders, Subscriptions, Contracts, or Appointments in HubSpot, your team just gained notification coverage they didn't have before.
- Onboarding and implementation teams. Any portal going live now should include a notification preferences review in the onboarding checklist, especially given the expanded defaults.
George's Take
I've audited a lot of portals where teams had quietly stopped trusting their HubSpot notifications. They'd click a mention, land somewhere unexpected, and eventually just... stop clicking. They'd go find the record manually. Or worse, they'd ask a colleague to resend the link. That friction compounds. Fixing the routing on @mentions isn't a flashy feature, but it's the kind of repair that rebuilds trust in the tool over time. The expanded object support is the bigger strategic move though. Humans who manage post-sale workflows in HubSpot have been missing a notification layer that Sales and Service teams take for granted. Now everyone's on the same footing.
“Fixing notification routing isn't glamorous. But it's the kind of thing that quietly rebuilds a team's trust in their CRM. When the tool works the way you expect, you use it more. And when you use it more, the data gets better. Everything downstream improves.”
If this update surfaces gaps in how your team is using HubSpot notifications, or if your portal has grown to include Commerce Hub objects without a clear ownership and notification strategy, that's exactly the kind of thing we help with at Sidekick Strategies. Book a strategy call and let's look at your portal together. We'll find the friction points and build a plan to fix them.
Frequently Asked Questions
What did HubSpot change about @mention notifications?
HubSpot fixed @mention notification routing so that clicking a notification takes you directly to the exact CRM record where the mention happened. Previously, the system sometimes redirected you to an associated record instead, causing confusion and extra clicks. This fix applies across all CRM object types and is enabled by default for all hubs and tiers.
Which new CRM object types now support HubSpot notifications?
HubSpot has added notification support to nine additional CRM object types: Appointments, Carts, Contracts, Courses, Listings, Marketing Events, Orders, Services, and Subscriptions. These objects now support @mention, follow, and assigned notifications. All three notification types are enabled by default, so users should review their notification preferences after the rollout.
Will this update increase the number of notifications my team receives?
Yes, likely. Because notification support has expanded to nine new CRM object types and is enabled by default, everyone in your account may start receiving more notifications. If your team doesn't actively work with objects like Orders or Appointments in HubSpot, you can turn off those notification types in your personal notification settings.
Do I need to do anything to activate the improved @mention routing?
No action is required to get the routing fix. It applies automatically once your portal is included in the rollout, which HubSpot is targeting for late July 2026. You should, however, review your notification settings after the rollout to manage the expanded defaults for the new object types.
Who gets access to the improved HubSpot @mention notifications?
All HubSpot users across every hub and tier get this update. There's no tier restriction. HubSpot is rolling it out as a private beta starting late July 2026, and all accounts are included. No manual opt-in is required beyond waiting for the rollout to reach your portal.
How does this notification fix affect HubSpot Commerce Hub workflows?
It's a significant improvement for Commerce Hub users. Objects like Orders, Subscriptions, and Contracts previously had no notification support. Teams managing post-sale workflows in HubSpot were not getting notified when activity happened on those records. With this update, assigned and @mention notifications now work on those objects, closing a real gap in post-sale coordination.
