Great minds think alike

Problem There’s no easy way to view or share a complete overview of a Company or Deal in HubSpot—especially on mobile.   The desktop view shows rich information, but the mobile app only displays limited properties and has no true overview page. This is a major pain point when preparing for meetings on the go.   Use Case You’re in the lift before a meeting, checking a Deal or Company on your phone. You can’t see all the key info in one place, and there’s no way to export or share a clean summary.   Proposed Solution Add a “Download as PDF” option on Company and Deal pages that: Shows all key information in a single overview Matches the desktop view (not a reduced mobile view) Includes a timestamp Is easy to view, download, and share   Why This Matters? This would significantly improve mobile usability, meeting prep, and information sharing—one of the biggest gaps in the current mobile experience. ...read more

We really like using HubSpot's message templates, especially because of the feature that allows you to insert personalisation tokens, which are then automatically filled in the email.   Unfortunately, there is one essential feature that is available when saving Outlook templates but is still missing from HubSpot's message templates: it would be nice if you could store fixed recipient email addresses for specific message templates.   Specifically, from our point of view: we work with partners whose products we resell. When one of our customers orders a partner product, we have to send an email to our partner specifying which customer ordered which product with which key data. The partner requires us to always send this information to specific email addresses. And it would of course be easier for us if these email addresses were always stored with the message templates. ...read more

I’m submitting this as an accessibility issue, not a cosmetic preference. Recent UI changes in the internal agent web interface (Tickets / Help Desk / Conversations) introduced blue/teal text on a white background. This creates a health-related accessibility barrier, as it triggers migraines and significant eye strain and affects my ability to work safely for extended periods. Important context: System-level blue-light filters (e.g., Night Shift / Night Light) do not help and actually worsen eye strain by reducing clarity and increasing visual fatigue. The only effective solution for my light sensitivity and migraines is a true dark interface (black or near-black background with light text), which I use successfully across other tools. Text color itself is a major trigger — certain hues (including blue/teal on white) significantly increase eye strain. Mobile app dark mode is not a viable workaround due to high ticket volume and the need for full web-based workflows. Currently, the internal agent web UI does not offer: A dark mode or high-contrast theme User control over background color User control over text/letter color The ability to adjust contrast in a way that accommodates light sensitivity and migraine triggers This creates an accessibility barrier for agents with light sensitivity, migraines, and visual processing conditions. While contrast ratios may technically meet minimum guidelines, accessibility also includes user-adjustable presentation, especially when specific color combinations cause adverse physical effects. Request: Please add one or more of the following for the internal agent web interface (Tickets / Help Desk / Conversations): A true dark mode A high-contrast or low-glare theme User-controlled theming, including the ability to adjust: Background color Text/letter color Overall contrast Providing control over both background and text colors would allow agents with different accessibility needs to configure a workspace that does not cause physical harm or limit their ability to work. This would align HubSpot with modern accessibility practices and with other enterprise tools that support agents with light sensitivity and migraine-related accessibility needs. Thank you for considering this from an accessibility and health-impact perspective. ...read more

HubSpot recently released the ability to ASSOCIATE Leads and Custom Objects. I want to extend this functionality, so that we can CREATE Leads from Custom Object records.  I spoke with HubSpot Support about this, and the main obstacle is that the Lead must be associated with a Contact or Company, not just the custom object. My proposal for this is that the Create Lead form would include a required association to either a Contact or Company record. We see this object association option in other object creation forms.  ...read more

HubSpot should provide a way to customize category slugs so users have proper control over language switching. Alternatively, they should offer a mechanism—similar to language_variants('localized') for standard pages—that allows developers to retrieve localized category URLs for multilingual implementations. Because currently, implementing a language-switch to a KB is a hastle. ...read more

The playbook card features a recently used and frequently used recommendation but does not allow us to reorder the playbooks in the card. It would be preferably to be able to show the playbooks in a set order (such as alphabetical/numeric so that playbook "1. aaa"  through "10. zzz" appear in order, or even a custom order like we can when adding properties to a record card.   The recommendations for frequent and recently used are not particularly helpful, as different records are at different stages - what was recently uesd may not be needed again on a record. ...read more

HubSpot allows you to create custom properties to organize assets such as marketing emails, marketing events, and workflows. For example, here is a custom property that groups marketing events by the product that the event is about.   Marketing Events list with the custom Product multi-select property.   Unfortunately, these properties are not available to be used anywhere in HubSpot. They are only available on the page listing those records as an additional column and filter. Here are some places you might want to use these properites that you can't: Lead Score. You can't filter marketing events or marketing emails or workflow enrolments by a custom property. (e.g. score any email with interaction = high as 2 points and emails interaction = low as 1 point based on a custom interaction level property.) Workflows. You can't take workflow actions based on custom properties. (e.g. unenroll if enrolled in workflow with Type = followup based on a custom Type property.) Segments. You can't filter records in segments based on these properties. (e.g. Attended a Marketng Event for the "Facilities" product based on the custom Product property.) These properties are very interesting because they are visible and accessible to the user and are pitched as a great way to organize assets. Unfortunately, we can't access that organization anywhere except the asset's page, so it's usefulnessis severely limited. ...read more

Now that I am a Partner Admin to some of our clients, I realized that I am not able to do "high-risk" actions like CRM Manual Data Back Up and Knowledge Base Migration.  I checked with Support and these actions can be done only by a Super Admin.  I normally have to do this work for clients, now I have to request for a paid Super Admin seat to be able to do this. I believe the expectation is that a Super Admin is meant to action on more "high-risk" actions (like migrating the KB) since it's irreversible.   I think a good middle ground would be something like a Partner-requested, Admin-approved setup so there doesn't need to be a change or permissions. Tagging Product team cause I can see how this would make things a lot smoother. ...read more

This idea is primarily for developers, technical admins, and advanced HubSpot users who regularly work with the CRM APIs, custom code actions, integrations, or external systems. Problem: Today, the only way to see a property’s internal name is to click into each individual property. When you’re working with APIs or external tools, internal names are what actually matter — not labels. If you need to reference or validate many properties at once, this becomes extremely time-consuming and disruptive. You’re forced into a repetitive loop of opening properties one by one just to copy a single value. Proposed Improvement: Add Internal Name as an optional, visible column in the Properties table (similar to how names, groups, and access types are shown). Ideally, this column would also be searchable and sortable. Why This Matters: Dramatically improves developer and admin efficiency Reduces friction when building integrations, workflows, and custom code Makes property audits and troubleshooting far easier Aligns the UI with how properties are actually used in APIs and automation This small UI enhancement would save significant time for anyone working at scale with HubSpot data and would meaningfully improve the developer experience across the platform. ...read more