Great minds think alike

I noticed that the recent update changed the comment color to a pale yellow, which blends in too closely with the white background, making it difficult to read. I would appreciate the option to revert to a brighter color or to select a color that I prefer. ...read more

Currently when we add any existing properties as a dashboard quick filters, the only available operators are  "contains any of, Is Known, Is Unknown and Doesnt contain any of" Its missing "has ever been equal to, has ever contained" This is crucial to track historical data! ...read more

Description: Right now, conditional logic in Record Customization for property cards only allows a property card to be displayed if a property equals a specific value. This is helpful, but it limits flexibility in building more dynamic, context-aware record views. Use Case: For example, I want to show Card A if a dropdown property equals “Active.” But I also want to show Card B if that same property is either blank (unknown) or set to something else (e.g., “Inactive,” “Archived,” etc.). Currently, there’s no way to set conditions for “not equal to” or “is unknown”, which would let us build cleaner and more user-specific record views. Request: Please add support for additional conditional logic in property card display rules, such as: • “Is not equal to” • “Is unknown” • “Contains” or multi-option matching This would be a huge improvement for customizing internal CRM experiences based on record status, lifecycle stage, or any property used for internal segmentation or process control. Thanks! ...read more

It would greatly improve our WhatsApp integration if HubSpot could automatically capture any user-initiated WhatsApp message—whether from the embedded chat widget or direct WhatsApp app—and: Auto-upsert contacts by phone number when a new user messages for the first time. Log inbound messages on the contact’s timeline and surface them in the Conversations inbox without manual copy-paste. Trigger workflows (opt-in, welcome series, unsubscribe handling, qualification flows, etc.) based on the inbound message or detected keywords. Allow chatflows to ask for custom fields (name, email, phone) directly in-chat, mapping replies back to HubSpot contact properties as part of the chatflow builder (no external middleware required). Use Case: We’ve connected our WhatsApp Business number and can send approved HSM templates outbound via workflows, but we cannot yet: Automatically create a new contact when an unrecognized number messages us. Sync their replies into HubSpot without manual record edits. Drive post-reply logic in chatflows based on those messages or property updates. Adding first-class support for inbound message capture, contact upsert, and chatflow-driven data collection would close the loop on the entire WhatsApp customer journey, reduce manual work, and let us build fully conversational lead-capture forms inside WhatsApp. Benefit to HubSpot Community: Many customers use WhatsApp as a primary support and sales channel. Native inbound sync and chatflow data collection would: Eliminate middleware complexity. Surface customer conversations in HubSpot automatically. Unlock powerful workflow triggers on live inbound messages. Reduce friction when building multi-step conversational forms. Please let me know if there’s any additional context I can share—and thanks for considering this enhancement! ...read more

  I manages three distinct brands within a single HubSpot portal: Data Axle USA, Salesgenie, and Exact Data. We regularly create and manage round-robin and team meeting links for different campaigns across these brands. However, the current Meeting Scheduler has a few limitations that are creating confusion and slowing down our workflow. Please Watch Video for Details    👤Who this is for: Teams managing multiple brands under a single HubSpot portal Users handling high volumes of meeting links (e.g., for sales or marketing campaigns) Admins and team leads who need to delegate, duplicate, or maintain brand-specific meetings What problems we’re facing (and what it needs to solve): 1. Meeting Link URL Changes Based on Personal Domain Settings Problem: When a user changes their meeting domain in personal calendar settings, it affects the base URL of all meeting links they’ve created even existing ones. Example: A Salesgenie link originally shows: https://hub.salesgenie.com/meetings/salesgenie Later, if the user switches their domain to hub.exactdata.com, the same link changes to: https://hub.exactdata.com/meetings/salesgenie Why it’s a problem: This breaks brand consistency and causes confusion, especially when links are shared externally. What we need: Meeting links should retain the domain they were created with, no matter what domain the user switches to later. 2. No Bulk Add Option for Round-Robin Meetings Problem: We must manually select each team member one by one to add them to a round-robin link, which is very time-consuming. What we need: Ability to select multiple users at once Or simply add an entire HubSpot team 3. No Option to Clone Meeting Links Problem: We often need similar meeting links with slight variations. Right now, we have to recreate them from scratch. What we need: A "Clone" or "Duplicate" option for meeting links to quickly replicate and edit them as needed. 4. Filters and Views Don’t Persist Problem: When filtering meeting links by brand or type (like round-robin), the filters reset when we click into a link and return to the list. What we need: HubSpot should remember the last-used filters and view settings, so we don’t have to reapply them every time. I hope Hubspot Product team takes this seriously and works on it it will solve a big problem. Thanks Akash Kodale ...read more

Being able to surface data from one object on another object without the use of workflows has been a huge improvement.    However, now that the data can be visualized on the second object, our users often times need to be able to update it while on that object without leaving the object's workscreen.    For example, we are syncing some key Company properties to the Lead Object so that data about the company stays evergreen but our sales teams can see that data in the leads tool while working their leads. It would be great if, as they engage with the lead, they had an easy way to update these values without having to leave the sales workspace. Currently it leads to some confusion when a property can not be edited due to it being a sync property - and even having a prompt that opens the appropriate Company property or something that tells them that the field needs to be updated on the Company object would be very useful in making sure data gets updated.    Ideally we'd be able to set sync rules the same way we do with other tools (such as data sync for integrations) but even just allowing for data to be updated in either object would help immensly!  ...read more

When knowledge base articles are created, we have a process for others to check those articles for accuracy. Once they are edited, there is only a filter on the backend that shows us who last updated the article but does not account for the original author. We need a way to be able to see the original author not just who last updated the article. ...read more

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

When creating a note and adding photos, can you add a feature so you can select multiple images at one time? It's extremely inefficient to have to select each image one at a time.  ...read more