Great minds think alike

Description: Currently, HubSpot’s dropdown fields only support a flat structure, which makes it challenging to organize and select options that naturally belong in a hierarchy (e.g., Category > Subcategory > Detail).  I’d like to suggest that HubSpot introduce tiered or hierarchical dropdown menus. For example: Selecting “A” could reveal sub-options like “AA,” which in turn could reveal further sub-options like “AAA.” This structure would make it easier for users to navigate complex option sets without cluttering the dropdown with too many items at the same level. A Level 1 └── AA Level 2 └── AAA Level 3   Use Cases: Classifying companies or deals with multi-level categories. Organizing product or service options by main category and subcategory. Streamlining forms and reducing user error by showing only relevant sub-options based on previous selections. Benefits: Enhanced user experience, especially for large datasets. Improved data quality through more intuitive field structures. More flexible customization for businesses with complex workflows. Possible Implementation Ideas: Allow admins to define parent-child relationships between dropdown options. Let users expand/collapse dropdowns to navigate tiers. Offer conditional dropdown logic within a single dropdown property, rather than relying on separate fields and conditional visibility. Thanks for considering this enhancement — it would be a game-changer for us and most likely other companies that rely on structured data collection in HubSpot! 🚀 ...read more

In short: Add the ability to view and reply to chats in Slack with the Helpdesk Slack integration, to mirror how it used to be with the legacy inbox Slack integration. Maybe this could be a toggle between posting comments or chat replies to Slack.   The legacy integration between Hubspot and Slack for inboxes allowed you to handle incoming visitor chats right in Slack - this meant seeing and responding to chats right in the Slack thread created by Hubspot for a specific chat. Helpdesk, while it also has a Slack integration, only allows internal comments to be communicated back and forth between Slack and Hubspot. If you keep the legacy inbox system and opt not to use Helpdesk, you miss out on key features. This could be a toggle when a user is configuring their Slack integration - perhaps they can toggle whether or not they want comments or chat replies to post to Slack. My screenshot below confirms this - look at the description below Bring conversations to Slack and Sync Help Desk tickets to Slack - they are different.   ...read more

In the future, it would be incredibly helpful if HubSpot forms could allow users to create multiple contacts from a single form submission. Use Case Example: Imagine a scenario where a customer is filling out a form on behalf of someone else, or needs to provide information for multiple stakeholders, such as their manager, billing contact, company owner, or other relevant parties. Proposed Solution: Add a “+” or “Add Contact” button to the form, allowing users to dynamically add more contact fields as needed. When clicked, a pop-up or conditional section appears where the user can enter the details for the additional contact (name, email, role, etc.). All submitted contact details are processed and create separate contact records in HubSpot, linked to the original submission. Benefits: Streamlines data collection for group registrations, event sign-ups, or any scenario involving multiple stakeholders. Reduces friction for customers who need to provide information for more than one person. Improves data accuracy by capturing all necessary details in one go. Example Workflow: User fills in their own details. Clicks “Add Contact” to include their manager’s information. Optionally adds more contacts (billing, owner, etc.) as needed. Form submission creates all relevant contact records in HubSpot. ...read more

Currently, HubSpot limits historical visibility on custom behavioral event data to 5 years. This restricts long-term trend analysis, customer lifecycle tracking, and strategic forecasting — especially for B2B companies with long sales cycles or multi-year journeys. Suggested Solution: 1. Introduce tiers and allow accounts to select from retention tiers, such as: 5 years (default), 7 years, 10+ years. (This can be paid for 10+ years or may be an enterprise feature.) 2. Implement an "Archive Access Mode" where data older than 5 years is not stored in active memory but is: Available on-demand and can be queried in a separate UI 3. Offer a native connector to sync all behavioral event data to external storage with an easy export and visualization toolkit. ...read more

As the title says "Access management per user/team on snippet folders" would be very handy. Currently this is not possible as i understand from the Hubspot knowledgebase: https://knowledge.hubspot.com/conversations/use-snippets. Please make this possible as this will provide more flexibility in managing a large set of snippets to a specific group of users. ...read more

Per this thread, I am requesting that you provide us a setting to turn off this feature. It would be ideal if we could turn this off at either at the individual user level or at the admin level. This autosave feature is extremely disruptive to our workflow. ...read more

It would be useful to be able to query a collection of lead records using GraphQL and/or query a collection of lead records that are associated to a Company/Deal record.   Currently the only way to do this is through the CRM Leads API. This would be useful when building out webpages with dashboards displaying lists of leads. ...read more

It would be very useful if HubSpot forms allowed the creation of questions that are not tied to CRM properties. These types of fields could serve internal purposes—such as driving conditional logic or collecting temporary input—without being saved to a contact or company record. For example, we might want to ask the user if their inquiry is urgent, or whether they’d like to skip a step in a guided experience. These responses could help determine which automated path the user takes, but they don’t need to be stored in the CRM long-term. This functionality would also be valuable for campaign-specific logic. Sometimes we need to collect information only relevant to a single campaign, and creating a new contact property just for that adds unnecessary clutter. Ideally, these “logic-only” or “non-binding” fields would still be usable within workflows and reporting—so we can trigger automated actions or analyze submission behavior—but without requiring permanent storage in the object model. Adding this flexibility would allow users to design cleaner, smarter forms that meet both operational and user experience goals, without overloading the property manager with transient fields. Thanks for considering this improvement. ...read more

Currently, HubSpot only lets users define a user’s general working hours in 30-minute increments. There’s no option to set start and end times (or break times) in 15-minute increments. This forces teams to either block off larger-than-necessary chunks of availability, reducing true capacity, or risk scheduling users back-to-back with zero transition time, leading to stress, late starts, and lower service quality. ...read more