HubSpot Updates: May 14, 2026
Four updates landed Tuesday, and two threads run through them. The first is post-sale and chat surfaces getting more attention, with two updates that touch how live chat and customer agent meet visitors. The second is the small, quiet kind of efficiency that does not get top billing but materially changes the day, with mobile list views finally mirroring what you have already configured on desktop and SurveyMonkey responses finally attributing to the right contact without a workaround.
If you watched the show today, you already heard the conversation around two of these. If you did not, watch the recap to hear our thoughts on these updates and more.
Platform Updates Detailed
Send SurveyMonkey Surveys With Automatic Contact Attribution
You can now embed SurveyMonkey surveys into HubSpot marketing emails and have responses automatically match to the right contact record. A custom variable on the survey URL identifies the contact, so you no longer need to ask respondents for their email address on every survey to attribute the response. This is live across all hubs and tiers.
Why it matters: The friction this removes is small per survey and large in aggregate. Asking a contact for their email address on a survey they were emailed is a strange experience for the recipient and a guaranteed source of bad data when typos or alternate email addresses get used. Closing the loop with a URL variable is the right approach, and the fact that it works across every hub and tier without a Survey-specific upcharge is worth flagging. For teams running ongoing CSAT, NPS, or product feedback programs through SurveyMonkey, this is an immediate cleanup.
For more details: SurveyMonkey surveys with automatic contact attribution live
Mobile List Views Now Mirror Desktop Table Views
Mobile list views in the HubSpot app now show the same properties you have configured in the corresponding desktop table view, up to 20 properties, starting from the left. The mobile experience previously showed a fixed set of properties with no way to customize them, which meant the columns you had carefully ordered on desktop did not carry over to your phone. This is live across all hubs and tiers, and works on iOS and Android with the latest version of the HubSpot mobile app.
Why it matters: This is the kind of small, overdue alignment that pays for itself every time someone opens the app in the field. The desktop table view is the surface where admins do their thinking about which properties matter for which list. Asking reps to mentally translate that work into a different set of columns on mobile was a tax on adoption. Reps who actually use the mobile app to check deal amounts, close dates, custom priority fields, or whatever they care about most can now do that without tapping into every record. It is an unflashy update with a real adoption lift for portals that rely on field activity.
For more details: Mobile list views mirror desktop table views live
Customer Agent Suggested Questions Update
Customer agent now shows suggested questions inside the chat widget itself, below the agent greeting, rather than as a hover state or page overlay before the chat is opened. The new placement appears when a visitor demonstrates clear intent to start a conversation, which makes the prompts feel more useful in context and the experience less cluttered on the page. This is in public beta and available across HubSpot Credits and the Professional and Enterprise tiers of Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM.
Why it matters: The pre-chat overlay was the kind of treatment that tried to do too much before the visitor had asked anything. Moving suggested questions inside the chat surface lines up with how people actually engage: they open the widget first, then look for a prompt that matches what they need. The bigger pattern worth watching is the steady accumulation of customer agent updates as HubSpot keeps tightening that surface. Customer portals are getting better, customer success rooms are real, and customer agent is getting more capable in the chat itself. The post-sale tooling is getting noticeably more attention.
For more details: Customer Agent suggested questions update public beta
Personalization Token Support in Rules-Based Chatflow Welcome Messages
You can now insert personalization tokens like first name, company name, or recent activity directly into the welcome message of a rules-based chatbot. When a visitor is recognized via tracking cookies, the token renders with their information; when they are not, configured default values keep the greeting natural. This is in private beta across all hubs and tiers.
Why it matters: Personalization tokens in the first message of a chat are a sharper tool than they look. Used on a logged-in customer portal or a customer success room, they feel like the company finally caught up with what it already knows. Used on a stranger's first visit to a marketing page, they cross into uncanny territory and undermine trust. The right deployment is post-sale or post-consent, on surfaces where the visitor expects to be recognized. This update arriving while customer portals and customer success rooms are getting better is not a coincidence: HubSpot is building the surfaces where personalized welcomes actually fit.
For more details: Personalization token support in rules-based chatflow welcome messages private beta
Key Takeaways and Next Steps
Post-sale tooling is getting real: Two of the four updates today, plus the broader arc of customer agent, customer portals, and customer success rooms across recent releases, point in the same direction. The post-sale experience inside HubSpot is moving from minimum viable to a surface HubSpot is actively investing in. If your portal has historically optimized everything around acquisition and treated the post-sale stack as an afterthought, the gap between what is possible and what you are using is widening.
Personalization belongs where consent has already happened: The chatflow welcome token update is powerful, but the question is not whether to use it. The question is where. Authenticated customer portals, customer success rooms, and post-form-fill chat interactions are the right places. Anonymous first-visit pages are not. Build the rules around recognition state, not around the technical capability.
Small alignments compound: Mobile list views matching desktop and SurveyMonkey responses attributing automatically are not headline updates, but they are the kind of fixes that quietly remove friction from daily work. Rep adoption of the mobile app and clean survey data are both downstream of choices like these. They are the updates that do not get the show segment but earn their place in the portal.